Zabbix icmp pinger processes more than 75% busy

[jmvillarreal]

Buenas a todos, a ver si alguien me puede ayudar.

La versión de zabbix que tengo es la 2.0.8 y estoy monitorizando 70 hots.

Tengo la siguiente alarma:

Zabbix icmp pinger processes more than 75% busy.

El trigger que uso es el que viene por defecto, la expresión es:

{Zabbix server:zabbix[process,icmp pinger,avg,busy].min(600)}>75

He modificado en zabbix_server.conf la opción de StartPingers, pero sigo con el problema.

### Option: StartPingers
# Number of pre-forked instances of ICMP pingers.
#
# Mandatory: no
# Range: 0-1000
# Default:
# StartPingers=1
StartPingers=5

Alguien tiene alguna idea de donde puede estar el problema?

Gracias y saludos.

[elemarmb]

Reiniciou o server ?

[jmvillarreal]

Si, reinicié zabbix server.

[elemarmb]

Veja em dados recentes do Zabbix Server o item Zabbix busy icmp pinger processes.

O grafico lhe dirá se sua alteração para StartPingers=5 foi suficiente ou precisa aumentar um pouco mais.

[jmvillarreal]

He aumentado a 100 los StartsPingers y despues de 12 horas, no ha habido cambio.
Sabéis alguna forma de comprobar cuantos StartsPingers está utilizando?

[jvalenzani]

Los datos vienen de un Proxy o directo al server? Puede que tengas demasiados items de ping y que la cantidad de procesos no sea suficiente. Como dicen por ahí, fijate la gráfica del item a ver com varió con el cambio y en todo caso incrementalo.

[jmvillarreal]

Los datos van directos al server. Tengo no llega a 60 hots con ítem de ping, y he cambiado el StartPinger de 1 a 5 y después a 100 que es como lo tengo ahora mismo, y en el último día la gráfica no ha variado, se mantiene igual que cuando tenía el StartPinger a 1.

[elemarmb]

No console do servidor zabbix execute :

ps ax | grep pinger

[elemarmb]

Cem pinger é muito. Cinco deveria bastar, com folga, para sessenta hosts monitorados.

[elemarmb]

Se ao alterar a quantidade de pingers e o gráfico não mudou, entãoi sugiro rever o processo de reiniciar o serviço zabbix.

[elemarmb]

Verifique se o fping está instalado. Por favor, execute no terminal fping.

[jvalenzani]

Fijate que realmente estén spawneados los procesos. Con esa cantidad debería ser más que suficiente para corregir el problema.
Lo otro que se me ocurre es bajarle el timeout, pero si lo tenés por defecto no debería ser un problema.
Fijate tener el fping instalado y en todo caso ver si en el server.log está tirando algun mensaje.

[jmvillarreal]

Este es el resultado de ps ax | grep pinger

root@monitoring:/# ps ax | grep pinger
4488 ? S 0:00 sh -c /usr/bin/fping -q -C3 2>&1 </tmp/zabbix_server_24650.pinger;/usr/bin/fping6 -q -C3 2>&1 </tmp/zabbix_server_24650.pinger;
4491 pts/0 S+ 0:00 grep pinger

La verdad es que no se interpretar el resultado.

El fping si que está instalado y funciona ya que los items con ping funcionan.

[elemarmb]

Sim o fping esta instalado e sendo executado. Observe o resultado do ps. Lá mostra o fping.

Eu uso o zabbix 2.2.1 e nele os processos possuem no nome as tarefas que executam para o zabbix. Por exemplo :

