July 2012 - Xymon - Xymon mailman web

Bug in ping tests?
by josh＠imaginenetworksllc.com 18 Jul '12

18 Jul '12

I have a front page with about a dozen hosts and then sub pages. Every CONN test on the front page failed. Each and every host on the subpages (well over a dozen) was just fine. After 6 minutes I restarted the hobbitd processes. They all came right back. I am running 4.2.3. Using fping to check - hobbitserver.cfg:FPING="/usr/sbin/fping" Has anyone seen this? Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373

3 8

Xymon 4.3.8 available
by henrik＠hswn.dk 18 Jul '12

18 Jul '12

Hi, I have uploaded a 4.3.8 maintenance-release of Xymon to Sourceforge. It should be available by the time you read this. This release is an attempt to pick up the various patches and fixes that have appeared since the 4.3.7 release. Some issues - especially the problem with DNS timeouts - seemed important enough to warrant a maintenance release. This release should also fix some build-problems that have occurred on some systems (e.g. newer Ubuntu systems). The build-scripts were backported from the current "trunk" version, so they haven't had as much testing as the rest of the code - if you run into problems, let me know. I know of one issue on older Red Hat Linux versions, where the PCRE include-files are not found automatically; adding "--pcreinclude /usr/include/pcre" to the configure-command should fix this. There are also some enhancements, most notably the Enable/Disable page now allows you to select a specific time when the disable expires, instead of a time-interval; inode-monitoring now works on Linux clients (no other platforms, unfortunately); and the SSL certificate checks can now check the size of the certificate public key. Several of these fixes and enhancements were contributed by members of the community - I am very pleased to see Xymon development being done by others than just myself. The full list of bugfixes, enhancements and file hashes are below. Regards, Henrik Bugfixes * Workaround for DNS timeout handling, now fixed at approximately 25 seconds. * "hostinfo" command for xymond documented * confreport only shows processes that are monitored * analysis.cfg parsing of COLOR for UP rules was broken * RRD handlers no longer crash after receiving 1 billion updates * Using .netrc for authentication could crash xymonnet * "directory" includes would report the wrong filename for missing directories. * useradm CGI would invoke htpassword twice * "include" and "directory" now ignores trailing whitespace * SSLv2 support disabled if SSL-library does not support it * Minor bugfixes and cleanups of compiler warnings. Enhancements * Service status on info page now links to the detailed status page. * Add RRDGRAPHOPTS setting to permit global user-specified RRD options, e.g. for font to showgraph CGI * Add check for the size of public keys used in SSL certificates (enabled via --sslkeysize=N option for xymonnet) * Optionally disable the display of SSL ciphers in the sslcert status (the --no-cipherlist option for xymonnet) * Improved build-scripts works on newer systems with libraries in new and surprising places * Reduce xymonnet memory usage and runtime for ping tests when there are multiple hosts.cfg entries with the same IP-address. * Add code for inode-monitoring on Linux. Does not currently work on any other client platform. * Added the ability to disable tests until a specific time, instead of for some interval. Disabling a test also now computes the expire time for the disable to happen at the next closest minute. SHA1 hashes: b9bc428090c53c1938ac965f04affa293917c2ac xymon-4.3.8.tar.gz 9a2ad2ebbed5e6796813810a3650bb5cce739f86 xymon_4.3.8_amd64.deb ac1418540c0f45de387b079499b9d8efec234963 xymon-client_4.3.8_amd64.deb e68f45327d8682a809cd8c800857b30bbdeb6c60 xymon_4.3.8_i386.deb 1e3df6d93747d9a8f87df91c48ab82bc901e775b xymon-client_4.3.8_i386.deb MD5 hashes: fbd59ca20083a31442f9d1fb37c8c859 xymon-4.3.8.tar.gz 92c4297a8f7588ab40240fbc573b721d xymon_4.3.8_amd64.deb 3ac5bbdd997aa449dc8da9b140792e2f xymon-client_4.3.8_amd64.deb 3d74acee2450311445377ad120d31d90 xymon_4.3.8_i386.deb 42ef4f5a85460aabc4f2711f1788d24d xymon-client_4.3.8_i386.deb

4 7

xymonnet build error FC17 on 4.3.8
by marty.litchfield＠gcsu.edu 18 Jul '12

18 Jul '12

I'm getting the following build error on Fedora 17: /bin/ld: note: 'ber_free' is defined in DSO /lib64/liblber-2.4.so.2 so try adding it to the linker command line /lib64/liblber-2.4.so.2: could not read symbols: Invalid operation collect2: error: ld returned 1 exit status make[1]: *** [xymonnet] Error 1 make[1]: Leaving directory `/home/mlitchfi/xymon-4.3.8/rpmbuild/BUILD/xymon-4.3.8/xymonnet' make: *** [xymonnet-build] Error 2 error: Bad exit status from /tmp/rpm-tmp.NPU9fZ (%build) 4.3.7 build with no issues. What changed? -Marty

2 1

xymon <svcs> Order
by Angela.L.Lindsey＠ocio.usda.gov 17 Jul '12

17 Jul '12

I noticed that when I added some new services to my bbwin.cfg file to be monitored in xymon they are not in the same order as I have them listed in the .cfg when looking at the web interface. How can I get what I see on the web to match what I put in the cfg file? [cid:image003.jpg at 01CD6421.5B114810] Example: What I have in the .cfg <setting name="HTTP SSL" value="started" autoreset="false" alarmcolor="red" /> <setting name="World Wide Web Publishing Service" value="started" autoreset="false" alarmcolor="red" /> <setting name="IIS Admin Service" value="started" autoreset="false" alarmcolor="red" /> <setting name="IDC Content Admin Service steldevc3_admin-oirecmsdvwa07" value="started" autoreset="false" alarmcolor="red" /> <setting name="IDC Content Admin Service steldevc4_admin-oirecmsdvwa07" value="started" autoreset="false" alarmcolor="red" /> <setting name="IDC Content Admin Service steldevc5_admin-oirecmsdvwa07" value="started" autoreset="false" alarmcolor="red" /> <setting name="IDC Content Admin Service steldevd1_admin-oirecmsdvwa07" value="started" autoreset="false" alarmcolor="red" /> <setting name="IDC Content Admin Service steldevd3_admin-oirecmsdvwa07" value="started" autoreset="false" alarmcolor="red" /> <setting name="IDC Content Service steldevc3_master-oirecmsdvwa07" value="started" autoreset="false" alarmcolor="red" /> <setting name="IDC Content Service steldevc4_master-oirecmsdvwa07" value="started" autoreset="false" alarmcolor="red" /> <setting name="IDC Content Service steldevc5_master-oirecmsdvwa07" value="started" autoreset="false" alarmcolor="red" /> <setting name="IDC Content Service steldevd1_master-oirecmsdvwa07" value="started" autoreset="false" alarmcolor="red" /> <setting name="IDC Content Service steldevd3_master-oirecmsdvwa07" value="started" autoreset="false" alarmcolor="red" /> Thank You, Angela Lindsey Oracle Enterprise Content Management USDA/NITC Contractor 816.926.2322 Angela.L.Lindsey at ocio.usda.gov<mailto:Angela.L.Lindsey at ocio.usda.gov> This electronic message contains information generated by the USDA solely for the intended recipients. Any unauthorized interception of this message or the use or disclosure of the information it contains may violate the law and subject the violator to civil or criminal penalties. If you believe you have received this message in error, please notify the sender and delete the email immediately.

1 0

Possible Xymon 4.3.8 build/ldap.sh bug
by novosirj＠umdnj.edu 17 Jul '12

