• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

*** /etc/psa/plesk-cron.daily/50plesk-daily Failed (code=1) ***

SabineW

Basic Pleskian
Hi to all!
Since 14th July I got this entry in my daily e-mail instead of
*** /etc/psa/plesk-cron.daily/50plesk-daily Completed ***

I've found out it is a mysql-problem and I tried to do a bootstrapper repair procedure, but it doesn't solve the problem.
Here is the output:
Code:
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.


**** Product repair started.

===> Checking for previous installation ... found.
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.


ERROR while trying to detect MySQL service name
Check the error reason(see log file: /var/log/plesk/install/plesk_12.0.18_repair.log), fix and try again

*****  problem report *****
ERROR while trying to detect MySQL service name
Check the error reason(see log file: /var/log/plesk/install/plesk_12.0.18_repair.log), fix and try again
In the logfile is no more information to find and I've no idea, what was happened and how to solve it.
And no daily dump is saved since this day.
A google-search was not really helpful.
On my server runs openSUSE 13.1.
I'm glad for every help and sorry for my bad english.
 
Workaround: Create symbolic links before bootstrapper repair:

# ln -s /usr/sbin/rcmysql /etc/init.d/mysql
# ln -s /usr/lib/systemd/system/mysql.service /usr/lib/systemd/system/mariadb.service
 
Back
Top