After upgrade from 1.8 to 2.0.4, several checks 'Not supported by Zabbix Agent'

[_brian]

[UPDATED - FIXED] Please see THIS POST for the fix. Basically, change the type to Zabbix Internal.


Hey all,

I'm seeing a problem after upgrading to 2.0.4 with some of my checks. Basically, many of the checks are throwing errors in the items table that read 'Not supported by Zabbix Agent'. The agents are still on 1.8. I used the upgrade script on our existing database and I did read the following note, but am unsure what to do or if there's an easy way to correct this:

A status item has been removed. Instead of it a new internal item - zabbix[host,agent,available] has been added. The database upgrade process doesn't convert all existing 'status' keys and associated triggers to the new syntax, so they have to be converted manually.

I've been working on this most of the day and have finally run out of ideas. Has anyone else encountered this and if so, how did you work around it?

[tchjts1]

Hi Brian. Are the items that are throwing "not supported", active agent items?

Zabbix 2.x has some new fields in the zabbix_agentd.conf file on the hosts. Try this on one of your hosts and see if it fixes the issue... add into the zabbix_agentd.conf file a new line: ServerActive= and define your Zabbix server on there, either IP or DNS. Then restart your agent.

Ideally, you would replace the old conf file with the complete new one on your monitored hosts.

[_brian]

Hello,

Unfortunately that doesn't seem to work. The agents are still on 1.8, but will be upgraded very soon. Here's an example of a check that isn't working (some.hostname replaced with an actual hostname in our config) ::

Name : Template_Linux: Server {HOSTNAME} is unreachable
Expression: {*some.hostname*:status.last(0)}=2

In the far right, a large red X indicating that it's not supported by the Zabbix Agent. This worked fine prior to the upgrade.

[_brian]

So I searched the forums and found no less than 40 different posts explaining the same issue, but none of them had an answer. In order to help anyone who stumbles across this via Google, Here's what I had to do to fix it.

If anyone has a better suggestion, I'm all ears

1. From within Zabbix, you will want to modify the existing Host Status item.
2. Locate the proper template (in this case, Linux_Template) by clicking on Configuration -> Templates
3. Click on Linux_Template.
4. Click on Items.
5. Click on Host Status.
6. Change Type from agent to Zabbix internal
7. Change Key to zabbix[host,agent,unavailable]
8. Click on show value mappings on the 'Show Value' line
9. Click on Create value map (make sure the dropdown shows Value mapping).
10. Choose a name for the new Host Status. I chose Host Status 2.0 so as not to interfere with the existing host status tables.
11. In the fields, populate it as follows ::
    
    • Name - Host Status 2.0
    • 0 - Unreachable
    • 1 - Up
    
    
12. Click Save
13. Go back to the Host Status modification page
14. In Show Value, change that to the new Host Status 2.0 value
15. Click Save
16. Click on Triggers
17. Locate Server {HOSTNAME} is Unreachable and click on the 3rd Field, which should be {Template_Linux:status.last(0)=2}
18. Modify the string to reflect the following :: {Template_Linux:zabbix[host,agent,available].last(0)}#1
19. Click Save

I hope this helps someone else who is running into issues!

[jdlyle]

Hey brian!

Thanks for posting that information. I am having the same issue, and I have also noticed that many people seem to be having an issue with the status key becoming not supported.

I followed the steps you provided, and I am still having the same issue even after changing the key.

The Zabbix Server log shows the following in relation to the issue:

27878:20130115:101342.281 item [*HOST NAME*:zabbix[host,agent,unavailable]] became not supported: Internal check is not supported

Is there anything else you can suggest? Monitoring the status of my servers is vital, and I in desperate need of a solution.

-----EDIT-----

Instead of manually entering the key, I selected the "zabbix[host,<type>, available]" (NOTE: it should be available and not unavailable) key from within the Zabbix Internal list. Then I changed "<type>" to "agent".

it works fine now.

[_brian]

Can you verify that your setup looks EXACTLY like this?



Note the Type line - set that to Zabbix Internal. That was previously set to Zabbix agent. That's what worked for me.

[jdlyle]

Thanks for the quick reply. I added an edit explaining what I did to get it working.

Thanks once more for pointing me in the right direction!

[ralopez58]

What specifically did you do to solve that problem? i have de same problem and i get in the log 1721:20130325:213109.565 item [orcvcv:zabbix[host,agent,unavailable]] became not supported: Internal check is not supported

[heaje]

Its in the post a couple before this one, but change "unavailable" to "available".

[ralopez58]

thank you indicated what I did and it worked

[ralopez58]

hello again

I got the same problem now with the windows agents What I can do?

[jdlyle]

Sorry buddy, I'm not sure about a Windows monitoring. I don't even have a Windows Server with which I could test it out.