Hi, i noticed following cron error after update from NC 10.0.2 to NC 11.
My cron runs every 15 minutes but every day at nearly the same time (23:45-24:00) the cron jobs fails with the following error message:
{“reqId”:“s3A90E7TFAgoiVkwYjiZ”,“remoteAddr”:“”,“app”:“PHP”,“message”:“Error while sending QUERY packet. PID=16308 at /var/www/nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php#91”,“level”:3,“time”:“2016-12-25T23:49:45+01:00”,“method”:“–”,“url”:“–”,“user”:“–”,“version”:“11.0.0.10”}
{“reqId”:“s3A90E7TFAgoiVkwYjiZ”,“remoteAddr”:“”,“app”:“cron”,“message”:“An exception occurred while executing ‘UPDATE oc_jobs SET reserved_at = ‘0’ WHERE id = ?’ with params ["7"]:\n\nSQLSTATE[HY000]: General error: 2006 MySQL server has gone away”,“level”:4,“time”:“2016-12-25T23:49:45+01:00”,“method”:“–”,“url”:“–”,“user”:“–”,“version”:“11.0.0.10”}
Any ideas or solution for this ?
Thanks in advanced, regards
Hi, @Cult Nextant isn´t active at the moment.
Before the log messages i posted there was a entry that the packet is to big , i have now increases it to 16 MB in mariadb default was 1 MB but i don’t know wether this is really necessary ? @tflidd Thats the output from oc_jobs:
The default settings of the database is very likely not the best for our purpose. Perhaps we should add a howto or something because this can improve the performance drastically.
If the changes don’t help, I would try to disable the antivirus app. It’s not that often use, known to have caused some problems and likely to use a certain amount of resources.
Thats okay if the people know that 1MB max_packet_size (MariaDB 5.x.x) are not enough, or in other words the mariadb default settings are not enough. I think in MariaDB version 10 + the default packet size is increased to 16M
Solution for Centos 7:
Edit the /etc/my.cnf and insert under the [mysqld] section max_allowed_packet=16M.
Example:
@tflidd The Antivirus App is not active at the moment because they have the old scan issue… but i don’t know why the entry in oc_jobs is still present ?
I check tomorrow wether the error is still present after cron run this night. cross fingers