• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • 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 Can't upgrade MariaDB

linuxman1

Basic Pleskian
Server operating system version
Alma Linux 8
Plesk version and microupdate number
18.0.68 Update 2
I have this issue blocking upgrade process, Restarting MySQL server ... Running mysqlcheck ... cloudfil_cloud.user_level warning : Found row where the auto_increment column has the value 0 The command exit code: 0
 
Martin can you explain why we need to do a manual upgrade when we get this error other than just tell us to do a manual upgrade.
 
Martin can you explain why we need to do a manual upgrade when we get this error other than just tell us to do a manual upgrade.
At the moment, the automatic tool does not yet support automatic fix of the increments being broken in tables. Since some warnings and error can cause big issues if ignored, the tool will not proceed.

It might be added in future depending on demand. No ETA or guarantee for such as of this moment.
 
Back
Top