MySQL Backup fail during scheduled full backup

I have setup default scheduled backups to take place every night at midnight (full backup of all virtual servers and all features). All has been running like a charm up until a few nights ago one of my virtual servers reports a fail in the mysql dump procedure (all others run this dump without error).

Specific error in the backup log is below

Dumping MySQL database wordpress_domain_name ..
    .. dump failed! su: failed to execute /bin/sh: Resource temporarily unavailable

This is about the 10th of 40 domains backed up in the procedure and the first wordpress mysql backup in the sequence if that matters. wordpress mysql dumps after this domain report as completed successfully.

Status: 
Closed (fixed)

Comments

Do you have any limits setup in Virtualmin on the number of processes each domain can run?

Yes good point, that domain I do have limits set as it sometimes brings the server to a crawl probably from an errant wordpress plugin somewhere. When the backup runs it does use a lot of resources as you know.

You should try increasing the process limit a bit so that the MySQL dump in the backup doesn't run into it.

OK, thank you, I am not 100% clear on the process limits. Is this the best way to stop a virtual host from spawning 50 httpd processes? Or is there a better way.

Currently for this virtual server I have set the following limits Maximum number of processes : 5 Maximum CPU time per process : 10 seconds

I doubled these limits and still had the issue so put the limits back to unlimited and the backup completed successfully. Just curious if there is a document somewhere to educate me on these settings so I can better manage this virtual server and its processor usage.

Yeah those process limits are a good way to accomplish that, but the downside is that setting them too low can inhibit normal functions from being able to work properly.

If you see unusual things failing, it may be too to process limits that are set to low.

You could always try to bump those up a bit and see if the backups are able to complete successfully after that.

Status: Active » Fixed
Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.