April 2015 - Xymon - Xymon mailman web

Accessing availabitlity or snapshot reports
by dirk.kastens＠uni-osnabrueck.de 10 Apr '15

10 Apr '15

Hi JC, > Would you mind testing > http://terabithia.org/rpms/xymon/testing/el6/x86_64/xymon-4.3.19-9.el6.x86_… > (et al.) and see if this fixes the problem for you? > > If possible, please first change the context back to: > > /usr/sbin/semanage fcontext -a -t httpd_cache_t '/var/cache/xymon(/.*)?' > and then run restorecon -Rv /var/cache/xymon I deleted my added file contexts, restored the original ones, and updated the RPM. Now the reports are working. Thanks for your support. Dirk

1 0

Is there a reason why the httpstatus test is case sensitive?
by john.thurston＠alaska.gov 10 Apr '15

10 Apr '15

Yesterday, I crashed xymonnet by doing a copy/paste into an httpstatus test. I eventually figured out what was wrong. This syntax is good: 0.0.0.0 foo.com # httpstatus;http://foo.com/index.html;401 This syntax is bad: 0.0.0.0 foo.com # httpstatus;HTTP://foo.com/index.html;401 The man page for hosts.cfg doesn't say anything about required or supported casing. Is there some reason why xymonnet shouldn't be able to handle mixed-case protocol names in the URLs provided? -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Administration State of Alaska

3 4

ps output cut
by gbegin＠csc.com 10 Apr '15

10 Apr '15

Any news ? Cordialement, Regards,Mit freundlichen Grüßen, Gautier BEGIN Global Service Support Solutions - Tools Support CACEIS and APERAM accounts CSC Computer Sciences Luxembourg S.A. 12D Impasse Drosbach L-1882 Luxembourg Global Outsourcing Service | p:+352 24 834 276 | m:+352 621 229 172 | gbegin at csc.com | 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 Computer Sciences SAS • Registered Office: Immeuble Le Balzac, 10 Place des Vosges, 92072 Paris La Défense Cedex, France • Registered in France: RCS Nanterre B 315 268 664 From: Gautier Begin/LUX/CSC To: John Horne <john.horne at plymouth.ac.uk> Cc: xymon at xymon.com, "Xymon" <xymon-bounces at xymon.com> Date: 04/01/2015 05:18 PM Subject: Re: [Xymon] ps output cut Hello John, Config on the XYMON proxy: MAXMSGSPERCOMBO="40" # Default 100 - prev 50 - 0 =>unlimited | decrease if the flow rises SLEEPBETWEENMSGS="100000" # microseconds - prev 5000 | increase if the flow does so # prev 5000 => but blocking the XYMON server # prev 10000 => No more blocking but false alerts Config on the XYMOn server # Pbl semaphore avec "209715200" => que faire ?? MAXLINE="209715200" # Previous value - 10485760 # Max size of a checkpoint files: 50M => 52428800 # but mux be double: current + the next one MAXMSG_CLIENT="209715200" MAXMSG_DATA="209715200" MAXMSG_STATUS="209715200" MAXMSG_STACHG="209715200" # No reason to change - Current value of the MAXMSG_STATUS setting ( 256 ) MAXMSG_NOTES="1229056" # Not used ? MAXMSG_PAGE="209715200" # No reason to change - Current value of the MAXMSG_STATUS setting ( 256 ) MAXMSG_ENADIS="614656" # Not used ? MAXMSG_CLICHG="209715200" # Default: Current value of the MAXMSG_CLIENT setting ( 512 ) Cordialement, Regards,Mit freundlichen Grüßen, Gautier BEGIN Global Service Support Solutions - Tools Support CACEIS and APERAM accounts CSC Computer Sciences Luxembourg S.A. 12D Impasse Drosbach L-1882 Luxembourg Global Outsourcing Service | p:+352 24 834 276 | m:+352 621 229 172 | gbegin at csc.com | 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 Computer Sciences SAS • Registered Office: Immeuble Le Balzac, 10 Place des Vosges, 92072 Paris La Défense Cedex, France • Registered in France: RCS Nanterre B 315 268 664 From: John Horne <john.horne at plymouth.ac.uk> To: xymon at xymon.com Date: 04/01/2015 04:37 PM Subject: Re: [Xymon] ps output cut Sent by: "Xymon" <xymon-bounces at xymon.com> On Wed, 2015-04-01 at 15:11 +0200, Gautier Begin wrote: > > On machines having a long ps output, the output arrived cut in the > XYMON server, provoking false alert on the check of the presence of > processes. > How to solve that ? > Increase the 'MAXMSG_CLIENT' setting in 'xymonserver.cfg'. The xymonserver.cfg man page has details about it: https://www.xymon.com/help/manpages/man5/xymonserver.cfg.5.html John. -- John Horne Tel: +44 (0)1752 587287 Plymouth University, UK _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

