503 server error after WHM upgrade

Foxhound

• December 27, 2013 08:26

This morning I performed an upgrade of my WHM. It is now on the latest version, WHM 11.40.1 (build 8). I needed to upgrade MySQL first cause that was still 5.0, so I upgraded that first to version 5.5.34-cll After performing both those updated I am now no longer able to see the contents on my website cause every link shows a 503 error: "Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. Additionally, a 503 Service Temporarily Unavailable error was encountered while trying to use an ErrorDocument to handle the request." For complete info here are all version info which might be usefull. Apache version 2.2.26 PHP version 5.4.23 MySQL version 5.5.34-cll I have been checking some logs for the past few hours but i really have no idea what is causing this 503 error. Before I did the upgrade this server was running just fine. Since I see no errors in the logs (but I am pretty novice with this) I have no clue how to troubleshoot this. Any assistance that can be offered would be very welcome! Thanks in advance.

• 

  quietFinn

  • December 27, 2013 13:56

  How did you do the upgrade to version 5.5? What do you see in /usr/local/apache/logs/error_log when you get those 503 errors?

  0
• 

  cPanelMichael

  • December 27, 2013 14:18

  Hello :) Did you check the Apache error log (/usr/local/apache/logs/error_log) for specific entries related to this problem? Thank you.

  0
• 

  Foxhound

  • December 27, 2013 14:19

  For the MySQL upgrade I simply did it in whm: Home "Software "MySQL Upgrade There is nothing in that error log when that 503 errors shows (nothing important at least). And it shows for every attempt I make to view that domain. No matter which file, which folder, it always and every time shows that 503 error. Here is the log with the latest 30 entires: [Fri Dec 27 13:57:56 2013] [error] [client 178.154.178.248] File does not exist: /usr/local/apache/htdocs/robots.txt [Fri Dec 27 13:58:58 2013] [error] [client 178.154.178.248] File does not exist: /usr/local/apache/htdocs/robots.txt [Fri Dec 27 13:58:58 2013] [error] [client 178.154.178.248] File does not exist: /usr/local/apache/htdocs/robots.txt [Fri Dec 27 14:03:22 2013] [error] [client 5.241.86.46] File does not exist: /home/xxxx/public_html/favicon.ico [Fri Dec 27 14:03:22 2013] [error] [client 5.241.86.46] File does not exist: /home/xxxx/public_html/http: [Fri Dec 27 14:10:27 2013] [error] [client 37.145.251.62] File does not exist: /home/xxxx/public_html/favicon.ico [Fri Dec 27 14:10:27 2013] [error] [client 37.145.251.62] File does not exist: /home/xxxx/public_html/http: [Fri Dec 27 14:10:33 2013] [error] [client 37.145.251.62] File does not exist: /home/xxxx/public_html/favicon.ico [Fri Dec 27 14:10:33 2013] [error] [client 37.145.251.62] File does not exist: /home/xxxx/public_html/http: [Fri Dec 27 14:13:41 2013] [error] [client 93.99.5.172] File does not exist: /home/xxxx/public_html/testers, referer: http://www.xxxx.com/forums/index.php...elease-thread/ [Fri Dec 27 14:13:41 2013] [error] [client 93.99.5.172] File does not exist: /home/xxxx/public_html/http:, referer: http://www.xxxx.com/forums/index.php...elease-thread/ [Fri Dec 27 14:42:21 2013] [error] [client 157.55.33.47] File does not exist: /usr/local/apache/htdocs/robots.txt [Fri Dec 27 14:46:15 2013] [error] [client 109.103.20.63] File does not exist: /home/xxxx/public_html/favicon.ico [Fri Dec 27 14:46:15 2013] [error] [client 109.103.20.63] File does not exist: /home/xxxx/public_html/http: [Fri Dec 27 14:46:20 2013] [error] [client 109.103.20.63] File does not exist: /home/xxxx/public_html/favicon.ico [Fri Dec 27 14:46:20 2013] [error] [client 109.103.20.63] File does not exist: /home/xxxx/public_html/http: [Fri Dec 27 15:05:28 2013] [error] [client 86.197.63.208] File does not exist: /home/xxxx/public_html/favicon.ico [Fri Dec 27 15:05:28 2013] [error] [client 86.197.63.208] File does not exist: /home/xxxx/public_html/http: [Fri Dec 27 15:06:36 2013] [error] [client 80.137.5.228] File does not exist: /home/xxxx/public_html/favicon.ico [Fri Dec 27 15:06:36 2013] [error] [client 80.137.5.228] File does not exist: /home/xxxx/public_html/http: [Fri Dec 27 15:14:01 2013] [notice] Graceful restart requested, doing restart [Fri Dec 27 15:14:02 2013] [notice] mod_bw : Memory Allocated 180 bytes (each conf takes 36 bytes) [Fri Dec 27 15:14:02 2013] [notice] mod_bw : Version 0.92 - Initialized [5 Confs] [Fri Dec 27 15:14:07 2013] [notice] Apache/2.2.26 (Unix) mod_ssl/2.2.26 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.4.23 configured -- resuming normal operations [Fri Dec 27 15:14:14 2013] [error] [client 2.99.244.55] File does not exist: /home/xxxx/public_html/favicon.ico [Fri Dec 27 15:14:14 2013] [error] [client 2.99.244.55] File does not exist: /home/xxxx/public_html/http: [Fri Dec 27 15:14:19 2013] [error] [client 2.99.244.55] File does not exist: /home/xxxx/public_html/favicon.ico [Fri Dec 27 15:14:19 2013] [error] [client 2.99.244.55] File does not exist: /home/xxxx/public_html/http: [Fri Dec 27 15:14:24 2013] [error] [client 79.176.0.134] File does not exist: /home/xxxx/public_html/favicon.ico [Fri Dec 27 15:14:24 2013] [error] [client 79.176.0.134] File does not exist: /home/xxxx/public_html/http:
  

  0
• 

  cPanelMichael

  • December 27, 2013 15:09

  Feel free to open a support ticket using the link in my signature so we can take a closer look. You can post the ticket number here so we can update this thread with the outcome. Thank you.

  0
• 

  Foxhound

  • December 27, 2013 15:38

  I have submitted a ticket. I hope I have done all correctly. Here is the ticket number: id is: 4430705 Thank you for your help so far!

  0
• 

  cPanelMichael

  • December 27, 2013 19:40

  To update, this was resolved by disabling the following line in the Apache configuration file: LoadModule bw_module modules/mod_bw.so
  Thank you.

  0
• 

  Foxhound

  • December 28, 2013 15:19

  Thanks for all the assistance in this matter. Our server is once again properly running. To make sure all info is here I would like to add the following: "This is a known issue with bw_module that one of our developers opened a bug report about in September of this year. It is filed under case ID # 78869"

  0
• 

  cPanelMichael

  • January 01, 2014 17:54

  Yes, there is an internal case open to address the issue with EasyApache incorrectly configuring mod_bandwidth. The case number is 78869. A time frame for a resolution is not yet available, but feel free to monitor the change log for the inclusion of this number: EasyApache Change Log Thank you.

  0

Please sign in to leave a comment.