• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved "Dump failed; The following domains were not found on the host"

Yes this will fix issue with backup but seems after this last update custom mysql limits directory and conf file from systemd is removed,and now default max_open_files limit value is set,at least in my case that is what happen.Can anyone else can confirm this?
 
Confirmed! In my case: 1024

My fix was:

/lib/systemd/system/mysql.service
Code:
[Service]
LimitNOFILE=infinity
LimitMEMLOCK=infinity
 
This fixed my issue too
Code:
apt-get update && apt-get install libdbd-mysql-perl


Confirmed! In my case: 1024

My fix was:

/lib/systemd/system/mysql.service
Code:
[Service]
LimitNOFILE=infinity
LimitMEMLOCK=infinity
It's better to do that different as my fix survived this latest MySQL-update.

Here's the thread where I posted the question and fix (which I too found on the Internet):
Resolved - Not enough filehandles during back-up for mysqldump

cat /etc/systemd/system/mysql.service.d/override.conf
Code:
[Service]
LimitNOFILE=4096
 
Last edited:
I had the same backup issues with Plesk 17.5.3 update #17 on CentOS 7 (7.3.1611). The installation of the package "perl-DBD-MySQL" solved the problem.
 
Will installing the perl-DBD-MySQL file have any affect on the MariaDB database or anything else on the server we should be concerned about? Also running CentOS 7.3.1611 and Plesk 17.5.3

Tried adding the [Service] file to the MariaDB config and reloading daemon and mariadb but still got the error.

BTW, the error did not occur before updating MariaDB from 10.1.25 to 10.1.26 .

[UPDATE]

Just saw this added to the Onyx update that came down today (but we didn't receive yet):

Removing package perl-DBD-MySQL / libdbd-mysql-perl resulted in subscription backup failing with message ‘No objects to dump found’. (PPPM-6764)

{mark as solved}
 
Last edited:
Will installing the perl-DBD-MySQL file have any affect on the MariaDB database or anything else on the server we should be concerned about? Also running CentOS 7.3.1611 and Plesk 17.5.3

Tried adding the [Service] file to the MariaDB config and reloading daemon and mariadb but still got the error.

BTW, the error did not occur before updating MariaDB from 10.1.25 to 10.1.26 .

The problem "Dump failed" should get solved by installing perl-dbd-mysql by hand (yum or apt).

Then there is the, in fact unrelated, problem with file handles.
Although the proposed patching of /lib/systemd/system/mysql.service works, it does not stick good enough.
Some update, may undo this.

I extensively researched and tested it and the better solution IMHO is the creation of the file: /etc/systemd/system/mysql.service.d/override.conf
 
Last edited:
Back
Top