August 2016 - Xymon - Xymon mailman web

Need help with upgrade from 4.3.17 to 4.3.20
by cleaver＠terabithia.org 17 Jul '18

17 Jul '18

Hmm. So far, the only way I've been able to reproduce this is by replacing the ScriptAlias directives with mere Alias's in the xymon.conf apache config. Has there been any change in the path you've used for the CGI directory since the previous version, or is there any chance that another Alias line is taking precedence over the ScriptAlias? Do you see anything in the apache access/error logs that indicates an error? -jc On Tue, May 19, 2015 10:37 am, Cortes, Manny wrote: > Having the same problem after installing 4.3.20 on both Ubuntu server > 14.04 and 15.04. > > Thanks, > > > Manuel A Cortes > > Systems Programmer III > > [IBM_Cert] > > IBM Certified System Administrator AIX 7 > > Information Services > > 321-841-6534 > > Orlandohealth.com > > Facebook.com/orlandohealth > > Youtube.com/orlandohealth > > @orlandohealth on twitter > > > > 1414 Kuhl Avenue.,MP136 > > Orlando, Florida 32806 > > From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Asif Iqbal > Sent: Tuesday, May 19, 2015 12:59 PM > To: J.C. Cleaver > Cc: xymon at xymon.com > Subject: Re: [Xymon] Need help with upgrade from 4.3.17 to 4.3.20 > > > > On Tue, May 19, 2015 at 12:40 PM, J.C. Cleaver > <cleaver at terabithia.org<mailto:cleaver at terabithia.org>> wrote: > Hmm. It seems like it's trying to pass along the binary rather than > actually execute it. Can you > > a) validate the permissions on the various .sh files inside the > /xymon-cgi/ directory. (Wondering if there's a case where make install > doesn't set permissions properly), and > > > /var/lib/xymon/cgi-bin$ ls -al > total 6560 > drwxr-xr-x 2 root root 4096 May 19 10:19 . > drwxr-xr-x 16 xymon xymon 4096 May 19 10:19 .. > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 acknowledgements.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 appfeed-critical.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 appfeed.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 certreport.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 columndoc.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 confreport-critical.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 confreport.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 criticalview.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 csvinfo.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 datepage.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 eventlog.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 findhost.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 ghostlist.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 historylog.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 history.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 hostgraphs.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 hostlist.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 nongreen.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 notifications.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 perfdata.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 reportlog.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 report.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 showgraph.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 snapshot.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 svcstatus.sh > -rwxr-xr-x 32 xymon xymon 255968 May 19 10:19 topchanges.sh > > > b) verify that the ScriptAlias or ExecCGI options are still present in > apache.conf. > > > grep xymon-cgi /etc/apache2/sites-enabled/xymon-apache.conf > # "/xymon" and "/xymon-cgi" URLs. > ScriptAlias /xymon-cgi/ "/var/lib/xymon/cgi-bin/" > RewriteRule ^/xymon-cgi/bb-hist.sh /xymon-cgi/history.sh [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-eventlog.sh /xymon-cgi/eventlog.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-rep.sh /xymon-cgi/report.sh [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-replog.sh /xymon-cgi/reportlog.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-snapshot.sh /xymon-cgi/snapshot.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-findhost.sh /xymon-cgi/findhost.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-csvinfo.sh /xymon-cgi/csvinfo.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbitcolumn.sh /xymon-cgi/columndoc.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-datepage.sh /xymon-cgi/datepage.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbitgraph.sh /xymon-cgi/showgraph.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-hostsvc.sh /xymon-cgi/svcstatus.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/bb-histlog.sh /xymon-cgi/historylog.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-confreport.sh /xymon-cgi/confreport.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-confreport-critical.sh > /xymon-cgi/confreport-critical.sh [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-nkview.sh /xymon-cgi/criticalview.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-certreport.sh /xymon-cgi/certreport.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-nongreen.sh /xymon-cgi/nongreen.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-hostgraphs.sh /xymon-cgi/hostgraphs.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-ghosts.sh /xymon-cgi/ghostlist.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-notifylog.sh /xymon-cgi/notifications.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-hostlist.sh /xymon-cgi/hostlist.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-perfdata.sh /xymon-cgi/perfdata.sh > [R=permanent,L] > RewriteRule ^/xymon-cgi/hobbit-topchanges.sh /xymon-cgi/topchanges.sh > [R=permanent,L] > > > HTH, > > -jc > > > On Tue, May 19, 2015 7:56 am, Asif Iqbal wrote: >> I am not sure what I need to after the upgrade for the columns to show >> data >> instead of >> something like this >> >> >> ELF ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½>ï¿½ ï¿½ï¿½ï¿½ >> @ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ Ã >> ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½8ï¿½ ï¿½@ï¿½%ï¿½"ï¿½ ï¿½ï¿½ï¿½ >> ï¿½ï¿½ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½Ã¸ >> ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½Ã¸ ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ >> ï¿½ï¿½ï¿½8 ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½8 >> @ï¿½ï¿½ï¿½ï¿½ï¿½8 @ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ >> ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ >> ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½@ï¿½ï¿½ï¿½ï¿½ï¿½Ã¤Ã¤ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½Ã¤Ã¤ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ >> >> I removed FollowSymLinks from xymon-apache.conf file under /xymon-cgi/ >> and /xymon-seccgi/ and restarted. >> >> I am using ubuntu >> >> -- >> Asif Iqbal >> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu<http://pgp.mit.edu> >> A: Because it messes up the order in which people normally read text. >> Q: Why is top-posting such a bad thing? >> _______________________________________________ >> Xymon mailing list >> Xymon at xymon.com<mailto:Xymon at xymon.com> >> http://lists.xymon.com/mailman/listinfo/xymon >> > > > > > -- > Asif Iqbal > PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu<http://pgp.mit.edu> > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > > ________________________________ > > This e-mail message and any attached files are confidential and are > intended solely for the use of the addressee(s) named above. If you are > not the intended recipient, any review, use, or distribution of this > e-mail message and any attached files is strictly prohibited. > > This communication may contain material protected by Federal privacy > regulations, attorney-client work product, or other privileges. If you > have received this confidential communication in error, please notify the > sender immediately by reply e-mail message and permanently delete the > original message. To reply to our email administrator directly, send an > email to: postmaster at orlandohealth.com . > > If this e-mail message concerns a contract matter, be advised that no > employee or agent is authorized to conclude any binding agreement on > behalf of Orlando Health by e-mail without express written confirmation by > an officer of the corporation. Any views or opinions presented in this > e-mail are solely those of the author and do not necessarily represent > those of Orlando Health. >

