Xymon Mailing List Archive search

Xymon crashes

3 messages in this thread

list Dlubbe · Sat, 30 Apr 2011 17:46:30 +0200 ·
Hi all,

I've got the following problem:

I used to run Xymon 4.2.3 on FreeBSD (using the ports collection) and it 
worked fine.
However, when I upgraded to 4.3.2, I got all sorts of weird behaviour, so 
I decided to start from scratch.

So I uninstalled Xymon, deleted everyting related to it and then installed 

a fresh copy of Xymon 4.3.2 (also via the port-collection)
The installation goes fine, but when I start it up, the html files aren't 
generated.
It seems that xymond crashes for reasons I don't understand

I did some digging and I see the following:

xymonlaunch.log:

2011-04-09 23:39:33 xymonlaunch starting
2011-04-09 23:39:33 Loading tasklist configuration from 
/usr/local/www/xymon/server/etc/tasks.cfg
2011-04-09 23:39:33 Cannot open directory ^T<C2>        (<C6><B1>
2011-04-09 23:39:33 Loading hostnames
2011-04-09 23:39:33 Loading saved state
2011-04-09 23:39:33 Cannot access checkpoint file 
/usr/local/www/xymon/server/tmp/xymond.chk for restore
2011-04-09 23:39:33 Setting up network listener on 0.0.0.0:1984
2011-04-09 23:39:33 Setting up signal handlers
2011-04-09 23:39:33 Setting up xymond channels
2011-04-09 23:39:33 Setting up logfiles
2011-04-09 23:39:38 Cannot open env file 
/usr/local/www/xymon/client/etc/xymonclient.cfg - No such file or 
directory
2011-04-09 23:39:39 Task xymond terminated by signal 6
2011-04-09 23:39:39 Loading hostnames
2011-04-09 23:39:39 Loading saved state
2011-04-09 23:39:39 Cannot access checkpoint file 
/usr/local/www/xymon/server/tmp/xymond.chk for restore
2011-04-09 23:39:39 Setting up network listener on 0.0.0.0:1984
2011-04-09 23:39:39 Cannot bind to listen socket (Address already in use)
2011-04-09 23:39:39 Task xymond terminated, status 1
2011-04-09 23:39:44 Loading hostnames
2011-04-09 23:39:44 Loading saved state
2011-04-09 23:39:44 Cannot access checkpoint file 
/usr/local/www/xymon/server/tmp/xymond.chk for restore
2011-04-09 23:39:44 Setting up network listener on 0.0.0.0:1984
2011-04-09 23:39:44 Cannot bind to listen socket (Address already in use)
2011-04-09 23:39:44 Task xymond terminated, status 1
2011-04-09 23:39:49 Loading hostnames
2011-04-09 23:39:49 Loading saved state
2011-04-09 23:39:49 Cannot access checkpoint file 
/usr/local/www/xymon/server/tmp/xymond.chk for restore
2011-04-09 23:39:49 Setting up network listener on 0.0.0.0:1984
2011-04-09 23:39:49 Cannot bind to listen socket (Address already in use)
2011-04-09 23:39:49 Task xymond terminated, status 1
2011-04-09 23:39:54 Loading hostnames
2011-04-09 23:39:54 Loading saved state
2011-04-09 23:39:54 Cannot access checkpoint file 
/usr/local/www/xymon/server/tmp/xymond.chk for restore
2011-04-09 23:39:54 Setting up network listener on 0.0.0.0:1984
2011-04-09 23:39:54 Setting up signal handlers
2011-04-09 23:39:54 Setting up xymond channels
2011-04-09 23:39:54 Setting up logfiles
.....

xymond.log

2011-04-09 23:39:33 Setup complete
2011-04-09 23:39:54 Whoops ! Failed to send message (timeout)
2011-04-09 23:39:54 ->
2011-04-09 23:39:54 ->  Recipient '127.0.0.1', timeout 15
2011-04-09 23:39:54 ->  1st line: 'status xymon,example,com.xymond red - 
Program crashed'
2011-04-09 23:39:54 Setup complete
2011-04-09 23:40:21 Whoops ! Failed to send message (timeout)
2011-04-09 23:40:21 ->
2011-04-09 23:40:21 ->  Recipient '127.0.0.1', timeout 15
2011-04-09 23:40:21 ->  1st line: 'status xymon,example,com.xymond red - 
Program crashed'
2011-04-09 23:50:09 Setup complete
2011-04-09 23:50:30 Whoops ! Failed to send message (timeout)
2011-04-09 23:50:30 ->
2011-04-09 23:50:30 ->  Recipient '127.0.0.1', timeout 15
2011-04-09 23:50:30 ->  1st line: 'status xymon,example,com.xymond red - 
Program crashed'
2011-04-09 23:50:30 Setup complete
2011-04-09 23:51:10 Whoops ! Failed to send message (timeout)
2011-04-09 23:51:10 ->
2011-04-09 23:51:10 ->  Recipient '127.0.0.1', timeout 15
2011-04-09 23:51:10 ->  1st line: 'status xymon,example,com.xymond red - 
Program crashed'
2011-04-10 00:00:58 Setup complete
2011-04-10 00:01:17 Whoops ! Failed to send message (timeout)
2011-04-10 00:01:17 ->
2011-04-10 00:01:17 ->  Recipient '127.0.0.1', timeout 15
2011-04-10 00:01:17 ->  1st line: 'status xymon,example,com.xymond red - 
Program crashed'
2011-04-10 00:01:17 Setup complete
2011-04-10 00:01:32 Whoops ! Failed to send message (timeout)
2011-04-10 00:01:32 ->
2011-04-10 00:01:32 ->  Recipient '127.0.0.1', timeout 15
2011-04-10 00:01:32 ->  1st line: 'status xymon,example,com.xymond red - 
Program crashed'
.......


Output from gdb bin/xymond tmp/xymond.core
 
#0  0x281afe17 in kill () from /lib/libc.so.7
#1  0x281afd76 in raise () from /lib/libc.so.7
#2  0x281ae98a in abort () from /lib/libc.so.7
#3  0x0805df23 in sigsegv_handler (signum=11) at sig.c:57
#4  <signal handler called>
#5  rbtFind (h=0x0, key=0x2822b047) at rbtr.c:380
#6  0x0805a461 in knownhost (hostname=0x2822b047 "Amp2hi-test", 
hostip=0xbfbfbcfc "", ghosthandling=GH_LOG) at loadhosts.c:344
#7  0x0804d626 in get_hts (msg=Variable "msg" is not available.) at 
xymond.c:1051
#8  0x08051be0 in do_message (msg=0x28204100, origin=0x806238f "") at 
xymond.c:2981
#9  0x08056871 in main (argc=8, argv=Cannot access memory at address 0x4) 
at xymond.c:4999

