Distributed Setup Questions.

[marc]

I've read the forum and issued an as it seems known problem (node2 is vanished from configuration after a while) but i have some general questions which i hope to get answered.

1.) i had a running standalone server which should be the master for my configuration. i run zabbix_server -n1 and added NodeID 1 to config file. Do the hosts/items/trigger configuration get replicated to my NodeID 2 if anything goes right? if i choose NodeID2 in the GUI (in the time befor node gets vanished, i do not see anything on host/item/trigger) tab.

2.) am i right that i have to configure NodeID2 via GUI and add NodeID 1 as type master, NodeID 2 stays as "Local node" and on NodeID1, NodeID1 is Local Node and NodeID2 is type "Remote"?

3.) is a fix available yet?

4.) is it correct that since i have clustering enabled, i cannot acknowlege any errors? it says permission denied if i try to acknowledge.

Thanks for some answers.. and as often requested, i must encourage to spend a week or so on documentation.

Marc

[marc]

no reply yet ...

[peter_field]

It simply doesnt work

Sorry, but I'm about to vent... so here goes..

Distributed monitoring does not work. Alexei says its a bug in 1.4.0, will be fixed in 1.4.1, well, its not. Neither is the problem with IE7 on Vista logging in (even though it was fixed in the 1.4.1 SVN).

There is no documentation on DM that is even remotely decent. And add to that it seems the DM is VERY limited anyway, and probably a pointless exercise (which I should be able to tell from the documentation, but oh wait, there is none). It seems it sends all data to the master, that seems pointless to me, should at least be optional to leave history and trends on the local nodes and only send events, because in reality, that it all that is really needed, particularly when you have slow WAN links.

My nodes don't disappear. However, when I switch the node to anything other than the local node, there is nothing in any configuration or data screens. No hosts, no templates, nothing. If I create them, they dont work. When I configure the node with its web interface, it all works like its standalone, none of the data shows up on the master, however, when I do this, the logs show that its sending data (it doesn't show any data transfers when I configure a node from the masters web interface). I'm sick of reinstalling the OS, recompiling and testing different configurations.

All in all, I've waited since the roadmap for 1.4 was released for DM, and it seems a waste of time. If its not working within a few weeks I'll be dumping Zabbix and going with another product.

Alexei, you need to understand that good documentation and proper testing before release is critical to making a good product. If nobody knows how to use it, or make it work, then its worthless.

[Alexei]

Didi you check the latest PDF manual from 1.4.1 distribution or available from http://www.zabbix.com/documentation.php. It does contain some more information about DM and it also has step-by-step instructions on creating a simple setup.

[peter_field]

maybe this thread

ok, this might be the answer here, I haven't tested it yet...

http://www.zabbix.com/forum/showthread.php?t=6764&page=2&pp=10

...and here I go again... Alexei, you really, REALLY need to be doing better testing before you release. This is painfully obvious, and would have been easily picked up if you had done any kind of decent testing before release. Come to think of it, I dont think there was a single release of 1.1.x that I didn't have to patch to get to work properly because of some stupid bug you missed. Get your act together, or people will lose confidence.

[Alexei]

Come to think of it, I dont think there was a single release of 1.1.x that I didn't have to patch to get to work properly because of some stupid bug you missed. Get your act together, or people will lose confidence.

Thanks for your comment. Developers section we introduced recently on zabbix.com is one of initial steps we plan to implement in order to improve pre-release testing and overall quality of the software. Other steps will include automated unit and system testing, public bug tracking system, and some other things. It takes time and resources...