8 25

Recovery notifications not generated when test goes red->yellow->green?
by hobbit＠elyograg.org 13 Dec '17

13 Dec '17

It appears that if a test goes from the red state, to the yellow state, and then to the green state, no recovery notification is sent. If it goes directly from red to green, then we get a notification. Initial notifications are only sent on RED and PURPLE. We have recovery notifications configured for most tests. Xymon server is 4.3.21, built using makerpm.sh and installed with yum on CentOS 6. I do not know whether our previous version (4.3.14) behaved similarly. It was almost an accident that I discovered the problem at all. Is this expected behavior? If it is, can I change it? Thanks, Shawn

4 3

CLASS not working as expected
by steve＠opendium.com 07 Nov '17

07 Nov '17

Under Xymon 4.3.25, I'm trying to use the class attribute to group hosts together by what monitoring and alerting they need. So for each host I have a hosts.cfg line like: 192.0.2.1 somehost.example.com # CLASS:Foo trace ssh Then in analysis.cfg I have: CLASS=Foo PROC this PROC that And alerts.cfg has: CLASS=Foo SCRIPT=blah However, the tests in analysis.cfg are not being applied. If I replace CLASS=Foo with HOST=somehost.example.com they work as expected. Also, CLASS=linux seems to work, which implies that the CLASS: directive in the hosts.cfg is being ignored. As far as I can tell, the messages on xymon's "client" channel don't contain the class name that was specified in hosts.cfg, so xymond_client is using the class that the client sent instead. Other channels, such as "status" do include the class name that was specified in hosts.cfg. Am I misunderstanding how the class is supposed to be used, or is this a bug? -- - Steve Hill Technical Director Opendium Limited http://www.opendium.com Direct contacts: Instant messager: xmpp:steve at opendium.com Email: steve at opendium.com Phone: sip:steve at opendium.com Sales / enquiries contacts: Email: sales at opendium.com Phone: +44-1792-824568 / sip:sales at opendium.com Support contacts: Email: support at opendium.com Phone: +44-1792-825748 / sip:support at opendium.com

