Futher problems with distributed monitoring

[vasiliy]

In your case, the child node must have exaclty the same configuration as the master node. Two nodes were successfully created for Node 1, so you may repeat exactly the same steps to create the two nodes for Node 2.

I have a test system which is configured in exactly the same way and its nodes operate absolutely fine.

alexej, can you please please grab a screen shot from the nodes screen on both master and slave... and post back?

I've reinstalled, getting the same thing.. Obviously somewhere I am being misled.

THANKS

[vasiliy]

Alexej,
I dont understand why in your documentation you explain us to have the child node to be on port 15052, instead of default 10051... Thats the scenario that I follow.

I do not modify any ports, leave them as default


Overall, I think zabbix is an extremely cool product, but the waste of time associated with setting up this system, is unrecoverable.

I would LOVE to update your wiki once I get a system going.

[Alexei]

Alexej,
I dont understand why in your documentation you explain us to have the child node to be on port 15052, instead of default 10051... Thats the scenario that I follow.

I do not modify any ports, leave them as default

This is absolutely fine, I should have used default ports (i.e. 10051) in the documentation.

[vasiliy]

This is absolutely fine, I should have used default ports (i.e. 10051) in the documentation.

Neither setups work Unfortunately.

Once I configure everything, I go to the Central Node's configuration page... switch the interface to configure the child node, and see no defined hosts there. While one should exist, the zabbix server which is not monitored.

[vasiliy]

This is absolutely fine, I should have used default ports (i.e. 10051) in the documentation.

you are referring to the documentation on the site, not the wiki or anywhere else, correct?

[vasiliy]

I am following the documentation from here
http://www.zabbix.com/downloads/ZABB...ual%20v1.4.pdf

[vasiliy]

Found my problem.

The make install is now installing things into $prefix/sbin, not /bin

So i was really launching an 1.4.1 server

THANKS!

[vasiliy]

im going to update the wiki

thanks for your help!

[Alexei]

Found my problem.

The make install is now installing things into $prefix/sbin, not /bin

So i was really launching an 1.4.1 server

THANKS!

A happy ending...

[Niels]

Wait wait wait!!! Do I have to have a webinterface on each node?

[Alexei]

Wait wait wait!!! Do I have to have a webinterface on each node?

Currently it is required to have the interface during initial configuration of the node. However it can be done locally and node database can be copied to a remote location which may not have the webinterface installed.

[Niels]

It would certainly have been helpful if the manual had contained that particular nugget...

Can you give a step-by-step guide to transferring a database as you suggest?

[Niels]

I installed a web interface on the child node, and made a similar configuration as on the central node. Configuration changes are now propagated between the two machines, but latest data aren't (using r4798).

But now I have a question: If the two nodes (central and child) are configured equally, how do I decide (or see) which machine controls which? As far as I can see, I can create a new host on the central node from the child node. Since the child node is not physically under my control, a malicious user can swamp my central node with dummy hosts, or other configuration changes. That looks like a security problem.