-
Notifications
You must be signed in to change notification settings - Fork 43
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
[wordpress-bitnami-aws-lightsail] Services are shutting down automatically again and again #1192
Comments
Hi @dangerdon78, Thanks for using Bitnami. Ligthsail instances are known to suffer performance issues due to the kind of those instances (burstable instances). We recommend you to check this in a more specialized forum or with the AWS support team directly. Apart from the above, it looks like the bndiagnostic tool found some issues on your installation. Did you have any issue trying to fix them? |
My Instance is running in sustainable zone and not in burstable zone. "Apart from the above, it looks like the bndiagnostic tool found some issues on your installation." - Can you please tell which installation has issues? Is it WordPress, Plugin, SSL or the Instance? |
Hi @dangerdon78, Although we publish our images in AWS, we don't have any access or control privileges in the servers you run using our images as base images. Because of that, there are some topics in which we can't be of much help, like those relative to performance, where either the instance type or your customization of the base image maybe causing these errors. According to the bndiagnostic output, there are errors related to WordPress plugins. I also found the next output in the support bundle: did you modify anything in the configuration of gonit so it can't monitor the expected services?
Apart from the above, I visited your website and it seems to be working properly now. Did you manage to fix your issue? |
Multiple issues have been opened regarding Lightsail instances going down randomly and the answer provided from Bitnami was always the same: It seemed a bit too strange that this was happening out of the blue, and to this many users, only on server started using Bitnami Wordpress Image, so we dug deeper. |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Platform
AWS
bndiagnostic ID know more about bndiagnostic ID
8c3e01c9-1a89-8de8-cd8c-29a62d82eb38
bndiagnostic output
[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/
[Processes]
Press [Enter] to continue:
One or more component's processes are not running:
You can try to restart the process with the following command:
$ sudo /opt/bitnami/ctlscript.sh start COMPONENT_NAME
[Wordpress]
Found recent WordPress plugin related error messages in the Apache error log.
Please check the following guide to deactivate plugins:
https://developer.wordpress.org/cli/commands/plugin/deactivate/
Press [Enter] to continue:
[Apache]
Found recent error or warning messages in the Apache error log.
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?
My server, db, and php-fpm are shutting down automatically
Describe your issue as much as you can
My services are shutting down automatically again and again.
apache not running mariadb not running php-fpm not running.\
When i restart using this command: sudo /opt/bitnami/ctlscript.sh restart, the services starts normally. But after 3-5 days the services are shutting down automatically again and again.
May i know the problem?
Is there any security vulnerability?
The text was updated successfully, but these errors were encountered: