Hi,I think I now have this under control. So you can ignore the previous email. No more ghosts!!
Is there a way to have the xymon client bind to a specific IP or interface? I have more than one interface on a machine and I am getting ghost reports because I setup xymon for eth0:0 instead of eth0.
--
sysadm cronomagic.com/gemstelecom.com e-mail ve2cii at canasoft.net
POWERED BY LINUX
On 6/5/2017 9:15 AM, Frank wrote:
Hi,
I think I now have this under control. So you can ignore the previous email. No more ghosts!!
Is there a way to have the xymon client bind to a specific IP or interface? I have more than one interface on a machine and I am getting ghost reports because I setup xymon for eth0:0 instead of eth0.
Hi,
It surprised me that this wasn't a configurable option. There's no way to currently (as opposed to binding on the listen interface), but looking at the code, I think this should be easily addable as a feature
Regards,
-jc
Hi,
I am doing something that I don't think has been done with xymon before. We are running asterisk on a failover heartbeat system. When the failover occurs heartbeat shuts down everything on the primary server and xymon goes nuts. So I set up heartbeat to stop xymon when it shuts everything else down. Now when the "floating IP" goes to the secondary server, the secondary starts up all the services and I set it up for xymon to start too. I was thinking would be a great idea if I could bind xymon to the floating IP the same way I do it for the rest of the services. So far during tests it seems to be working out ok without the binding, but may be necessary after all.
On 6/7/17 5:24 PM, Japheth Cleaver wrote:
On 6/5/2017 9:15 AM, Frank wrote:
Hi,
I think I now have this under control. So you can ignore the previous email. No more ghosts!!
Is there a way to have the xymon client bind to a specific IP or interface? I have more than one interface on a machine and I am getting ghost reports because I setup xymon for eth0:0 instead of eth0.
Hi,
It surprised me that this wasn't a configurable option. There's no way to currently (as opposed to binding on the listen interface), but looking at the code, I think this should be easily addable as a feature
Regards,
-jc
-- sysadm cronomagic.com e-mail ve2cii at canasoft.net
POWERED BY LINUX
On 8/6/17 07:46, Frank wrote:
Hi,
I am doing something that I don't think has been done with xymonbefore. We are running asterisk on a failover heartbeat system. When the failover occurs heartbeat shuts down everything on the primary server and xymon goes nuts. So I set up heartbeat to stop xymon when it shuts everything else down. Now when the "floating IP" goes to the secondary server, the secondary starts up all the services and I set it up for xymon to start too. I was thinking would be a great idea if I could bind xymon to the floating IP the same way I do it for the rest of the services. So far during tests it seems to be working out ok without the binding, but may be necessary after all.
When you say "xymon" do you mean xymon-client or are you running the xymon server components on this redundant system?
It seems to me that running the monitoring system on the same system that you are monitoring is likely to lead to problems (ie, on total system failure you won't be told about it). I would suggest to run the monitoring on a 3rd server, which is stand-alone from this pair. Xymon doesn't care which IP address the client reports originate from, as long as the name is correct.
However, I would advise to have both systems report status individually, with their own names, then you can see the status of each server in the pair. In order to alert and see the status of the services provided by the pair, then you can use combined status such as procs on serverA OR procs on serverB = procs green for Service and so on.
Hope this helps...
Regards, Adam
--
participants (3)
-
cleaver＠terabithia.org
-
mailinglists＠websitemanagers.com.au
-
ve2cii＠canasoft.net