2 1

Documentation doesn't match behavior
by john.thurston＠alaska.gov 10 Apr '15

10 Apr '15

The man file for hosts.cfg describes the .default. option and explicitly states which tags are accepted. I have observed that with 4.3.17, delayred and delayyellow are also accepted. I don't object at all to having them accepted, but the documentation and the code should be reconciled. (I have not investigated 4.3.19 to see if this has already been done) As of 4.3.17, the man file says: > NOTE: The ".default." host entry will only accept the following tags - others are silently ignored: > NOCOLUMNS > COMMENT > DESCR > CLASS > dialup > testip > nonongreen > nodisp > noinfo > notrends > TRENDS > NOPROPRED > NOPROPYELLOW > NOPROPPURPLE > NOPROPACK > REPORTTIME > WARNPCT > NET > noclear > nosslcert > ssldays > DOWNTIME > depends > noping > noconn > trace > notrace > HIDEHTTP > browser > pulldata -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Administration State of Alaska

2 1

Accessing availabitlity or snapshot reports
by dirk.kastens＠uni-osnabrueck.de 10 Apr '15

10 Apr '15

> /var/cache/xymon(/.*)? system_u:object_r:httpd_cache_t:s0 I found a solution. I changed the file context of the cache directories to httpd_sys_rw_content_t and now the reports are working: semanage fcontext -a -t httpd_sys_rw_content_t "/var/cache/xymon/rep(/.*)?" semanage fcontext -a -t httpd_sys_rw_content_t "/var/cache/xymon/snap(/.*)?" restorecon -R -v /var/cache/xymon Is this an error in the Therabitia RPMs? Dirk

2 2

Red alert delay.
by eliap09＠yahoo.com 09 Apr '15

09 Apr '15

Thanks much Phil, that solved my issue. Phil Crooker <Phil.Crooker at orix.com.au> wrote: > > >Ah, understand now. Have a look at the host.cfg man page: > > >delayred=STATUSCOLUMN:DELAY[,STATUSCOLUMN:DELAY...]Usually, status changes happen immediately. This tag is used to defer an update to red for the STATUSCOLUMN status for DELAY minutes. E.g. with delayred=disk:10,cpu:30, a red disk-status will not appear on the Xymon webpages until it has been red for at least 10 minutes. Note: Since most tests only execute once every 5 minutes, it will usually not make sense to set N to anything but a multiple of 5. The exception is network tests, since xymonnet-again.sh(1) will re-run failed network tests once a minute for up to 30 minutes. > >However, this probably isn't what you want either as I assume you are querying the status directly via xymon. Your script can use the xymon xymondlog message (see the man page on xymon), the first line returned has the status times in Unix seconds: > > ># xymon 127.0.0.1 "xymondlog hostname.com.cpu" >hostname.com|cpu|green||1428554585|1428561954|1428563754|0|0|10.9.8.7||||Y| > >You can pick out the lastchange column and calculate if it has been 15 mins. > > >cheers, Phil > >From: Eli <eliap09 at yahoo.com> >Sent: Thursday, 9 April 2015 1:31 PM >To: Phil Crooker >Cc: xymon at xymon.com >Subject: Re: [Xymon] Red alert delay. > > > >Thanks Phil, I am looking delay on color change not on alarm. I have script monitoring the color change and act on it. > > >Sent from my Verizon Wireless 4G LTE DROID > > > >Phil Crooker <Phil.Crooker at orix.com.au> wrote: > > >>Hi all, >>I do want to delay CPU load red alert. As you know the default yellow or red based on the >threshold number but I want that include time delay. If the CPU load 9 and stay like that for 15 >min the color to change red instead of turn red immidiatly reach 8. >> >>Current setup >> >>Load. 6.0 9.0 >> >>For idle >> >>DS CPU vmstat.rrd:CPU_IDL <10 color=red "TEXT=CPU usage critical" >> >>Thanks >>--------------------------------------- > >Have a look at the help text in alerts.cfg. You can use the DURATION flag: > ># A sample rule: ># ># HOST=www.foo.com SERVICE=http ># MAIL webadmin at foo.com REPEAT=20 RECOVERED ># MAIL cio at foo.com DURATION>60 COLOR=red ># SCRIPT /usr/local/bin/sendsms 1234567890 FORMAT=SMS > >cheers. >-- > >This message from ORIX Australia might contain confidential and/or >privileged information. If you are not the intended recipient, any use, >disclosure or copying of this message (or of any attachments to it) is >not authorised. > >If you have received this message in error, please notify the sender >immediately and delete the message and any attachments from your >system. Please inform the sender if you do not wish to receive future >communications by email. > >ORIX handles personal information according to a Privacy Policy that is >consistent with the National Privacy Principles. Please let us know if >you would like a copy. It is also available at http://www.orix.com.au . > >

