Not sure if this is the right venue for posting feature requests, but it
would be useful if html which is generated by programs specified unique
html classes wherever possible to allow CSS styling. an example, for
Information Tables:
*** web/csvinfo.c 2017-06-19 14:14:13.186316715 -0500
--- web/csvinfo.c.new 2017-06-19 14:11:16.385617041 -0500
***************
*** 185,191 ****
sethostenv(wantedname, "", "", colorname(bgcolor), NULL);
headfoot(stdout, hffile, "", "header", bgcolor);
! printf("<table align=center border=1 summary=\"Information
table\">\n");
for (i=0; (headers[i]); i++) {
printf("<tr>\n");
--- 185,191 ----
sethostenv(wantedname, "", "", colorname(bgcolor), NULL);
headfoot(stdout, hffile, "", "header", bgcolor);
! printf("<table class=\"informationTable\" align=center border=1
summary=\"Information table\">\n");
for (i=0; (headers[i]); i++) {
printf("<tr>\n");
which would permit one to specify in file:
gifs/xymonbody.css
table.informationTable td { margin-left: 1em; margin-right: 1em }
to add a little spacing within the table cells around the text.
-- David Boldt
<user-945c7be1b8e4@xymon.invalid>
On Thu, Jun 8, 2017 at 10:33 AM, Frank <user-fbc5ef527f6f@xymon.invalid> wrote:
Well it was working HI!!
Here is an except from my hosts.cfg
EXAMPLE:
192.168.55.55 eth0:0
192.168.2.56 voip1.example.com (eth0) but voip1 is actually
mapped on the DNS to eth0:0
I have xymon-client starting up /home/xymon/runclient.sh --hostname=
voip1.example.com
Up till now everything runs ok. (I have not tried a failover, as I just
wanted to get it to work).
Probably report as a ghost when it fails over.
When I add this, then I get ghost reports: Weird, xymon-server reports
itself as one of the ghosts.
192.168.2.56 voip1-2.example.com (eth0 on primary)
192.168.2.57 voip1-3.example.com (eth0 on secondary)
On 6/8/17 9:49 AM, Adam Goryachev wrote:
Just a nudge, consider what I said about monitoring both servers all the
time. Otherwise, if one server dies, but xymon shows all green, you won't
know there is a problem until the second server dies too.
Regards,
Adam
On 8/6/17 23:10, Frank wrote:
When I say xymon, I mean the xymon-client. The xymon-server is on a
different machine.
On 6/7/17 7:46 PM, Adam Goryachev wrote:
On 8/6/17 07:46, Frank wrote:
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.
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
--
sysadm cronomagic.com/gemstelecom.com
e-mail user-fbc5ef527f6f@xymon.invalid
POWERED BY LINUX