Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Crucible - Run as a daemon - Mac OSX

Hi everyone,

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.

http://confluence.atlassian.com/display/FISHEYE/How+to+run+Fisheye+or+Crucible+on+startup+on+Mac+OS+X

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!

Gavin.

2 answers

1 vote
Conor Atlassian Team Oct 03, 2011

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?

Hi Connor,

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!

Gavin.

Seems I was missing a few steps;

(copying the data / var and cache directories).

Also I did not have the FISHEYE_INST variable set either.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

107 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you