17 Jul '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Tried configure.server on a machine running Solaris 10 x86 that I plan to upgrade from 4.2.3 today and had it crash out during the LDAP section. As it turns out, I had no LDAP libraries at all on the machine. This was the result (I did configure.server with -x to show the commands being run -- I'm only showing the LDAP section which is the final part that ran): + . build/ldap.sh + echo Checking for LDAP ... Checking for LDAP ... LDAPINC= LDAPLIB= + test -f /opt/openldap*/include/ldap.h + test -f /opt/openldap*/lib/libldap.so + test -f /opt/openldap*/lib/libldap.a + test -f /opt/openldap*/lib64/libldap.so + test -f /opt/openldap*/lib64/libldap.a + test -f /opt/ldap*/include/ldap.h + test -f /opt/ldap*/lib/libldap.so + test -f /opt/ldap*/lib/libldap.a + test -f /opt/ldap*/lib64/libldap.so + test -f /opt/ldap*/lib64/libldap.a + test -f /usr/local/openldap*/include/ldap.h + test -f /usr/local/openldap*/lib/libldap.so + test -f /usr/local/openldap*/lib/libldap.a + test -f /usr/local/openldap*/lib64/libldap.so + test -f /usr/local/openldap*/lib64/libldap.a + test -f /usr/local/ldap*/include/ldap.h + test -f /usr/local/ldap*/lib/libldap.so + test -f /usr/local/ldap*/lib/libldap.a + test -f /usr/local/ldap*/lib64/libldap.so + test -f /usr/local/ldap*/lib64/libldap.a + test -f /usr/local/include/ldap.h + test -f /usr/local/lib/libldap.so + test -f /usr/local/lib/libldap.a + test -f /usr/local/lib64/libldap.so + test -f /usr/local/lib64/libldap.a + test -f /usr/pkg/include/ldap.h + test -f /usr/pkg/lib/libldap.so + test -f /usr/pkg/lib/libldap.a + test -f /usr/pkg/lib64/libldap.so + test -f /usr/pkg/lib64/libldap.a + test -f /opt/csw/include/ldap.h + test -f /opt/csw/lib/libldap.so + test -f /opt/csw/lib/libldap.a + test -f /opt/csw/lib64/libldap.so + test -f /opt/csw/lib64/libldap.a + test -f /opt/sfw/include/ldap.h + test -f /opt/sfw/lib/libldap.so + test -f /opt/sfw/lib/libldap.a + test -f /opt/sfw/lib64/libldap.so + test -f /opt/sfw/lib64/libldap.a + test != + test != + test -f /liblber.a + test -f /liblber.so LDAPOK=YES + test ! -z ./configure.server: test: argument expected Installing Blastwave's CSWoldaprt package solved the problem (it contains the following files): /opt/csw/include /opt/csw/include/lber.h /opt/csw/include/lber_types.h /opt/csw/include/ldap.h /opt/csw/include/ldap_cdefs.h /opt/csw/include/ldap_features.h /opt/csw/include/ldap_schema.h /opt/csw/include/ldap_utf8.h /opt/csw/include/slapi-plugin.h /opt/csw/lib /opt/csw/lib/amd64 /opt/csw/lib/amd64/liblber-2.4.so.2 /opt/csw/lib/amd64/liblber-2.4.so.2.4.2 /opt/csw/lib/amd64/liblber.a /opt/csw/lib/amd64/liblber.la /opt/csw/lib/amd64/liblber.so /opt/csw/lib/amd64/libldap-2.4.so.2 /opt/csw/lib/amd64/libldap-2.4.so.2.4.2 /opt/csw/lib/amd64/libldap.a /opt/csw/lib/amd64/libldap.la /opt/csw/lib/amd64/libldap.so /opt/csw/lib/amd64/libldap_r-2.4.so.2 /opt/csw/lib/amd64/libldap_r-2.4.so.2.4.2 /opt/csw/lib/amd64/libldap_r.a /opt/csw/lib/amd64/libldap_r.la /opt/csw/lib/amd64/libldap_r.so /opt/csw/lib/liblber-2.3.so /opt/csw/lib/liblber-2.3.so.0 /opt/csw/lib/liblber-2.3.so.0.2.27 /opt/csw/lib/liblber-2.4.so.2 /opt/csw/lib/liblber-2.4.so.2.4.2 /opt/csw/lib/liblber.a /opt/csw/lib/liblber.la /opt/csw/lib/liblber.so /opt/csw/lib/libldap-2.3.so /opt/csw/lib/libldap-2.3.so.0 /opt/csw/lib/libldap-2.3.so.0.2.27 /opt/csw/lib/libldap-2.4.so.2 /opt/csw/lib/libldap-2.4.so.2.4.2 /opt/csw/lib/libldap.a /opt/csw/lib/libldap.la /opt/csw/lib/libldap.so /opt/csw/lib/libldap_r-2.3.so /opt/csw/lib/libldap_r-2.3.so.0 /opt/csw/lib/libldap_r-2.3.so.0.2.27 /opt/csw/lib/libldap_r-2.4.so.2 /opt/csw/lib/libldap_r-2.4.so.2.4.2 /opt/csw/lib/libldap_r.a /opt/csw/lib/libldap_r.la /opt/csw/lib/libldap_r.so Now if I run configure.server now, after those files are installed, I get the following: + . build/ldap.sh + echo Checking for LDAP ... Checking for LDAP ... LDAPINC= LDAPLIB= + test -f /opt/openldap*/include/ldap.h + test -f /opt/openldap*/lib/libldap.so + test -f /opt/openldap*/lib/libldap.a + test -f /opt/openldap*/lib64/libldap.so + test -f /opt/openldap*/lib64/libldap.a + test -f /opt/ldap*/include/ldap.h + test -f /opt/ldap*/lib/libldap.so + test -f /opt/ldap*/lib/libldap.a + test -f /opt/ldap*/lib64/libldap.so + test -f /opt/ldap*/lib64/libldap.a + test -f /usr/local/openldap*/include/ldap.h + test -f /usr/local/openldap*/lib/libldap.so + test -f /usr/local/openldap*/lib/libldap.a + test -f /usr/local/openldap*/lib64/libldap.so + test -f /usr/local/openldap*/lib64/libldap.a + test -f /usr/local/ldap*/include/ldap.h + test -f /usr/local/ldap*/lib/libldap.so + test -f /usr/local/ldap*/lib/libldap.a + test -f /usr/local/ldap*/lib64/libldap.so + test -f /usr/local/ldap*/lib64/libldap.a + test -f /usr/local/include/ldap.h + test -f /usr/local/lib/libldap.so + test -f /usr/local/lib/libldap.a + test -f /usr/local/lib64/libldap.so + test -f /usr/local/lib64/libldap.a + test -f /usr/pkg/include/ldap.h + test -f /usr/pkg/lib/libldap.so + test -f /usr/pkg/lib/libldap.a + test -f /usr/pkg/lib64/libldap.so + test -f /usr/pkg/lib64/libldap.a + test -f /opt/csw/include/ldap.h LDAPINC=/opt/csw/include + test -f /opt/csw/lib/libldap.so LDAPLIB=/opt/csw/lib + test -f /opt/csw/lib/libldap.a LDAPLIB=/opt/csw/lib + test -f /opt/csw/lib64/libldap.so + test -f /opt/csw/lib64/libldap.a + test -f /opt/sfw/include/ldap.h + test -f /opt/sfw/lib/libldap.so + test -f /opt/sfw/lib/libldap.a + test -f /opt/sfw/lib64/libldap.so + test -f /opt/sfw/lib64/libldap.a + test != + test != + test -f /opt/csw/lib/liblber.a LDAPLBER=-llber + test -f /opt/csw/lib/liblber.so LDAPLBER=-llber LDAPOK=YES + test ! -z /opt/csw/include INCOPT=-I/opt/csw/include + test ! -z /opt/csw/lib LIBOPT=-L/opt/csw/lib + cd build + gmake -f Makefile.test-ldap clean + uname -s + tr [/] [_] OS=SunOS + gmake -f Makefile.test-ldap test-compile + test 0 -eq 0 + echo Compiling with LDAP works OK Compiling with LDAP works OK + gmake -f Makefile.test-ldap test-link + test 2 -eq 0 + echo WARNING: Cannot link with LDAP WARNING: Cannot link with LDAP LDAPOK=NO + gmake -f Makefile.test-ldap clean + uname -s + tr [/] [_] OS=SunOS + cd .. + test NO = NO + echo (Open)LDAP include- or library-files not found. (Open)LDAP include- or library-files not found. + echo If you want to perform detailed LDAP tests (queries), you need to If you want to perform detailed LDAP tests (queries), you need to + echo install LDAP an LDAP client library that Xymon can use. install LDAP an LDAP client library that Xymon can use. + echo OpenLDAP can be found at http://www.openldap.org/ OpenLDAP can be found at http://www.openldap.org/ + echo + echo If you have OpenLDAP installed, use the "--ldapinclude DIR" and "--ldaplib DIR" If you have OpenLDAP installed, use the "--ldapinclude DIR" and "--ldaplib DIR" + echo options to configure to specify where they are. options to configure to specify where they are. + echo + sleep 3 + echo Continuing with LDAP support disabled. Continuing with LDAP support disabled. + test NO = NO ENABLELDAP=n LDAPDEF= I don't know if this is a Solaris-only problem or not, but it seems like this script should do much the same thing in either circumstance, no (the former where I have no LDAP installed at all and the latter where I have only the runtimes installed)? - -- - ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAFolMACgkQmb+gadEcsb7ALACgtg7uNik4aeTFYUAtHtdqPXAZ tzUAmQGYf1iPrXNYLuDSto/BoIjOlb1/ =oEoJ -----END PGP SIGNATURE-----

