I attempted to start using upstart, but that evolved into a nightmare. Nothing seems to work to get it to see the right pid. Even using expect daemon option still does not get the right pid, so upstart ends up with a pid that does not even exist (by the way, I had some process to try to reap that fake pid to clear upstart status up, but that only works sometimes). Anyway, what is the ideal way to start automatically bamboo? No /wrapper folder exists that I can find that is mentioned in some articles, the bamboo.sh does not work anymore (warns you not to use), and the stop-bamboo.sh and start-bamboo.sh work weird--in that, stop-bamboo.sh fails the first time you run it, but works if you run it again. Do we use old fashion init.d stuff? chkconfig? upstart with a working conf file (what is that conf file)?
When I say stop-bamboo.sh fails. I see java.net.ConnectException: Connection refused the first time I run it and ps -ef shows it is still running. I did wait to see if it goes away, but it never does. If I run stop-bamboo.sh again, it does seem to work the second time.
I had no great answer on my issue. We use the bundle. That is our solution choice. I was just looking for the best way to start/stop the application in Linux as there are so many ways now to do so. The only thing I could see is that you need to put a sleep in after sending a stop request before you can start again (i.e., doing a restart). I saw no good way to use upstart that I could figure out, which is what I was hoping to use.
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
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