Ad Widget

Collapse

Zabbix-Agent2 Postgresql - Service is down

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • __Sigma_Prism__
    Junior Member
    • Nov 2021
    • 2

    #1

    Zabbix-Agent2 Postgresql - Service is down

    Hi all,

    I have been adding more zabbix agents into my environment and everything has been going well but I seem to be having an issue when it comes to zabbix seeing my postgresql service as being online.

    From the main "latest data" screen I can see that the agent can talk to the postgres server and is pulling statistics from it yet I keep getting a warning on my dashboard saying "PostgreSQL: Service is down" and I cant figure out how to resolve this as when i go to the cli it is showing as up and functional.

    OS: Ubuntu 20.04
    Agent:
    Sigma@pgdb:/usr/local$ zabbix_agent2 -V
    zabbix_agent2 (Zabbix) 5.4.7
    Revision 84dc2ec5dc 28 October 2021, compilation time: Oct 28 2021 08:01:17



    ● postgresql.service - PostgreSQL RDBMS
    Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled)
    Active: active (exited) since Sun 2021-11-07 03:01:13 UTC; 3s ago
    Process: 3491 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
    Main PID: 3491 (code=exited, status=0/SUCCESS)

    Nov 07 03:01:13 pgdb.wozinga.local systemd[1]: Starting PostgreSQL RDBMS...
    Nov 07 03:01:13 pgdb.wozinga.local systemd[1]: Finished PostgreSQL RDBMS.

    I have also read that some people where having issues of pg_isready not showing up in the environment area path which caused the same issue, when I type it directly into the cli I get a positive response:

    Sigma@pgdb:/etc/postgresql/12/main$ pg_isready
    /var/run/postgresql:5432 - accepting connections


    Everything else seems to be working normally but im wondering if I am just missing something obvious (which I sure I am) and I was wondering if anyone else has been able to resolve this or could point me in the right direction?
  • __Sigma_Prism__
    Junior Member
    • Nov 2021
    • 2

    #2
    After a bit more investigation it turned out that there was a typo mistake in the macro and it was refusing connection to the db.

    Comment

    Working...