Line 6 surprises me, because 'Amp2hi-test' is one of the hosts that I used 

to monitor, but I removed all the old configs etc from the server.
I've started up xymon several times and sometimes I see other 'old' 
hostnames in the output file of xymond.core
It appears that I didn't completely remove all traces of the old 
installation after all...

Any help would be appreciated,

Dennis


Disclaimer.

This email is intended only for use by the addressee and may contain
confidential information. If you receive this email unintentionally,
please delete the email and inform Toshiba Medical Systems Europe BV
(TMSE) immediately.

TMSE does not guarantee that email transmission is secure or error-free as
information could be intercepted, corrupted, lost, destroyed, arrive late
or
incomplete, or contain viruses. If verification is required please request
a written confirmation. TMSE accepts no liability for any damage resulting
from the use and/or acceptation of the content of this e-mail.

The sale and delivery of products are subject to the General Conditions
of TMSE, which have been filed with the trade registrar in the
Netherlands under no. HR 27 143 943.
A copy of the General Conditions will be forwarded upon request

P Please consider the environment before printing this email
list Henrik Størner · Sat, 30 Apr 2011 17:55:50 +0200 ·
quoted from Dlubbe
So I uninstalled Xymon, deleted everyting related to it and then installed
a fresh copy of Xymon 4.3.2 (also via the port-collection)
The installation goes fine, but when I start it up, the html files aren't
generated.
It seems that xymond crashes for reasons I don't understand

