Ad Widget

**moneynut** · 14-03-2014, 14:57

Bump! Can somebody please assist me. I've been getting around 100 emails every few minutes..

**moneynut** · 14-03-2014, 15:32

The expression i'm using is
{Template App Zabix Agent:agent.ping.nodata(5m)}=1

Someone needs to help us. I know many had this issue and changing timeout worked for some. My timeout is 10 in zabbix config file

**moneynut** · 15-03-2014, 20:35

Come on guys... So many certified guys and some experts without certification and yet I don't get help? I wish if there was enough online video tutorials that would make me learn enough to help others. Yes I'm active on other forums and I'm helpful to others. Take a minute and share your knowledge even if you're wrong, I just want opinions and advice or a solution.

**steveboyson** · 16-03-2014, 00:27

Try increasing the timeouts both on server and agent. It seems that the agent does not respond in the given period.
Also note that windows' perfmon counters are quite time-sensible and get executed only when the windows box thinks that this is ok (roughly said).

You could try to set the failing items to "passive" if that is possible and watch what is happening then.

Oh and pls. do not think that nobody tries to help just because we don't want to. Perhaps just nobody knows what's failing on your environment?

**kloczek** · 16-03-2014, 19:37

Originally posted by moneynut

Come on guys... So many certified guys and some experts without certification and yet I don't get help? I wish if there was enough online video tutorials that would make me learn enough to help others. Yes I'm active on other forums and I'm helpful to others. Take a minute and share your knowledge even if you're wrong, I just want opinions and advice or a solution.

Don't get me wrong but zabbix it monitoring tools and nothing more

Zabbix cannot answer on questions like "why I have active trigger A?"
You are not asking for share knowledge but for support.

Causes of what you are observing can be many and in most cases all these causes have nothing to do with zabbix.
If you see log message "cannot connect to [[10.48.12.163]:10051]" try first to confirm this diagnosing this using telnet command (telnet 10.48.12.163 10051). After this you can ask yourself "why it is not possible to establish this connectivity?".

Without these steps changing anything in zabbix setup is pointless.
Why? Again: because in this case with almost 100% certainty what you see has nothing to do with zabbix antit is network layer problem (wrong routing, wrong FW policy, doggy cable, network device/part ..)

**moneynut** · 16-03-2014, 23:10

Originally posted by kloczek

Don't get me wrong but zabbix it monitoring tools and nothing more

Zabbix cannot answer on questions like "why I have active trigger A?"
You are not asking for share knowledge but for support.

Causes of what you are observing can be many and in most cases all these causes have nothing to do with zabbix.
If you see log message "cannot connect to [[10.48.12.163]:10051]" try first to confirm this diagnosing this using telnet command (telnet 10.48.12.163 10051). After this you can ask yourself "why it is not possible to establish this connectivity?".

Without these steps changing anything in zabbix setup is pointless.
Why? Again: because in this case with almost 100% certainty what you see has nothing to do with zabbix antit is network layer problem (wrong routing, wrong FW policy, doggy cable, network device/part ..)

Well I've already tested telnet and whatnot. I see no network issues either. I wonder what caused zabbix sending false alerts.

**kloczek** · 17-03-2014, 04:00

Originally posted by moneynut

Well I've already tested telnet and whatnot. I see no network issues either. I wonder what caused zabbix sending false alerts.

Could you please show what exactly you did and what exactly was displayed by telnet command test?

**moneynut** · 17-03-2014, 13:55

Originally posted by kloczek

Could you please show what exactly you did and what exactly was displayed by telnet command test?

Telnet zabbix_server_ip 10051
Conencted to zabbix_server_ip 10051
Escape character is '^]'.

Like I said there is no connection issue. Zabbix server can connect to agent host on port 10050 as well.

**moneynut** · 18-03-2014, 07:55

Can someone at least give me the link to pre-compiled 2.2 zabbix server for Ubuntu server 12.04, x86-64??
I'm planning to upgrade from 2.0 to 2.2

**steveboyson** · 18-03-2014, 09:43

LMGTFY - Let Me Google That For You

http://lmgtfy.com/?q=zabbix+2.2+ubuntu+packages

For all those people who find it more convenient to bother you with their question rather than to Google it for themselves.

**moneynut** · 18-03-2014, 09:56

Originally posted by steveboyson

http://lmgtfy.com/?q=zabbix+2.2+ubuntu+packages

I was searching in zabbix repo directory.

Zabbix Official Repository

http://repo.zabbix.com/zabbix/2.2/debian/pool/main/z/zabbix/?C=M;O=D

But anyway I already got the link from the documentation.

**tchjts1** · 18-03-2014, 20:15

Did you also follow Steve's advice on incrementing your Timeout= value in your Zabbix server (zabbix_server.conf ) as well as on your agents ( zabbix_agentd.conf ) ?

The default value of 3 seems to cause this issue quite a bit. maybe try 10 or 15 for this value. If you modify conf values, you need to restart the Zabbix processes.

**moneynut** · 19-03-2014, 00:53

Timeout value is 10 since the very first day it was installed. I've tried it with 15 as well. Same issue.

**tchjts1** · 19-03-2014, 09:33

The next thing to look at then is how your Zabbix internal processes are allocated and being used.

Look at this post, the final paragraph and the graphs that follow. Then take a look at what your setup is doing. This will tell a lot about whether you need to tune other settings besides the Timeout= value. It is possible you simply do not have enough pollers/trappers/cache configured to handle the workload.

We’ll be back soon!

https://www.zabbix.com/forum/showthread.php?t=41219

Ad Widget

Many Servers are unreachable for more than 5 minutes

Many Servers are unreachable for more than 5 minutes

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment