Page 1 of 1

Consistent Aborted Connections

Posted: Tue Jan 18, 2022 11:06 pm
by Pedulla
What happens at 00:00, 08:00 and/or 16:00 that causes 4 Aborted connections to the zm database by zmuser?

Code: Select all

2022-01-17 16:05:35 13777 [Warning] Aborted connection 13777 to db: 'zm' user: 'zmuser' host: '10.X.X.X' (Got timeout reading communication packets)
2022-01-17 16:05:35 13785 [Warning] Aborted connection 13785 to db: 'zm' user: 'zmuser' host: '10.x.x.x' (Got timeout reading communication packets)
2022-01-17 16:05:36 13835 [Warning] Aborted connection 13835 to db: 'zm' user: 'zmuser' host: '10.x.x.x' (Got timeout reading communication packets)
2022-01-17 16:05:36 13833 [Warning] Aborted connection 13833 to db: 'zm' user: 'zmuser' host: '10.x.x.x' (Got timeout reading communication packets)

Code: Select all

2022-01-17  8:00:04 434866 [Warning] Aborted connection 434866 to db: 'zm' user: 'zmuser' host: 'localhost' (Got timeout reading communication packets)
2022-01-17  8:00:04 434865 [Warning] Aborted connection 434865 to db: 'zm' user: 'zmuser' host: 'localhost' (Got timeout reading communication packets)
2022-01-17  8:00:04 434875 [Warning] Aborted connection 434875 to db: 'zm' user: 'zmuser' host: 'localhost' (Got timeout reading communication packets)
2022-01-17  8:00:15 434886 [Warning] Aborted connection 434886 to db: 'zm' user: 'zmuser' host: 'localhost' (Got timeout reading communication packets)
UB20.04, LEMP, zm 1.36.12
Logs from two different servers, but consistent.

Re: Consistent Aborted Connections

Posted: Fri Apr 01, 2022 8:26 pm
by albazeus
Same problem here. My logs are flooded with this error

Code: Select all

2022-04-01 22:24:15 4572 [Warning] Aborted connection 4572 to db: 'zm' user: 'zmuser' host: 'localhost' (Got an error reading communication packets)

Re: Consistent Aborted Connections

Posted: Sat Apr 02, 2022 9:54 pm
by iconnor
Typically that would be caused by a crash. Crashes will be logged. Look in your logs.

Re: Consistent Aborted Connections

Posted: Mon Apr 04, 2022 7:25 pm
by albazeus
Thanks, the problem was a camera that was not connected. Because of this, I got several errors in zm log and then the errors in system log that I reported. I deleted the camera and now I get no more log errors. I thought that disabling the camera was sufficient not to have log errors: it was not.
Is there a way to keep the configuration of a camera that's not connected without deleting it AND without getting errors in the log? Thanks.