Stash unreachable after startup

Patrick Hiesel July 28, 2014

Hi,

I have the problem that stash (3.1.3) - while starting without errors - is unreachable. I even tried a clean install with no success. Any ideas? Thanks!

The log:

2014-07-29 16:21:46,621 INFO [localhost-startStop-1] c.a.s.i.server.BuildInfoLogger Starting Stash 3.1.3 (faa46f8 built on Wed Jul 09 01:29:27 GMT+01:00 2014)

2014-07-29 16:21:46,625 INFO [localhost-startStop-1] c.a.s.i.server.BuildInfoLogger JVM: Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 1.7.0_51-b13

2014-07-29 16:21:48,330 INFO [localhost-startStop-1] c.a.s.internal.home.HomeLockAcquirer Successfully acquired lock on home directory /var/atlassian/application-data/stash for 26587@xxx.net

2014-07-29 16:22:06,610 INFO [localhost-startStop-1] c.a.s.i.hook.DefaultHookService Hook callback socket listening on 127.0.0.1:60422

2014-07-29 16:22:15,341 WARN [ThreadPoolAsyncTaskExecutor::Thread 22] o.s.beans.TypeConverterDelegate PropertyEditor [com.sun.beans.editors.EnumEditor] found through deprecated global PropertyEditorManager fallback - consider using a more isolated form of registration, e.g. on the BeanWrapper/BeanFactory!

2014-07-29 16:22:16,369 INFO [ThreadPoolAsyncTaskExecutor::Thread 11] c.a.s.i.s.g.t.DefaultTranscodeServer Callback socket listening at 127.0.0.1:49633

2014-07-29 16:22:17,303 WARN [ThreadPoolAsyncTaskExecutor::Thread 25] n.s.e.config.CacheConfiguration Cache 'com.atlassian.applinks.core.DefaultReadOnlyApplicationLinkService.links' is set to eternal but also has TTI/TTL set. To avoid this warning, clean up the config removing conflicting values of eternal, TTI and TTL. Effective configuration for Cache 'com.atlassian.applinks.core.DefaultReadOnlyApplicationLinkService.links' will be eternal='true', timeToIdleSeconds='0', timeToLiveSeconds='0'.

2014-07-29 16:22:17,507 WARN [ThreadPoolAsyncTaskExecutor::Thread 11] n.s.e.config.CacheConfiguration Cache 'HostLicenseCache' is set to eternal but also has TTI/TTL set. To avoid this warning, clean up the config removing conflicting values of eternal, TTI and TTL. Effective configuration for Cache 'HostLicenseCache' will be eternal='true', timeToIdleSeconds='0', timeToLiveSeconds='0'.

2014-07-29 16:22:17,522 WARN [ThreadPoolAsyncTaskExecutor::Thread 11] n.s.e.config.CacheConfiguration Cache 'UpmRoleBasedMetadataCache' is set to eternal but also has TTI/TTL set. To avoid this warning, clean up the config removing conflicting values of eternal, TTI and TTL. Effective configuration for Cache 'UpmRoleBasedMetadataCache' will be eternal='true', timeToIdleSeconds='0', timeToLiveSeconds='0'.

2014-07-29 16:22:17,976 WARN [ThreadPoolAsyncTaskExecutor::Thread 11] n.s.e.config.CacheConfiguration Cache 'UpmPluginLicenseCache' is set to eternal but also has TTI/TTL set. To avoid this warning, clean up the config removing conflicting values of eternal, TTI and TTL. Effective configuration for Cache 'UpmPluginLicenseCache' will be eternal='true', timeToIdleSeconds='0', timeToLiveSeconds='0'.

2014-07-29 16:22:20,165 WARN [localhost-startStop-1] c.a.s.i.p.OsgiBundledPathScanner Cannot scan directory /com/atlassian/oauth/shared/servlet/ in bundle com.atlassian.oauth.atlassian-oauth-service-provider-plugin as it does not exist

2014-07-29 16:22:23,922 INFO [localhost-startStop-1] c.a.s.internal.ssh.server.SshServer Starting SSH server on port 7999...

2014-07-29 16:22:23,979 INFO [localhost-startStop-1] c.a.s.internal.ssh.server.SshServer Started SSH server successfully.

2014-07-29 16:22:23,994 INFO [localhost-startStop-1] c.a.s.internal.scm.PluginScmService Stash is using /usr/bin/git version 1.7.10.4

7 answers

1 accepted

0 votes
Answer accepted
Patrick Hiesel July 30, 2014

