Upgraded from 1.34.16 to 1.34.19 - mysqld CPU usage

Forum for questions and support relating to the 1.34.x releases only.
Post Reply
fontiano
Posts: 27
Joined: Wed Dec 25, 2019 10:29 am

Upgraded from 1.34.16 to 1.34.19 - mysqld CPU usage

Post by fontiano » Wed Aug 12, 2020 6:54 am

This morning I updated to 1.34.19 and I noticed high CPU usage (244%) by mysqld process:

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1180 mysql 20 0 4027068 197412 11888 S 244,6 1,2 18:37.76 /usr/sbin/mysqld

/var/log/mysql/error.log
2020-08-12 8:46:02 1477 [Warning] Aborted connection 1477 to db: 'zm' user: 'zmuser' host: 'localhost' (Got an error reading communication packets)
2020-08-12 8:46:27 1460 [Warning] Aborted connection 1460 to db: 'zm' user: 'zmuser' host: 'localhost' (Got an error reading communication packets)
2020-08-12 8:46:27 1489 [Warning] Aborted connection 1489 to db: 'zm' user: 'zmuser' host: 'localhost' (Got an error reading communication packets)
2020-08-12 8:46:27 1493 [Warning] Aborted connection 1493 to db: 'zm' user: 'zmuser' host: 'localhost' (Got an error reading communication packets)
2020-08-12 8:46:27 1482 [Warning] Aborted connection 1482 to db: 'zm' user: 'zmuser' host: 'localhost' (Got an error reading communication packets)
2020-08-12 8:46:28 1498 [Warning] Aborted connection 1498 to db: 'zm' user: 'zmuser' host: 'localhost' (Got an error reading communication packets)
2020-08-12 8:46:28 1501 [Warning] Aborted connection 1501 to db: 'zm' user: 'zmuser' host: 'localhost' (Got an error reading communication packets)
2020-08-12 8:46:33 1509 [Warning] Aborted connection 1509 to db: 'zm' user: 'zmuser' host: 'localhost' (Got an error reading communication packets)
2020-08-12 8:46:33 1510 [Warning] Aborted connection 1510 to db: 'zm' user: 'zmuser' host: 'localhost' (Got an error reading communication packets)

These warnings were present even before the upgrade

The problem persists after init 6.

It seems that the system is working like before and I have not identified any further problems.
zm 1.34.22 - Debian 10

fontiano
Posts: 27
Joined: Wed Dec 25, 2019 10:29 am

Re: Upgraded from 1.34.16 to 1.34.19 - mysqld CPU usage

Post by fontiano » Wed Aug 12, 2020 7:33 am

Now the process is back to standard cpu usage.

I think it was due to the fact that a camera was not initialized properly.

When this happens usually zoneminder goes into crisis and fills the virtual memory (/dev/shm) even if at that moment there is some free giga

as in this situation
tmpfs 12G 8.7G 3.4G 73% / dev / shm
zm 1.34.22 - Debian 10

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests