Recent content by opus68

I am facing the same issue - upgrading with Plesk 18.0.76 still results in the same error as for @first4it . See also my earlier post. I am somewhat apprehensive as to whether this is really a "false positive". Has this been confirmed by the MariaDB team? @Sebahat.hadzhi - has the fix been...

Thanks a lot for the quick response and the clarification, @Sebahat.hadzhi - I restored a server backup, since I was unsure as to how serious the corruption is, so I am back to MariaDB 10.6. I'll wait for Plesk Obsidian 18.0.76 to be released and then try again. Thanks again!

I have just tried to upgrade from 10.6.22 to 10.11 on Ubuntu 22.04 using the Plesk MariaDB upgrade mechanism and the problem still seems to exist, although the ticket shows that the problem has been resolved in MariaDB 10.11.15. Can anybody confirm this or did I do something wrong?

18.0.57 #2 fixes the problem on my server. Thanks a lot!

Will do so - thank you very much for the quick response, @Peter Debik.

Immediately after updating to Plesk 18.0.57 I started receiving hourly cron job notices by email: Subject: Cron <root@hostname> run-parts /etc/cron.hourly /etc/cron.hourly/01-awp_hourly: AIR_GAPPED set to yes. Skipping execution of awp_hourly And indeed, in /var/awp/etc/config (sourced...

Great - thanks a lot for the feedback, @Peter Debik!

Hi all, some added information: it seems to me that the "ReportUsage" daily maintenance task is being called during upgrade/repair and returns a warning which may be the culprit. Running the daily maintenance task manually gives plesk daily -f ReportUsage PHP Warning: Trying to access array...

I ran into a problem report when updating two servers from 18.0.49 to 18.0.50. When trying to "repair plesk installation" the same problem re-appears and repair fails. However, "plesk repair all -n" flags no errors or warnings. Please see below the relevant excerpt from the installation log...