Zabbix discoverer processes more than 75% busy

[alexand3r]

Hi everyone !

First of all I'd like to say that I'm totally new with Zabbix and I'm a begginer on Linux but I try to get better !

Here is my issues.

I've installed a Zabbix server yesterday, and so far it seems to work correctly except that I started to receive this alert :
Zabbix discoverer processes more than 75% busy

According to the graph of this event, processes reached 100% during almost an hour and then gets back to 0% and after few minutes 100% again.

Here is the trigger linked to this alert :
{Zabbix server:zabbix[process,"discoverer",avg,busy].avg(600)}>75

The second problem is since I've installed Zabbix I've got this alert :
Some items are not supported

With this trigger :
{Zabbix server:zabbix[items_unsupported].last(0)}>0

The graph seems to show that there are 9 items unsupported but I have no clue of which one there are, how can I know ?

What is going wrong and how can I fix it ?

Thank you all for your help and answers !

[justinc]

First of all I'd like to say that I'm totally new with Zabbix and I'm a begginer on Linux but I try to get better !

Welcome.

I've installed a Zabbix server yesterday, and so far it seems to work correctly except that I started to receive this alert :
Zabbix discoverer processes more than 75% busy

According to the graph of this event, processes reached 100% during almost an hour and then gets back to 0% and after few minutes 100% again.

Here is the trigger linked to this alert :
{Zabbix server:zabbix[process,"discoverer",avg,busy].avg(600)}>75

This is my guess: you have enabled discovery.
Look at your zabbix_server.conf file
Most likely you have this set like this:
StartDiscoverers=1
Go ahead and increase the number of pre-forked instances of discovers.

If you decided not to use the discovery feature you can always set the parameter to:
StartDiscoverers=0

The second problem is since I've installed Zabbix I've got this alert :
Some items are not supported

With this trigger :
{Zabbix server:zabbix[items_unsupported].last(0)}>0

The graph seems to show that there are 9 items unsupported but I have no clue of which one there are, how can I know ?

What is going wrong and how can I fix it ?

There could be multiple reasons why a item goes to unsupported, you will learn with time to resolve these with ease. First you will want to identify which items are are unsupported.
1. First go Configuration -> Host -> Select Items(x) for a Host.
2. Then click the filter link that is in on the blue bar if you are using the default theme.
3. Remove the Host name that is listed
4. On the status pull down select unsupported.
5. Select Filter

Okay now you have list. If you look on the far right you will have a red x. mouse over that and you should get an error message that should help you solve your problem.

[alexand3r]

Hey !

Thank you so much for you answer and help I've followed your instructions and I think I've understood quiet a lot more now !

For the "busy discoveres" I've increased this number on the conf file and so far it's working so I'll let it like this and will come back to it later if it's needed.

And for my other issue, for most of the unsupported items, it was not supported by the Zabbix agent for reasons I ignore, so I just disabled them, there're not usefull for me right now.

Thanks again and have a good day !

[GeneBean]

This is my guess: you have enabled discovery.
Look at your zabbix_server.conf file
Most likely you have this set like this:
StartDiscoverers=1
Go ahead and increase the number of pre-forked instances of discovers.

If you decided not to use the discovery feature you can always set the parameter to:
StartDiscoverers=0

Just wanted to chime in and say that this helped me out too.

[kingsolmn]

[QUOTE=justinc;n181893]
Welcome.


This is my guess: you have enabled discovery.
Look at your zabbix_server.conf file
Most likely you have this set like this:
StartDiscoverers=1
Go ahead and increase the number of pre-forked instances of discovers.

If you decided not to use the discovery feature you can always set the parameter to:
StartDiscoverers=0


Adding another instance of info helped me out too! So, I can confirm that this works on the current 5.x version. Guess I didn't look closely enough when I poked through the configs!