• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Issue Plesk server shuts down randomly

MortezaHeydari

New Pleskian
Hi Everyone,

Let me explain the situation. The Plesk server shuts down early morning our time(Not server's timezone) multiple time recently. The error log doesn't show any errors at the time of shutdown.

here some info about the server:

· Plesk version: Plesk v12.0.18_build1200140606.15 os_CentOS 6

· The server has 5 websites plus a PIWIK(analytic tool) website on it.

· the traffic used is always between 200 GB to 300 GB per month.

· the website which has the most traffic has around 400,000 views monthly.


Anyone had similar issue? what is best way to troubleshoot this problem?

Thank you in advance.
 
Do you have any scheduled task at this morning time? Backup or something else?
 
The only schedule task i have found is under System Users root:

0 0 * * 0 /usr/local/psa/admin/bin/php -c '/usr/local/psa/admin/conf/php.ini' -dauto_prepend_file=sdk.php '/usr/local/psa/admin/plib/modules/servershield/scripts/update-servershield.php'
 
What about

# plesk db "select * from BackupsScheduled"
 
... just a shoot "out of the blue":

If you experience issues EVERY DAY, at the same time, it is most likely, that it has something to do with logrotate issues. See for example:

Hi Chris1,

consider to use "/bin/systemctl restart httpd.service" instead of "/bin/systemctl reload httpd.service"... untill you found the cause of your issue.

Consider as well to raise the open-file -limit for the apache system user. ( /etc/security/limits.conf ), or to setup a higher limit than the standart 1024 limit.

Example:
Code:
...
apache        soft    nofile          64000
apache        hard    nofile          64000
...

Consider as well to un-install modules, that you don't really need and use.


For further suggestion, please wait for another forum - user to answer you, but please be informed, that this doesn't seem to be a Plesk - related issue at all, so I would change the title of the thread. :)

I had the same problem (CentOS 7, Plesk 12.5).
It started when I installed mod_security.

As far as I understand, it occurs at logrotation, because both
/etc/logrotate.d/httpd
/etc/logrotate.d/mod_security
contain a line for httpd reload.
Apparently, they happen simultaneously and cause the 'seg fault' error of apache.

Replacing 'reload' with 'restart' solved the problem.

Hello @ehrenwert

Did changing the "reload" command to "restart" solve your problem as well?

I don't understand why this bug isn't fixed yet. I'm not sure who is at fault though.

This seems similar: https://bugzilla.redhat.com/show_bug.cgi?id=1143908

..but I don't have mod_php installed/loaded.

In the last week I did not mention a segfault. So it seems to be a valid workaround..
 
Back
Top