Jira won't start after virtual server migration

[Maggie]

I have server-side instances of Jira, Bitbucket, & Crowd set up on the same virtual server.

Components:

• Windows Server 2019, x64
• SSMS 18
• Java JDK/JRE 8

The virtual server was moved to another VM a few days ago. IP changed, but no change in server name. Crowd & Bitbucket had no issues restarting, but Jira will not restart. All three programs were due to be updated anyway. So I backed up the data, & tried updating based on suggestions from some Atlassian Community articles. Crowd has updated without any issues, I haven't tried Bitbucket yet.

Jira will NOT load. I have checked the following:

• Java installation & version
• Environment variables (JAVA_HOME, JRE_HOME, CATALINA_HOME, JIRA_HOME)
• Directory permissions 
• jira-application.properties file (copied from previous install)
• seraph-config.xml file (copied from previous install)
• web.xml file (copied from previous install)
• setenv.bat file (copied from previous install)
• tomcat & tcnative-1 executables (switched on 64-bit, turned off 32-bit)

I went into Crowd & updated the IP addresses for all 3 programs, but I cannot find any configuration or properties file in JIRA's files that explicitly references the IP address.

I'm out of ideas. The command prompt window that appears when I run start-jira.bat seems to contain a lot less errors since I've run through all of the above checks, but after running the batch files remains open, & Jira won't load in my browser. There are no "ERROR" or "SEVERE" events reported.

Also, the Logs folder is completely empty. (I think this has been the case since reinstalling.)

A sample of the start-jira.bat batch file window results are included below.

Any help would be most appreciated!

