Proxy data sync problems

[Gigoudt]

Hi ,

im facing a problem and i figure out what is the problem and solution but cant find what is the cause of it.

The problem is in data being syncronize from proxies to zabbix_server. In our network we have 2500 proxies and from time to time we find that data in some proxies are outdate but hosts being monitored are up.

Everything is correctly configure but no data tranfer to server.

Looking closer in proxy database i found that the nextid in ids table is much bigger than the last id in the proxy_history table.

With this proxy think than all the data has been syncronized and no new data is transfer.

Solution setting the nextid with a number close to the last in the proxy_history.

I dont know if houskeeping clear every data and the id start from 1 again. I guess...

With all the proxies we have this is really laborious to solve. I am thinking to workaround this with a scrip in each proxy or a remoe command in zabbix_server.

Someone can give me a clue of the problem im facing. Or a simplier solution way.

Thanks to all

[Gigoudt]

anyone ?

this is a bug of the aplicaction or something being wrong configured.

the following statement is correct ?

the id is the primary key of the table proxy_histroy, so if all data is erased id has to be always the maximun value, not restored to 0.

i try to delete data and id is not restored , only if use truncate command of all data id is restored.

[bashman]

I'm facing the same problem with one active proxy that monitors 385 hosts through 2460 monitors and 10.99 vps.

mysql> SELECT max(id) from proxy_history;
+---------+
| max(id) |
+---------+
| 2906356 |
+---------+
1 row in set (0.00 sec)

mysql> select * from ids;
+--------+--------------------+---------------------+---------+
| nodeid | table_name         | field_name          | nextid  |
+--------+--------------------+---------------------+---------+
|      0 | proxy_autoreg_host | autoreg_host_lastid |   66285 |
|      0 | proxy_history      | history_lastid      | 2906383 |
+--------+--------------------+---------------------+---------+
2 rows in set (0.00 sec)

Here MATSUDA Daiki explains the cause:

https://support.zabbix.com/browse/ZBX-6249

[Gigoudt]

Bashman ,

i dont know what version of zabbix_proxy you are using. This problem we faced it in 1.8.2. And solved using a workaround by seting nextid with a number lower and close to the last in the proxy_history and then every started to work again.

I dont remember where , but what I have read , that this is a bug that is solved in .1.8.11 . Please upgrade if using lower version.

bye !!

[bashman]

Thanks Gigoudt, I'm using zabbix vesión 1.8.15, but your workaround didn't work for me.

mysql> select * from ids;
+--------+--------------------+---------------------+---------+
| nodeid | table_name         | field_name          | nextid  |
+--------+--------------------+---------------------+---------+
|      0 | proxy_autoreg_host | autoreg_host_lastid |   74568 |
|      0 | proxy_history      | history_lastid      | 3269730 |
+--------+--------------------+---------------------+---------+
2 rows in set (0.00 sec)

mysql> SELECT max(id) from proxy_history;
+---------+
| max(id) |
+---------+
| 3269750 |
+---------+
1 row in set (0.00 sec)