vfs.fs.discovery not support by the agent?

[coco]

Hi everyone,

I installed zabbix-1.9.5 on one VM (CentOS 5.4) to test to filesystem auto-detection.

I have followed this guide http://www.zabbix.com/documentation/...evel_discovery but I'm having an annoying problem.

It seems like the key vfs.fs.discovery is not supported by the agent agent.

I tried to search in the agent log but found nothing.

The only thing I found was in the zabbix-server log :

921:20110809:155956.396 Item [myhostname:vfs.fs.discovery] became not supported: Not supported by Zabbix Agent

As anyone ever encountered something like this?

Thank you.

[richlv]

seems to work just fine here. is the running agent indeed of version 1.9.5 ?

what do you get for this ?

zabbix_get -s 127.0.0.1 -k vfs.fs.discovery

[coco]

Erf seems like I don't have zabbix_get installed.

To install zabbix-1.9.5., I followed the steps here : http://www.zabbix.com/documentation/...lation/install

when compiling it, I ran the command : ./configure --enable-server --with-mysql --enable-ipv6

and then make, make install.

I skiped step 7.

I also skiped the part about the proxy and everything after this until the part about the frontend.

I guess I missed something big?

[richlv]

yes. well. possibly. you said "I tried to search in the agent log but found nothing.", but "when compiling it, I ran the command : ./configure --enable-server --with-mysql --enable-ipv6" doesn't even include agent

one guess might be that you are checking a remote agent - but if so, what is the version of that agent ? note that discovery of network devices and mounted filesystems is an agent feature.

[zalex_ua]

I guess I missed something big?

It seems zabbix_agent missing at all .

Add --enable-agent to your configure command and then configure and make install again.

I'm 100% sure - vfs.fs.discovery works in the CentOS5.5

[coco]

I'm not sure on how to verify the agent version, but I guess I could reinstall it and this time include --enable-agent in the command?

What bugs me a bit is that the VM is being monitored, so I must assume there is an agent on it. Maybe it is an agent from the 1.8.2 that was already installed on the VM...

Anyways, I'll try to do another fresh install in about 2-3hours and come back to you with feedback.


Zalex, I'll compile it again right now and if it's still not working I'll try a fresh install to make sure if vfs.fs.discovery works with CentOS.

[richlv]

if that vm had older zabbix version, you should remove that, otherwise it will lead to confusing situations (like this one )

[coco]

It was not supposed to have any older version hehe, it was just a supposition since we use Chef for our kickstarts so something about zabbix might have been left

[zalex_ua]

Maybe it is an agent from the 1.8.2 that was already installed on the VM...

Yes, it's root of problem. Do what i said early, all should become fine.

[coco]

So I did a fresh install but since we use chef, zabbix-agentd 1.8.5 was already installed. I deleted it with (yum remove zabbix*) but still I'm having problems to get the agent to work.

After doing ./configure --enable-server --with-mysql --enable-agent everything seemed fine telling me the agent was enabled.

Then I ''make, make install'' but still the agentd doesn't seem to be installed. If I try "service zabbix-agentd status" I got : zabbix-agentd: unrecognized service (tried it too with zabbix_agentd).

I also launched it from /usr/local/sbin but still, not working.

When I go read the logs, I see this : "4257:20110811:102804.445 No active checks on server: host [myhost] not monitored" many times.

(sorry for my terrible english, I'm tired this morning hehe)

Edit : zabbix-agentd is nowhere to be found under /etc/init.d

[zalex_ua]

I suppose that init script /etc/init.d/zabbix_agentd was removed when you deleted zabbix 1.8.5 (yum remove zabbix*)

Maybe in this case you removed init script for zabbix_server too? Be careful with the *

In CentOS script usually named as zabbix_agentd.

The error "4257:20110811:102804.445 No active checks on server: host [myhost] not monitored" is quite an another story

[coco]

I ran the command yum remove zabbix* before downloading zabbix-1.9.5. I had it my that by doing so, it would be like installing zabbix on a fresh CentOS install. Is that wrong?

As for the error, since there is some entry going in the log, does this mean the agent is "running" or maybe exists on the vm?

[zalex_ua]

I ran the command yum remove zabbix* before downloading zabbix-1.9.5. I had it my that by doing so, it would be like installing zabbix on a fresh CentOS install. Is that wrong?

It seems you have deleted init scripts (i'm not sure)
Take into account - make install do not installs init scripts automatically. You need to install they manually and to configure properly or use proper RPM for CentOS.

As for the error, since there is some entry going in the log, does this mean the agent is "running" or maybe exists on the vm?

Seems agent works, but how it will start after machine reboot? You need init scripts in any case.

[coco]

Alright, I'll re-kickstart the machine and online run yum remove zabbix-agent, that way maybe the scripts won't be all lost. I'll come back as soon as the machine in up and write down what I can find about the current zabbix installation.

Thx for helping a newb such as me