• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Upgrade to 12.5 pre-upgrade check corrupted database entries

It is just warning but not error. If you are not familiar with SQL, you can just continue upgrade procedure and when it will be finished you can fix database inconsistencies with:

# plesk repair db

in command line.
 
I had this warning on a other server. after upgrade and plesk repair db users cant login in the mailboxes. mchk failed and i need direcly plesk support on the server.
Root cause was in database inconsistency that was not fixed with plesk repair db.
I am therefore a little concerned that there is in other servers too.
 
Do you have Apparmor enabled on your server before starting upgrade?
 
no there is no apparmor
/etc/init.d/apparmor stop
-bash: /etc/init.d/apparmor: No such file or directory

i have test an upgrade yet
after upgrade plesk repair all
db issues were fixed
mchk failed

i read the answer from plesk support from the server were they fixed ist directly on the server.
it was exact the same problem
"outgoing_email_mode_explicit_ip_v4" had value ="6", but "IP_Addresses" has id="7".
To fix the issue I set "outgoing_email_mode_explicit_ip_v4" = 7:

after that mchk without error.
i think i musst check db before upgrade.
 
Can Some one please share the exact steps to fix such issue?

The link which it suggest to check is not working any more , it says it is outdated
 
Hello,

Did anyone find a solution for this.
Am trying to upgrade from 12.0.18 Update #75 to 12.5.30 on Centos 6 Linux and am getting this warning that refers to an outdated link below.

"WARNING: Some database entries related to Panel IP addresses are corrupted. Please see http://kb.odin.com/en/113826 for the solution."
 
Usually this error related to orphaned records in "IpAddressesCollections" table in psa database. I would suggest you contact Plesk Support Team you can't fix this database inconsistency by yourself.
 
Back
Top