Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Failed to initialize connector [Connector[HTTP/1.1-80]] : after migrated jira jira is not starting

venugopal123
venugopal123 September 28, 2017

Hi ,

I migrated the jira in Linux . When am trying to open the jira ..its not starting . Please find the below logs.please try to resolve this

 

Logs:

28-Sep-2017 17:05:04.334 SEVERE [main] org.apache.catalina.core.StandardService.initInternal Failed to initialize connector [Connector[HTTP/1.1-80]]
org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-80]]
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
at org.apache.catalina.core.StandardService.initInternal(StandardService.java:568)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:869)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.startup.Catalina.load(Catalina.java:580)
at org.apache.catalina.startup.Catalina.load(Catalina.java:603)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:310)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:484)
Caused by: org.apache.catalina.LifecycleException: Protocol handler initialization failed
at org.apache.catalina.connector.Connector.initInternal(Connector.java:962)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
... 12 more

 

 

 

28-Sep-2017 17:05:04.334 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 563 ms
28-Sep-2017 17:05:04.344 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Catalina
28-Sep-2017 17:05:04.344 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.33
28-Sep-2017 17:05:12.475 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 8141 ms
28-Sep-2017 17:18:38.067 INFO [Thread-3] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-80"]
28-Sep-2017 17:18:38.067 INFO [Thread-3] org.apache.catalina.core.StandardService.stopInternal Stopping service Catalina
28-Sep-2017 17:19:05.187 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [JonasBatch] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:502)
org.objectweb.jonas_timer.TimerManager.batch(TimerManager.java:193)
org.objectweb.jonas_timer.Batch.run(TimerManager.java:65)
28-Sep-2017 17:19:05.188 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [JonasClock] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.lang.Thread.sleep(Native Method)
org.objectweb.jonas_timer.TimerManager.clock(TimerManager.java:142)
org.objectweb.jonas_timer.Clock.run(TimerManager.java:46)
28-Sep-2017 17:19:05.197 INFO [Thread-3] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-80"]
28-Sep-2017 17:19:05.198 INFO [Thread-3] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-80"]
28-Sep-2017 17:21:17.474 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.0.33
28-Sep-2017 17:21:17.475 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Mar 18 2016 20:31:49 UTC
28-Sep-2017 17:21:17.475 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.0.33.0
28-Sep-2017 17:21:17.475 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Linux
28-Sep-2017 17:21:17.475 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 2.6.32-696.10.2.el6.x86_64
28-Sep-2017 17:21:17.475 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64
28-Sep-2017 17:21:17.476 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: /data/apps/jira7.2.1/jre
28-Sep-2017 17:21:17.476 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_102-b14
28-Sep-2017 17:21:17.476 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation
28-Sep-2017 17:21:17.476 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: /data/apps/jira7.2.1
28-Sep-2017 17:21:17.476 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: /data/apps/jira7.2.1
28-Sep-2017 17:21:17.476 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/data/apps/jira7.2.1/conf/logging.properties
28-Sep-2017 17:21:17.476 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
28-Sep-2017 17:21:17.477 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms1024m
28-Sep-2017 17:21:17.477 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx4096m
28-Sep-2017 17:21:17.477 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
28-Sep-2017 17:21:17.477 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Datlassian.standalone=JIRA
28-Sep-2017 17:21:17.477 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
28-Sep-2017 17:21:17.483 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dmail.mime.decodeparameters=true
28-Sep-2017 17:21:17.483 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory
28-Sep-2017 17:21:17.483 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+PrintGCDateStamps
28-Sep-2017 17:21:17.483 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:-OmitStackTraceInFastThrow
28-Sep-2017 17:21:17.483 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.endorsed.dirs=/data/apps/jira7.2.1/endorsed
28-Sep-2017 17:21:17.483 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=/data/apps/jira7.2.1
28-Sep-2017 17:21:17.483 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=/data/apps/jira7.2.1
28-Sep-2017 17:21:17.483 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=/data/apps/jira7.2.1/temp
28-Sep-2017 17:21:17.484 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
28-Sep-2017 17:21:17.644 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"]
28-Sep-2017 17:21:17.658 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
28-Sep-2017 17:21:17.660 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 570 ms
28-Sep-2017 17:21:17.670 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Catalina
28-Sep-2017 17:21:17.670 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat

Answer
Watch
Like Be the first to like this
32509 views

2 answers

1 vote
somethingblue
somethingblue
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 28, 2017

Hi Venu,

  • Are you starting JIRA as root?

Linux restricts the first 1024 ports to the root user only. If JIRA is running on port below 1024 as a non-root user, then you will get the above error.  For more information on this Linux restriction, please have a look at First 1024 ports restricted to root user in Linux.

There are several options to handle this:

  1. Run JIRA on port a port greater than 1024, but through a reverse proxy so that JIRA can be accessed on 80. Further information can be found in the following documentation:

  2. Using Linux, you can reroute port 80 to redirect to other ports. For example this will cause port 80 to route to port 8080 and means you can run Tomcat on 8080 and users can connect to it from port 80:

    iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080

