• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Adding Hosting to subscription fails

Klaas_Chielens

New Pleskian
Hi all,

I can create a new subscription but when it saves it does so without hosting, returning this error:

Error: Unable to load object of type SysUser with id=57: SysUser: unable to select: no such row in the table

When trying to add web hosting afterwards I get the same error. I found a couple of solutions here that all start of by asking to do

grep '<domain name>' /etc/passwd

but as the subscription is started and no domain is created, there also is no list of this in the /etc/passwd

OS ‪CentOS 6.6 (Final)‬
Plesk version 12.5.30 Update #8, last updated at Oct 27, 2015 11:16 AM

all help welcome.

Kind regards,

K
 
Hi Vlihtanskiy,

allas, this did not solve the problem.
# plesk repair db
Checking the Plesk database using the native database server tools .. [OK]
Checking the structure of the Plesk database ........................ [OK]
Checking the consistency of the Plesk database
Inconsistency in the table 'domains' for the column cert_rep_id: No
rows in the table 'Repository' with rep_id = 2 .................... [WARNING]
To see more details, run the command in the verbose mode: plesk repair db -verbose
Fix broken references in the table 'domains'? [Y/n] Y
Creating a database dump ........................................ [OK]
A dump of the database was created before an attempt to repair the database: /var/lib/psa/dumps/mysql.preresolve.20151029-142918.dump.gz
Fixing broken references ........................................ [FIXED]
Error messages: 0; Warnings: 1; Errors resolved: 1​


#plesk repair ftp
Checking system users ............................................... [OK]
Error messages: 0; Warnings: 0; Errors resolved: 0

---
but the problem persists (with the same error)
 
Hi Klaas_Chielens,

as suggested by the plesk repair utility ( => "To see more details, run the command in the verbose mode: plesk repair db -verbose" ), you could try to use the command

plesk repair db -verbose

... to get a verbose output of the current error(s).


Some errors can't be automatically repaired with the repair utility and have to be solved manually. Consider to read and follow:

 
Back
Top