delay of proxy

[vmedek]

Hi all,

I have a problem with servers monitored via zabbix proxy. All items in "latest data" are 60-90 minutes old. (all directly checked servers are OK). I have changed "config frequency" in proxy configuration, but nothing has changed. Does anybody know where is the problem?

[kc5kse]

One thing that was recommended was to make sure that number of trappers was set to 2 * # of proxies. Also, StartDBSyncers=1.

I have to admit, this hasn't helped me. Log files are showing "History buffer full...". I've doubled the RAM on my master server and saw a small improvement but I'm back to an hour lag from proxies this morning.

Anyone have any idea how I can just wipe out the history buffer? I'm going through and triming down the time I keep history but it hasn't helped so far.

[kc5kse]

Ok, data from proxies is over 2 DAYS old. Has anyone else had this problem? If so, how did you deal with it? It's getting to the point where management is questioning the ability of Zabbix.

[richlv]

you can try nuking table proxy_history on all proxies. beware that this will remove all gathered data by proxies so far.

oh, before you do that... have you checked that proxies can actually connect to the server ?
for proxy host :

telnet <zabbix_server_ip> 10050

and make sure hostnames as configured in proxy config files match the ones in server configuration.

[kc5kse]

you can try nuking table proxy_history on all proxies. beware that this will remove all gathered data by proxies so far.

oh, before you do that... have you checked that proxies can actually connect to the server ?
for proxy host :

telnet <zabbix_server_ip> 10050

and make sure hostnames as configured in proxy config files match the ones in server configuration.

Yes, all hostnames from proxy config files match the server. I've also verified network communications both ways successfully.
I'll try nuking that table. Not really worried about the data gathered at this point.

Thank you very much!!!

[kc5kse]

My log is full of the following:

3545:20091006:111847 History buffer is full. Sleeping for 1 second.
3547:20091006:111847 History buffer is full. Sleeping for 1 second.
3549:20091006:111847 History buffer is full. Sleeping for 1 second.

What is causing this? What do I need to do? Nothing is getting updated.

[richlv]

so you mean nothing at all got synced to the server ?
even right after you started up the proxy ?
this would mean that proxy can't connect to the server, or that server does not recognise it.
is "Hostname" option in proxy config really matching the one configured in zabbix frontend ?
can you indeed telnet to port 10051 port on server from zabbix proxy ?
what gets logged in proxy and server logfiles right after proxy starts up ?

[kc5kse]

Proxies can't communicate to the Master server, but after I restart Zabbix, they can for a while. Zabbix log says History buffer is full. After a while, I am unable to telnet to port 10051 or 10050 to the master server.

The Queue shows over 10,000 updates over 10 minutes, but details don't show anything. I don't know what to do.

[kc5kse]

And, yes, the hostnames in the proxy config matches the zabbix frontend.

[richlv]

Proxies can't communicate to the Master server, but after I restart Zabbix, they can for a while. Zabbix log says History buffer is full. After a while, I am unable to telnet to port 10051 or 10050 to the master server.

The Queue shows over 10,000 updates over 10 minutes, but details don't show anything. I don't know what to do.

oooook. any reason why you withheld this information before ?
let's leave proxies out for a moment. if you stop all proxies and start zabbix server, can you connect to port 10051 after the time it usually becomes inaccessible ?
which logfile (server or proxy) talks about history buffer being full ?

are other items gathering data correctly when port 10051 becomes inaccessible ?
i somehow suspect that you have simply overloaded zabbix, but let's see more.

[kc5kse]

oooook. any reason why you withheld this information before ?
let's leave proxies out for a moment. if you stop all proxies and start zabbix server, can you connect to port 10051 after the time it usually becomes inaccessible ?
which logfile (server or proxy) talks about history buffer being full ?

are other items gathering data correctly when port 10051 becomes inaccessible ?
i somehow suspect that you have simply overloaded zabbix, but let's see more.

I'm pulling my hair out so possible that my brains came with it

Ok, all proxies are stopped. Zabbix master log is showing History buffer full and I can telnet to port 10051 from proxy to master. Now, if I am overloading zabbix, what would I need to do?

[richlv]

ok, sorry for stupid question... but is database actually running ?
which database are you using ?

[kc5kse]

ok, sorry for stupid question... but is database actually running ?
which database are you using ?

Not stupid at all. I may be, but not you *heh* I'm using mysql and it is running on the same box as the master server.

[kc5kse]

Hmmm, I'm attempting to disable 2 clients that are directly connected to the master server. It's just sitting there saying "waiting for <master zabbix server>....."

[richlv]

it sounds to me like zabbix is unable to connect to the database.
shut zabbix server down, start it and check the zabbix server logfile immediately after that.
also check mysql error log.