Website is down after lightsail instance reboot

Hi,

If your WordPress website is down after rebooting your Amazon Lightsail instance and you're encountering the error "ERR_CONNECTION_REFUSED," it indicates that the server hosting the website (www.marketinghouse.ge in this case) is not running and not able to handle connection requests.

You tried to restart all services using the sudo /opt/bitnami/ctlscript.sh restart command and got the following message:

bitnami@ip-172-26-3-58:$ sudo /opt/bitnami/ctlscript.sh restart Restarting services.. Job for bitnami.service failed because the control process exited with error code. See "systemctl status bitnami.service" and "journalctl -xe" for details. bitnami@ip-172-26-3-58:$

The message you received indicates that there was an error while attempting to restart the Bitnami services for your WordPress installation on AWS lightsail. The error is related to the "bitnami.service" control process. To gather more information about the error and its details, you are advised to check the output of two commands:

1. systemctl status bitnami.service: This command provides the status of the "bitnami.service" unit, including any error messages or relevant information about why it failed to restart.
2. journalctl -xe -u bitnami.service: This command allows you to view the system journal, which contains logs and information about various processes and events on your AWS instance. Running this command with the "-xe" options will show you any recent log entries that might shed light on the issue with the Bitnami service.

By running journalctl -xe -u bitnami.service, you'll see the most recent logs with more details. It's helpful for troubleshooting any issues or errors you might be experiencing with your Bitnami WordPress instance. Scroll through the logs to locate any error messages or relevant information. The logs will show the timestamp, service name, and log messages. Note that the “-xe” option is used to display the most recent entries and to show the logs until the end of the file, even if there are no new entries. This can be helpful for getting a complete overview of recent events and errors. If you encounter any error messages or issues, review the log details to identify the cause and take appropriate action

You tried to chech the status of your service using the sudo /opt/bitnami/ctlscript.sh status command and got the following message:

Cannot find any running daemon to contact. If it is running, make sure you are pointing to the right pid file (/var/run/gonit.pid)

The output of the command "sudo /opt/bitnami/ctlscript.sh status" indicates that it was unable to find any running daemon to communicate with. A daemon is a background process that runs continuously on a system. In this case, it appears that the command is trying to check the status of a daemon related to Bitnami services.

The error message specifically mentions the absence of a pid file or an incorrect path to the pid file. A pid file, short for process identifier file, is a file that typically contains the process ID (PID) of a running daemon. It helps other processes or scripts identify and interact with the running daemon.

The command is looking for the pid file at the location "/var/run/gonit.pid" but is unable to find it. This could be due to one of the following reasons:

1. The daemon associated with the Bitnami services is not running.
2. The pid file is located in a different directory.
3. The pid file is named differently.

To resolve the issue, you can try the following steps:

1. Restart the server or the specific daemon associated with Bitnami services using the appropriate command, such as "sudo /opt/bitnami/ctlscript.sh restart" or "sudo systemctl restart bitnami".
2. If the issue persists, check if the pid file is located in a different directory. You can search for the correct location or consult the Bitnami documentation for the expected location of the pid file.
3. Verify if the pid file has a different name than "gonit.pid". You can look for files with a ".pid" extension in the expected directory or refer to the documentation for the specific Bitnami installation.

By ensuring that the daemon is running and the correct pid file is located in the expected directory, you should be able to resolve the error and successfully check the status of the Bitnami services using the command "sudo /opt/bitnami/ctlscript.sh status".

For additional troubleshooting and reference, you can consult the following AWS documentation: Popular Articles – All docs | Lightsail Documentation

Thank you.