Aug 13, 2012 11:56 AM
Remote Collector graphs not working
-
Like (0)
Hello there,
I am a Zenoss newbie. I recently installed a zenoss 3.2.1 stack and attempted to turn it into a remote collector for another 3.2.1 core. However, the graphs through the remote collector do not seem to show up.
I tried different ways to change the Render URL:
None of it helped, though.
Does anyone have a tested step-by-step method of debugging this issue?
Also, I understand that 4.2 fixed a fair amount of issues when it comes to remote collectors. Did anyone upgrade to 4.2 from 3.2.1 and had those issues solved?
Thanks for your time,
Doru Davidson
Same thing for me on a clean Zenoss Core v4.2 install. I tried all the suggestions other people made on this forum (by the way they were all about v3 or earlier) but with no success. The RRD files are being updated on the remote collector but instead of each graph all I have is the placeholder for the image and no error message in the logs.
I've run into this quite a bit (albeit always on 3x). It generally comes down to the render URL of the collector. I'm guessing yours looks something like http://collectorname:8090? If so can you confirm your able to telnet into 8090 on the collector from your workstation (NOT your zenoss master)?
I too have a problem in my remote collector (i am using zenoss 4.2 on centos 5). i have installed the distributed collector zenpack but then i dont get any graph for the devices monitored by my remote collector.I had referred docs/DOC-2496 . Can anyone explain in brief about installing distributed collector in zenoss 4.2. please help me out
Dpetzel,
No I'm not able to telnet into the collector on the port you indicated and on a closeer inspection I could see the port 8090 in not open on the collector.
Thanks.
Dpetzel,
Actually you pointed me to the right direction. Reading the document about how to manually add a collector and doing some troubleshooting allowed me to solve the problem. It seems that installing the distributed collector zenpack does not start the zenrender service on any of the servers. All I had to do is to start zenrender on the hub and on the collector and the graphs came out just fine.
Too bad I can't give you helpful answer points because you really deserve them.
hmm interesting. zenrender use to be started on 3.x... I don't know about 4.x quite yet, but I wonder if we shouldnt bring this thread to BigEgor's attention so the pack can handle this situation.
I also noticed that after installing the distributed collector zenpack, the zenrender.conf configuration file was not modified with the new values for monitor and hubhost so I had to do it manually.
I am also having the same problem here. I am running 4.2.3. I used the distributed collector zenpack to configure my collector.
I have verified zenrender if running on both the master and collector. I can telnet both ways (from the collector to master and backward) over port 8090 and 8091. I have tried all the address listed above in the first post.
If i actually try an other render URL besides http://<zenmaster>:8091/<collector> the graps do not show up at all. With this URL i at least see the graphs but all the data points show up at NAN. If i got to that URL it says 'The image "http://<zenmaster>:8091/<collector>" cannot be diplayed because it contains errors.
If i look on the collector at /opt/zenoss/perf/Daemons/<collector>/ all of the graphs are getting updated every 5 minutes. If i take a look at the RRDs using RRDtool they are showing values
renaming the hosts.allow and hosts.deny seems to have done the trick. With these files up none of the service can talk to rrdcached
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||