Hi everyone! Um, any ideas on this? I didn't get a single reply - maybe my original post didn't make it to the list?

Thanks......

From: Brodie, Kent Sent: Friday, July 21, 2006 11:08 AM To: 'hobbit at hswn.dk' Subject: Weird hobbit/proxy/CONN catch-22?

OK guys, here's what I have (thank to all that helped me thus far, especially Henrik!)

My setup involves a hidden cluster-- which means that from my MAIN Hobbit server (BBDISPLAY), I cannot see nor ping the cluster nodes, but I *can* see and talk to the cluster "head node".

Based on prior suggestions, I set it all up as follows:

Main BB server has config entries for everything, including the cluster head node AND the cluster nodes it "can't see" directly.

These entries are listed as:

Hidden.ip.address.here host.name.here # noconn

"noconn" obviously, since the network tests from the main Hobbit server would fail!

Next, I set up the cluster head node as a BB server. Actually, its main purpose is to run the network and such tests, and act as a proxy server for the whole cluster.

It all works. Sort of! On my main BB display, I see the entries for the "unreachable" cluster nodes, which is very cool. I see the cpu, disk, files, msgs, etc. But-- there's no connectivity (conn) information or status information.

Catch-22? How do I get the "conn" test to show up? If I list "conn" in the bb-hosts on my main Hobbit server, I am going to assume that the conn tests will have issues, since that server(s) really are unreachable from the BBDISPLAY host. But if I set it up listed as "noconn" on the BBDISPLAY server-- um, there's no conn data/column (a Homr Simpson "D'oh!" goes here).

Any ideas? The BBPROXY setup described above is working as far as information exchange, as I am indeed seeing cpu, disk, files, info, msgs, ports, procs, and that's all very very cool and good. But I need 'conn' most of all.

Help! (and thanks)

By the way - a suggestion for stuff down the road a bit: When I set up my proxy server (./configure -server), there was of course all of the requirements I had to have met, such as having RRDTOOL, libpng, etc etc all there. That's great, except I have no intention of having this other server doing anything other than running a few tests, and forwarding it all on to the BBD server. No data, no RRD, no graphs, no apache, no html. One big suggestion I have (since the proxy is such a cool thing) is to perhaps including things like: ./configure -proxy-only ? Just a thought. This may or may not be complicated...

Kent C. Brodie - brodie at phys.mcw.edu

Department of Physiology

Medical College of Wisconsin

(414) 456-8590