1 0

Graphs (PCU,MEM,TEMP etc.)
by cleaver＠terabithia.org 09 Apr '15

09 Apr '15

On Fri, April 3, 2015 2:23 am, Ales Krek wrote: > I have a problem.I have red hosts.cfg help file but still don't know how > to get cpu, memory etc. graphs on my xymon server page. For now i want to > monitor just Xymon Server. > > I really need help with that. > > I tried a lot of different things but no success. > Thank you all for your patience and support, > AleÅ¡ Krek. > > Â > Assuming the web pages are up and running and being updated every few minutes, and that xymond is showing up in the output of 'ps', you'll want to make sure that XYMONSERVERS is set to your localhost IP. If you compiled by hand, you would have been asked this on setup. If you installed via a package, it's probably located at /etc/default/xymon-client or /etc/sysconfig/xymon-client, depending on your distribution. You'll also want to take a look at the config / install guide: https://www.xymon.com/help/xymon-config.html HTH, -jc

2 3

"Preview" button on Enable/Disable
by john.r.rothlisberger＠accenture.com 09 Apr '15

09 Apr '15

What is the intention of the "Preview" check box when Enabling/Disabling clients? Personally, I have never used it and never had a need to. But, one of my coworkers did and was confused by its behavior. I did a quick test, selecting multiple hosts, a single test, filled in the reason, set a time, clicked in the preview button, and then finally apply. That takes me to a page that shows something like this: Disabling host <myclient> test *: OK Then when you click on continue, it takes you back to the Enable/Disable screen with everything that was already selected cleared out. Again, I don't use it. But someone else may. Thanks, John Upcoming PTO: _____________________________________________________________________ John Rothlisberger IT Strategy, Infrastructure & Security - Technology Growth Platform TGP for Business Process Outsourcing Accenture 312.693.3136 office _____________________________________________________________________ ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. ______________________________________________________________________________________ www.accenture.com

1 0

Accessing availabitlity or snapshot reports
by dirk.kastens＠uni-osnabrueck.de 09 Apr '15

09 Apr '15

Hi, I'm not able to access the availability or snapshot reports through the web interface (Xymon 4.3.19-3.el6.terabithia). When I click on "Generate report", the web browser shows the message "Forbidden. You don't have permission to access /xymon/rep/27957-1428575496/ on this server." When I look at the directory /var/cache/xymon/rep/27957-1428575496, there's a symbolic link "index.html -> xymon.html". But the file xymon.html doesn't exist. There's only the empy file xymon.html.tmp. The same happens with the snapshot reports under /var/cache/xymon/snap. Any idea what could be wrong? Regards, Dirk

2 2

Red alert delay.
by eliap09＠yahoo.com 09 Apr '15

09 Apr '15

Thanks Phil, I am looking delay on color change not on alarm. I have script monitoring the color change and act on it. Sent from my Verizon Wireless 4G LTE DROID Phil Crooker <Phil.Crooker at orix.com.au> wrote: > >>Hi all, >>I do want to delay CPU load red alert. As you know the default yellow or red based on the >threshold number but I want that include time delay. If the CPU load 9 and stay like that for 15 >min the color to change red instead of turn red immidiatly reach 8. >> >>Current setup >> >>Load. 6.0 9.0 >> >>For idle >> >>DS CPU vmstat.rrd:CPU_IDL <10 color=red "TEXT=CPU usage critical" >> >>Thanks >>--------------------------------------- > >Have a look at the help text in alerts.cfg. You can use the DURATION flag: > ># A sample rule: ># ># HOST=www.foo.com SERVICE=http ># MAIL webadmin at foo.com REPEAT=20 RECOVERED ># MAIL cio at foo.com DURATION>60 COLOR=red ># SCRIPT /usr/local/bin/sendsms 1234567890 FORMAT=SMS > >cheers. >-- > >This message from ORIX Australia might contain confidential and/or >privileged information. If you are not the intended recipient, any use, >disclosure or copying of this message (or of any attachments to it) is >not authorised. > >If you have received this message in error, please notify the sender >immediately and delete the message and any attachments from your >system. Please inform the sender if you do not wish to receive future >communications by email. > >ORIX handles personal information according to a Privacy Policy that is >consistent with the National Privacy Principles. Please let us know if >you would like a copy. It is also available at http://www.orix.com.au . > >

2 1