27-May-2020 19:51:11.011 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR based Apache Tomcat Native library [1.2.23] using APR version [1.7.0].
27-May-2020 19:51:11.026 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
27-May-2020 19:51:11.026 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true]
27-May-2020 19:51:11.026 INFO [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized [OpenSSL 1.1.1c 28 May 2019]
27-May-2020 19:51:11.276 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8095"]
27-May-2020 19:51:11.370 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
27-May-2020 19:51:11.386 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 720 ms
27-May-2020 19:51:11.401 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
27-May-2020 19:51:11.401 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.42
27-May-2020 19:51:11.417 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deploying configuration descriptor [C:\Program Files\Atlassian\Crowd\atlassian-crowd-4.0.0\apache-tomcat\conf\Catalina\localhost\crowd.xml]
2020-05-27 19:51:22,885 localhost-startStop-1 INFO [ContainerBase.[Catalina].[localhost].[/crowd]] No Spring WebApplicationInitializer types detected on classpath
2020-05-27 19:51:22,885 localhost-startStop-1 INFO [ContainerBase.[Catalina].[localhost].[/crowd]] No Spring WebApplicationInitializer types detected on classpath
2020-05-27 19:51:23,167 localhost-startStop-1 INFO [apache.jasper.servlet.TldScanner] At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
2020-05-27 19:51:23,167 localhost-startStop-1 INFO [apache.jasper.servlet.TldScanner] At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.

2020-05-27 19:51:26,714 localhost-startStop-1 INFO [ContainerBase.[Catalina].[localhost].[/crowd]] Initializing Spring root WebApplicationContext
2020-05-27 19:51:31,667 localhost-startStop-1 INFO [persistence.hibernate.connection.DelegatingConnectionProvider] Configuring delegated connection provider: org.hibernate.c3p0.internal.C3P0ConnectionProvider@11120510
2020-05-27 19:51:31,713 MLog-Init-Reporter INFO [mchange.v2.log.MLog] MLog clients using slf4j logging.
2020-05-27 19:51:31,885 localhost-startStop-1 INFO [mchange.v2.c3p0.C3P0Registry] Initializing c3p0-0.9.5.4 [built 23-March-2019 23:00:48 -0700; debug? true; trace: 10]
2020-05-27 19:51:32,010 localhost-startStop-1 INFO [v2.c3p0.impl.AbstractPoolBackedDataSource] Initializing c3p0 pool... com.mchange.v2.c3p0.PoolBackedDataSource@d829e5e4 [ connectionPoolDataSource -> com.mchange.v2.c3p0.WrapperConnectionPoolDataSource@f9ce0543 [ acquireIncrement -> 1, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 0, connectionCustomizerClassName -> null, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, contextClassLoaderSource -> caller, debugUnreturnedConnectionStackTraces -> false, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, forceSynchronousCheckins -> false, identityToken -> 2rwch8aaommk4vnowywl|1002c6ec, idleConnectionTestPeriod -> 100, initialPoolSize -> 0, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 30, maxIdleTimeExcessConnections -> 0, maxPoolSize -> 30, maxStatements -> 0, maxStatementsPerConnection -> 0, minPoolSize -> 0, nestedDataSource -> com.mchange.v2.c3p0.DriverManagerDataSource@fd1f3856 [ description -> null, driverClass -> null, factoryClassLocation -> null, forceUseNamedDriverClass -> false, identityToken -> 2rwch8aaommk4vnowywl|42da89ad, jdbcUrl -> jdbc:jtds:sqlserver://fsstllabvm2:1433/Crowd, properties -> {handling_mode=DELAYED_ACQUISITION_AND_RELEASE_AFTER_TRANSACTION, user=******, password=******} ], preferredTestQuery -> null, privilegeSpawnedThreads -> false, propertyCycle -> 0, statementCacheNumDeferredCloseThreads -> 0, testConnectionOnCheckin -> false, testConnectionOnCheckout -> false, unreturnedConnectionTimeout -> 0, usesTraditionalReflectiveProxies -> false; userOverrides: {} ], dataSourceName -> null, extensions -> {}, factoryClassLocation -> null, identityToken -> 2rwch8aaommk4vnowywl|1a1178bb, numHelperThreads -> 3 ]
2020-05-27 19:51:40,417 localhost-startStop-1 INFO [opensaml.core.config.InitializationService] Initializing OpenSAML using the Java Services API
2020-05-27 19:51:42,042 localhost-startStop-1 INFO [opensaml.xmlsec.algorithm.AlgorithmRegistry] Algorithm failed runtime support check, will not be usable: http://www.w3.org/2001/04/xmlenc#ripemd160
2020-05-27 19:51:42,054 localhost-startStop-1 INFO [opensaml.xmlsec.algorithm.AlgorithmRegistry] Algorithm failed runtime support check, will not be usable: http://www.w3.org/2001/04/xmldsig-more#hmac-ripemd160

22020-05-27 19:51:48,669 localhost-startStop-1 INFO [plugin.osgi.factory.UnrecognisedModuleDescriptorFallbackFactory] Unknown module descriptor of type rest registered as an unrecognised descriptor.
2020-05-27 19:51:48,700 localhost-startStop-1 INFO [plugin.osgi.factory.UnrecognisedModuleDescriptorFallbackFactory] Unknown module descriptor of type analytics-whitelist registered as an unrecognised descriptor.
2020-05-27 19:51:48,731 localhost-startStop-1 INFO [plugin.osgi.factory.UnrecognisedModuleDescriptorFallbackFactory] Unknown module descriptor of type supported-inbound-authentication registered as an unrecognised descriptor.

2020-05-27 19:51:52,388 ThreadPoolAsyncTaskExecutor::Thread 6 INFO [plugin.osgi.factory.UnrecognizedModuleDescriptorServiceTrackerCustomizer] Turned unrecognized plugin module com.atlassian.upm.atlassian-universal-plugin-manager-plugin:applicationPropertiesContextItem into module com.atlassian.upm.atlassian-universal-plugin-manager-plugin:applicationPropertiesContextItem (null)
2020-05-27 19:51:52,419 ThreadPoolAsyncTaskExecutor::Thread 6 INFO [plugin.osgi.factory.UnrecognizedModuleDescriptorServiceTrackerCustomizer] Turned unrecognized plugin module com.atlassian.upm.atlassian-universal-plugin-manager-plugin:linkBuilderContextItem into module com.atlassian.upm.atlassian-universal-plugin-manager-plugin:linkBuilderContextItem (null)

2020-05-27 19:51:52,419 ThreadPoolAsyncTaskExecutor::Thread 1 INFO [plugin.osgi.factory.OsgiPlugin] Plugin 'com.atlassian.cluster.monitoring.cluster-monitoring-plugin' found service '&soyTemplateRenderer' with filter '(objectClass=com.atlassian.soy.renderer.SoyTemplateRenderer)'

2020-05-27 19:52:08,684 localhost-startStop-1 INFO [server.manager.site.ApprovalWhitelist] Using file as a site approval whitelist: C:\Program Files\Atlassian\Crowd\atlassian-crowd-4.0.0\crowd-openidserver-webapp\WEB-INF\classes\crowdid.approval-whitelist
2020-05-27 19:52:08,825 localhost-startStop-1 WARN [org.openid4java.server.RealmVerifier] RP discovery / realm validation disabled;
2020-05-27 19:52:11,950 openid-spray-akka.actor.default-dispatcher-3 INFO [spray.server.servlet.Boot] v2 configuration: OpenIdServerConfig(baseUri=http://localhost:8095/openidserver/v2, cookieConfig=CookieConfig(crowd.token_key), crowdRestConfig=CrowdRestConfig(baseUri=http://localhost:8095/crowd, applicationName=crowd-openid-server, applicationPassword=*****, timeout=Timeout(10 minutes)), sessionRoutes=ServletSessionRoutes(http://localhost:8095/openidserver?returnToUrl=${RETURN_TO_URL}), isRelyingPartyAuthorised=<function1>)
27-May-2020 19:52:12.872 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.

2020-05-28 00:28:11,990 PluginSchedulerTask-com.atlassian.analytics.client.upload.S3EventUploader:job INFO [com.amazonaws.http.AmazonHttpClient] Unable to execute HTTP request: btf-analytics.s3.amazonaws.com
java.net.UnknownHostException: btf-analytics.s3.amazonaws.com
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:929)
at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1324)
at java.net.InetAddress.getAllByName0(InetAddress.java:1277)
at java.net.InetAddress.getAllByName(InetAddress.java:1193)
at java.net.InetAddress.getAllByName(InetAddress.java:1127)
at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:45)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.resolveHostname(DefaultClientConnectionOperator.java:263)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:162)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:326)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:835)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:464)
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:273)
at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3660)
at com.amazonaws.services.s3.AmazonS3Client.putObject(AmazonS3Client.java:1432)
at com.atlassian.analytics.client.s3.AnalyticsS3Client.uploadFilesToS3Bucket(AnalyticsS3Client.java:88)
at com.atlassian.analytics.client.upload.S3EventUploader.execute(S3EventUploader.java:81)
at com.atlassian.scheduler.compat.local.LocalOnlyPluginJob.execute(LocalOnlyPluginJob.java:30)
at com.atlassian.sal.core.scheduling.TimerPluginScheduler$PluginTimerTask.run(TimerPluginScheduler.java:75)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
2020-05-28 00:28:11,990 PluginSchedulerTask-com.atlassian.analytics.client.upload.S3EventUploader:job INFO [com.amazonaws.http.AmazonHttpClient] Unable to execute HTTP request: btf-analytics.s3.amazonaws.com
java.net.UnknownHostException: btf-analytics.s3.amazonaws.com
at java.net.InetAddress.getAllByName0(InetAddress.java:1281)
at java.net.InetAddress.getAllByName(InetAddress.java:1193)
at java.net.InetAddress.getAllByName(InetAddress.java:1127)
at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:45)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.resolveHostname(DefaultClientConnectionOperator.java:263)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:162)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:326)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:835)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:464)
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:273)
at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3660)
at com.amazonaws.services.s3.AmazonS3Client.putObject(AmazonS3Client.java:1432)
at com.atlassian.analytics.client.s3.AnalyticsS3Client.uploadFilesToS3Bucket(AnalyticsS3Client.java:88)
at com.atlassian.analytics.client.upload.S3EventUploader.execute(S3EventUploader.java:81)
at com.atlassian.scheduler.compat.local.LocalOnlyPluginJob.execute(LocalOnlyPluginJob.java:30)
at com.atlassian.sal.core.scheduling.TimerPluginScheduler$PluginTimerTask.run(TimerPluginScheduler.java:75)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)

