• 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 Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue error message in my plesk after a restore

aymen.benncir

New Pleskian
Server operating system version
Debian 10.13
Plesk version and microupdate number
Plesk Obsidian 18.0.67
bonjour à tous ,

j'ai un message d'erreur au niveau de ma suite plesk à une restauration et j'ai besoin d'aide

ci_joint le message d'erreur

1744023647478.png

Système d'exploitation : Debian 10.13
Produit : Mise à jour Plesk Obsidian 18.0.67

[courtesy admin translation]

Hello everyone,

I have an error message regarding my Plesk suite during a restore, and I need help.

Attached is the error message.
 
Last edited by a moderator:
le même message d'erreur reçu par email:

run-parts: /etc/cron.hourly/50plesk-hourly exited with return code 1

[courtesy admin translation]

the same error message received by email:

run-parts: /etc/cron.hourly/50plesk-hourly exited with return code 1
 
Last edited by a moderator:
Hello, @aymen.benncir . Are you able to connect to the server via SSH? If yes, please check what's the status of the database service:

systemctl status mariadb

If stopped/disabled, please start it and let us know if you get any error messages. It also makes sense to check the /var/log/mariadb/mariadb.log file.
 
Back
Top