• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Default page on working domain after backup requires httpd restart

D

DeanW

Guest
I think this might have something to do with the backup process. It seems that ONE of my two domains on the server does not recover. My client reported the site went down at exactly the backup time, but it never came back up even 7 hours later. I verified the other site still worked and this site didn't. So I assume this is a problem with turning the domain back on after a backup. Note that this didn't happen with a manual backup and doesn't seem to happen every time, just once every few weeks (its a weekly script)

Plesk Version:
psa-7.5.4-fc2.build75050824.12

Backup Version:
psa-bu-7.5.4-fc2.build75050926.17

Backup Command:
/usr/local/psa/bin/psadump -f - --nostop --do-not-dump-logs | gzip | split -b 1000m - dump-`hostname`.

Restarting apache seems to fix it. I have added a "/sbin/service httpd restart" after the Plesk backup to hopefully resolve the issue, but wish it never had to happen in the first place.

If anyone has the same issue and/or any ideas please let me know.

Regards, DW

UPDATE: This is in the logs...

Jan 29 04:00:06 my.server.com psadump: Can't locate XML/Parser/Style/Dom.pm

UPDATE: I manually updated the XML::Dom perl module check out this post and the message seems to have disappeared. Not sure if I'll ever know about the reason a domain might not be turned back on. :)
 
I have created a small script file that restarts apache/mysql/psa imediately after creating the backup.

This script is run with a cron task on a daily basis.
 
I seem to have experienced an httpd crash NOT at backup time this time. I saw the message "MaxClients" reached in the logs and increased this in the config file. Of course, I don't think this will fix it either... and don't know why it would freeze completely.....

DW
 
My recent troubles were, I believe, caused by a runaway client script filling up their error_log to 18GB resulting in the /home folder being unwritable. The server would take a connection but wouldn't show anything...

Due to a short temporary error when restarting httpd manually with 'httpd restart' I added a 5 second delay between httpd stop and httpd start proceeding my backup script.

DW
----
Unlimited email lists with a PHP script on your web site!
http://listmailpro.com
 
Back
Top