1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Default page on working domain after backup requires httpd restart

Discussion in 'Plesk for Linux - 8.x and Older' started by DeanW, Jan 29, 2006.

  1. DeanW

    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:

    Backup Version:

    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. :)
  2. koalatxu

    koalatxu Guest

    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.
  3. DeanW

    DeanW Guest

    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.....

  4. DeanW

    DeanW Guest

    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.

    Unlimited email lists with a PHP script on your web site!