I did some digging and I see the following:

xymonlaunch.log:

2011-04-09 23:39:33 xymonlaunch starting
2011-04-09 23:39:33 Loading tasklist configuration from
/usr/local/www/xymon/server/etc/tasks.cfg
2011-04-09 23:39:33 Cannot open directory ^T<C2> (<C6><B1>
Looks like something weird in your configuration - that "directory" name 
doesn't look right. Check your configuration files - especially the 
xymonserver.cfg and tasks.cfg files, this is something that happens very 
early in the setup.

Maybe tasks.cfg has a "directory" include pointing to a non-existing 
directory. Maybe xymonserver.cfg is missing or unreadable.

Maybe your config files are not ascii, but in UTF-16 format.
quoted from Dlubbe

2011-04-09 23:39:33 Setting up xymond channels
2011-04-09 23:39:33 Setting up logfiles
2011-04-09 23:39:38 Cannot open env file
/usr/local/www/xymon/client/etc/xymonclient.cfg - No such file or
directory
2011-04-09 23:39:39 Task xymond terminated by signal 6
2011-04-09 23:39:39 Loading hostnames
Are you logging all tasks to the same logfile ? It looks like it, and 
this makes it difficult to separate out which task logs an error.

xymond shouldn't be reading xymonclient.cfg - it should use 
xymonserver.cfg ...
quoted from Dlubbe

Output from gdb bin/xymond tmp/xymond.core

#0 0x281afe17 in kill () from /lib/libc.so.7
#1 0x281afd76 in raise () from /lib/libc.so.7
#2 0x281ae98a in abort () from /lib/libc.so.7
#3 0x0805df23 in sigsegv_handler (signum=11) at sig.c:57
#4 <signal handler called>
#5 rbtFind (h=0x0, key=0x2822b047) at rbtr.c:380
#6 0x0805a461 in knownhost (hostname=0x2822b047 "Amp2hi-test",
hostip=0xbfbfbcfc "", ghosthandling=GH_LOG) at loadhosts.c:344
#7 0x0804d626 in get_hts (msg=Variable "msg" is not available.) at
xymond.c:1051
#8 0x08051be0 in do_message (msg=0x28204100, origin=0x806238f "") at
xymond.c:2981
#9 0x08056871 in main (argc=8, argv=Cannot access memory at address 0x4)
at xymond.c:4999

Line 6 surprises me, because 'Amp2hi-test' is one of the hosts that I used
to monitor, but I removed all the old configs etc from the server.
I've started up xymon several times and sometimes I see other 'old'
hostnames in the output file of xymond.core
It appears that I didn't completely remove all traces of the old
installation after all...
Yep, something's lying around somewhere.


Regards,
Henrik
list Buchan Milne · Tue, 3 May 2011 12:49:45 +0200 ·
quoted from Henrik Størner
On Saturday, 30 April 2011 17:55:50 Henrik Størner wrote:
So I uninstalled Xymon, deleted everyting related to it and then
installed a fresh copy of Xymon 4.3.2 (also via the port-collection)
The installation goes fine, but when I start it up, the html files aren't
generated.
It seems that xymond crashes for reasons I don't understand

I did some digging and I see the following:

xymonlaunch.log:

2011-04-09 23:39:33 xymonlaunch starting
2011-04-09 23:39:33 Loading tasklist configuration from
/usr/local/www/xymon/server/etc/tasks.cfg
2011-04-09 23:39:33 Cannot open directory ^T<C2> (<C6><B1>
Looks like something weird in your configuration - that "directory" name
doesn't look right. Check your configuration files - especially the
xymonserver.cfg and tasks.cfg files, this is something that happens very
early in the setup.

Maybe tasks.cfg has a "directory" include pointing to a non-existing
directory. Maybe xymonserver.cfg is missing or unreadable.

Maybe your config files are not ascii, but in UTF-16 format.
No. I have seen this before, and I forgot to note it.

In my case there was a permissions problem on either the directory, or a file 
in the directory. The function handling this does not catch errors in opening 
the file.

Regards,
Buchan