Ad Widget

**richlv** · 31-10-2011, 20:20

that's because you haven't patched your database. there are no official incremental patches, though - but unofficial ones for mysql can be found at http://www.zabbix.org/svn/zabbixorg/...emental/README

**frater** · 31-10-2011, 20:40

I patched the database and now

ftp changed into net.tcp.service["ftp"]

Before this patch I tried to do this by hand (http://www.zabbix.com/documentation/..._simple_checks)

I wasn't able to do this because it conflicted with the Zabbix agent check net.tcp.service[ftp]

I didn't use quotes around ftp, BTW

Shouldn't a check from type "Agent" never conflict with a check "Simple" ?

**richlv** · 31-10-2011, 21:14

Originally posted by frater

Shouldn't a check from type "Agent" never conflict with a check "Simple" ?

well, this was discussed... in general, the item key must be unique, so having different types won't help you. there doesn't seem to be an easy way around this either

**frater** · 31-10-2011, 22:22

Originally posted by richlv

well, this was discussed... in general, the item key must be unique, so having different types won't help you. there doesn't seem to be an easy way around this either

An easy way would be naming them differently.
There's no need to name these 2 functions the same.
One is done on the server and the other one on the client.

I created a function "agent.ping" and didn't name it this way to avoid this conflict, I did it because it would always be clear the agent is doing the ping.

**richlv** · 02-11-2011, 20:01

Originally posted by frater

An easy way would be naming them differently.
There's no need to name these 2 functions the same.
One is done on the server and the other one on the client.

well... there isn't really such notation being used in zabbix item keys. and naming them differently might be argued against that same check shouldn't use different keys just based on where it is executed... currently one may change item type and thus easily move the check on the other daemon

**frater** · 03-11-2011, 00:47

Originally posted by richlv

well... there isn't really such notation being used in zabbix item keys.

That's what I ment...
I deliberately didn't name it icmp.ping

and naming them differently might be argued against that same check shouldn't use different keys just based on where it is executed... currently one may change item type and thus easily move the check on the other daemon

From a troubleshooting perspective, running net.tcp.service[http] on the server itself is something completely different than running it from the monitoring server...

But the real issue here is that it's important to be able to do both, isn't it?

If I can reach the http server from the server itself, but I can't reach it from a remote location this is valuable info...
Combine that with being able to ping or not and it's almost certain a firewall issue.

Maybe it's a bit hard to implement into the code how it is now (and all but respect for your work), but that shouldn't be the reason not to do it.
I'm now able to have both these tests on the same machine because the database was directly patched and didn't go through the error checking module.

Ad Widget

A lot of 1.9.7 simple checks became unsupported....

A lot of 1.9.7 simple checks became unsupported....

Comment

Comment

Comment

Comment

Comment

Comment