Distributed monitoring syncing only few data

[adriano]

Greetings,

Here I do have a Master node and two Slaves.

Slave A is syncing fine, it has few computers in the network, there is no problem, but Slave B has 50~60 computers, and a lot of data to sync to the Master.

Master server 1.8.11
Slave A server 1.8.10
Slave B server 1.8.5

Slave A has all data up to date, but Slave B only updates the Events.

Every log, conf or spec if you need more debug.
Someone can help me?

[adriano]

Solved

mysql_upgrade zabbix -uzabbix -pXXXXXXXXXXXXX

[adriano]

still not ok

Items 5 seconds 10 seconds 30 seconds 1 minute 5 minutes More than 10 minutes
Zabbix agent 0 5 1 104 157 95
Zabbix agent (active) 0 0 0 0 0 0
Simple check 0 0 0 0 0 0
SNMPv1 agent 0 0 0 0 0 0
SNMPv2 agent 0 0 0 0 307 0
SNMPv3 agent 0 0 0 0 0 0
Zabbix internal 0 0 0 0 0 0
Zabbix aggregate 0 0 0 0 0 0
External check 0 0 0 0 0 0
Database monitor 0 0 0 0 0 0
IPMI agent 0 0 0 0 0 0
SSH agent 0 0 0 0 0 0
TELNET agent 0 0 0 0 0 0
Calculated 0 0 0 0 0 0

Sorry about the table.. can't take the original image now, but it is still understandable..
This is the queue the slave node that was not working.. it is syncing, and I can see the data fine on the server, but it still don't sync on real time, or almost it, so it gives me UNKNOWN status on maps..
~edit: it is syncing, but it has about 20 minutes delay on some hosts.. (95 items)

My configurations are default, just a CentOS 6.2 with Zabbix 1.8.11 server, MySQL InnoDB 5.5.. 74 new values per second..
Slave has default configs too.. CentOS 6 with Zabbix 1.8.5 and MySQL 5.3..

How can I boost sync between nodes?

[markl]

Hi,

Did you get anywhere with this? We have a similar issue when our comms go down between server and remote proxies. Most catch up fine but one site always seems to take an absolute age to catch up. We currently use 1.8.9. I'm hoping upgrading to 2.0.0 will fix the issue.

Cheers,

Mark.

[adriano]

Hi,

Did you get anywhere with this? We have a similar issue when our comms go down between server and remote proxies. Most catch up fine but one site always seems to take an absolute age to catch up. We currently use 1.8.9. I'm hoping upgrading to 2.0.0 will fix the issue.

Cheers,

Mark.

Hi markl,

I've reinstalled both Master node and Slave node, so I can't get the point to fix it, but I don't think upgrading is a good idea if you are going to do it only on one of the servers, they will stop syncing, because it will have different tables, so it will screw up everything.

But if u re going to do it anyway, follow the manuals, wiki and forum, so you can get a full tutorial on how to do this in the most secure way and not lose any data.

Kind regards.