1 0

Client pulldata, no data?
by Marco.Schoemaker＠nlr.nl 17 Jul '12

17 Jul '12

I started looking for the "Duplicate client message" and based on the source code of xymond_client.c decided to remove the "--local" flag from the xymonclient.sh command line in clientlaunch.cfg. Data is now pulled succesfully by the server. Marco Schoemaker ****************************************************************************************************************** The NLR disclaimer is valid for NLR e-mail messages. This message is only meant for providing information. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of the sender. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. Sender accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. ******************************************************************************************************************

1 0

Conn test fails after server reboot
by john.horne＠plymouth.ac.uk 17 Jul '12

17 Jul '12

Hello, Using Xymon 4.3.7 I have noticed that if I reboot the Xymon server then the 'conn' test fails for all the clients. E.g.: ============================ Thu Jul 12 10:24:11 2012 conn NOT ok Service conn on dns1 is not OK : Host does not respond to ping System unreachable for 5 poll periods (984 seconds) ============================ If, from the server, I run 'ping' to the client then that works fine. So does fping. If I stop then start the Xymon service on the server then the client conn tests all report ok. Any ideas about this? John. -- John Horne Tel: +44 (0)1752 587287 Plymouth University, UK Fax: +44 (0)1752 587001

5 9

Client pulldata, no data?
by Marco.Schoemaker＠nlr.nl 17 Jul '12

