Wordpress Bitnami image on AWS failed to start bitnami service

[PaulOliverppt]

Describe your issue as much as you can

Platform
AWS

bndiagnostic ID know more about bndiagnostic ID
54ea1ca6-2ce9-1d4b-714b-b721dcd0e618

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

bndiagnostic was not useful. Could you please tell us why?
Couldn't identify the Root Cause

Describe your issue as much as you can

Our wordpress site went down at around 11:16 AM GMT.

It is running on an aws ec2 instance with this ami: aws-marketplace/bitnami-wordpress-6.0.1-9-r07-linux-debian-11-x86_64-hvm-ebs-nami-7d426cb7-9522-4dd7-a56b-55dd8cc1c8d0

Restarting the bitnami service using the ctlscript.sh tool fails.

[Apache]

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

[Fri Nov 29 11:16:29.820695 2024] [proxy:error] [pid 51069:tid 140109802231552]
(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 Nov 29 11:16:29.820799 2024] [proxy_fcgi:error] [pid 51069:tid
140109802231552] [client **ip_address**:36524] AH01079: failed to make
connection to backend: httpd-UDS
 [Fri Nov 29 11:16:41.041126 2024] [core:error] [pid 1509:tid 140111853741888]
AH00046: child process 50786 still did not exit, sending a SIGKILL

[PaulOliverppt]

The issue was /opt/bitnami/apache/var/run/httpd.pid was corrupted so the bitnami service was unable to start.

I removed the file, restarted the service and all was well.

I discovered this by starting the bitnami service manually:
sudo /etc/init.d/bitnami start

That allowed me to see the output