Thanks for all the comments! In the end it was a weird issue. Once I restarted Crowd (residing on the same server) stash was reachable again, even without a restart. Now both systems are working just fine.

0 votes
Mehmet Kazgan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 29, 2014

One other thing is install the previous version and manually add the plugins from there and restart. See what happens.

0 votes
Mehmet Kazgan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 29, 2014

I have a feeling that this was caused by a plugin not initializing properly in the beginning. If you removed all plugins manually, that also might be an issue as Stash might be looking for a particular plugin initially.

Is this a fresh install? It seems like they have fixed couple issues with plugin incompatibility issues.

https://confluence.atlassian.com/display/STASH/Stash+3.1+release+notes

I would revert back to a previous version if I were you as the logs don't tell us much.

0 votes
Patrick Hiesel July 28, 2014

Not really. I removed all plugins manually today after Stash didn't start anymore. (I deleted the jar files of the plugins)

0 votes
Mehmet Kazgan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 28, 2014

OK, thanks.

Did you recently install or update a plugin?

0 votes
Patrick Hiesel July 28, 2014

Hi Mehmet,

thank's for your reply. I have set the log level to ERROR. Here is the output:

2014-07-29 17:20:13,620 INFO [localhost-startStop-1] c.a.s.i.server.BuildInfoLogger Starting Stash 3.1.3 (faa46f8 built on Wed Jul 09 01:29:27 GMT+01:00 2014)

2014-07-29 17:20:13,624 INFO [localhost-startStop-1] c.a.s.i.server.BuildInfoLogger JVM: Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 1.7.0_51-b13

2014-07-29 17:20:14,941 INFO [localhost-startStop-1] c.a.s.internal.home.HomeLockAcquirer Successfully acquired lock on home directory /var/atlassian/application-data/stash for 1204@__.net

2014-07-29 17:20:28,334 WARN [localhost-startStop-1] ROOT Switching to log level [ERROR]

2014-07-29 17:20:28,335 INFO [localhost-startStop-1] com.atlassian.stash Switching to log level [ERROR]

2014-07-29 17:20:39,296 WARN [ThreadPoolAsyncTaskExecutor::Thread 24] o.s.beans.TypeConverterDelegate PropertyEditor [com.sun.beans.editors.EnumEditor] found through deprecated global PropertyEditorManager fallback - consider using a more isolated form of registration, e.g. on the BeanWrapper/BeanFactory!

2014-07-29 17:20:41,755 WARN [ThreadPoolAsyncTaskExecutor::Thread 5] n.s.e.config.CacheConfiguration Cache 'HostLicenseCache' is set to eternal but also has TTI/TTL set. To avoid this warning, clean up the config removing conflicting values of eternal, TTI and TTL. Effective configuration for Cache 'HostLicenseCache' will be eternal='true', timeToIdleSeconds='0', timeToLiveSeconds='0'.

2014-07-29 17:20:41,774 WARN [ThreadPoolAsyncTaskExecutor::Thread 5] n.s.e.config.CacheConfiguration Cache 'UpmRoleBasedMetadataCache' is set to eternal but also has TTI/TTL set. To avoid this warning, clean up the config removing conflicting values of eternal, TTI and TTL. Effective configuration for Cache 'UpmRoleBasedMetadataCache' will be eternal='true', timeToIdleSeconds='0', timeToLiveSeconds='0'.

2014-07-29 17:20:41,937 WARN [ThreadPoolAsyncTaskExecutor::Thread 9] n.s.e.config.CacheConfiguration Cache 'com.atlassian.applinks.core.DefaultReadOnlyApplicationLinkService.links' is set to eternal but also has TTI/TTL set. To avoid this warning, clean up the config removing conflicting values of eternal, TTI and TTL. Effective configuration for Cache 'com.atlassian.applinks.core.DefaultReadOnlyApplicationLinkService.links' will be eternal='true', timeToIdleSeconds='0', timeToLiveSeconds='0'.

2014-07-29 17:20:42,057 WARN [ThreadPoolAsyncTaskExecutor::Thread 5] n.s.e.config.CacheConfiguration Cache 'UpmPluginLicenseCache' is set to eternal but also has TTI/TTL set. To avoid this warning, clean up the config removing conflicting values of eternal, TTI and TTL. Effective configuration for Cache 'UpmPluginLicenseCache' will be eternal='true', timeToIdleSeconds='0', timeToLiveSeconds='0'.

Thanks!

0 votes
Mehmet Kazgan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 28, 2014

Hi Patrick,

Can you turn on error logging and copy the log again?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events