Oh the pain of migrating JSM to a new server 😭

[Mariano Edvardsson]

Before using secrets and whatnot, moving JSM to a new server was a breeze, now (10.3.1) I can't seem to get it to work at all.

What I've tried so far:

• scp the while jira app directory and jira home directory and importing DB backup, no work.
• rsyncing with all perms jira app directory and home directory, no work.
• Following this doc: https://confluence.atlassian.com/adminjiraserver103/migrating-jira-applications-to-another-server-1489807155.html  , no work.

I'm at loss. I have installed a new instance and try to connect to the DB, no good either. the new server is a full mirror of the current and working server.

I tried deleting secrets-config.yaml from the new server, also editing it so it is the same as the current server, still no good.

The error I get is the following (trimmed for brevity):

```

 set to PT48H 2025-01-25 21:35:02,035-0300 JIRA-Bootstrap INFO [c.a.j.util.stats.JiraStats] [JIRA-STATS] [LOGIN-STORE-STATS] stats created: loggingIntervalInMin=5, printInThread=true 2025-01-25 21:35:02,171-0300 JIRA-Bootstrap ERROR [c.a.event.internal.AsynchronousAbleEventDispatcher] There was an exception thrown trying to dispatch event [com.atlassian.plugin.event.events.PluginFrameworkStartingEvent@3916eb04] from the invoker [com.atlassian.event.internal.ComparableListenerInvoker@34e720e3] java.lang.RuntimeException: java.lang.InternalError: java.lang.reflect.InvocationTargetException. Listener: com.atlassian.jira.plugin.JiraOsgiContainerManager event: com.atlassian.plugin.event.events.PluginFrameworkStartingEvent at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:53) at com.atlassian.diagnostics.internal.platform.monitor.event.EventSystemMonitor.invokeMonitored(EventSystemMonitor.java:105)

  at java.desktop/sun.awt.X11FontManager.(X11FontManager.java:56) ... 84 more 2025-01-25 21:35:02,366-0300 JIRA-Bootstrap WARN [c.a.j.application.install.BundlesVersionDiscovery] Can't read manifest of file: /var/atlassian/application-data/jira/plugins/installed-plugins/plugin.5730693154657208477.jira-toolkit-2.0.0.jar java.lang.NullPointerException at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:906) at com.atlassian.plugin.osgi.util.OsgiHeaderUtil.getValidatedAttribute(OsgiHeaderUtil.java:361) at com.atlassian.plugin.osgi.util.OsgiHeaderUtil.extractOsgiPluginInformation(OsgiHeaderUtil.java:396)

2025-01-25 21:35:03,696-0300 JIRA-Bootstrap ERROR [c.a.plugin.loaders.ScanningPluginLoader] Because of the following exception: java.lang.IllegalStateException: Unable to create a tracker when osgi is not running

2025-01-25 21:35:03,722-0300 JIRA-Bootstrap ERROR [c.a.plugin.loaders.ScanningPluginLoader] Unable to deploy plugin 'com.atlassian.analytics.analytics-client' from 'Unit: /opt/atlassian-jira-software-10.3.1-standalone/atlassian-jira/WEB-INF/atlassian-bundled-plugins/analytics-client-9.2.2.jar (1734509846000)'. 2025-01-25 21:35:03,722-0300 JIRA-Bootstrap ERROR [c.a.plugin.loaders.ScanningPluginLoader] Because of the following exception: java.lang.IllegalStateException: Unable to create a tracker when osgi is not running at com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager.getServiceTracker(FelixOsgiContainerManager.java:446) at com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager.getServiceTracker(FelixOsgiContainerManager.java:438) at com.atlassian.plugin.osgi.factory.OsgiChainedModuleDescriptorFactoryCreator.create(OsgiChainedMo

2025-01-25 21:35:03,731-0300 JIRA-Bootstrap ERROR [c.a.plugin.loaders.ScanningPluginLoader] Unable to deploy plugin 'com.atlassian.analytics.analytics-whitelist' from 'Unit: /opt/atlassian-jira-software-10.3.1-standalone/atlassian-jira/WEB-INF/atlassian-bundled-plugins/analytics-whitelist-3.107.jar (1734509866000)'. 2025-01-25 21:35:03,731-0300 JIRA-Bootstrap ERROR [c.a.plugin.loaders.ScanningPluginLoader] Because of the following exception: java.lang.IllegalStateException: Unable to create a tracker when osgi is not running at com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager.getServiceTracker(Felix

```

I'm at loss of what else can I do in order to migrate my current PROD app to another bare metal server. If anyone can help me I'd greatly appreciate it!

PS: Both servers are running SLES 15.6, same timezone same everything. 

[Joseph Chung Yin]

@Mariano Edvardsson -

How did you setup your new server node?  Is your new node's configuration different than your Prod server setup in Data Center env?

Please provide more information, so we can further advise.

Best, Joseph Chung Yin

[Mariano Edvardsson]

Hello @Joseph Chung Yin ! New server node is an exact copy of the current Prod server setup. Same OS, same release.