Bitnami jenkins Failed to start LSB: bitnami init script

user_10819464 0
Viewed 873

I'm trying to upgrade my jenkins instance RAM at GCP. It's all normal until I start again the instance. It starts gracefully but cannot run the jenkins service.

Jun 24 12:44:57 jenkins-1-vm bitnami[6657]: no listening sockets available, shutting down
Jun 24 12:44:57 jenkins-1-vm bitnami[6657]: AH00015: Unable to open logs
Jun 24 12:44:57 jenkins-1-vm bitnami[6657]: ## 2021-06-24 12:44:57+00:00 ## INFO ## Running /opt/bitnami/var/init/post-start/010_bitnami_agent_extra…
Jun 24 12:44:57 jenkins-1-vm bitnami[6657]: ## 2021-06-24 12:44:57+00:00 ## INFO ## Running /opt/bitnami/var/init/post-start/020_bitnami_agent…
Jun 24 12:44:57 jenkins-1-vm bitnami[6657]: ## 2021-06-24 12:44:57+00:00 ## INFO ## Running /opt/bitnami/var/init/post-start/030_update_welcome_file…
Jun 24 12:44:57 jenkins-1-vm bitnami[6657]: ## 2021-06-24 12:44:57+00:00 ## INFO ## Running /opt/bitnami/var/init/post-start/040_bitnami_credentials_file…
Jun 24 12:44:57 jenkins-1-vm bitnami[6657]: ## 2021-06-24 12:44:57+00:00 ## INFO ## Running /opt/bitnami/var/init/post-start/050_clean_metadata…
Jun 24 12:44:57 jenkins-1-vm systemd[1]: bitnami.service: Control process exited, code=exited, status=1/FAILURE
Jun 24 12:44:57 jenkins-1-vm systemd[1]: bitnami.service: Failed with result ‘exit-code’.
Jun 24 12:44:57 jenkins-1-vm systemd[1]: Failed to start LSB: bitnami init script.

I spent hours for walk around try to fix this issue but still cannot find any solution. Any suggestion how can I fix it?

Many thanks.

bitnami google-cloud-platform jenkins
2 Answers

After walk around and asking to Bitnami support for Jenkins, finally I got the point of the issues. The log doesn't provide me the real issue when i checked it. So, Its just because bitnami automaticly running apache on the instance when I restart again. Just stop and disabled the apache service then try to start the bitnami service. bitnami works well again. you can see here, the full step how to fixing the problem with support tools from bitnami.

user_108194640

If going back to previous RAM amount does not solve the issue, then the issue lies somewhere else.
I suspect bitnami config files have been corrupted when the VM has been stopped.
Try re-deploying and make sure you shutdown the system gracefully (e.g. shutdown -h) before changing specs.

user_146634970
Related