HELP! Virtualmin Slow down, Website 500 Error

3 posts / 0 new
Topic locked
Last post
#1 Mon, 10/31/2016 - 11:19
Miker1029

HELP! Virtualmin Slow down, Website 500 Error

HELP!!!

This is really ODD, Virtualmin is TAKING OVER 20 MINUTES to LOAD, and my Forum is reporting a 500 Error: Here is the Story,

Everything was FINE yesterday, Matter of fact was playing Call of Duty Most of the day...(Nothing Changed on OS/Vurtualmin/Forum)

Last Night my Server monitor Reported the Site was down for 10 Minutes, I got up this morning and the Server is reporting a 500 Error and Virtualmin (As of now) is 20 Minutes in loading...

I've Shutdown and reset the OS (5x), I did a Speed test on the OS and All is fine there....

When I brought Virtualmin up the 1st time, It reported ALL the Modules (Apache, BIND, Etc) where OFF, I puttied in and the OS says HTTPD is running, (only thing I checked...).

I'm really at a LOSS here, I contact the VPS Provider and they said the seen no issues, and the Logins for the OS and Virtualmin all Reported Me as the last logins....

CPU/Memory looked fine memory was a little High at %70 which it normally runs around %50....

Anyone have ANY Ideas on what this could be, and where/what to look for on the OS the could be causing this, and Virtualmin IS STILL LOADING!!!

Thanks for ANY help.

Mike

Mon, 10/31/2016 - 15:09
Miker1029

Ok this has been resolved, My VPS host advised my it MIGHT be an Apache Config error, Which I let VIrtualmin Handle. The MAIN Issue was the "STEAL" in the KVM was at like %78, and the RedHat site says a HIGH steal is the HOSTS problem, You can decide as I have no clue, I did Numerous reboots of the server, and Numerous HTTPD shutdown restarts and it didn't fix it. So Whatever the Tech did on his side fixed it, he wouldn't tell me....

The Basics I do Know:

A Report from my Server Montior at "11:35PM (CDT) reported the site down for 10 Minutes. Upon me trying to go to the website I got a 500 eror (And Running SLOWER then a SNAIL MOVES) same with Virtualmin. Rebooted server and HTTPD Many times and did not resolve the Issue. Finally waited 30 Minutes for Virtualmin to load, and it was set for the WRONG IP, now keep in mind The day before ALL was fine, and the IP was Correct. Changed the IP to what it was Supposed to be, Resolved the Server 500 error. But Still Running at a Snails pace. Shutdown the server as per Techs request and let him restart or redo whatever... Everything is back to normal with a "STEAL" for %42-%51 from %71...

For reference here's my Apache logs for the time the Monitor Reported the site down:

[Sun Oct 30 23:22:20.571728 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 27857 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:22:20.655096 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 27851 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:24:21.539483 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 26951 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:31:08.738432 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 27850 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:32:18.643818 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 27866 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:32:46.746785 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28312 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:32:58.844633 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 27475 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:33:57.047118 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28624 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:34:14.838389 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28274 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:34:18.055599 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 27881 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:34:24.135798 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28587 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:34:24.135915 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28637 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:34:30.146555 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 26973 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:34:30.146688 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28269 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:34:35.630732 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28650 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:34:35.630875 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28649 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:34:35.630898 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28647 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:34:35.630911 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28645 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:34:35.630940 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28644 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:34:47.743518 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28666 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:34:47.743739 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28665 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:34:47.743779 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28664 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:34:53.744831 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28668 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:35:03.450876 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28682 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:35:03.451126 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28680 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:35:03.451148 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28678 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:37:15.248768 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28807 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:37:21.329408 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28811 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:37:21.329532 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28692 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:43:31.445558 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28744 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:43:41.127772 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28705 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:44:17.337855 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 29098 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:47:24.753594 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28691 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:53:46.328963 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 29221 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:53:58.942734 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28729 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:54:20.052456 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28902 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:57:06.848051 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 29448 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:58:48.746157 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28893 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:58:48.746573 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28904 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:59:22.543045 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 28730 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:59:22.552361 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 29464 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:59:32.230535 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 29669 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:59:32.334062 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 29508 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:59:32.334147 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 6998 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:59:42.540127 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 29677 graceful kill fail, sending SIGKILL
[Sun Oct 30 23:59:42.540431 2016] [fcgid:warn] [pid 6865] mod_fcgid: process 29676 graceful kill fail, sending SIGKILL

And Here it is Now After Tech Did whatever he did..

[Mon Oct 31 13:12:24.313212 2016] [fcgid:warn] [pid 1996] mod_fcgid: process 3390 graceful kill fail, sending SIGKILL
[Mon Oct 31 13:12:29.614197 2016] [fcgid:warn] [pid 1996] mod_fcgid: process 3515 graceful kill fail, sending SIGKILL
[Mon Oct 31 13:12:40.914240 2016] [fcgid:warn] [pid 1996] mod_fcgid: process 3541 graceful kill fail, sending SIGKILL
[Mon Oct 31 13:12:40.914344 2016] [fcgid:warn] [pid 1996] mod_fcgid: process 3536 graceful kill fail, sending SIGKILL
[Mon Oct 31 13:12:46.526940 2016] [fcgid:warn] [pid 1996] mod_fcgid: process 3355 graceful kill fail, sending SIGKILL
[Mon Oct 31 13:12:57.825206 2016] [fcgid:warn] [pid 1996] mod_fcgid: process 3555 graceful kill fail, sending SIGKILL
[Mon Oct 31 13:13:12.325770 2016] [fcgid:warn] [pid 1996] mod_fcgid: process 3588 graceful kill fail, sending SIGKILL
[Mon Oct 31 13:15:27.922401 2016] [fcgid:warn] [pid 1996] mod_fcgid: process 3619 graceful kill fail, sending SIGKILL
[Mon Oct 31 14:04:09.446555 2016] [mpm_prefork:notice] [pid 1498] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Oct 31 14:08:46.018891 2016] [suexec:notice] [pid 1348] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Oct 31 14:08:47.108040 2016] [auth_digest:notice] [pid 1348] AH01757: generating secret for digest authentication ...
[Mon Oct 31 14:08:47.117326 2016] [lbmethod_heartbeat:notice] [pid 1348] AH02282: No slotmem from mod_heartmonitor
[Mon Oct 31 14:08:49.609390 2016] [mpm_prefork:notice] [pid 1348] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips mod_fcgid/2.3.9 PHP/5.4.16 SVN/1.7.14 configured -- resuming normal operations
[Mon Oct 31 14:08:49.609429 2016] [core:notice] [pid 1348] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'

So I guess what I'm curious about is it an Apache Config Error, or My VPS Host? Guess not really important as everything is working as it did, Just looking for some knowledge...

Thanks Mike

Fri, 11/04/2016 - 15:37
midihipi
midihipi's picture

Just my two cents... EVERY TIME I get a 500 Internal Server Error, It is permissions on some resource Apache needs or is told to load but cannot due to missing permissions. Every time. I'll elaborate a little more. If apache is asked via php or another resource to load up a set of files and it cannot it will throw that error. If the site root for a virtual domain exists but it cannot access it, it throws that error. It's kind of a "run home to mama" error for permission problems. Could they have had some kind of monitoring client upgrade or something going on reset the perms on directories? Look in their forums for a trend on issues with other users all at once. Upgrade scripts can be the worst form of viruses. Just thinking.

Midi

Owner of Linux Nuts Professional Services

Topic locked