[Alexis Robert · Accepted solution]

Hi @Maggie , 

have you tried an installation from scratch with the installer first ? If that works and you're available to access Jira this way, you can then edit the dbconfig.xml file in the HOME_DIR and point it to your production Jira database.

Let me know if this helps, 

--Alexis

[Maggie]

Alexis,

Thank you very much for your suggestion. I tried this, and observed the following:

• After the initial install, Jira started.
• I stopped Jira, & replaced the new dbconfig.xml with the copy from my old instance.
• When I tried to restart Jira, I experienced the same issues as I described earlier.
• I checked my dbconfig.xml file against the settings recommended here: https://confluence.atlassian.com/adminjiraserver/connecting-jira-applications-to-sql-server-2017-970613480.html. My file matches the specified format. I have posted my file below (with server name, user name, & password replaced).

<?xml version="1.0" encoding="UTF-8"?>

<jira-database-config>
<name>defaultDS</name>
<delegator-name>default</delegator-name>
<database-type>mssql</database-type>
<schema-name>jira</schema-name>
<jdbc-datasource>
<url>jdbc:sqlserver://;serverName=serverName;portNumber=1433;databaseName=Jira</url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
<username>userName</username>
<password>userPassword</password>
<pool-min-size>20</pool-min-size>
<pool-max-size>20</pool-max-size>
<pool-max-wait>30000</pool-max-wait>
<validation-query>select 1</validation-query>
<min-evictable-idle-time-millis>60000</min-evictable-idle-time-millis>
<time-between-eviction-runs-millis>300000</time-between-eviction-runs-millis>
<pool-max-idle>20</pool-max-idle>
<pool-remove-abandoned>true</pool-remove-abandoned>
<pool-remove-abandoned-timeout>300</pool-remove-abandoned-timeout>
<pool-test-on-borrow>false</pool-test-on-borrow>
<pool-test-while-idle>true</pool-test-while-idle>
</jdbc-datasource>
</jira-database-config>

 Thank you very much for your help. Again, I would appreciate any advice you have to offer.

[Maggie]

I tried restarting again, & Jira loaded! Again, thank you for your help!

[Alexis Robert]

Great news then ! Hope it will stay stable on your new server :)

Thanks !

--Alexis