-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fe_sendauth: no password supplied #30
Comments
Firstly, thanks for taking a look at the existing issues before raising a new one. I agree this is not the same as #19. The easiest way forward, since you are installed on the DB server, would be to tell the template to connect using Unix sockets. You should be able to connect with the default (blank) connection string set in the template. This is what When you call Your zabbix template on the other hand, is connecting via TCP/IP ( Please advise how you go. |
:argh: You are correct! Had to have the .pgpass file for the agent to use in the default Zabbix agent user account home directory /var/run/zabbix. Permanent fit was to change the Zabbix agent home directory to |
Excellent! Thanks for providing the answer. |
i love u |
This isn't a duplicate of #19 I swear!
I have a new Zabbix server installation running an Ubuntu 14.04 Zabbix 2.4.7 installation with a PostgreSQL 9.4 as the DB on another server. The Agent is set up and running on the DB server, and successfully collecting data, as well as talking back to the Zabbix server.
Like Issue #19, I've followed the installation instructions to get libzbxpgsql installed, and it is actually loading as per the Zabbix agent logs:
Checking the Zabbix Agent for PostgreSQL info I see:
Also, running a Zabbix Agent check from the commandline as the Zabbix user also shows a result:
The item prototypes on the Template, however, are all showing the error
ZBX_NOTSUPPORTED
and the Zabbix Agent log is also showing a lot of errors:Any idea why when I can get that information directly via the Zabbix Agent, the Zabbix Template wouldn't be able to?
The text was updated successfully, but these errors were encountered: