Problem: AWS WordPress website is down.
Reason: Unknown.
So here comes the diagnosis.
Useful commands
//super user login
sudo su –
//echo apache error log
cat /opt/bitnami/apache2/logs/error_log
//edit httpd
vim /opt/bitnami/apache2/conf/bitnami/httpd.conf
//no pagespeed
https://www.angularjs4u.com/?ModPagespeed=off
//restart server
sudo /opt/bitnami/ctlscript.sh restart
AWS “scoreboard is full, not at MaxRequestWorkers”
/opt/bitnami/ctlscript.sh restart apache
/opt/bitnami/ctlscript.sh restart
Small Instance
1 2 3 4 5 6 7 8 9 |
<IfModule prefork.c> StartServers 2 MinSpareServers 1 MaxSpareServers 3 MaxClients 8 MaxRequestsPerChild 1000 </IfModule> |
[Tue Jun 07 08:56:39.136976 2016] [mpm_event:error] [pid 6605:tid 140336218933056] AH00484: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting
Bitnami child process still did not exit.
OK I GUESS CHECK THE NEWS BEFORE YOU START HAHAAHAH
Web chaos mostly over after Amazon Web Services hit by power outage during Sydney storm
Still they are down though.
References:
- https://linuxamination.blogspot.com.au/2016/05/server-reached-maxrequestworkers.html
- https://linuxamination.blogspot.com.au/2016/05/cannot-allocate-memory-fork-unable-to.html
“pagespeed:warn fetch timed out”
Load from ModPagespeedLoadFromFile?
“To get rid of these messages, I suggest you configure pagespeed to load files from disk instead[1] using ModPagespeedLoadFromFile and friends, which will resolve these messages, and brings these other benefits:”
https://stackoverflow.com/questions/17355899/very-many-fetch-timed-out-errors-in-apache-log
https://wiki.bitnami.com/Applications/BitNami_Wordpress#XML-RPC_and_Pingback
Refreshing Elastic IP Address seems to have worked?
“proxy_fcgi:error the timeout specified has expired”
STOP INSTANCE.
START INSTANCE.
WORKED.