6 7

DNS failures causing "runtime longer than time limit"
by jlaidman＠rebel-it.com.au 11 Sep '17

11 Sep '17

Hi I'm running Xymon v4.3.10 on Linux, and I'm quite sure it's compiled with c-ares support. I have 12 new DNS servers that were added to Xymon about one month ago. All of my server entries in hosts.cfg have "testip". The tasks.cfg runs xymonet with "--dns-timeout=3". The hosts entries look like so: 10.10.10.1 dnshost1.example.com # testip dns=NS:example.com,SOA: example.com About a week ago, connectivity to all of these servers failed, and at the same time, the xymonnet run time jumped from less than 15 seconds to about 330 seconds, so about 315 seconds extra. The xymonnet page says 295 seconds is taken up by DNS tests. If the increase in time taken is about 315 and is entirely due to the 12 servers failing, then each failed server is adding about 26 seconds to the total run time. I don't think this should be happening like this. With two DNS checks per server, the DNS checks should be taking 6 seconds each to time-out, not 26. If I run xymonnet with "--timing --no-update" and specify only one hostname, I can view the results and the timing. This shows that the ping check gets reported after about 3 seconds, and then the DNS tests are executed and take 26 seconds total. My naiive assumption was that when a server failed a ping (and didn't have "noclear" defined in hosts.cfg) then the network checks would be skipped. On re-reading the man page for hosts.cfg, it dawned on me that a failed ping simply suppresses failed test /results/, but doesn't stop the tests from being run. So the real problem is that the "--dns-timeout=3" is not being taken into consideration by xymonnet. If I run xymonnet with "--debug" it tells me: 1900 2015-06-03 12:02:20 ares_search: tlookup='example.com', class=1, type=2 1900 2015-06-03 12:02:20 ares_search: tlookup='example.com', class=1, type=6 1900 2015-06-03 12:02:20 Processing 0 DNS lookups with ARES 1900 2015-06-03 12:02:46 Finished ARES queue after loop 423 This is peculiar. Why would it say "processing 0 DNS lookups" when there are two lookups to test? Could this be because xymonnet hasn't actually been built with ARES support and I didn't know it? Is there a good way to tell? If I add "--no-ares" I get the same results perhaps suggesting a lack of ARES support. On the other hand, if I add "timeout:3" and "attempts:1" into resolv.conf, I also get the same results. If I run "nm /path/to/xymonnet | grep gethostby" it returns "ares_gethostbyname". Just for fun, I compiled Xymon v4.3.21 and ran the xymonnet binary from there, with no change in behaviour. I also tried removing the "--dns-timeout" option so that it defaults to 30 seconds, but still no change - 26 seconds for two DNS tests. So, I'm not really sure what the problem is, but xymonnet certainly isn't behaving as I would expect. Cheers Jeremy

2 3

Fwd: Bug#828611: xymon: Fails to build from source with OpenSSL 1.1.0
by abe＠debian.org 31 Oct '16

31 Oct '16

Hi, this has been reported in Debian at https://bugs.debian.org/828611 ----- Forwarded message from Kurt Roeckx <kurt at roeckx.be> ----- Date: Sun, 26 Jun 2016 12:24:54 +0200 From: Kurt Roeckx <kurt at roeckx.be> To: submit at bugs.debian.org Subject: Bug#828611: xymon: FTBFS with openssl 1.1.0 Reply-To: Kurt Roeckx <kurt at roeckx.be>, 828611 at bugs.debian.org Source: xymon Version: 4.3.27-1 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/xymon_4.3.27… On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt ----- End forwarded message ----- Regards, Axel -- ,''`. | Axel Beckert <abe at debian.org>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE

2 2

Unusual dnsreg behaviour
by rich＠corporationpop.co.uk 01 Sep '16

01 Sep '16

Hi all. I have recently added in the dnsreg script from the xymon.com site https://www.xymon.com/xymon-cgi/viewconf.sh?dnsreg All appears to be working well apart from I am getting some strange behaviour for a couple of domains. For some domains I am simply not receiving any data back, which is causing the test to show red with the following line of information: Domain somedomain.co.uk expires on Normally I would see the expiration date here, but it simply doesn't show. I have tested the domain using whois on the server, and this all returns fine. So I'm not too sure why this is happening. Any ideas? *Rich Jones* | Web Developer Corporation Pop 21-23 Shudehill Manchester M4 2AF 0161 838 0808 www.corporationpop.co.uk This email message (and any attached file) is intended only for the use of the individual or entity to whom the sender intended it to be addressed and may contain information that constitutes a trade secret, or that is privileged, confidential or subject to copyright. No part of it may be circulated, quoted, or reproduced without prior written approval from Corporation Pop Ltd. The contents of this document are strictly confidential and owned by Corporation Pop Ltd. Copyright © Corporation Pop Ltd. All rights reserved. Corporation Pop is a limited company registered in England + Wales. Company number 4869229. VAT number 533 8932 26.

4 5

Not able to access Xymon GUI
by mailnsa＠gmail.com 30 Aug '16

30 Aug '16

Hi Jeremy, Thanks for the quick update. But, I was waiting for 2hrs still I couldnt get the file. I even restarted the xymon and apache server. I'm still getting forbidden error. If I change the permissions of my xymon folder to 775 I can able to get the folder structure ... 😑 -- regards, Shankar http://discoveringweblogic.webs.com/ https://in.linkedin.com/in/shankar-anand-nagalingam-622b6833 On Tue, Aug 30, 2016 at 2:17 AM, Jeremy Laidman <jlaidman at rebel-it.com.au> wrote: > Shankar > > It takes a few minutes for xymongen to make the index.html. Until then you > usually get a directory listing. > > Cheers > Jeremy > > On Tue, 30 Aug 2016, 01:48 Shankar Shiva <mailnsa at gmail.com> wrote: > >> Hi Support, >> >> I'm working on the installation of xymon on AWS cloud. Below, is my >> system information:- >> >> *[root at ip-ip xymon]# arch* >> *x86_64* >> *[root at ip-ip xymon]# cat /etc/redhat-release* >> *Red Hat Enterprise Linux Server release 7.2 (Maipo)* >> *[root at ip-ip xymon]# uname -a* >> *Linux ip-ip.ap-south-1.compute.internal 3.10.0-327.10.1.el7.x86_64 #1 >> SMP Sat Jan 23 04:54:55 EST 2016 x86_64 x86_64 x86_64 GNU/Linux* >> *[root at ip-ip xymon]#* >> >> >> After extracting Xymon software, I executed ./configure --server, but I'm >> getting below exceptions:- >> *./configure --server --rrdinclude /root/rrdtool-1.5.5/* >> >> *Configuration script for Xymon* >> >> *This script asks a few questions and builds a Makefile to compile Xymon* >> >> *Checking your make-utility* >> *Checking pre-requisites for building Xymon* >> >> *Checking for fping ...* >> *Xymon has a built-in ping utility (xymonping)* >> *However, it is not yet fully stable and therefore it* >> *may be best to use the external fping utility instead.* >> *I could not find fping on your system* >> *Do you want to use xymonping [Y/n] ?* >> *y* >> *OK, I will use xymonping.* >> >> >> *Checking for PCRE ...* >> *Compiling with PCRE library works OK* >> *Linking with PCRE library works OK* >> >> >> *Checking for C-ARES library ...* >> *test-cares.c:5:18: fatal error: ares.h: No such file or directory* >> * #include <ares.h>* >> * ^* >> *compilation terminated.* >> *make: *** [test-compile] Error 1* >> *ERROR: Cannot compile using c-ares library.* >> *The system C-ARES library is missing or not usable. I will use the >> version shipped with Xymon* >> >> >> *Checking for RRDtool ...* >> *Not RRDtool 1.0.x, checking for 1.2.x* >> *test-rrd.c:3:17: fatal error: rrd.h: No such file or directory* >> * #include <rrd.h>* >> * ^* >> *compilation terminated.* >> *make: *** [test-compile] Error 1* >> *ERROR: Cannot compile with RRDtool.* >> *ERROR: Linking with RRDtool fails* >> *RRDtool include- or library-files not found.* >> *These are REQUIRED for trend-graph support in Xymon, but Xymon can* >> *be built without them (e.g. for a network-probe only installation.* >> >> *RRDtool can be found at http://oss.oetiker.ch/rrdtool/ >> <http://oss.oetiker.ch/rrdtool/>* >> *If you have RRDtool installed, use the "--rrdinclude DIR" and "--rrdlib >> DIR"* >> *options to configure to specify where they are.* >> >> *Continuing with all trend-graph support DISABLED* >> >> >> Since, system ignored this exceptions I continued with my other >> installation steps. But, post installation I'mnot getting the GUI screen. >> When I access the application with xymon context path I only get the folder >> structure. >> >> Could you please help me?/ >> >> -- >> regards, >> Shankar >> http://discoveringweblogic.webs.com/ >> https://in.linkedin.com/in/shankar-anand-nagalingam-622b6833 >> _______________________________________________ >> Xymon mailing list >> Xymon at xymon.com >> http://lists.xymon.com/mailman/listinfo/xymon > >

3 3

am unable to send mail
by velpulavenkat6＠gmail.com 30 Aug '16

30 Aug '16

Hi, Am unable to send xymon mail alerts to my gmail plz help any one. Regards Venkat

1 0

Not able to access Xymon GUI
by mailnsa＠gmail.com 29 Aug '16

29 Aug '16

Hi Support, I'm working on the installation of xymon on AWS cloud. Below, is my system information:- *[root at ip-ip xymon]# arch* *x86_64* *[root at ip-ip xymon]# cat /etc/redhat-release* *Red Hat Enterprise Linux Server release 7.2 (Maipo)* *[root at ip-ip xymon]# uname -a* *Linux ip-ip.ap-south-1.compute.internal 3.10.0-327.10.1.el7.x86_64 #1 SMP Sat Jan 23 04:54:55 EST 2016 x86_64 x86_64 x86_64 GNU/Linux* *[root at ip-ip xymon]#* After extracting Xymon software, I executed ./configure --server, but I'm getting below exceptions:- *./configure --server --rrdinclude /root/rrdtool-1.5.5/* *Configuration script for Xymon* *This script asks a few questions and builds a Makefile to compile Xymon* *Checking your make-utility* *Checking pre-requisites for building Xymon* *Checking for fping ...* *Xymon has a built-in ping utility (xymonping)* *However, it is not yet fully stable and therefore it* *may be best to use the external fping utility instead.* *I could not find fping on your system* *Do you want to use xymonping [Y/n] ?* *y* *OK, I will use xymonping.* *Checking for PCRE ...* *Compiling with PCRE library works OK* *Linking with PCRE library works OK* *Checking for C-ARES library ...* *test-cares.c:5:18: fatal error: ares.h: No such file or directory* * #include <ares.h>* * ^* *compilation terminated.* *make: *** [test-compile] Error 1* *ERROR: Cannot compile using c-ares library.* *The system C-ARES library is missing or not usable. I will use the version shipped with Xymon* *Checking for RRDtool ...* *Not RRDtool 1.0.x, checking for 1.2.x* *test-rrd.c:3:17: fatal error: rrd.h: No such file or directory* * #include <rrd.h>* * ^* *compilation terminated.* *make: *** [test-compile] Error 1* *ERROR: Cannot compile with RRDtool.* *ERROR: Linking with RRDtool fails* *RRDtool include- or library-files not found.* *These are REQUIRED for trend-graph support in Xymon, but Xymon can* *be built without them (e.g. for a network-probe only installation.* *RRDtool can be found at http://oss.oetiker.ch/rrdtool/ <http://oss.oetiker.ch/rrdtool/>* *If you have RRDtool installed, use the "--rrdinclude DIR" and "--rrdlib DIR"* *options to configure to specify where they are.* *Continuing with all trend-graph support DISABLED* Since, system ignored this exceptions I continued with my other installation steps. But, post installation I'mnot getting the GUI screen. When I access the application with xymon context path I only get the folder structure. Could you please help me?/ -- regards, Shankar http://discoveringweblogic.webs.com/ https://in.linkedin.com/in/shankar-anand-nagalingam-622b6833

1 0

analysis.cfg DISK statement
by bb4＠richter-it.net 29 Aug '16

29 Aug '16

An HTML attachment was scrubbed... URL: <http://lists.xymon.com/pipermail/xymon/attachments/20160829/9a915148/attach…>

1 0