Yes, you’ll be fine. The web server isn’t automatically turned on when you install the server.

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Joseph De Nicolo Sent: Thursday, June 27, 2013 2:04 PM To: Adam Goryachev Cc: xymon at xymon.com Subject: Re: [Xymon] Xymon server to monitor off-site cluster [private nodes]

Installed the client first on the head-node. It reports to my xymon server perfectly fine.

Now I installed an xymon server on the head-node, where can I disable the server daemon and enable xymonproxy? I also want to make sure that there is no xymon web server running, does disabling the xymon server daemon automatically take care of this or is there an extra step to shutting down the web server? I want everything displayed on my off-site central xymon server and nowhere else.

Thanks!

Joseph De Nicolo Secure Database Administrator Center for Complex Network Research<http://www.barabasilab.com> Northeastern University [http://forum.lazioland.com/Smileys/Blue/laziostend.gif]

On Thu, Jun 27, 2013 at 12:28 PM, Adam Goryachev <mailinglists at websitemanagers.com.au<mailto:mailinglists at websitemanagers.com.au>> wrote: On 28/06/13 02:24, Joseph De Nicolo wrote: Xymon users & admins,

I write to you in seek of help for a problem that may be simple for some but I am having trouble tackling. I will try my best explain:

I wish to monitor a scientific computing cluster, these are the details: There is a head node and 9 slave blade servers - 10 nodes total. The slave servers are all connected to a private network, therefore The head node has 2 active network devices - 1 for the private network, and 1 for the outer network to allow remote access to the cluster. This is the ONLY entry/outgoing point If the slave nodes need to go out to the internet for updates, ect.. they connect through a proxy on the head node.

My xymon server is located off-site but firewall settings allow communication between the head node of the cluster and my xymon server. I am currently just probing network tests on the head node, I did NOT install a xymon client or server yet on any node of the cluster.

How can I get a report pushed / pulled to my xymon server so that I can monitor and test all aspects of EVERY NODE? I want to be able to receive hardware and custom tests as well. Do I need to setup some sort of relay xymon server on the head node, or can I just configure the xymon slave clients to use tinyproxy which is already set up on the head node?

Yes, install xymon onto the head node, make sure the xymon server is disabled, but xymonproxy is enabled, and xymon client is enabled.

Then install xymon client on the remaining 9 nodes, and set the "xymon server" as the head node internal/private IP.

Hope this helps.

Regards, Adam

--

Adam Goryachev

Website Managers

www.websitemanagers.com.au<http://www.websitemanagers.com.au>

Xymon mailing list Xymon at xymon.com<mailto:Xymon at xymon.com> http://lists.xymon.com/mailman/listinfo/xymon

thanks for the help guys. I was able to get the hardware tests from the child nodes to my xymon server.

Is it possible to retrieve network tests on private nodes such as my setup? I'm not sure what to set on the xymon server side in hosts.cfg. I used the IP address of the HEAD NODE but used the host name of the child nodes and that seemed to work, but for network tests it will ping / ssh / ect using the ip of the head node. Does this mean I will have to use the head node as a server to ping and issue network tests to the child nodes? Is it a matter of deleting the line in tasks.cfg for the network test modules that say "NEEDS xymond"?

This is my hosts.cfg on my central xymon server: page mubs Cluster group Mubs - Head Node 212.456.132.5 mubs.example.com # ssh group Mubs - Child Nodes 212.456.132.5 mubs-child01 212.456.132.5 mubs-child02 ... group Mubs - Dell Remote Access Controllers 169.21.89.56 mubs-drac.example.com # noconn https://mubs-drac.example.com

How can I grab checks for the idrac cards which is basically just a https network check? A work around would be to just set up ports / procs check and look to see if ssh, and web services are running. The dracs are plugged into the same private switch for child nodes so they are only reachable by using X forwarding with the head node first.

Thanks,

•                                                        *

  *Joseph De Nicolo* *Secure Database Administrator
• *Center for Complex Network Research <http://www.barabasilab.com>* *Northeastern University*

On Fri, Jun 28, 2013 at 1:03 AM, Jeremy Laidman <jlaidman at rebel-it.com.au>wrote:

On 28 June 2013 05:03, Joseph De Nicolo <denicoloj at gmail.com> wrote:

...

Now I installed an xymon server on the head-node, where can I disable the server daemon and enable xymonproxy?

The server and proxy are launched by xymonlaunch, as specified in the tasks.cfg file. Edit tasks.cfg and look for the [xymond] and [xymonproxy] entries, and add, comment out or remove DISABLED as required. For readability or self-documentation, you can change DISABLED to ENABLED, but ENABLED is the default. Be sure to put your Xymon server IP address in the xymonproxy command line after "--server=" (within tasks.cfg).

You need to have the xymon service (xymonlaunch) running, otherwise xymonproxy won't run.

Cheers Jeremy