• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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

JulianDot

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

Code:
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
 
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
 
Can be fixed by running from CLI the :
Bash:
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 :)
 
Thanks for the heads up (often needed) in such a cluttered and negatively impacted environment.
 
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
 
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.
 
Back
Top