• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Cannot backup in 11.5.3 #19

HoracioS

Regular Pleskian
I got the following error when trying to backup:

Warning: mysql "forum"
Failed to pack files backup_forum_1_1310221723 in /var/lib/psa/dumps/domains/xxxxxxx.com/databases/forum_1 [ 106140502016 bytes free of 107374182400 bytes total on mount point 0]
Warning: mysql "forum"
mysqldump: Got error: 23: Out of resources when opening file './forum/vbp__trackerstatus.MYD' (Errcode: 24) when using LOCK TABLES

Any help?

Best regards,
Horacio
 
mysqldump: Got error: 23: Out of resources when opening file './forum/vbp__trackerstatus.MYD' (Errcode: 24) when using LOCK TABLES

According to here - "OS error code 24: Too many open files" which lines up with the more general error 23 "Out of resources".

So it seems as though you are running out of file handles. This is usually server-end setting/problem, either in MySQL, or in the OS itself.

Perhaps check/adjust the --open-files-limit setting in MySQL itself and see if that helps.

Also, perhaps try running the dump, while no one else is using the DB, with the --single-transaction setting instead of --Lock-File, as several people suggest this will work one table at a time instead of opening them all at once (therefore using less file handles).

Beyond that you'll probably have to find a root cause as to why this particular server is running out of resources. which would probably involve troubleshooting by disabling as many services/processes as possible and see if the dump goes through. Then figure out from there who the culprit is that's eating too many resources and perhaps not freeing them correctly.
 
Back
Top