Hi,

My postgresql sensonsor causes a log spam in my postgresql instance which is located in a kubernetes cluster. I am using the standard query: SQL Query File "Demo Serveruptime.sql" which already came with prtg. PRTG Version: 21.2

Best regards George

Article Comments

Hello George,

Does the sensor work? Or does he just show the error that you mentioned?

Kind regards,
Sasa Ignjatovic, Tech Support Team


Dec, 2021 - Permalink

The Sensor itself is working. But postgres itself is producing log spam. My guess is the Senser doesn`t disconnect properly from postgres.


Jan, 2022 - Permalink

Hello George,

Could you let us know what error message you get in postgres?

Kind regards,
Sasa Ignjatovic, Tech Support Team


Jan, 2022 - Permalink

Every time the Sensor scans this message appears:

2022-01-14 11:17:36.008 GMT [508121] LOG:  could not receive data from client: Connection reset by peer
2022-01-14 11:17:40.913 GMT [508137] LOG:  could not receive data from client: Connection reset by peer
2022-01-14 11:18:36.023 GMT [508220] LOG:  could not receive data from client: Connection reset by peer
2022-01-14 11:18:40.889 GMT [508237] LOG:  could not receive data from client: Connection reset by peer
2022-01-14 11:19:36.003 GMT [508322] LOG:  could not receive data from client: Connection reset by peer
2022-01-14 11:19:40.860 GMT [508339] LOG:  could not receive data from client: Connection reset by peer
2022-01-14 11:20:36.007 GMT [508426] LOG:  could not receive data from client: Connection reset by peer
2022-01-14 11:20:40.871 GMT [508442] LOG:  could not receive data from client: Connection reset by peer

Jan, 2022 - Permalink

Hello George,

I would suggest that you open a support ticket for this. This way you could also provide us with some screenshots and log files from the sensor.

Kind regards,
Sasa Ignjatovic, Tech Support Team


Jan, 2022 - Permalink