Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bitnami Wordpress] Services not starting automatically and not starting/restarting properly in command-line #1738

Open
alexgobert opened this issue Dec 14, 2024 · 4 comments
Assignees
Labels
tech-issues The user has a technical issue about an application triage Triage is needed wordpress

Comments

@alexgobert
Copy link

Platform

AWS

bndiagnostic ID know more about bndiagnostic ID

5d450c08-3eb7-1892-bd67-9fc991a04815

bndiagnostic output

===== Begin of bndiagnostic tool output =====

✓ Processes: No issues found
? Connectivity: Found possible issues
✓ Php: No issues found
? Apache: Found possible issues
✓ Resources: No issues found
✓ Wordpress: No issues found

[Connectivity]

Server ports 22, 80 and/or 443 are not publicly accessible. Please check the
following guide to open server ports for remote access:

https://docs.bitnami.com/general/faq/administration/use-firewall/

[Apache]

Found recent error or warning messages in the Apache error log.
Press [Enter] to continue:

[Fri Dec 13 23:10:57.547573 2024] [proxy_fcgi:error] [pid 799:tid 1057] [client
**ip_address**:39866] AH01079: failed to make connection to backend: www-fpm
 [Fri Dec 13 23:22:57.023125 2024] [proxy:error] [pid 4986:tid 5251] (2)No such
file or directory: AH02454: FCGI: attempt to connect to Unix domain socket
/opt/bitnami/php/var/run/www.sock (www-fpm:8000) failed
 [Fri Dec 13 23:22:57.023181 2024] [proxy_fcgi:error] [pid 4986:tid 5251]
[client **ip_address**:56806] AH01079: failed to make connection to backend:
www-fpm

Please check the following guide to troubleshoot server issues:

https://docs.bitnami.com/general/apps/wordpress/troubleshooting/debug-erro
rs-apache/

===== End of bndiagnostic tool output =====

bndiagnostic was not useful. Could you please tell us why?

Does not address issue at hand.

Describe your issue as much as you can

Running a Lightsail instance of Bitnami Wordpress. On startup, neither apache nor gonit are running, verified by sudo /opt/bitnami/ctlscript.sh status and sudo gonit status. When I click the reboot button in Lightsail, the instance restarts automatically. I do not believe this is normal. I must ssh into the instance on every start up to turn on gonit and apache using sudo gonit and sudo /opt/bitnami/ctlscript.sh start apache. Without any arguments after start, ctlscript.sh fails with a bitnami.service error. Below is output from sudo systemctl status bitnami.service

`× bitnami.service - LSB: bitnami init script
Loaded: loaded (/etc/init.d/bitnami; enabled; preset: enabled)
Active: failed (Result: exit-code) since Fri 2024-12-13 23:26:56 CST; 9min ago
Process: 5885 ExecStart=/etc/init.d/bitnami start (code=exited, status=1/FAILURE)
CPU: 2.273s

Dec 13 23:26:56 ip-172-26-12-225 bitnami[5944]: 2024-12-14T05:26:56.325Z - error: Unable to perform start operation Export start for mariadb failed with exit code 1
Dec 13 23:26:56 ip-172-26-12-225 bitnami[6023]: ## 2024-12-13 23:26:56-06:00 ## INFO ## Running /opt/bitnami/var/init/post-start/010_bitnami_agent_extra...
Dec 13 23:26:56 ip-172-26-12-225 bitnami[6023]: ## 2024-12-13 23:26:56-06:00 ## INFO ## Running /opt/bitnami/var/init/post-start/020_bitnami_agent...
Dec 13 23:26:56 ip-172-26-12-225 bitnami[6023]: ## 2024-12-13 23:26:56-06:00 ## INFO ## Running /opt/bitnami/var/init/post-start/030_update_welcome_file...
Dec 13 23:26:56 ip-172-26-12-225 bitnami[6023]: ## 2024-12-13 23:26:56-06:00 ## INFO ## Running /opt/bitnami/var/init/post-start/040_bitnami_credentials_file...
Dec 13 23:26:56 ip-172-26-12-225 bitnami[6023]: ## 2024-12-13 23:26:56-06:00 ## INFO ## Running /opt/bitnami/var/init/post-start/050_clean_metadata...
Dec 13 23:26:56 ip-172-26-12-225 systemd[1]: bitnami.service: Control process exited, code=exited, status=1/FAILURE
Dec 13 23:26:56 ip-172-26-12-225 systemd[1]: bitnami.service: Failed with result 'exit-code'.
Dec 13 23:26:56 ip-172-26-12-225 systemd[1]: Failed to start bitnami.service - LSB: bitnami init script.
Dec 13 23:26:56 ip-172-26-12-225 systemd[1]: bitnami.service: Consumed 2.273s CPU time.`

I tried to follow other issues with the same LSB: bitnami init script error, but I found little success.

Side note, I disabled mariadb using this issue because I am using AWS RDS as my database.

@alexgobert alexgobert added the tech-issues The user has a technical issue about an application label Dec 14, 2024
@github-actions github-actions bot added the triage Triage is needed label Dec 14, 2024
@gongomgra
Copy link
Collaborator

gongomgra commented Dec 19, 2024

Hi @alexgobert,

Thanks for using Bitnami. Can you tell us how did you disable the database in your server? I understand Gonit is returning errors about MariaDB because although you disabled it in your server, Gonit still believes it has to monitor it. Can you rename the Gonit's config file for MariaDB to mariadb.conf.disabled and then restart the Bitnami service with SystemD? The config files are located under the /etc/monit/conf.d folder

https://docs.bitnami.com/aws/apps/wordpress-multisite/administration/configure-use-gonit/#modify-gonit-configuration

@alexgobert
Copy link
Author

Thanks for the reply, @gongomgra

I have already renamed the .conf file, but I can try to restart bitnami.service again. I'll attach screenshots when I get back to my computer.

@gongomgra
Copy link
Collaborator

@alexgobert once the /etc/monit/conf.d/mariadb.conf file has been renamed into mariadb.conf.disabled, reload Gonit and SystemD configs

sudo gonit reload
sudo systemctl daemon-reload
sudo gonit status

@alexgobert
Copy link
Author

alexgobert commented Dec 24, 2024

image
image

Still no dice. See above screenshots for the outputs of those commands. When I clicked Lightsail's "Reboot" button, it instantly went back to running and my terminal refused to reconnect via SSH. When I hard stop and start the instance, gonit is not running. See below for output of sudo gonit status once the instance is running again.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tech-issues The user has a technical issue about an application triage Triage is needed wordpress
Projects
None yet
Development

No branches or pull requests

2 participants