Resolved Checking the consistency of the Plesk database Inconsistency in the table 'smb_roleServicePermissions'

[JulianDot]

Centos 8.2, LXC container
After upgrade to 18.0.30
I got the below warning when i run the Diagnose tool:

Checking the consistency of the Plesk database Inconsistency in the table 'smb_roleServicePermissions' for the column servicePermissionId: No rows in the table 'smb_servicePermissions' with id = 1

 

[jose carlos vega]

same problem after upgrade to 18.0.30

Checking the consistency of the Plesk database Inconsistency in the table 'smb_roleServicePermissions

 

[UHolthausen]

Hello

Debian 9.13
Upgrade to 18.0.30

same problem

Checking the consistency of the Plesk database Inconsistency in the table 'smb_roleServicePermissions' for the column servicePermissionId: No rows in the table 'smb_servicePermissions' with id = 1

 

[IgorG]

Have you tried to fix it with

# plesk repair db

?

 

[UHolthausen]

that worked now, must admit that I only requested it via the repair function yesterday.


Thanks

 

[JulianDot]

Can be fixed by running from CLI the :

plesk repair db -verbose

Remove unnecessary rows from the table 'smb_roleServicePermissions'? [Y/n]

But when is about to modify data in Plesk database, is always a good idea to ask first

 

[ssldn]

Thanks for the heads up (often needed) in such a cluttered and negatively impacted environment.

 

[learning_curve]

FWIW, this bug is nearly two weeks old now. It's been tested & acknowledged by Plesk and is set to be fixed in a future release:
PPPM-12392: "Database inconsistency after update to 18.0.30.0"
It can easily be fixed via CLI meanwhile (as posted above) but it is not possible to fix it via the Plesk UI, currently, hence the future bug/fix

 

[IgorG]

PPPM-12392: "Database inconsistency after update to 18.0.30.0"

Fixed in Plesk 18.0.31:

Running the plesk bin repair --db command after updating to Plesk Obsidian 18.0.30 no longer results in a misleading error message. (PPPM-12392)

 

[MitchellvB995]

Still happens on Ubuntu 20.04.1 Clean Installation of Plesk 18.0.32?

 

[Talistech]

Still happens on Ubuntu 20.04.1 Clean Installation of Plesk 18.0.32?

Yes, same here, still happens on Ubuntu 20.04.1 Clean Installation of Plesk 18.0.32.

 

[learning_curve]

We recently migrated an Ubuntu 18.04.5 LTS / Plesk 18.0.32 server onto a new, clean install Ubuntu 20.04.1 / Plesk 18.0.32 server.
FWIW - We've never seen this, since back on that previous server, back in late September 2020.