nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Starting Bamboo as a service in Centos 7

Jason Fuller

Hi,

I tried following the instructions at:

https://confluence.atlassian.com/bamboo/running-bamboo-as-a-linux-service-416056046.html

But the script on that page requires an argument (start, restart, stop), but this is not specified anywhere in the procedure.

And my installation is not starting upon boot, but I can manually start with that script.

I've checked the catalina.out file, but it doesn't even get that far -

How can I troubleshoot this?

How do you enter the "start" argument with the start of the system?

Accepted answers

Jeremy Owen

But the script on that page requires an argument (start, restart, stop), but this is not specified anywhere in the procedure.

It's not necessary to reference these explicitly anywhere. They're standard commands issued by the underlying OS service manager once the service has been registered.

Rather than troubleshooting the systemv service, for CentOS 7 I'd recommend setting it up as a systemd service using these instructions instead:

How to add Bamboo startup script to systemd

It's the standard on modern distros and more robust. I'll get the above instructions linked in the official doc too.

Hope this helps

All comments

Christian Glockner

Hi Jason,

It sounds like Bamboo isn't starting when you reboot the system. Did you run sudo /sbin/chkconfig --add bamboo, which configures Bamboo to start on system startup?

Cheers,

Christian

Premier Support Engineer

Atlassian

Marcel Van der Vliet

Jason Fuller

Hi Christian, yes. But as I mentioned - it makes sense that it will fail, as the script requires an argument, and none is provided upon reboot, as far as i can see.

Jeremy Owen

But the script on that page requires an argument (start, restart, stop), but this is not specified anywhere in the procedure.

It's not necessary to reference these explicitly anywhere. They're standard commands issued by the underlying OS service manager once the service has been registered.