Applicable to:
- Plesk for Linux
Symptoms
-
Unable to manage domain settings (rename a domain, change a hosting type, add an email account, etc.):
PLESK_ERROR: mailmng-outgoing failed: ERROR:outgoing:No backend DB entries were modified.
PLESK_ERROR: mailmng-outgoing failed: ERROR:outgoing:domain_aliases.domain_id may not be NULL
-
In
/var/lib/plesk/mail/outgoing/data.dbSQLite database, there is a record aboutalias.example.com:# sqlite3 /var/lib/plesk/mail/outgoing/data.db
MYSQL_LIN: sqlite> SELECT id,name,subscription_id,out_limit FROM domains WHERE name='alias.example.com';
13|alias.example.com|11|500' -
There is no
alias.example.com recordinpsa.domainstable:# plesk db 'select id, name from domains where name like "%alias.example.com%";'
Empty set (0.00 sec)
Cause
An inconsistency of internal database: a domain was not renamed.
Resolution
-
Connect to the server using SSH.
-
Create a backup of
/var/lib/plesk/mail/outgoing/data.dbdatabase:# cp /var/lib/plesk/mail/outgoing/data.db{,_bk}
-
Log in to SQLite database:
# sqlite3 /var/lib/plesk/mail/outgoing/data.db
-
Get the ID of the domain:
MYSQL_LIN: SELECT id,name,subscription_id,out_limit FROM domains WHERE name='alias.example.com';
10|alias.example.com|1|130 -
Rename the domain using the domain ID from the previous step:
MYSQL_LIN: UPDATE domains SET name='example.com' WHERE id=10;
If it is necessary to remove domain, delete the related records from the database:
MYSQL_LIN: DELETE FROM domains WHERE id=10;
-
Verify the directory
/var/qmail/mailnames/example.comdoes not exist. If it exists, perform steps from this article:
Unable to swap domain and domain alias names: boost::filesystem::filesystem_error Directory not empty
Note: if additional errors occur during the attempt to rename a domain, step 5 should be repeated.
Comments
3 comments
When are you going to fix this one? Still seeing it in 17.8.11 Update #66
Hi, burnleyvic!
There is an database issue which can be caused by many factors from MySQL performance to manual removal of the record from the database. Since there is no way to track the issue back, the resolution from the article needs to be applied to resolve it. If you can provide us with steps to reproduce the issue, please submit request to Plesk support as described in the link below and we would gladly look into this closer:
https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support-
The article in step 6, is not accessible even after logging in to Plesk 360
Please sign in to leave a comment.