Futher problems with distributed monitoring

[Niels]

Hi,

I never could get DM working with 1.4.0 or even 1.4.1 -- now I'm trying with a developer snapshot. I now get items properly propagated to child nodes, but nothing more happens. Apparently the remote agent doesn't see that it's supposed to monitor these items, nothing related turns up in its log. Also, I'm not seeing the remote server (the child node) log a "NODE 2: Sending data of node 2 to node 1" as the manual claims it should.

[vasiliy]

I am glad to see more and more people are working to get this going.

Please keep me posted on how things turn out

[Niels]

I am glad to see more and more people are working to get this going.

It's just too bad it's not the developers...

[vasiliy]

I would LOVE to help, and would be glad to update the docs

I am sure people are working on the stuff. I sincerely hope

[peter_field]

This whole DM thing has been one big joke.

When 1.4 first came out and I tried it, I thought I'll give it a month and it should be fixed. Tried it again, still not working, I thought I'll give it another month. Its still not working. Actually its probably been longer than two months.

I currently don't have time to work on this, or I would have, but really, seriously, this isn't a beta, this is a major new feature of a STABLE release, IT SHOULD BE WORKING ALREADY, or it should still be called a BETA.

I've just started at a new company. They currently run Nagios, and are looking to replace it. I don't feel comfortable even merely suggesting Zabbix at the moment. My previous employer wants me to continue work on Zabbix for them, and I'm not far from the point of telling them to scrap the project and start development on a new product.

Originally Posted by Niels
It's just too bad it's not the developers...

Don't you mean developer?

Alexei, if your going to introduce major new features you need to make sure you have the resources required to implement, test, and support them properly. If you don't, then don't release them, it justs makes you and your product look bad.

[Niels]

This whole DM thing has been one big joke.

When 1.4 first came out and I tried it, I thought I'll give it a month and it should be fixed. Tried it again, still not working, I thought I'll give it another month. Its still not working. Actually its probably been longer than two months.

My feelings exactly.

I currently don't have time to work on this, or I would have, but really, seriously, this isn't a beta, this is a major new feature of a STABLE release, IT SHOULD BE WORKING ALREADY, or it should still be called a BETA.

I quite agree. If I take two computers, install a fresh Debian and Zabbix on them, it doesn't work. How come this configuration is too obscure to have been tested?

Alexei, if your going to introduce major new features you need to make sure you have the resources required to implement, test, and support them properly. If you don't, then don't release them, it justs makes you and your product look bad.

Or open up the development process a lot more -- we can't tell what's going on! Making a public bugzilla isn't rocket surgery, there are many solutions available. Making daily or weekly reports of "what happened in SVN" is easy.

Testing isn't easy, writing documentation isn't easy, but that's where open source and the community can help -- if you let us!

[vasiliy]

I have spent 1 week in zabbix world... and am in love with the concepts and ideas...

Furthermore, I would love to extend any services for testing/documentation for the project, if I was given a chance

Sucks you guys have had such an experience. Few moments ago I was ready to close the browser and move on to nagios 3.0... but i really like zabbix's front end, and really feel like this product is far superior.

[Alexei]

I currently don't have time to work on this, or I would have, but really, seriously, this isn't a beta, this is a major new feature of a STABLE release, IT SHOULD BE WORKING ALREADY, or it should still be called a BETA

...

Alexei, if your going to introduce major new features you need to make sure you have the resources required to implement, test, and support them properly. If you don't, then don't release them, it justs makes you and your product look bad.

Thanks for sharing your thoughts.

I absolutely agree that ZABBIX 1.4 should have been better tested. It was a major release, introducing lots of new functionality: complex upgrade procedure, new (DM ready) database schema, improved front-end, WEB monitoring, install wizard, auto-discovery, distributed monitoring, unification of windows/unix code, etc etc etc.

Despite of this, I do believe that 1.4 was a big leap forward not only in terms of functionality but also in terms of code quality and better internal processes.

We are learning from our mistakes! We already made an access to nightly builds, access to our bug tracking system is about to be released, and most important is that quality is the priority number one. This is the main reason why we do not have 1.4.2 released yet, while the latest pre-1.4.2 can be downloaded and tested.

FYI ZABBIX 1.4.2 is to be released within a week or two.

[Niels]

Please let us know when DM is working in SVN.

[vasiliy]

Hello PEOPLE!

It has been some time. Have the issues been worked on/resolved?

THANKS!

[Alexei]

It has been some time. Have the issues been worked on/resolved?

We are doing final testing. I'm pretty sure the code will be committed to 1.4.2 and trunk today.

[Niels]

I'm trying r4559, and the nodes seem to be communicating now. The remote agent still doesn't see what it's supposed to do though. The node has two items the agent should check, but in the agent log, nothing appears.

[Alexei]

I'm trying r4559, and the nodes seem to be communicating now. The remote agent still doesn't see what it's supposed to do though. The node has two items the agent should check, but in the agent log, nothing appears.

Please give more details. I do not quite understand what you are talking about

[Niels]

I'm talking about DM. It doesn't work, and never did. For the nth time I'm trying svn HEAD on two Debian machines. And, as usual, I get the IKSEMEL error:

~/zabbix# ./go
Pre-making...
configure.in:31: installing `./config.sub'
configure.in:23: installing `./missing'
configure.in:23: installing `./install-sh'
configure.in:31: installing `./config.guess'
src/libs/zbxcommon/Makefile.am: installing `./depcomp'
src/libs/zbxdbhigh/Makefile.am:11: compiling `host.c' with per-target flags requires `AM_PROG_CC_C_O' in `configure.in'
src/libs/zbxdbhigh/Makefile.am:11: compiling `host.c' with per-target flags requires `AM_PROG_CC_C_O' in `configure.in'
Configuring...
/root/zabbix
Cleaning...
Making...
Installing...

WARNINGS
-----------------------------------
./configure: line 8363: syntax error near unexpected token `IKSEMEL,iksemel,'
./configure: line 8363: ` PKG_CHECK_MODULES(IKSEMEL,iksemel,'
make: *** No rule to make target `clean'. Stop.
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target `install'. Stop.
-----------------------------------

So now I have to hand edit configure. Or maybe I'll just go home.

[vasiliy]

Hi, whats the status ? I see 1.4.2 released, hwoever, I am not able to get things working!!! Extremely frustrating.

I see history and events being passed around... however, no configuration changes!

same problem I saw with 1.4.1...