Ad Widget
Collapse
Active agents stopped reporting after upgrading to 1.6
Collapse
X
-
We have server 1.6 (fresh install) and an 1.6 agent (both on Solaris 9 SPARC)
running fine, even with active checks.
But we suffer from the agent crash under Windows as well.
Time to replace Windows and Linux by Solaris
Yesterday we even were successful in connecting a Linux (intel) Proxy
to this 1.6 server and it seems to work fine, i.e. active checks from the agent monitored by the Proxy, SNMP checks, Ping checks all done by the Proxy.
Proxy is running on Ubuntu using SQLite3.
Regards
Norbert.Comment
-
I have active checks running between agentd and master server.
Will test active checks between proxy and agentd later.
I had to use the hostname instead of ip-address for
Hostname=
in agentd.conf.
Is this correct behaviour? For proxy config setting IPAddress suffices.Comment
-
Some extra info to see if it helps...
# ldd zabbix_server
libcurl.so.3 => /usr/lib64/libcurl.so.3 (0x0000003ca0000000)
libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x0000003ca5000000)
libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x0000003ca3800000)
libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x0000003ca5800000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x0000003ca3000000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x0000003ca2c00000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003c9e000000)
libidn.so.11 => /usr/lib64/libidn.so.11 (0x0000003c9f000000)
libssl.so.6 => /lib64/libssl.so.6 (0x0000003ca7c00000)
libcrypto.so.6 => /lib64/libcrypto.so.6 (0x0000003ca1c00000)
libz.so.1 => /usr/lib64/libz.so.1 (0x0000003c9ec00000)
libnetsnmp.so.10 => /usr/lib64/libnetsnmp.so.10 (0x0000003c9f400000)
libm.so.6 => /lib64/libm.so.6 (0x0000003c9e400000)
libwrap.so.0 => /usr/lib64/libwrap.so.0 (0x00002aea9fbdc000)
libmysqlclient.so.15 => /usr/lib64/mysql/libmysqlclient.so.15 (0x0000003c9e800000)
libc.so.6 => /lib64/libc.so.6 (0x0000003c9dc00000)
libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x0000003ca5c00000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x0000003ca5400000)
/lib64/ld-linux-x86-64.so.2 (0x0000003c9d800000)
libnsl.so.1 => /lib64/libnsl.so.1 (0x0000003ca0c00000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x0000003caea00000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00002aea9fde7000)
libsepol.so.1 => /lib64/libsepol.so.1 (0x0000003c9f800000)
Linux zabbix 2.6.18-92.1.6.el5 #1 SMP Wed Jun 25 13:45:47 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
mysql Ver 14.12 Distrib 5.0.45, for redhat-linux-gnu (x86_64) using readline 5.0Comment
-
I've had to revert back to 1.4... 90% of my agents are remote and I can't poke holes in all those firewalls just to allow zabbix communications...
If a patch comes out for this issue then I'll happily test it...
Fixing it is beyond my programming skills thoughComment
-
I think I have figured out my problem with this, the hostname in the web interface and in the agent.conf file are now case sensitive. I was looking really closely and realized that i had a few agents that were working and some that weren't.
The ones that weren't working the case was different in the agent.conf file from what I had in the web interface. Apparently that didn't matter in previous versions of zabbix, but does now.
DanComment
-
I have the same problem with the windows client 1.6
Hi, I have made the update from 1.4.5 to 1.6. I have also the problem with the active client check. I Have an Item for eventlog[Application]. I tried the client 1.4.5 and also the 1.6. The 1.6 client crashed after the start of the service in windows. The client 1.4.5 funktion. The server 1.6 didn't collect data from the eventlog when I change it to Zabbix active check. When I put the item back to Zabbix agent then I get the message in the Data filed that I must change to active check to get data.
Will be a patch released to resolve this problem????
Thx in advanceComment
-
I never made it to v1.6 because this version has been working flawless. I didn't see the point of upgrading if I wasn't experiencing any bugs
ZABBIX Server (daemon) v1.5.4 (19 August 2008)
Compilation time: Aug 25 2008 11:40:46
Are you using 1.6.0 or a newer build? I would try something newer.Comment

Comment