Fisheye fails to start, but no errors appear in the logs

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

Fisheye still appears to be running and is present in the process list ("ps -ef | grep fisheye" to check on *nix machines). However, the port appears to be closed (netstat -an | grep <server_port>) and no errors are recorded in Fisheye server logs:

2008-08-05 22:34:56,103 INFO  [main] fisheye.app SvnLoader-setup - Loading included SvnKit from lib/svn
2008-08-05 22:34:56,107 INFO  [main] fisheye.app SvnLoader-setupJarsFromDir - Loaded svn jar from directory /etc/fisheye/lib/svn
2008-08-05 22:34:56,347 INFO  [main] fisheye.app PassivateManager-load - Cache-sizing: repcache.memcache.total_size=22216704
2008-08-05 22:34:56,348 INFO  [main] fisheye.app PassivateManager-load - Cache-sizing: com.cenqua.fisheye.config.ConfigProperty@14dd758=50
2008-08-05 22:34:56,363 INFO  [main] fisheye.app InfinityDbHandle-open - opening /etc/fisheye/var/data/data0.bin with cachesize=2500000
2008-08-05 22:34:59,689 INFO  [main] fisheye.app NotificationManager-startNotifier - Notifier started.
2008-08-05 22:34:59,840 INFO  [FishEye Shutdown Service] fisheye.app ShutdownService-runServer - listening on 127.0.0.1:8059
2008-08-05 22:35:49,817 INFO  [Thread-1] fisheye.app HibernateUtil-destroy - Shutting down Crucible DB.

Cause

This is a known issue with Jetty. Please see JETTY-331 for more details.

Resolution

Add -Djava.security.egd=file:/dev/./urandom to the Fisheye Environment variables.

For example:

export FISHEYE_OPTS=-Xmx256m -Djava.security.egd=file:/dev/./urandom

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Last modified on Jul 31, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.