17 Jul '12

Thanks in advance for your time and patience (i hope :) I'm trying to get xymonfetch working, but no data seems to be pulled into the server. Can anybody give me a hint to good documentation/examples/...? I've googled a lot the past days and see more questions about pull, but no solutions. Server runs 4.3.7, client runs 4.3.8. On the server i added "pulldata xymonfetch" to the client tags. On the client i have clientlaunch.cfg: [msgcache] ENVFILE $XYMONCLIENTHOME/etc/xymonclient.cfg CMD $XYMONCLIENTHOME/bin/msgcache --debug --no-daemon --pidfile=$XYMONCLIENTLOGS/msgcache.pid LOGFILE $XYMONCLIENTLOGS/msgcache.log # The main client task [client] ENVFILE $XYMONCLIENTHOME/etc/xymonclient.cfg CMD $XYMONCLIENTHOME/bin/xymonclient.sh --local --debug LOGFILE $XYMONCLIENTLOGS/xymonclient.log INTERVAL 5m and xymonclient.cfg states XYMSRV="127.0.0.1". On the client, msgcache.log shows: 26961 2012-07-17 08:34:15 Saved client response: 26961 2012-07-17 08:34:15 -> oksender 26961 2012-07-17 08:34:15 <- oksender(1-a) 26961 2012-07-17 08:34:15 Got pullclient request: pullclient 1 and xymonclient.log shows (5 minute interval): 26296 2012-07-17 08:33:52 Want msg 1, startpos 0, fillpos 0, endpos -1, usedbytes=0, bufleft=528383 26296 2012-07-17 08:33:52 Got 34742 bytes 26296 2012-07-17 08:33:52 /home/xymon/client/bin/xymond_client: Got message 1 @@client#1|0|127.0.0.1|sodn159u|linux 26296 2012-07-17 08:33:52 startpos 34742, fillpos 34742, endpos -1 26296 2012-07-17 08:33:52 Opening file /home/xymon/client/etc/localclient.cfg 26296 2012-07-17 08:33:52 Client report from host sodn159u 26296 2012-07-17 08:33:52 sodn159u: Duplicate client message at time 0, seq 1, lastseq 0 26296 2012-07-17 08:33:52 Want msg 2, startpos 34742, fillpos 34742, endpos -1, usedbytes=0, bufleft=493641 26296 2012-07-17 08:33:52 get_xymond_message: Returning NULL due to EOF Marco Schoemaker National Aerospace Laboratory NLR The Netherlands ****************************************************************************************************************** The NLR disclaimer is valid for NLR e-mail messages. This message is only meant for providing information. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of the sender. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. Sender accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. ******************************************************************************************************************

