Hi All,
We have been in a shocking situation, that while rebooting BB servers suddenly we are ending up with error LSB failed to start on all servers, nothing in logs, manual start of the script is not helping, after hours of trying we tried to create a new bitbucket.service file and start the service then that worked, but we need to understand what happened, please help.
[root@server1 bitbucket]# systemctl status atlbitbucket -l
Loaded: loaded (/etc/rc.d/init.d/atlbitbucket; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2020-02-07 21:05:30 GMT; 6s ago
Docs: man:systemd-sysv-generator(8)
Process: 17568 ExecStop=/etc/rc.d/init.d/atlbitbucket stop (code=exited, status=1/FAILURE)
Process: 17659 ExecStart=/etc/rc.d/init.d/atlbitbucket start (code=exited, status=1/FAILURE)
Feb 07 21:05:30 server1 systemd[1]: Starting LSB: Start Bitbucket daemon at boot time...
Feb 07 21:05:30server1 atlbitbucket[17659]: Starting Atlassian Bitbucket as dedicated user atlbitbucket
Feb 07 21:05:30 server1 systemd[1]: atlbitbucket.service: control process exited, code=exited status=1
Feb 07 21:05:30 server1 systemd[1]: Failed to start LSB: Start Bitbucket daemon at boot time.
Feb 07 21:05:30 server1 systemd[1]: Unit atlbitbucket.service entered failed state.
Feb 07 21:05:30 server1 systemd[1]: atlbitbucket.service failed.
[root@ies-med-bitbucket bitbucket]#
[root@server2 ~]# systemctl status atlbitbucket
Loaded: loaded (/etc/rc.d/init.d/atlbitbucket; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2020-02-07 20:16:39 GMT; 14min ago
Docs: man:systemd-sysv-generator(8)
Feb 07 20:16:39 server2 systemd[1]: Starting LSB: Start Bitbucket daemon at boot time...
Feb 07 20:16:39 server2 atlbitbucket[16662]: Starting Atlassian Bitbucket as dedica...et
Feb 07 20:16:39 server2 systemd[1]: atlbitbucket.service: control process exited, ...s=1
Feb 07 20:16:39 server2 systemd[1]: Failed to start LSB: Start Bitbucket daemon at...me.
Feb 07 20:16:39 server2 systemd[1]: Unit atlbitbucket.service entered failed state.
Feb 07 20:16:39 server2 systemd[1]: atlbitbucket.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[root@server2 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Workstation release 7.5 (Maipo)
[root@server2 ~]# systemctl status atlbitbucket
Loaded: loaded (/etc/rc.d/init.d/atlbitbucket; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2020-02-07 20:16:39 GMT; 36min ago
Docs: man:systemd-sysv-generator(8)
Even test server we just use Thursday
[root@server3 ~]# systemctl status atlbitbucket -l
Loaded: loaded (/etc/rc.d/init.d/atlbitbucket; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2020-02-07 12:34:50 PST; 8s ago
Docs: man:systemd-sysv-generator(8)
Process: 25022 ExecStop=/etc/rc.d/init.d/atlbitbucket stop (code=exited, status=0/SUCCESS)
Process: 23603 ExecStart=/etc/rc.d/init.d/atlbitbucket start (code=exited, status=1/FAILURE)
Feb 07 12:34:50 server3 systemd[1]: Starting LSB: Start Bitbucket daemon at boot time...
Feb 07 12:34:50 server3 atlbitbucket[23603]: Starting Atlassian Bitbucket as dedicated user atlbitbucket
Feb 07 12:34:50 server3 atlbitbucket[23603]: runuser: warning: cannot change directory to /home/atlbitbucket: No such file or directory
Feb 07 12:34:50 server3 systemd[1]: atlbitbucket.service: control process exited, code=exited status=1
Feb 07 12:34:50 server3 systemd[1]: Failed to start LSB: Start Bitbucket daemon at boot time.
Feb 07 12:34:50 server3 systemd[1]: Unit atlbitbucket.service entered failed state.
Feb 07 12:34:50 server3 systemd[1]: atlbitbucket.service failed.
This servers have not changed for a year, so from application perspective nothing, our system admins confirmed they changed nothing.
I just need to understand the error, and for some reason the old atlbitbucket.service is now back to work despite of hours giving LSB errors yesterday.
I am trying to understand what is happening to create a root cause analysis.
How to debug BB in such situation as it was not responding, no logs, all what it was giving is LSB failed to start.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.