PDA

View Full Version : Those annoying ZBX_NOTSUPPORTED


James Wells
15-06-2005, 01:26
Greetings,

I was recently asked to get some real monitoring in place for my Lab systems and decided to go with Zabbix. I had played with Zabbix at home and found the power to be more than sufficient for my needs. I set up a small Gentoo server to act as the DB and Zabbix server, and set about trying to get the agents installed.

First issue I ran into was the lack of a RedHat RPM for the Zabbix agents, I ended up getting around this by compiling it on my Gentoo workstation, and I suspect this may be what's causing me problems.

The agents are all running 1.1Alpha10 agents, and are all recieving requests from the server correctly, however, due to the way the firewalling works, the agents are unable to load process_active_checks. Not worried about that just yet, though it too may be a source of my issues.

The issues that I am having are ZBX_NOTSUPPORTED messages for certain basic / key information I need to monitor, specifically;
1. disk_*_ops* --- I have double / tripple checked the configs for these and as far as I can tell they are correct. All of my machines are using generic SCSI interfaces so my configs are disk_*_ops*[sda]. Obviously the * have the correct values such as read and 15.
2. netload* --- These are actually the defaults that come in the host.unix template. All of my machines use ETH0 + Loopback only and I have removed the references to netload*[eth1]

Any help to resolve these issues would be greatly appreciated.

PS. The servers I am trying to monitor are stripped down RedHat ES2.1 servers running an old 2.4 kernel whereas the agents were compiled on a fairly up-to-date Gentoo (Unstable Branch) workstation running 2.6 kernel.

welshpjw
15-06-2005, 15:39
Wow, lots of places to go wrong... Linux distro issues, firewall issues (like you note) etc...

Did you start with a template that already had the services noted as notsupported? I have previously found that the not supported note lies. I thought it was because of the original template I had used. I edited ("Change") the setting to "Monitored" and it works. Give that a try and report to us, please.

As a side note, if you want to more directly support your RHES2.1 better, I would generaly suggest having a "devel" box for it. Of course RHES is not free to do that with, but CentOS is free http://centos.org They have a goal to have a binary compatable $RH free version. They do a VERY GOOD job! I have used centos to skirt issues with some software having "$RH compatable ONLY" issues.

James Wells
15-06-2005, 18:28
Okay, I broke down and recompiled the agent on a RHEL 2.1 system, pushed the agent over and still get the same thing, so now I know it was not caused by my compiling it on Gentoo.

Additionally, I ran the queries manually, to see if maybe there was a comminication issue caused by the firewall, from one of the machines I was trying to monitor, I telneted to the local ethernet on the Zabbix port and issued the netloadin15[eth0] command and recieved the ZBX_NOTSUPPORTED response.

welshpjw
15-06-2005, 19:45
Bummer :confused:

I was hoping for the easy answer... sorry.

James Wells
15-06-2005, 20:00
Did some more diagnostics on this and found that the agent really is testing these items as evidenced by this snippet from the zabbix_agentd.tmp file;
netloadout1[lo] 21.333333
netloadout5[lo] 38.530612
netloadout15[lo] 38.530612
netloadin1[lo] 21.333333
netloadin5[lo] 38.530612
netloadin15[lo] 38.530612
netloadout1[eth0] 5090.133333
netloadout5[eth0] 3301.877551
netloadout15[eth0] 3301.877551
netloadin1[eth0] 840.533333
netloadin5[eth0] 809.795918
netloadin15[eth0] 809.795918
disk_read_ops1[sda] 0.000000
disk_read_ops5[sda] 0.000000
disk_read_ops15[sda] 0.000000
disk_read_blks1[sda] 0.000000
disk_read_blks5[sda] 0.000000
disk_read_blks15[sda] 0.000000
disk_write_ops1[sda] 10.733333
disk_write_ops5[sda] 11.459184
disk_write_ops15[sda] 11.459184
disk_write_blks1[sda] 261.333333
disk_write_blks5[sda] 299.510204
disk_write_blks15[sda] 299.510204

So I am really confused by the fact that the agent continues to return ZBX_NOTSUPPORTED. Any other ideas on how to go about resolving this issue please?

welshpjw
15-06-2005, 20:05
Did you make the web gui changes noted before?

James Wells
15-06-2005, 20:12
Yup, sure did. Additionally, by querying the agentd directly, I "force" it grab the information.