Facebook
Twitter
Jean Pierre Kolb
New Pleskian
Strange error during backups (manual or scheduled) on a server running Plesk Onyx, Version 17.0.17 Update #29 and Ubuntu 16.04 (all available updates were installed). Since today (21.07.2017) every backup action fails with an error message like this:
The backup log for such an action looks looks like this:
Yesterday there were no errors and all backups (manual and scheduld) ran successfully.
No limits (e. g. file system, cpu, ram, db ...) are exhausted, all backups are stored locally ("/var/lib/psa/dumps"), no other errors or strange behaviors on this server (Plesk, NGINX, MySQL etc.)
It doesn't mater if the account is old, was updated today (e. g. added new domain) or was completly new created today with a new customer. The backup tasks on all accounts always fail, with the same error message.
The following commands where executed without errors or any effect:
The "plesk repair all" command outputs this:
The psa database was dumped manually ("mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` psa > psa.sql") and checked, but no errors or inconstancies could be found. Even the sql queries, shown in the log file above, were running perfectly and displays the correct data.
The only strange thing, which I can not understand, is the line:
The guid "c3d3524b-52dc-4352-87bf-0d916acf6bc1" isn't set or written in or into the database. If this should be the guid for the corresponding domain (e. g. example.com) in the psa database table "domains", then this must be the problem causing the error, because in the database table, there is another guid for this domain. Every time the backup task is running and failing, there is a new guid outputted in this line - for the same domain?
Even no changes for the server or psa configuration were made, during the last 24 hours.
An diff command on the database today's dump "/var/lib/psa/dumps/mysql.daily.dump.0.gz" and "/var/lib/psa/dumps/mysql.daily.dump.2.gz" from the day before yesterday, only shows differences in tables for e. g. logs. But there was a new table created:
Maybe there was an update for plesk migrator?
Has anybody an idea, which thing could cause this error?
Thanks in advance!
The backup log for such an action looks looks like this:
Code:
see attached file: "plesk_backup_error_log.txt"Yesterday there were no errors and all backups (manual and scheduld) ran successfully.
No limits (e. g. file system, cpu, ram, db ...) are exhausted, all backups are stored locally ("/var/lib/psa/dumps"), no other errors or strange behaviors on this server (Plesk, NGINX, MySQL etc.)
It doesn't mater if the account is old, was updated today (e. g. added new domain) or was completly new created today with a new customer. The backup tasks on all accounts always fail, with the same error message.
The following commands where executed without errors or any effect:
Code:
service psa restart
service mysql restart
service psa-firewall restart
service psa-health-monitor-notificationd restart
service sw-collectd restart
service sw-cp-server restart
service sw-engine restart
plesk repair all
plesk repair db
plesk repair mysql
plesk repair fsThe "plesk repair all" command outputs this:
Code:
Reconfiguring the Plesk installation
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 ...................... [OK]
Checking system users ............................................... [OK]
Checking Linux system files ......................................... [OK]
Checking virtual hosts' file system ................................. [OK]
Checking Plesk version .............................................. [OK]
Checking for custom configuration templates ......................... [OK]
Checking for the JkWorkersFile directive in the Apache configuration [OK]
Checking associations between domains and IP addresses .............. [OK]
Checking for corrupted reference between IP collections and IP
addresses ........................................................... [OK]
Checking for links between APS applications and subscriptions ....... [OK]
Checking for the Zend extension declaraion in php.ini ............... [OK]
Check symbolic links for latest virtual host config files ........... [OK]
Checking for system users home directories consistency .............. [OK]
Checking for records with empty name field in the Configurations table[OK]
Checking for nginx ULIMIT value ..................................... [OK]
Checking for extra configurations in database not owned by any object [OK]
Repairing web server configuration .................................. [OK]
Checking the usage of PHP handlers .................................. [OK]
Repairing the mail server configuration ............................. [OK]
Checking the DNS configuration file ................................. [OK]
Restoring DNS server configuration .................................. [OK]
Checking MySQL database servers ..................................... [OK]
Repair databases on available servers ............................... [OK]
Repair database users on available servers .......................... [OK]
Error messages: 0; Warnings: 0; Errors resolved: 0The psa database was dumped manually ("mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` psa > psa.sql") and checked, but no errors or inconstancies could be found. Even the sql queries, shown in the log file above, were running perfectly and displays the correct data.
The only strange thing, which I can not understand, is the line:
Code:
[19717]: 2017-07-21 08:00:22.745 WARN c3d3524b-52dc-4352-87bf-0d916acf6bc1 The following domains were not found on the host: example.comThe guid "c3d3524b-52dc-4352-87bf-0d916acf6bc1" isn't set or written in or into the database. If this should be the guid for the corresponding domain (e. g. example.com) in the psa database table "domains", then this must be the problem causing the error, because in the database table, there is another guid for this domain. Every time the backup task is running and failing, there is a new guid outputted in this line - for the same domain?
Even no changes for the server or psa configuration were made, during the last 24 hours.
An diff command on the database today's dump "/var/lib/psa/dumps/mysql.daily.dump.0.gz" and "/var/lib/psa/dumps/mysql.daily.dump.2.gz" from the day before yesterday, only shows differences in tables for e. g. logs. But there was a new table created:
Code:
+-- Table structure for table `gtid_executed`
+--
+
+DROP TABLE IF EXISTS `gtid_executed`;
+/*!40101 SET @saved_cs_client = @@character_set_client */;
+/*!40101 SET character_set_client = utf8 */;
+CREATE TABLE `gtid_executed` (
+ `source_uuid` char(36) NOT NULL COMMENT 'uuid of the source where the transaction was originally executed.',
+ `interval_start` bigint(20) NOT NULL COMMENT 'First number of interval.',
+ `interval_end` bigint(20) NOT NULL COMMENT 'Last number of interval.',
+ PRIMARY KEY (`source_uuid`,`interval_start`)
+) ENGINE=InnoDB DEFAULT CHARSET=latin1 STATS_PERSISTENT=0;
+/*!40101 SET character_set_client = @saved_cs_client */;
+
+--
+-- Dumping data for table `gtid_executed`
+--
+
+LOCK TABLES `gtid_executed` WRITE;
+/*!40000 ALTER TABLE `gtid_executed` DISABLE KEYS */;
+/*!40000 ALTER TABLE `gtid_executed` ENABLE KEYS */;
+UNLOCK TABLES;
+
+--Maybe there was an update for plesk migrator?
Has anybody an idea, which thing could cause this error?
Thanks in advance!
