Welcome to the Treehouse Community
Looking to learn something new?
Kevin Korte28,135 Points
Live Apache server crashes at random intervals - continuing problem - help
Hello, so at work we have a VPS running Linux 2.6.18-028stab092.1 with psa v8.6.0_build86081001.15 os_Debian 4.0 (Plesk).
I believe this starting happening after they installed a SSL certificate for us months ago, but I haven't been able to make that connection yet, it's all just coincidental. Nothing in the server settings have changed, the guy who set it up is long gone, the only thing that has changed was the addition of the SSL cert.
There seems to be no pattern to when it crashes, no rhyme or reason. When it does crash, the sites stay offline until it is manually reset (usually by me online), and than it is good to go until it happens again.
Well, it just happened this morning. I would look like the company hero if I can solve this. This is what was in the error reports, and all that I ever find in the error reports. Been searching for days, but havent found anything to help me much.
Does this mean anything to anybody. Any help is greatly appreciated.
[Mon Oct 14 11:59:33 2013] [notice] caught SIGTERM, shutting down Processing config directory: /opt/psa/admin/conf/httpsd.*.include [Mon Oct 14 12:00:22 2013] [notice] Apache configured -- resuming normal operations [Mon Oct 14 12:00:22 2013] [notice] Accept mutex: sysvsem (Default: sysvsem)
James Barnett39,199 Points
My guess is you've got an issue with Plesk possibly a permissions error. Take a look to see if SELinux is on and causing havoc. Take a look at your log files, Plesk, Apache, System see if there's anything suspicious in them.
If you are confused on how to to do that, remember to never send a dev to do a sysadmins job
I'd suggest you contact either VPS hosting support or Plesk support and send them your log files.
Also if you are still running Debian 4 (etch), you are 3 years out of date and security updates, so there's that.
Kevin Korte28,135 Points
Thank you James, at least I have some direction to go. That was the kind of advice I was looking for. That would make sense being 3 years out of date, that's been about how long it was since the guy who set this up left. From what I know we don't need a VPS, especially since nobody in the building is a sysadmin, but I may know one locally that might be able to help. I'll start with tracking in those error logs and see what I can find. I know enough to know I can be very dangerous in there!