June 2012 - Xymon - Xymon mailman web

Sort By in Xymon Alert Emails
by dbalders＠ucsd.edu 19 Jun '12

19 Jun '12

Hey, So I have xymon setup to email us when the cpu usage of a machine gets too high for an extended period of time. It sends the top 50 processes in an email. Right now, it is sending them in ascending order by process id. This is not super helpful because then I have to parse through to find which is taking the most cpu %. Do you guys have any suggestions on how I can get the email to be sorted by the cpu% instead of the proc id? Thanks! David B

2 1

WG: WG: clientlaunch.cfg: CRONDATE problem / error?
by christian.becker＠rhein-zeitung.net 18 Jun '12

18 Jun '12

Hello, any advise on this compile / patch issue (see my previous posting below...) ? Regards CHRISTIAN BECKER System Engineer CSC August-Horch-Strasse 28, 56070 Koblenz, Germany Global Outsourcing Services Central Region | www.csc.com -----Ursprüngliche Nachricht----- Von: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] Im Auftrag von Becker Christian Gesendet: Freitag, 15. Juni 2012 11:19 An: cleaver at terabithia.org Cc: xymon at xymon.com Betreff: [Xymon] WG: clientlaunch.cfg: CRONDATE problem / error? Hello, i found an article describing how to patch a source code. I have created a file xymonlaunch.c.patch in the common directory from my xymon install directory. The file contains just this code: --- trunk/common/xymonlaunch.c 2012/02/02 23:00:35 6905 +++ trunk/common/xymonlaunch.c 2012/02/07 10:19:43 6906 @@ -260,7 +260,8 @@ else if (curtask && (strncasecmp(p, "CRONDATE ", 9) == 0)) { p+= 9; xfreedup(curtask->cronstr,p); - if (curtask->crondate) { crondatefree(curtask->crondate);curtask->crondate=parse_cron_time(curtask->cronstr); } + if (curtask->crondate) crondatefree(curtask->crondate); + curtask->crondate = parse_cron_time(curtask->cronstr); if (!curtask->crondate) { errprintf("Can't parse cron date: %s->%s\n", curtask->key, curtask->cronstr); curtask->disabled = 1; Then i did the following (with some errornous results): [root at xymon common]# patch -p0 <xymonlaunch.c.patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- trunk/common/xymonlaunch.c 2012/02/02 23:00:35 6905 |+++ trunk/common/xymonlaunch.c 2012/02/07 10:19:43 6906 -------------------------- File to patch: xymonlaunch.c patching file xymonlaunch.c Hunk #1 succeeded at 260 with fuzz 2. [root at xymon common]# [root at xymon common]# [root at xymon common]# [root at xymon common]# [root at xymon common]# make cc -c -o xymonlaunch.o xymonlaunch.c xymonlaunch.c:32:22: error: libxymon.h: No such file or directory xymonlaunch.c: In function âload_configâ: xymonlaunch.c:94: error: âstrbuffer_tâ undeclared (first use in this function) xymonlaunch.c:94: error: (Each undeclared identifier is reported only once xymonlaunch.c:94: error: for each function it appears in.) xymonlaunch.c:94: error: âinbufâ undeclared (first use in this function) xymonlaunch.c:121: warning: assignment makes pointer from integer without a cast xymonlaunch.c:141: warning: assignment makes pointer from integer without a cast xymonlaunch.c:186: warning: initialization makes pointer from integer without a cast xymonlaunch.c:264: warning: assignment makes pointer from integer without a cast xymonlaunch.c: In function âmainâ: xymonlaunch.c:500: error: âdebugâ undeclared (first use in this function) xymonlaunch.c:510: warning: passing argument 1 of âstrdupâ makes pointer from integer without a cast /usr/include/string.h:175: note: expected âconst char *â but argument is of type âintâ xymonlaunch.c:514: warning: passing argument 1 of âstrdupâ makes pointer from integer without a cast /usr/include/string.h:175: note: expected âconst char *â but argument is of type âintâ xymonlaunch.c:526: warning: passing argument 1 of âstrdupâ makes pointer from integer without a cast /usr/include/string.h:175: note: expected âconst char *â but argument is of type âintâ xymonlaunch.c:598: error: âsave_errbufâ undeclared (first use in this function) xymonlaunch.c:716: warning: assignment makes pointer from integer without a cast xymonlaunch.c:720: warning: initialization makes pointer from integer without a cast make: *** [xymonlaunch.o] Error 1 [root at xymon common]# Did i miss something or did i do something else the wrong way? Regards Christian CHRISTIAN BECKER System Engineer CSC August-Horch-Strasse 28, 56070 Koblenz, Germany Global Outsourcing Services Central Region | www.csc.com -----Ursprüngliche Nachricht----- Von: Becker Christian Gesendet: Donnerstag, 14. Juni 2012 09:14 An: 'cleaver at terabithia.org' Cc: xymon at xymon.com Betreff: AW: [Xymon] clientlaunch.cfg: CRONDATE problem / error? Hello, Thank you for this information. Unfortunately I don't know how to apply a patch or to re-compile xymonlaunch - can you point me to the right way to do this? Best regards Christian CHRISTIAN BECKER System Engineer CSC August-Horch-Strasse 28, 56070 Koblenz, Germany Global Outsourcing Services Central Region | www.csc.com -----Ursprüngliche Nachricht----- Von: cleaver at terabithia.org [mailto:cleaver at terabithia.org] Gesendet: Mittwoch, 13. Juni 2012 19:14 An: Becker Christian Cc: xymon at xymon.com Betreff: Re: [Xymon] clientlaunch.cfg: CRONDATE problem / error? This is fixed in trunk and the 4.3.7 branch, but isn't in the tarball. http://xymon.svn.sourceforge.net/viewvc/xymon?view=revision&revision=6906 http://xymon.svn.sourceforge.net/viewvc/xymon?view=revision&revision=6899 This specific patch should fix it: http://xymon.svn.sourceforge.net/viewvc/xymon/trunk/common/xymonlaunch.c?r1… -jc > Hello out there, > > we are using Xymon 4.3.7 as xymon server. There is a particular client > running Ubuntu 9.04 as operating system and Xymon 4.3.7 as client, > reporting successfully to the Xymon server. > I have been in the need to write a script that is running on a fixed time > of a day. Therefore I configured the script in the clientlaunch.cfg on the > client as follows: > > [xymoncheckscript-custom] > ENVFILE $XYMONCLIENTHOME/etc/xymonclient.cfg > CMD $XYMONCLIENTHOME/ext/xymoncheckscript-custom.sh > LOGFILE $XYMONCLIENTHOME/logs/ xymoncheckscript-custom.log > CRONDATE 0 11 * * * > > When restarting the xymon services on the client I get the following entry > in clientlaunch.log: > > 2012-06-13 10:58:53 Can't parse cron date: xymoncheckscript-custom->0 11 * > * * > > The man page of tasks.cfg has the section: > =============================================================== > > [monthlyreport] > > ENVFILE /usr/local/xymon/server/etc/xymonserver.cfg > > CMD /usr/local/xymon/server/ext/monthlyreport.sh > > CRONDATE 30 4 1 * * > : > : > > The CRONDATE keyword is used for tasks that must run at regular intervals > or at a specific time. The time specification is identical to the one used > by cron in > crontab<http://xymon.mrv.de/xymon/help/manpages/man5/crontab.5.html>(5) > entries, i.e. a sequence of numbers for minute, hour, day-of-month, month > and day-of-week. Three-letter abbreviations in english can be used for the > month and day-of-week fields. An asterisk is a wildcard. So in the example > above, this job would run once a month, at 4:30 AM on the 1st day of the > month. > =============================================================== > > For my understanding everything I've set up should work, but it doesn't. > > Where's my fault? I would really like to fire this check-script from > clientlaunch.cfg instead of an crontab entry. > > Regards > Christian > > > CHRISTIAN BECKER > System Engineer > CSC > > August-Horch-Strasse 28, 56070 Koblenz, Germany > Global Outsourcing Services Central Region | www.csc.com > > > ________________________________ > > CSC * This is a PRIVATE message. If you are not the intended recipient, > please delete without copying and kindly advise us by e-mail of the > mistake in delivery. NOTE: Regardless of content, this e-mail shall not > operate to bind CSC to any order or other contract unless pursuant to > explicit written agreement or government initiative expressly permitting > the use of e-mail for such purpose * CSC Deutschland Services GmbH * > Registered Office: Abraham-Lincoln-Park 1, 65189 Wiesbaden, Germany * > Board of Directors: Gerhard Fercho (Chairman),Thomas Nebe, Peter Schmidt * > Registered in Germany: HRB 7574, Wiesbaden > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon > ________________________________ CSC • This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose • CSC Deutschland Services GmbH • Registered Office: Abraham-Lincoln-Park 1, 65189 Wiesbaden, Germany • Board of Directors: Gerhard Fercho (Chairman),Thomas Nebe, Peter Schmidt • Registered in Germany: HRB 7574, Wiesbaden _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon ________________________________ CSC • This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose • CSC Deutschland Services GmbH • Registered Office: Abraham-Lincoln-Park 1, 65189 Wiesbaden, Germany • Board of Directors: Gerhard Fercho (Chairman),Thomas Nebe, Peter Schmidt • Registered in Germany: HRB 7574, Wiesbaden ________________________________ CSC • This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose • CSC Deutschland Services GmbH • Registered Office: Abraham-Lincoln-Park 1, 65189 Wiesbaden, Germany • Board of Directors: Gerhard Fercho (Chairman),Thomas Nebe, Peter Schmidt • Registered in Germany: HRB 7574, Wiesbaden

3 2

Please help Re: Please clarify: http yellow when delayred is set? Or, what makes http yellow?
by betsy.schwartz＠gmail.com 15 Jun '12

15 Jun '12

I'm sorry, that was my fault. I've got multiple servers that are each monitoring multiple URL's, and I'm seeing different behavior on different servers, just to make life complicated. All of the servers have two or three URL's monitored. Some of the time, http goes yellow and then goes red after 10 minutes, when one URL out of three is unreachable Most of the time, though, http is just going yellow and staying yellow when one URL out of three is unreachable. I claim http shouldn't go yellow **at all**. But I would like a clear definition of how it's supposed to behave. The URL's that are failing are Cold Fusion URL's and appear in the history log as , for example: red http://host.example.com/monitor/monitor.cfm - Server timeout Seconds: 22.01

1 0

Please clarify: http yellow when delayred is set? Or, what makes http yellow?
by betsy.schwartz＠gmail.com 15 Jun '12

15 Jun '12

I have this default set: 0.0.0.0 .default. # DOWNTIME=0:0000:0300 delayred=http:10 and servers that are monitoring three URL's like so: 10.1.2.3 web1.example.com # CLASS:webzone ssh apache http://web1.example.com/url1.htm http://web1.example.com/url2.cfm http://web1.example.com/url3.cfm What I'm seeing is, with one URL going red with a timeout after 22 seconds, the http test is going YELLOW and then going RED ten minutes later. Does delayred turn the test yellow? If not, why is this test turning yellow? We want it to be RED. What exactly determines whether an http test is red or yellow? thanks Betsy

3 4

XYMWEBHIKEY question redux
by jglouisjr＠gmail.com 15 Jun '12

15 Jun '12

Not having received one reply on this question I am resending: Hi Everyone, In trying to resolve a trends graph issue it was stated to "set the XYMWEBHIKEY" variable. I haven't been able to find documentation on what and where this is set at. I tried to set it to TRUE in xymonserver.cfg but that doesn't seem to do anything. If anyone could expand on what was meant by setting this value that would be great. Thanks, Jim If anyone can help it would be greatly appreciated!! -- To be is to do = Immanuel Kant To do is to be = Descartes. Do be do be do = Frank Sinatra

5 9

xymonnet "red"
by joea＠j4computers.com 15 Jun '12

15 Jun '12

xymonnet version 4.3.7 Shows red. New-ish install. Has been red all along. Found this on the page details: "Error output: Execution of '/usr/sbin/fping -Ae' failed - program not suid root? This program can only be run by root, or it must be setuid root." I find fping in /usr/sbin. It works logged in as root if I specify a host name or IP, even a bogus one (for latter, it reports "address not found". However, if I do not specify a host (just do "fping") it appears to hang. I did not wait for hours, just a couple of minutes. But that is not likely the cause, because if I say su - xymon -c "/usr/sbin/fping -Ae something" I get" "This program can only be run by root, or it must be setuid root." Have I missed a step in setting up? Or am I still sleeping? joe a.

2 2

WG: clientlaunch.cfg: CRONDATE problem / error?
by christian.becker＠rhein-zeitung.net 15 Jun '12

15 Jun '12

Hello, i found an article describing how to patch a source code. I have created a file xymonlaunch.c.patch in the common directory from my xymon install directory. The file contains just this code: --- trunk/common/xymonlaunch.c 2012/02/02 23:00:35 6905 +++ trunk/common/xymonlaunch.c 2012/02/07 10:19:43 6906 @@ -260,7 +260,8 @@ else if (curtask && (strncasecmp(p, "CRONDATE ", 9) == 0)) { p+= 9; xfreedup(curtask->cronstr,p); - if (curtask->crondate) { crondatefree(curtask->crondate);curtask->crondate=parse_cron_time(curtask->cronstr); } + if (curtask->crondate) crondatefree(curtask->crondate); + curtask->crondate = parse_cron_time(curtask->cronstr); if (!curtask->crondate) { errprintf("Can't parse cron date: %s->%s\n", curtask->key, curtask->cronstr); curtask->disabled = 1; Then i did the following (with some errornous results): [root at xymon common]# patch -p0 <xymonlaunch.c.patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- trunk/common/xymonlaunch.c 2012/02/02 23:00:35 6905 |+++ trunk/common/xymonlaunch.c 2012/02/07 10:19:43 6906 -------------------------- File to patch: xymonlaunch.c patching file xymonlaunch.c Hunk #1 succeeded at 260 with fuzz 2. [root at xymon common]# [root at xymon common]# [root at xymon common]# [root at xymon common]# [root at xymon common]# make cc -c -o xymonlaunch.o xymonlaunch.c xymonlaunch.c:32:22: error: libxymon.h: No such file or directory xymonlaunch.c: In function âload_configâ: xymonlaunch.c:94: error: âstrbuffer_tâ undeclared (first use in this function) xymonlaunch.c:94: error: (Each undeclared identifier is reported only once xymonlaunch.c:94: error: for each function it appears in.) xymonlaunch.c:94: error: âinbufâ undeclared (first use in this function) xymonlaunch.c:121: warning: assignment makes pointer from integer without a cast xymonlaunch.c:141: warning: assignment makes pointer from integer without a cast xymonlaunch.c:186: warning: initialization makes pointer from integer without a cast xymonlaunch.c:264: warning: assignment makes pointer from integer without a cast xymonlaunch.c: In function âmainâ: xymonlaunch.c:500: error: âdebugâ undeclared (first use in this function) xymonlaunch.c:510: warning: passing argument 1 of âstrdupâ makes pointer from integer without a cast /usr/include/string.h:175: note: expected âconst char *â but argument is of type âintâ xymonlaunch.c:514: warning: passing argument 1 of âstrdupâ makes pointer from integer without a cast /usr/include/string.h:175: note: expected âconst char *â but argument is of type âintâ xymonlaunch.c:526: warning: passing argument 1 of âstrdupâ makes pointer from integer without a cast /usr/include/string.h:175: note: expected âconst char *â but argument is of type âintâ xymonlaunch.c:598: error: âsave_errbufâ undeclared (first use in this function) xymonlaunch.c:716: warning: assignment makes pointer from integer without a cast xymonlaunch.c:720: warning: initialization makes pointer from integer without a cast make: *** [xymonlaunch.o] Error 1 [root at xymon common]# Did i miss something or did i do something else the wrong way? Regards Christian CHRISTIAN BECKER System Engineer CSC August-Horch-Strasse 28, 56070 Koblenz, Germany Global Outsourcing Services Central Region | www.csc.com -----Ursprüngliche Nachricht----- Von: Becker Christian Gesendet: Donnerstag, 14. Juni 2012 09:14 An: 'cleaver at terabithia.org' Cc: xymon at xymon.com Betreff: AW: [Xymon] clientlaunch.cfg: CRONDATE problem / error? Hello, Thank you for this information. Unfortunately I don't know how to apply a patch or to re-compile xymonlaunch - can you point me to the right way to do this? Best regards Christian CHRISTIAN BECKER System Engineer CSC August-Horch-Strasse 28, 56070 Koblenz, Germany Global Outsourcing Services Central Region | www.csc.com -----Ursprüngliche Nachricht----- Von: cleaver at terabithia.org [mailto:cleaver at terabithia.org] Gesendet: Mittwoch, 13. Juni 2012 19:14 An: Becker Christian Cc: xymon at xymon.com Betreff: Re: [Xymon] clientlaunch.cfg: CRONDATE problem / error? This is fixed in trunk and the 4.3.7 branch, but isn't in the tarball. http://xymon.svn.sourceforge.net/viewvc/xymon?view=revision&revision=6906 http://xymon.svn.sourceforge.net/viewvc/xymon?view=revision&revision=6899 This specific patch should fix it: http://xymon.svn.sourceforge.net/viewvc/xymon/trunk/common/xymonlaunch.c?r1… -jc > Hello out there, > > we are using Xymon 4.3.7 as xymon server. There is a particular client > running Ubuntu 9.04 as operating system and Xymon 4.3.7 as client, > reporting successfully to the Xymon server. > I have been in the need to write a script that is running on a fixed time > of a day. Therefore I configured the script in the clientlaunch.cfg on the > client as follows: > > [xymoncheckscript-custom] > ENVFILE $XYMONCLIENTHOME/etc/xymonclient.cfg > CMD $XYMONCLIENTHOME/ext/xymoncheckscript-custom.sh > LOGFILE $XYMONCLIENTHOME/logs/ xymoncheckscript-custom.log > CRONDATE 0 11 * * * > > When restarting the xymon services on the client I get the following entry > in clientlaunch.log: > > 2012-06-13 10:58:53 Can't parse cron date: xymoncheckscript-custom->0 11 * > * * > > The man page of tasks.cfg has the section: > =============================================================== > > [monthlyreport] > > ENVFILE /usr/local/xymon/server/etc/xymonserver.cfg > > CMD /usr/local/xymon/server/ext/monthlyreport.sh > > CRONDATE 30 4 1 * * > : > : > > The CRONDATE keyword is used for tasks that must run at regular intervals > or at a specific time. The time specification is identical to the one used > by cron in > crontab<http://xymon.mrv.de/xymon/help/manpages/man5/crontab.5.html>(5) > entries, i.e. a sequence of numbers for minute, hour, day-of-month, month > and day-of-week. Three-letter abbreviations in english can be used for the > month and day-of-week fields. An asterisk is a wildcard. So in the example > above, this job would run once a month, at 4:30 AM on the 1st day of the > month. > =============================================================== > > For my understanding everything I've set up should work, but it doesn't. > > Where's my fault? I would really like to fire this check-script from > clientlaunch.cfg instead of an crontab entry. > > Regards > Christian > > > CHRISTIAN BECKER > System Engineer > CSC > > August-Horch-Strasse 28, 56070 Koblenz, Germany > Global Outsourcing Services Central Region | www.csc.com > > > ________________________________ > > CSC * This is a PRIVATE message. If you are not the intended recipient, > please delete without copying and kindly advise us by e-mail of the > mistake in delivery. NOTE: Regardless of content, this e-mail shall not > operate to bind CSC to any order or other contract unless pursuant to > explicit written agreement or government initiative expressly permitting > the use of e-mail for such purpose * CSC Deutschland Services GmbH * > Registered Office: Abraham-Lincoln-Park 1, 65189 Wiesbaden, Germany * > Board of Directors: Gerhard Fercho (Chairman),Thomas Nebe, Peter Schmidt * > Registered in Germany: HRB 7574, Wiesbaden > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon > ________________________________ CSC • This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose • CSC Deutschland Services GmbH • Registered Office: Abraham-Lincoln-Park 1, 65189 Wiesbaden, Germany • Board of Directors: Gerhard Fercho (Chairman),Thomas Nebe, Peter Schmidt • Registered in Germany: HRB 7574, Wiesbaden

1 0

Multiple graph from one SERVICE
by joel＠carnat.net 15 Jun '12

15 Jun '12

Hello, I'm writing custom scripts and, so far, I could create graphs from single RRD and from multiple RRD (like "la"). I'm working on some SNMP-based network interface graphing. On one of my multiple-NIC server, the script generates RRD files this way: /usr/local/www/xymon/server/bin/bb 127.0.0.1 'data esxi.trends [snmp_net.vmnic0.rrd] DS:ibit:DERIVE:600:0:U 2130119859 DS:ierr:DERIVE:600:0:U 0 DS:obit:DERIVE:600:0:U 6920041 DS:oerr:DERIVE:600:0:U 0 ' /usr/local/www/xymon/server/bin/bb 127.0.0.1 'data esxi.trends [snmp_net.vmnic1.rrd] DS:ibit:DERIVE:600:0:U 589307058 DS:ierr:DERIVE:600:0:U 0 DS:obit:DERIVE:600:0:U 0 DS:oerr:DERIVE:600:0:U 0 ' The RRD files are properly created /usr/local/www/xymon/data/rrd/esxi/snmp_net.vmnic0.rrd /usr/local/www/xymon/data/rrd/esxi/snmp_net.vmnic1.rrd Then, my graph section goes like this: [snmp_net] FNPATTERN ^snmp_net.(.+).rrd <snip> DEF:ibit at RRDIDX@=@RRDFN@:ibit:AVERAGE DEF:ierr at RRDIDX@=@RRDFN@:ierr:AVERAGE DEF:obit at RRDIDX@=@RRDFN@:obit:AVERAGE DEF:oerr at RRDIDX@=@RRDFN@:oerr:AVERAGE CDEF:nobit at RRDIDX@=obit at RRDIDX@,-1,* AREA:ibit at RRDIDX@#@COLOR at 22:@RRDPARAM@ download GPRINT:ibit at RRDIDX@:LAST:%6.2lf%s GPRINT:ibit at RRDIDX@:MIN:%6.2lf%S GPRINT:ibit at RRDIDX@:AVERAGE:%6.2lf%S GPRINT:ibit at RRDIDX@:MAX:%6.2lf%S\j AREA:obit at RRDIDX@#@COLOR at 22:@RRDPARAM@ upload GPRINT:obit at RRDIDX@:LAST:%6.2lf%s <snip> This creates a single PNG with both NIC metrics. What I would like to do is rather create a single PNG for each of my NICs. Something like snmp_net.vmnic0.png, snmp_net.vmnic1.png... Is there a way to do that ? Thanks, Jo

2 2

Premature end of script headers: showgraph.sh
by tim.myers.eim＠gmail.com 15 Jun '12

15 Jun '12

I have a new install of xymon-4.3.7 - I get "Premature end of script headers" on showgraph and I don't get any graphs -- I see that xymond-rrd is running. I have not graphs and only see a red X followed by "xymongraph" and a type like tcp disk tcp:http or what ever type of graph I would be expecting. selecting that only takes me to: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, root at localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log ===== and error log has the Premature end of script headers message: [Thu Jun 07 15:39:45 2012] [error] [client x.x.x.x] Premature end of script headers: showgraph.sh, referer: https://myname1:46248/xxymon-cgi/svcstatus.sh?HOST=myname1&SERVICE=trends [Thu Jun 07 15:40:06 2012] [error] [client x.x.x.x] Premature end of script headers: showgraph.sh, referer: https://myname1:46248/xymon-cgi/svcstatus.sh?HOST=myname1&SERVICE=disk [Thu Jun 07 15:41:06 2012] [error] [client x.x.x.x] Premature end of script headers: showgraph.sh, referer: https://myname1:46248/xymon-cgi/svcstatus.sh?HOST=myname1&SERVICE=http ======= I have tried different servers different charts but no graphs for any servers

4 3

analysis.cfg config issues
by rbrusletto＠glptrading.com 15 Jun '12

15 Jun '12

I *thought* I'd used this type of setup in the past, but it doesn't seem to be working in the current setup as follows: HOST=somehost LOAD 4.0 6.0 TIME=W:0730:1630 MEMACT 50 60 TIME=W:0730:1630 LOAD 10.0 12.0 MEMACT 80 90 DEFAULT # These are the built-in defaults. UP 20m LOAD 1.0 2.0 MEMACT 90 97 Currently, I'm getting warning(yellow) alerts for what seems to be anything over a load of 5, which in the documentation seems like the default, when nothing is specified. Clearly the load is defined in the default(which IS at the end of the analysis.cfg). We expect the load to be lower than 4 during week work hours, and higher in the evening/night due to a large amount of load processing. Is there something simple I'm missing here, or is it simply the way the times are configured? -- Thanks! Rolf Brusletto Senior Network And Systems Admin Global Liquidity Partners, LLC rolf at glptrading.com 303-638-8013 mobile

2 1