1 0

xymonnet Fatal signal caught
by sjpostsr＠gmail.com 16 Jul '12

16 Jul '12

I can definitely try downloading it/updating I don't have a ~xymon/data/tmp/ directory

1 0

Solaris 10 SPARC Xymon 4.3.8 build problem
by novosirj＠umdnj.edu 16 Jul '12

16 Jul '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I'm using gcc 3.4.3 and gmake 3.82 on Solaris 10 and I'm having difficulty. At first, I tried just copying the Makefile I used for Xymon 4.3.7 over and changing the 4.3.7 to 4.3.8 (I install in /opt/xymon-4.3.# and symlink /opt/xymon). That failed, so I tried starting from a configure. I get an error that says I don't have PCRE and to specify where it is. So I did: MAKE=/usr/sfw/bin/gmake ./configure.server --pcreinclude /opt/csw/include --pcrelib /opt/csw/lib ...but I still get the same error. I added -x to "configure.server" to see what was happening, and it looks like there's something wrong somewhere but I can't figure out what: + test /opt/csw/include != PCREINC=/opt/csw/include + test /opt/csw/lib != PCRELIB=/opt/csw/lib PCREOK=YES + cd build + test ! -z /opt/csw/include INCOPT=-I/opt/csw/include + test ! -z /opt/csw/lib LIBOPT=-L/opt/csw/lib + /usr/sfw/bin/gmake -f Makefile.test-pcre clean + tr [/] [_] + uname -s Bad string OS= Makefile.test-pcre:1: Makefile.: No such file or directory gmake: *** No rule to make target `Makefile.'. Stop. + /usr/sfw/bin/gmake -f Makefile.test-pcre test-compile PCREINC=-I/opt/csw/include + tr [/] [_] + uname -s Bad string OS= Makefile.test-pcre:1: Makefile.: No such file or directory gmake: *** No rule to make target `Makefile.'. Stop. + test 2 -eq 0 + echo ERROR: Cannot compile using PCRE library. ERROR: Cannot compile using PCRE library. PCREOK=NO + /usr/sfw/bin/gmake -f Makefile.test-pcre test-link PCRELIB=-L/opt/csw/lib + tr [/] [_] + uname -s Bad string OS= Makefile.test-pcre:1: Makefile.: No such file or directory gmake: *** No rule to make target `Makefile.'. Stop. + test 2 -eq 0 + echo ERROR: Cannot link with PCRE library. ERROR: Cannot link with PCRE library. PCREOK=NO + /usr/sfw/bin/gmake -f Makefile.test-pcre clean + tr [/] [_] + uname -s Bad string OS= Makefile.test-pcre:1: Makefile.: No such file or directory gmake: *** No rule to make target `Makefile.'. Stop. + cd .. + test NO = NO + echo Missing PCRE include- or library-files. These are REQUIRED for xymond Missing PCRE include- or library-files. These are REQUIRED for xymond + echo PCRE can be found at http://www.pcre.org/ PCRE can be found at http://www.pcre.org/ + echo If you have PCRE installed, use the "--pcreinclude DIR" and "--pcrelib DIR" If you have PCRE installed, use the "--pcreinclude DIR" and "--pcrelib DIR" + echo options to configure to specify where they are. options to configure to specify where they are. + exit 1 ...sorta looks like the fact that OS= winds up undefined is not a great thing. Anyone have any ideas? I did get 4.3.7 compiled, but I no longer remember if I had to do anything special. Thanks. - -- - ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAEbykACgkQmb+gadEcsb7xawCg40QI7xPBBS9TT4LTBEekyn2c yvAAn1E2B2zIZrirK9NS0hkv5nGLEJr/ =as74 -----END PGP SIGNATURE-----

2 7