I have also seen issues when JIRA did not have enough memory.  I would perform a search in the logs for OutofMemory.  If you do find OOM errors, increase the heap memory and restart JIRA.

At this point confirm what user is starting JIRA and that you do indeed have enough heap memory.  If all that checks out and none of the above helps let me know and we'll go from there.

Cheers,

Branden

View More Comments
venugopal123
venugopal123 October 2, 2017

Hi @Brant Schroeder,

Thank you very much.That health plugin issue was resolved .Even it is resolved Jira is not launching(opening at all) on the browser. It seems no error in the log files . Iam not getting what is going wrong with this . Even i tried a fresh installation not migration and also i checked but ntg is coming in the browser

 

Catalina.out:

 

___ Starting the JIRA Plugin System _________________

2017-10-03 11:58:29,552 JIRA-Bootstrap INFO [c.a.plugin.manager.DefaultPluginManager] Plugin system earlyStartup begun
2017-10-03 11:58:32,835 JIRA-Bootstrap INFO [c.a.plugin.loaders.ScanningPluginLoader] No plugins found to be deployed
2017-10-03 11:58:33,319 JIRA-Bootstrap INFO [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (16): [com.atlassian.plugins.less-transformer-plugin, com.atlassian.soy.soy-template-plugin, tac.jira core.languages.ja_JP, tac.jira core.languages.ru_RU, com.atlassian.auiplugin, com.atlassian.plugins.issue-status-plugin, tac.jira core.languages.de_DE, com.atlassian.jira.jira-languages.en_US, tac.jira core.languages.ko_KR, com.atlassian.jira.jira-languages.en_UK, tac.jira core.languages.es_ES, tac.jira core.languages.fr_FR, tac.jira core.languages.pt_BR, com.atlassian.plugin.jslibs, com.atlassian.plugins.jquery, com.atlassian.jira.jira-less-integration], 60 seconds remaining
2017-10-03 11:58:33,321 ThreadPoolAsyncTaskExecutor::Thread 5 WARN [c.a.p.s.scanner.util.ProductFilterUtil] Couldn't detect product, will use ProductFilter.ALL
2017-10-03 11:58:34,601 JIRA-Bootstrap INFO [c.a.plugin.manager.DefaultPluginManager] Plugin system earlyStartup ended
2017-10-03 11:58:34,736 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /data/apps/jirahome/dbconfig.xml
2017-10-03 11:58:34,747 JIRA-Bootstrap INFO [c.a.j.instrumentation.external.DatabaseExternalGauges] Installing DBCP monitoring instruments: DatabaseExternalGauges.JiraDbcpInstruments[instruments=[DBCP_MAX, DBCP_ACTIVE, DBCP_IDLE],objectName=com.atlassian.jira:name=BasicDataSource]
2017-10-03 11:58:34,778 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks.
2017-10-03 11:58:34,781 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] JIRA pre-database startup checks completed successfully.
2017-10-03 11:58:34,814 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Database Checklist Launcher on post-database-configured-but-pre-database-activated queue
2017-10-03 11:58:34,815 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Post database-configuration launchers on post-database-activated queue
2017-10-03 11:58:34,842 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 147 MiB. Committed: 482 MiB. Max: 740 MiB
Non-heap memory : Used: 64 MiB. Committed: 67 MiB. Max: 1264 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 212 MiB. Committed: 549 MiB. Max: 2004 MiB
---------------------------------------------------------------------------------

Like
somethingblue
somethingblue
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 3, 2017

Hi Venu,

It seems that JIRA is trying to read the dbconfig.xml from E:\Jira_Home and may not be able to.  One reason could be that the user running JIRA doesn't have permission to read the file.  This does tend to be more common when JIRA is configured to run as a Windows service.  Please  check that the user that JIRA is running as has full read/write permissions to JIRA_HOME and its subdirectories. If JIRA has been previously run as a different user, these files may not be accessible. 

One other thing could be that the dbconfig.xml file is corrupted somehow, in this case you may delete it and recreate it using JIRA Configuration Tool.

Once you verify the permissions, you'll want to try the following:

  • Backup your JIRA HOME DIrectory
  • Stop JIRA
  • Delete the following folders:
    • <jira-home>/bundled-plugins
    • <jira-home>/caches
  • Start JIRA

Let me know if that helps.

Cheers,

Branden

Like
Reply
0 votes
Kundan Singh
Kundan Singh August 9, 2019

Run the following command and you will able to login:

 

In the place of port 80, use your tomcat port.

 

#sudo touch /etc/authbind/byport/80

#sudo chmod 500 /etc/authbind/byport/80

In below command tomcat8 is a userand you have to enter your user name:

#sudo chown tomcat8 /etc/authbind/byport/80

Reply

Suggest an answer

Log in or Sign up to answer
Jira
Jira Software
TAGS
AUG Leaders

Atlassian Community Events

    See all events