ps ax | grep zabbix_server
24328 ? S 0:00 /usr/local/sbin/zabbix_server
24346 ? S 9:32 /usr/local/sbin/zabbix_server: configuration syncer [synced configuration in 0.343230 sec, idle 900 sec]
24347 ? S 4:43 /usr/local/sbin/zabbix_server: db watchdog [pinging database]
24348 ? S 19:52 /usr/local/sbin/zabbix_server: poller #1 [got 3 values in 0.003987 sec, idle 1 sec]
24349 ? S 18:54 /usr/local/sbin/zabbix_server: poller #2 [got 2 values in 0.004637 sec, idle 1 sec]
24350 ? S 19:02 /usr/local/sbin/zabbix_server: poller #3 [got 1 values in 0.001759 sec, idle 1 sec]
24351 ? S 19:43 /usr/local/sbin/zabbix_server: poller #4 [got 1 values in 0.002672 sec, idle 1 sec]
24352 ? S 19:34 /usr/local/sbin/zabbix_server: poller #5 [got 1 values in 0.001496 sec, idle 1 sec]
24353 ? S 0:34 /usr/local/sbin/zabbix_server: unreachable poller #1 [got 0 values in 0.000003 sec, idle 5 sec]
24354 ? S 0:34 /usr/local/sbin/zabbix_server: unreachable poller #2 [got 0 values in 0.000006 sec, idle 5 sec]
24355 ? S 25:28 /usr/local/sbin/zabbix_server: trapper #1 [processed data in 0.002064 sec, waiting for connection]
24356 ? S 26:03 /usr/local/sbin/zabbix_server: trapper #2 [processed data in 0.015379 sec, waiting for connection]
24357 ? S 25:18 /usr/local/sbin/zabbix_server: trapper #3 [processed data in 0.010698 sec, waiting for connection]
24358 ? S 25:36 /usr/local/sbin/zabbix_server: trapper #4 [processed data in 0.008060 sec, waiting for connection]
24359 ? S 25:28 /usr/local/sbin/zabbix_server: trapper #5 [processed data in 0.000531 sec, waiting for connection]
24360 ? S 1:45 /usr/local/sbin/zabbix_server: icmp pinger #1 [got 1 values in 2.006543 sec, idle 5 sec]
24361 ? S 1:44 /usr/local/sbin/zabbix_server: icmp pinger #2 [got 0 values in 0.000040 sec, idle 5 sec]
24362 ? S 1:45 /usr/local/sbin/zabbix_server: icmp pinger #3 [got 1 values in 2.007082 sec, idle 5 sec]
24363 ? S 1:45 /usr/local/sbin/zabbix_server: icmp pinger #4 [got 1 values in 2.007118 sec, idle 5 sec]
24364 ? S 0:37 /usr/local/sbin/zabbix_server: alerter [sent alerts: 0 success, 0 fail in 0.001657 sec, idle 30 sec]
24365 ? S 23:51 /usr/local/sbin/zabbix_server: housekeeper [deleted 323199 hist/trends, 0 items, 0 events, 0 sessions, 0 alarms, 0 audit items in 297.411764 sec, idle 1 hour(s)]
24366 ? S 1:28 /usr/local/sbin/zabbix_server: timer #1 [processed 1 triggers, 0 events in 0.003536 sec, 0 maint.periods in 0.004639 sec, idle 30 sec]
24367 ? S 3:43 /usr/local/sbin/zabbix_server: http poller #1 [got 0 values in 0.002225 sec, idle 5 sec]
24368 ? S 3:46 /usr/local/sbin/zabbix_server: http poller #2 [got 0 values in 0.002006 sec, idle 5 sec]
24369 ? S 0:22 /usr/local/sbin/zabbix_server: discoverer #1 [processed 0 rules in 0.001499 sec, idle 60 sec]
24370 ? S 20:47 /usr/local/sbin/zabbix_server: history syncer #1 [synced 0 items in 0.000001 sec, idle 5 sec]
24371 ? S 20:41 /usr/local/sbin/zabbix_server: history syncer #2 [synced 0 items in 0.000001 sec, idle 5 sec]
24372 ? S 20:43 /usr/local/sbin/zabbix_server: history syncer #3 [synced 0 items in 0.000002 sec, idle 5 sec]
24373 ? S 20:44 /usr/local/sbin/zabbix_server: history syncer #4 [synced 461 items in 0.075350 sec, idle 5 sec]
24374 ? S 20:54 /usr/local/sbin/zabbix_server: history syncer #5 [synced 0 items in 0.000001 sec, idle 5 sec]
24375 ? S 20:57 /usr/local/sbin/zabbix_server: history syncer #6 [synced 1 items in 0.011014 sec, idle 5 sec]
24376 ? S 7:01 /usr/local/sbin/zabbix_server: escalator [processed 0 escalations in 0.001399 sec, idle 3 sec]
24377 ? S 0:38 /usr/local/sbin/zabbix_server: proxy poller #1 [exchanged data with 0 proxies in 0.000004 sec, idle 5 sec]
24378 ? S 3:27 /usr/local/sbin/zabbix_server: self-monitoring [processed data in 0.000005 sec, idle 1 sec]

