I'm running distributed monitoring on 3 servers, 1 master and 2 slaves.
If I import a template for one of the slaves, using the web interface from the master server, the graphids show the node number as the master node, not the slave.
The workaround I use is to connect directly to the web interface of the slave node and then import the template.
Stats:
1.6.2 server on master node (.3 and .4 still seg fault there)
1.6.4 php frontend on master node
1.6.4 server and frontends on slave nodes
Steps to reproduce:
Connect to master node frontend and login
Change the "current node" to one of the slave nodes
Import a template with graphs (I'm using the Cisco 5906 template)
Check the output of "SELECT * FROM zabbix.graphs" on the database on the slave node.
For my node 3, I see the new graphid entries, but they begin with the master node id, such as: "3001000..." instead of "3003000..."
To see how it should look like, repeat the above steps, but connect to the slave frontend to import the template. For my node 3, the entries then properly import the graphids starting with "3003000..."
Not a huge deal since I have a workaround, but I thought I'd mention it.
Thanks!
-Ron
If I import a template for one of the slaves, using the web interface from the master server, the graphids show the node number as the master node, not the slave.
The workaround I use is to connect directly to the web interface of the slave node and then import the template.
Stats:
1.6.2 server on master node (.3 and .4 still seg fault there)
1.6.4 php frontend on master node
1.6.4 server and frontends on slave nodes
Steps to reproduce:
Connect to master node frontend and login
Change the "current node" to one of the slave nodes
Import a template with graphs (I'm using the Cisco 5906 template)
Check the output of "SELECT * FROM zabbix.graphs" on the database on the slave node.
For my node 3, I see the new graphid entries, but they begin with the master node id, such as: "3001000..." instead of "3003000..."
To see how it should look like, repeat the above steps, but connect to the slave frontend to import the template. For my node 3, the entries then properly import the graphids starting with "3003000..."
Not a huge deal since I have a workaround, but I thought I'd mention it.
Thanks!
-Ron