-
Notifications
You must be signed in to change notification settings - Fork 12
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
Zabbix server not accepting the data from Zabbix sender: info from server: "processed: 0; failed: 28; total: 28; seconds spent: 0.000392" #9
Comments
the problem could be the wrong host name or the template is not attached the the host |
I've checked both the host name and the item names. They are both correct. The strange thing is, I had this template working fine on my old Zabbix install (4.0.23). |
I'm using Zabbix-5.0.2 and everything is working fine, I exported my template, try this one |
I've tried the attached template, but I still get the same error. I doubt it's something with the template or the command line as they were both the same as on my old installation. I feel like I need to change something in a Zabbix configuration file (e.g. /etc/zabbix/zabbix_server.conf ) to make the trapper/sender work. |
I don't think so, but for reference, here are my configuration Server and agent in the same machine. zabbix_server.conf
zabbix_agentd.conf
|
I'm executing the script manually with the following commandline arguments:
./zbxApacheStatusCheck --host=99.99.99.99 --zabbixsource="the host name" --zabbixserver=127.0.0.1 -d
Where 99.99.99.99 is the IP of the webserver, and "the host name" is the host name of the machine in Zabbix.
Every time I run the script I get the following error:
This is the commandline for the sender:
/usr/bin/zabbix_sender -v --zabbix-server 127.0.0.1 --host 'the host name' --port 10051 --input-file /tmp/tmp.PmTQvSti2f
I can see that the metrics which are to be send are Correct. Any idea why the Zabbix server is not accepting this data?
The text was updated successfully, but these errors were encountered: