Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
We value your experience with Plesk during 2024 Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024. Please take this short survey: https://pt-research.typeform.com/to/AmZvSXkx
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.
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?
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)
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