[ZBX-18319] PostgreSQL monitoring using zabbix-agent2 5.0.2 and 5.0.3 is broken Created: 2020 Aug 28 Updated: 2020 Nov 17 Resolved: 2020 Nov 17 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Agent2 plugin (G) |
Affects Version/s: | 5.0.2, 5.0.3 |
Fix Version/s: | None |
Type: | Incident report | Priority: | Trivial |
Reporter: | Humberto Fraga | Assignee: | Zabbix Development Team |
Resolution: | Duplicate | Votes: | 1 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Centos 7.8.2003 |
Attachments: |
![]() |
||||||||
Issue Links: |
|
Description |
zabbix-agent2 monitoring does not fully work after upgrading to version 5.0.2 and 5.0.3 . Some of the items in the status are not supported with an error - the only supported schemes are: tcp and unix. The discovery item "pgsql.db.discovery" is marked as "not supported" with the above error. After downgrading to zabbix-agent2-5.0.1, and modifying the configuration file, the discovery item and dependent items are supported again. |
Comments |
Comment by Andrei Gushchin (Inactive) [ 2020 Sep 01 ] |
Hello Humberto, Can you attach the zabbix_agent2.log here? and screenshot with error for unsupported items? |
Comment by Humberto Fraga [ 2020 Sep 02 ] |
Hi, I'm pasting bellow the relevant log messages (loglevel debug): 2020/09/02 08:30:35.934819 received passive check request: 'pgsql.db.discovery' from '<REDACTED>' And the screenshot of the discovery item: |
Comment by Humberto Fraga [ 2020 Sep 28 ] |
Hi, any updates on this? |
Comment by Humberto Fraga [ 2020 Oct 08 ] |
zabbix-agent2 version 5.0.4 is still broken. |
Comment by Alexander Vladishev [ 2020 Nov 17 ] |
Closed as duplicate of |