bitnami / vms

Bitnami VMs
https://bitnami.com
Other
203 stars 42 forks source link

Failed to restart apache: Failed to restart apache #1415

Closed lecmaj closed 5 months ago

lecmaj commented 5 months ago

Platform

AWS

bndiagnostic ID know more about bndiagnostic ID

b9e31de5-2bde-b0a9-7793-416732cfa800

bndiagnostic output

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

[Resources]

Your instance has little available RAM memory.

 total used free shared buff/cache available Mem: 1947 856 142 4 947 902 Swap: 
2047 0 2047

You could try to increase your instance's memory. Please check your cloud provider's documentation for more information. Press [Enter] to continue:

[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/

[Wordpress]

Some files don't have the expected permissions Please check the following guide:

https://docs.bitnami.com/general/apps/wordpress/administration/understand- file-permissions/

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

Completed suggested items, apache still does not start.

Describe your issue as much as you can

System worked for last month and stopped working now. Per suggestions from bndiagnostic and other reported issues:

  1. Validated MYSQL / MariaDB and PHP were running services.
  2. Updated certificates to try to resolve "Server ports 22, 80 and/or 443 are not publicly accessible"
  3. Updated permissions to try to resolve "Some files don't have the expected permissions"
  4. Checked various logs and could not determine root cause.
  5. Cannot start apache interactively or on restart

Resource issues were not showing up initially, after restarting and running it again did not see resource issues. Rebooted, ran diagnostics again with ID: 2c8e381f-ab99-7acb-d8a2-0475c50826a1 and do not see the resource issues. Only see connectivity and Wordpress issues.

Appreciate your help.

gongomgra commented 5 months ago

Hi @lecmaj,

Thanks for using Bitnami. According to your latest bndiagnostic output, your filesystem permissions are wrong, and also Bitnami services were not running on the instance, but I was able to visit your website. Did you manage to fix your issue?

-----------------------------------
Get the ctlscript status
-----------------------------------
Running: ./ctlscript.sh status
In: /opt/bitnami

Output:

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)
lecmaj commented 5 months ago

Thank you for getting back to us @gongomgra, we could not wait long and had to create new instance from backup.

Running on the new instance: sudo ./ctlscript.sh status apache already running mariadb already running php-fpm already running

Running on the old instance where we have issues:

bitnami@ip-XX-XX-XX-XX:/opt/bitnami$ sudo ./ctlscript.sh status 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)

I am not sure why it is not starting?

gongomgra commented 5 months ago

HI @lecmaj,

According to the output you shared, the gonit monitor is not running. Did you modify anything in its configuration files? Can you try to start it manually?

sudo gonit

Then check the running status with

sudo gonit status
lecmaj commented 5 months ago

It seems the monitor was not running, not sure why it was not starting. We have recovered from backup and things seems to be working better. We will see if there will still be issues, I think we can close this for now.