Server keeps crashing and sites time out , cannot even curl or ping the site,

[gaurav3]

Keywords: LAMP/MAMP/WAMP - AWS - Technical issue - Services (Apache, MariaDB, MySQL…)

bndiagnostic ID: 073aaf7a-7d38-b97c-44bd-216a92c3c477

bndiagnostic output:

? Apache: Found possible issues
? Resources: Found possible issues
https://docs.bitnami.com/general/apps/wordpress/troubleshooting/debug-errors-apache/

bndiagnostic failure reason: The documentation did not make any significant change

Description:
so here the site crashed and the site could not be curled or pinged, time out erorr, packet loss 100 percent, however, on diagnosis the tool says (bitnami diagnostic tool) that the port 80 is not available for public listening but netstat should it as LIsten , from the apche logs I have this:

[mpm_event:notice] [pid 1929:tid 140071891786624] AH0049 1: caught SIGTERM, shutting down [Sun Apr 24 05:27:09.505947 2022] [mpm_event:notice] [pid 685:tid 139735187913600] AH00489 : Apache/2.4.49 (Unix) OpenSSL/1.1.1n configured – resuming normal operations

so can it be the parameters like Start servers , pls suggest

[michiel]

Hi @gaurav3,

The Apache error log shows the following suspicious error:

[Sun Apr 24 16:37:09.187724 2022] [core:error] [pid 688:tid 139734135269120] [client xx.xxx.xxx..xx:55440] AH10244: invalid URI path (/../../../../../../../../../etc/passwd)

It seems like an attempt to read the /etc/passwd file. I recommend checking the following guide for blocking bots/hackers:

https://docs.bitnami.com/aws/apps/wordpress/troubleshooting/deny-connections-bots-apache/

I also recommend upgrading to a more powerful instance:

https://docs.bitnami.com/aws/faq/administration/upgrade-ami/

Regards,
Michiel

Regards,
Michiel

[gaurav3]

Yes I see this, but here can you tell what was this for?

] AH0049 1: caught SIGTERM, shutting down [Sun Apr 24 05:27:09.505947 2022] [mpm_event:notice] [pid 685:tid 139735187913600] AH00489 : Apache/2.4.49 (Unix) OpenSSL/1.1.1n configured – resuming normal operations

and why the ports were timing out and the site was nnot pinged

[michiel]

Hi @gaurav3,

I’m not sure what caused that error but it’s most probably due to the suspicious activity. I recommend launching a new instance and migrate your data there.

Regards,
Michiel