Facebook
Twitter
G
gwider
Guest
Dear Colleagues,
for the last weeks we've been battling with huge cpu loads of 3 to 10, before we realised that /var/qmail/queue was 1.9 GB large. Eventually we found a bounced message to root@ containing presumable the entire backup data of 1.8 GB.
This is likely to be in some connection with a connection problem to the backup servers at a large German webhoster. After execution of the psadump cron job, psa (or at least some services) won't restart.
Main question:
How can I stop psadump from dumping it's data in an email? I can't believe this is a feature!?
Any ideas on how to let psa wake up again after an erroneous backup?
Your ideas would be appreciated! Thanks!
Have a great day!
German
for the last weeks we've been battling with huge cpu loads of 3 to 10, before we realised that /var/qmail/queue was 1.9 GB large. Eventually we found a bounced message to root@ containing presumable the entire backup data of 1.8 GB.
This is likely to be in some connection with a connection problem to the backup servers at a large German webhoster. After execution of the psadump cron job, psa (or at least some services) won't restart.
Main question:
How can I stop psadump from dumping it's data in an email? I can't believe this is a feature!?
Any ideas on how to let psa wake up again after an erroneous backup?
Your ideas would be appreciated! Thanks!
Have a great day!
German
