[ZBX-21810] PostgreSQL Template does not use macros Created: 2022 Oct 25 Updated: 2024 Apr 10 Resolved: 2023 Oct 20 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Agent2 plugin (G) |
Affects Version/s: | 5.0.28 |
Fix Version/s: | None |
Type: | Problem report | Priority: | Major |
Reporter: | Humberto Fraga | Assignee: | Zabbix Integration Team |
Resolution: | Fixed | Votes: | 0 |
Labels: | Agent2, PostgreSQL, plugin | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Linux Centos 7 |
Team: |
Description |
Steps to reproduce:
Yes, my PostgreSQL is running on the non-default port 5433. Result: The discovery rule Database discovery fails with the following error:
Connection failed: failed to connect to `host=localhost user=postgres database=postgres`: dial error (dial tcp 127.0.0.1:5432: connect: connection refused). The same message shows up on the zabbix-agent log. Additional Info: On the zabbix-server console, I can run: zabbix_get -s XXX.XXX.XXX.XXX -k 'pgsql.db.discovery[postgresql://localhost:5433,zbx_monitor,,postgres]' This command returns the correct discovery value. The zabbix_get command bellow: zabbix_get -s 10.1.1.10 -k 'pgsql.db.discovery[]' Gives me the same error above. I have other hosts running PostgreSQL and zabbix-agent2 version 5.0.1. On those hosts, the monitoring is working fine.
|
Comments |
Comment by Aleksandre Sebiskveradze [ 2023 Oct 20 ] |
Working fine on versions 6 and up. |