I am running Crucible (starter edition) with PostgreSQL.
(I am also running Jira and have Jira starting as a daemon on startup. I also have the linkage between Jira and Crucible successfully working)
However for some reason I cannot get crucible to start, using the folowing instructions.
My question relates to the FISHEYE_INST key.
Is it needed if using an external database? and subsequently, if this was set incorrectly - could it be the cause of Crucible not starting on system startup?
As always - a big thanks for any thoughts you might have!
The FISHEYE_INST variable designates the location of your FishEye (and Crucible) instance data and it is not related to the use of an external database.
If FISHEYE_INST is not set correctly it could certainly cause Crucible problems when it attempts to start up.
Can you provide any details about what actually happens?
If I run the start.sh script from /bin - then crucible loads correctly and works fine and dandy.
it is simply a case of; it does not start automatically on "power on" of the machine.
I created a "data" directory to be FISHEYE_INST;
I copied config.xml into that directory, too.
And when I attept to use /bin/start.sh - crucible failed to start at all.
I copied the XML back to FISHEYE_HOME and all was well again.
I am sure I am missing something simple... but obviously can't work it out for myself!
Everything below is tested on Ubuntu 17.10. I prefer to use Jira in a docker container because: 1. I can install Jira with a couple of commands. 2. I can start and stop Jira just by starting and s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot