Unknown database 'atmail' when selecting the database

[LarsenD]

This is just a bug report. No help needed as it doesn´t seem to cause problems.

When I update servers via CLI autoinstaller, I always (afair) get this mysqldump error message:

Stopping psa... * Stopping Plesk engine pool manager sw-engine-fpm
...done.
done
-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.

mysqldump: Got error: 1049: Unknown database 'atmail' when selecting the database

===> Cumulative APS controller database (apsc) upgrade has been started.
===> Cumulative upgrade of APS controller database has been completed.
===> Cumulative Plesk database upgrade (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade of Plesk database (revertable stage) has been completed.
Reading package lists...

There is no database "atmail" on any of our Plesk servers. Simple solution should be to first check if the DB exists before performing actions on it.

As a bonus, perhaps it would be possible to suppress the warning about mysql.event.

 

[UFHH01]

The autoinstaller is coded to serve all possible variations for all possible Plesk environments - some checks might not be usefull for your specific servers, but the coding to check each specific environment in order to perform a specific mysql dump, instead of doing a complete basic psa - database dump is not really a bug. It might look a bit better in the logs, if you don't see any error - message, but the actual psa - dump is still done, when you use the autoinstaller - with, or without some basic psa tables, which might not exist on your specific server.

The warning "Specify the --events option explicitly" is as well a warning from MySQL and not from Plesk. You could dump this specific table from the mysql - database only if you use the "--events" string, but due to the fact that only very few people use the MySQL - Event - Scheduler feature at all, you could either ignore that warning, or make a separate dump with the command:

mysqldump -u root -p --events mysql > /usr/src/mysql.sql​

... but if you insist, that such a warning shouldn't be in your logfiles, you might consider modifying your own "my.cnf" - configuration by adding:

[mysqldump]
events
ignore-table=mysql.event

 

[24x7serversupports]

adding ignore-table=mysql.event worked for me to resolve same kind of issue.

 

[LarsenD]

@parallels: Will the error about "Unknown database 'atmail'" be fixed?

 

[IgorG]

Before upgrade Plesk makes dumps of all known databases including atmail database. It is hardcoded. It is considered as defect but not bug:

What is Bug?
A fault in a program which causes the program to perform in an unintended or unanticipated manner.

What is Defect?
If software misses some feature or function from what is there in requirement it is called as defect.

I hope it will be fixed but it has a very low priority.

 

[LarsenD]

Shouldn´t be so hard to check if any database exists before making a dump, should it? The right thing for junior-programmers to get started ;-)