Pelo visto o zabbix 2.0 não tem isto implementado.

Vocẽ pode verificar no log do zabbix e ver quantos pinger são disparados.

Experimente isto :

Em um terminal no servidor zabbix faça :

Edite o arquivo de configuração do zabbix e diminua a quantidade de pingers para dez.

Neste arquivo de configuração identifique o nome completo do arquivo de log. Por exemplo /var/log/zabbix_server.log.

Execute tail -f no arquivo de log, por exemplo :

tail -f /var/log/zabbix_server.log

Abra outro terminal no servidor e nele reinicie o servidor zabbix.

No terminal em que mostra o log você verá mensagens mostrando que reiniciou o sertvidor zabbix e a quantidade de pingers deverá ser mostrada.

Para sair do tail pressione Ctrl-C.

[jmvillarreal]

Despues de tail -f /var/log/zabbix_server.log y reiniciar, solo aparece un pinger

1309:20140702:155113.230 Got signal [signal:15(SIGTERM),sender_pid:3058,sender_uid:0,re ason:0]. Exiting ...
1309:20140702:155115.231 syncing history data...
1309:20140702:155115.244 syncing history data done
1309:20140702:155115.244 syncing trends data...
1309:20140702:155115.653 syncing trends data done
1309:20140702:155115.653 Zabbix Server stopped. Zabbix 2.0.8 (revision 38017).
3082:20140702:155115.677 Starting Zabbix Server. Zabbix 2.0.8 (revision 38017).
3082:20140702:155115.677 ****** Enabled features ******
3082:20140702:155115.677 SNMP monitoring: YES
3082:20140702:155115.677 IPMI monitoring: YES
3082:20140702:155115.677 WEB monitoring: YES
3082:20140702:155115.677 Jabber notifications: YES
3082:20140702:155115.677 Ez Texting notifications: YES
3082:20140702:155115.677 ODBC: YES
3082:20140702:155115.677 SSH2 support: YES
3082:20140702:155115.677 IPv6 support: YES
3082:20140702:155115.677 ******************************
3096:20140702:155115.825 server #1 started [configuration syncer #1]
3097:20140702:155115.825 server #2 started [db watchdog #1]
3098:20140702:155115.826 server #3 started [poller #1]
3099:20140702:155115.826 server #4 started [poller #2]
3100:20140702:155115.827 server #5 started [poller #3]
3106:20140702:155115.827 server #11 started [trapper #3]
3110:20140702:155115.828 server #15 started [alerter #1]
3101:20140702:155115.828 server #6 started [poller #4]
3112:20140702:155115.828 server #17 started [timer #1]
3104:20140702:155115.828 server #9 started [trapper #1]
3115:20140702:155115.829 server #20 started [history syncer #1]
3117:20140702:155115.829 server #22 started [history syncer #3]
3102:20140702:155115.829 server #7 started [poller #5]
3111:20140702:155115.829 server #16 started [housekeeper #1]
3111:20140702:155115.829 executing housekeeper
3105:20140702:155115.829 server #10 started [trapper #2]
3119:20140702:155115.830 server #24 started [escalator #1]
3082:20140702:155115.830 server #0 started [main process]
3103:20140702:155115.830 server #8 started [unreachable poller #1]
3120:20140702:155115.830 server #25 started [proxy poller #1]
3107:20140702:155115.830 server #12 started [trapper #4]
3108:20140702:155115.831 server #13 started [trapper #5]
3121:20140702:155115.831 server #26 started [self-monitoring #1]
3109:20140702:155115.831 server #14 started [icmp pinger #1]
3113:20140702:155115.831 server #18 started [http poller #1]
3114:20140702:155115.831 server #19 started [discoverer #1]
3116:20140702:155115.831 server #21 started [history syncer #2]
3118:20140702:155115.832 server #23 started [history syncer #4]