Xymon Mailing List Archive search

Version 4.3.14 is out

18 messages in this thread

list Henrik Størner · Sun, 26 Jan 2014 14:27:13 +0100 · 
Hi,

4.3.14 is available on Sourceforge now, carrying the fixes and 
enhancements that have been discussed over the past couple of weeks.


Regards,
Henrik

           <<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>
            * * *   Release notes for Xymon 4.3.14   * * *
           <<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>


In previous Xymon versions, a client-only configuration (i.e. one
configured with "./configure --client") would place the client
files in a "client" subdirectory below the directory specified
during configuration. This is the same directory layout as a server
installation, where the server and client parts of Xymon are
in separate subdirectories.
In 4.3.14, the default has changed so a client-only installation
now installs in the directory given during the configure-step.
The "/client" has been eliminated, so if you are upgrading an
existing client you must either move the old client installation
one level up from the "client/" directory, or change the Makefile
generated by "configure --client" and add "/client" to the
XYMONTOPDIR setting.

The SNI support added in 4.3.13 causes problems with some older
webservers, whose SSL implementation cannot handshake correctly
when SNI is used. The failed handshake causes Xymon to report
the site as down. In 4.3.14, the default is changed so SNI is
disabled. A new "--sni" option was added to xymonnet to control the
default setting, and two new tags "sni" and "nosni" can be used in
hosts.cfg to control SNI for each host that is tested.


           <<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>
                * * *   Changes in Xymon 4.3.14   * * *
           <<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>

* Fix critical ack not working for hosts where the display-name is
   set (via "NAME:" tag). From Any Smith.
* SNI (Server Name Indication) causes some SSL connections to fail
   due to server-side buggy SSL implementations. Add "sni" and "nosni"
   flags to control SNI for specific hosts, and "--sni" option for
   xymonnet to control the default. Reported by Mark Felder.
* Fix build process to fully obey any XYMONTOPDIR setting from the
   top-level Makefile. NOTE: Client-only builds no longer install the
   client in a "client/" subdirectory below XYMONHOME.
* Fix showgraph so it silently ignores stale rrdctl files when trying
   to flush RRD data before showing a graph.
* Fix xymond_alert crashing when trying to strip <cr> characters
   from the alert message. Bug introduced in 4.3.13.
* Fix Solaris client to report memory even when no swap is configured.
* Fix bug where alerts that were initially suppressed due to TIME
   restrictions are delayed until REPEAT interval expires.
* Fix crash in xymonlaunch when trying to find tasks.cfg
* Fix HTML generated by acknowledge.cgi (missing '>')
* Fix Linux client reporting garbled client data if top output ends
   without a new-line (causes CPU load and other vmstat graphs to
   stop updating)
* Fix Debian installation so it enables Apache mod_rewrite
* Fix merge-lines utility crashing when first line was an include
* Fix "make install" failing when server/www/help was a symlink
* Document existing OPTIONAL setting in analysis.cfg for file-checks
   on files which may not exist.
* Document existing CLASS setting in alerts.cfg
* Add new INFOCOLUMNGIF and TRENDSCOLUMNGIF settings so the icons
   used for these pages are configurable.
* Enhance Solaris client to correctly handle Solaris zones.
* Add new search facilities to xymond to select hosts with the
   'xymondboard' and 'hostinfo' commands.
* New --ack-each-color option for xymondd changes ack behaviour so a
   yellow ack does not apply when status changed to red, but a red ack
   applies if status goes yellow
* New "headermatch" tag for http tests so content checks can look at
   HTTP headers in addition to the HTML body.
* Use system-wide c-ares library. The pre-built Debian packages now
   require the "libc-ares2" package.
list Robert Schetterer · Sun, 26 Jan 2014 17:08:42 +0100 · 
Am 26.01.2014 14:27, schrieb Henrik Størner:
▸ quoted from Henrik Størner
Hi,

4.3.14 is available on Sourceforge now, carrying the fixes and
enhancements that have been discussed over the past couple of weeks.


Regards,
Henrik

after update i get alarm
xymond_alert

Program crashed


Fatal signal caught!

any Idea ?


Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
list Henrik Størner · Sun, 26 Jan 2014 17:45:29 +0100 ·
▸ quoted from Robert Schetterer
Den 26-01-2014 17:08, Robert Schetterer skrev:
Am 26.01.2014 14:27, schrieb Henrik Størner:
Hi,

4.3.14 is available on Sourceforge now, carrying the fixes and
enhancements that have been discussed over the past couple of weeks.
It shouldn't do that :-((

Can you try getting a stack trace using this procedure?
http://www.xymon.com/xymon/help/known-issues.html#bugreport


Regards,
Henrik
list Henrik Størner · Sun, 26 Jan 2014 17:51:05 +0100 ·
▸ quoted from Henrik Størner
Den 26-01-2014 14:27, Henrik Størner skrev:
Hi,

4.3.14 is available on Sourceforge now, carrying the fixes and
enhancements that have been discussed over the past couple of weeks.
Seems a couple of files were accidentally left out of the 4.3.14 
tar-ball. I'll do an update in a few minutes.


Regards,
Henrik
list Robert Schetterer · Sun, 26 Jan 2014 18:00:29 +0100 · 
Am 26.01.2014 17:51, schrieb Henrik Størner:
▸ quoted from Henrik Størner
Den 26-01-2014 14:27, Henrik Størner skrev:
Hi,

4.3.14 is available on Sourceforge now, carrying the fixes and
enhancements that have been discussed over the past couple of weeks.
Seems a couple of files were accidentally left out of the 4.3.14
tar-ball. I'll do an update in a few minutes.


Regards,
Henrik


so i wait and retry
▸ quoted from Robert Schetterer


Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
list Robert Schetterer · Sun, 26 Jan 2014 18:31:15 +0100 · 
Am 26.01.2014 17:45, schrieb Henrik Størner:
▸ quoted from Robert Schetterer
Den 26-01-2014 17:08, Robert Schetterer skrev:
Am 26.01.2014 14:27, schrieb Henrik Størner:
Hi,

4.3.14 is available on Sourceforge now, carrying the fixes and
enhancements that have been discussed over the past couple of weeks.
It shouldn't do that :-((

Can you try getting a stack trace using this procedure?
http://www.xymon.com/xymon/help/known-issues.html#bugreport
wait for upgrade again, some files may missing, then perhaps trace the
issue to debug

but for complete
alert log shows

2014-01-26 18:27:14 Peer not up, flushing message queue
2014-01-26 18:27:14 Child process 26619 died: Signal 6

2014-01-26 18:29:17 Stale alert for mail.example.de:msgs dropped
2014-01-26 18:29:17 Child process 26771 died: Signal 6

etc

Regards,
Henrik
▸ quoted from Robert Schetterer


Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
list Henrik Størner · Sun, 26 Jan 2014 18:53:58 +0100 ·
▸ quoted from Robert Schetterer
Den 26-01-2014 18:31, Robert Schetterer skrev:
Am 26.01.2014 17:45, schrieb Henrik Størner:
Den 26-01-2014 17:08, Robert Schetterer skrev:
Am 26.01.2014 14:27, schrieb Henrik Størner:
Hi,

4.3.14 is available on Sourceforge now, carrying the fixes and
enhancements that have been discussed over the past couple of weeks.
It shouldn't do that :-((

Can you try getting a stack trace using this procedure?
http://www.xymon.com/xymon/help/known-issues.html#bugreport
wait for upgrade again, some files may missing, then perhaps trace the
issue to debug
Actually, with the missing files you shouldn't be able to build 4.3.14. 
Did you use an existing Makefile ?


Regards,
Henrik
list Robert Schetterer · Sun, 26 Jan 2014 19:42:44 +0100 · 
Am 26.01.2014 18:53, schrieb Henrik Størner:
▸ quoted from Robert Schetterer
Den 26-01-2014 18:31, Robert Schetterer skrev:
Am 26.01.2014 17:45, schrieb Henrik Størner:
Den 26-01-2014 17:08, Robert Schetterer skrev:
Am 26.01.2014 14:27, schrieb Henrik Størner:
Hi,

4.3.14 is available on Sourceforge now, carrying the fixes and
enhancements that have been discussed over the past couple of weeks.
It shouldn't do that :-((

Can you try getting a stack trace using this procedure?
http://www.xymon.com/xymon/help/known-issues.html#bugreport
wait for upgrade again, some files may missing, then perhaps trace the
issue to debug
Actually, with the missing files you shouldn't be able to build 4.3.14.
Did you use an existing Makefile ?
i rebuilded deb from your new tar, and reinstalled
but sees issues are not fixed, now i got back to   4.3.13
lets see whats happen now
▸ quoted from Robert Schetterer
Regards,
Henrik


Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
list Robert Schetterer · Sun, 26 Jan 2014 20:07:17 +0100 · 
Am 26.01.2014 19:42, schrieb Robert Schetterer:
▸ quoted from Robert Schetterer
Am 26.01.2014 18:53, schrieb Henrik Størner:
Den 26-01-2014 18:31, Robert Schetterer skrev:
Am 26.01.2014 17:45, schrieb Henrik Størner:
Den 26-01-2014 17:08, Robert Schetterer skrev:
Am 26.01.2014 14:27, schrieb Henrik Størner:
Hi,

4.3.14 is available on Sourceforge now, carrying the fixes and
enhancements that have been discussed over the past couple of weeks.
It shouldn't do that :-((

Can you try getting a stack trace using this procedure?
http://www.xymon.com/xymon/help/known-issues.html#bugreport
wait for upgrade again, some files may missing, then perhaps trace the
issue to debug
Actually, with the missing files you shouldn't be able to build 4.3.14.
Did you use an existing Makefile ?
i rebuilded deb from your new tar, and reinstalled
but sees issues are not fixed, now i got back to   4.3.13
lets see whats happen now
with 4.3.13 alert log is fine/empty again but

xymond_alert which i set blue doesnt recover to green

any hints ?
▸ quoted from Robert Schetterer
Regards,
Henrik


Best Regards
MfG Robert Schetterer

Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
list Henrik Størner · Sun, 26 Jan 2014 20:43:13 +0100 ·
▸ quoted from Robert Schetterer
Den 26-01-2014 20:07, Robert Schetterer skrev:
with 4.3.13 alert log is fine/empty again but

xymond_alert which i set blue doesnt recover to green

any hints ?
The 'crash report' status have to be manually removed with

	xymon 127.0.0.1 "drop <your xymon servername> xymond_alert"


Regards,
Henrik
list Robert Schetterer · Sun, 26 Jan 2014 21:06:15 +0100 · 
Am 26.01.2014 20:43, schrieb Henrik Størner:
▸ quoted from Robert Schetterer
Den 26-01-2014 20:07, Robert Schetterer skrev:
with 4.3.13 alert log is fine/empty again but

xymond_alert which i set blue doesnt recover to green

any hints ?
The 'crash report' status have to be manually removed with

    xymon 127.0.0.1 "drop <your xymon servername> xymond_alert"

that removes xymond_alert, so lets see what happen next
▸ quoted from Robert Schetterer
Regards,
Henrik


Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
list Robert Schetterer · Sun, 26 Jan 2014 22:32:21 +0100 · 
Am 26.01.2014 21:06, schrieb Robert Schetterer:
▸ quoted from Robert Schetterer
Am 26.01.2014 20:43, schrieb Henrik Størner:
Den 26-01-2014 20:07, Robert Schetterer skrev:
with 4.3.13 alert log is fine/empty again but

xymond_alert which i set blue doesnt recover to green

any hints ?
The 'crash report' status have to be manually removed with

    xymon 127.0.0.1 "drop <your xymon servername> xymond_alert"

that removes xymond_alert, so lets see what happen next

Regards,
Henrik


Best Regards
MfG Robert Schetterer

i did serveral test with upgrade to 4.3.14

it always log

alert log
▸ quoted from Robert Schetterer

2014-01-26 18:27:14 Peer not up, flushing message queue
2014-01-26 18:27:14 Child process 26619 died: Signal 6

2014-01-26 18:29:17 Stale alert for mail.example.de:msgs dropped
2014-01-26 18:29:17 Child process 26771 died: Signal 6


2014-01-26 22:15:20 Peer at 0.0.0.0:0 failed: Broken pipe
2014-01-26 22:16:00 Peer not up, flushing message queue

etc

http://www.xymon.com/xymon/help/known-issues.html#bugreport

does not help, no core file found

so speculate something is broken, might xymonnet

not really other bug messages in other logs

everything is fine with 4.3.13
▸ quoted from Robert Schetterer


Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
list David W David Gore · Sun, 26 Jan 2014 22:33:59 -0500 · 
Crashes for us, RedHat 6.5 64-bit.

[xymon at xymon1 logs]$ uname -a
Linux xymon1 2.6.32-431.1.2.el6.x86_64 #1 SMP Sun Nov 24 09:37:37 EST 2013 x86_64 x86_64 x86_64 GNU/Linux

[xymon at xymon1 logs]$ tail alert.log
2014-01-27 01:25:49 Peer not up, flushing message queue
2014-01-27 01:25:49 Stale alert for iciomtw2:se dropped
2014-01-27 01:25:49 Stale alert for ipgpdcjbpm2:autom-cnt dropped
2014-01-27 02:06:01 Child process 6570 died: Signal 6
2014-01-27 02:06:02 Peer at 0.0.0.0:0 failed: Broken pipe
2014-01-27 02:06:02 Peer not up, flushing message queue
2014-01-27 02:06:02 Stale alert for iciompd2:se dropped

(gdb) bt
#0  0x0000003f39432925 in raise () from /lib64/libc.so.6
#1  0x0000003f39434105 in abort () from /lib64/libc.so.6
#2  0x00000000004117a3 in sigsegv_handler (signum=<value optimized out>) at sig.c:57
#3  <signal handler called>
#4  next_alert (alert=0x1fbf210) at do_alert.c:708
#5  0x0000000000403985 in main (argc=<value optimized out>, argv=<value optimized out>) at xymond_alert.c:925

xymon xymon1 "drop xymon1 xymond_alert"

~David
▸ quoted from Robert Schetterer


-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Robert Schetterer
Sent: Sunday, January 26, 2014 4:32 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Version 4.3.14 is out

Am 26.01.2014 21:06, schrieb Robert Schetterer:
Am 26.01.2014 20:43, schrieb Henrik Størner:
Den 26-01-2014 20:07, Robert Schetterer skrev:
with 4.3.13 alert log is fine/empty again but

xymond_alert which i set blue doesnt recover to green

any hints ?
The 'crash report' status have to be manually removed with

    xymon 127.0.0.1 "drop <your xymon servername> xymond_alert"

that removes xymond_alert, so lets see what happen next

Regards,
Henrik


Best Regards
MfG Robert Schetterer

i did serveral test with upgrade to 4.3.14

it always log

alert log

2014-01-26 18:27:14 Peer not up, flushing message queue
2014-01-26 18:27:14 Child process 26619 died: Signal 6

2014-01-26 18:29:17 Stale alert for mail.example.de:msgs dropped
2014-01-26 18:29:17 Child process 26771 died: Signal 6

2014-01-26 22:15:20 Peer at 0.0.0.0:0 failed: Broken pipe
2014-01-26 22:16:00 Peer not up, flushing message queue

etc

http://www.xymon.com/xymon/help/known-issues.html#bugreport

does not help, no core file found

so speculate something is broken, might xymonnet

not really other bug messages in other logs

everything is fine with 4.3.13


Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
list Henrik Størner · Mon, 27 Jan 2014 07:09:01 +0100 · 
Hi,
▸ quoted from David W David Gore

Den 27-01-2014 04:33, Gore, David W (David) skrev:
Crashes for us, RedHat 6.5 64-bit.

[xymon at xymon1 logs]$ uname -a
Linux xymon1 2.6.32-431.1.2.el6.x86_64 #1 SMP Sun Nov 24 09:37:37 EST 2013 x86_64 x86_64 x86_64 GNU/Linux

[xymon at xymon1 logs]$ tail alert.log
2014-01-27 01:25:49 Peer not up, flushing message queue
2014-01-27 01:25:49 Stale alert for iciomtw2:se dropped
2014-01-27 01:25:49 Stale alert for ipgpdcjbpm2:autom-cnt dropped
2014-01-27 02:06:01 Child process 6570 died: Signal 6
2014-01-27 02:06:02 Peer at 0.0.0.0:0 failed: Broken pipe
2014-01-27 02:06:02 Peer not up, flushing message queue
2014-01-27 02:06:02 Stale alert for iciompd2:se dropped

(gdb) bt
#0  0x0000003f39432925 in raise () from /lib64/libc.so.6
#1  0x0000003f39434105 in abort () from /lib64/libc.so.6
#2  0x00000000004117a3 in sigsegv_handler (signum=<value optimized out>) at sig.c:57
#3  <signal handler called>
#4  next_alert (alert=0x1fbf210) at do_alert.c:708
#5  0x0000000000403985 in main (argc=<value optimized out>, argv=<value optimized out>) at xymond_alert.c:925
well, that points the finger right at some code that was changed in 
4.3.14 - so it makes sense.

I don't understand how it triggers, though - but the code before 4.3.14 
would catch it. So let's try merging those two pieces.

Does this patch help?


Regards,
Henrik
Attachments (1)
list Robert Schetterer · Mon, 27 Jan 2014 17:04:32 +0100 · 
Am 27.01.2014 07:09, schrieb Henrik Størner:
▸ quoted from Henrik Størner
Hi,

Den 27-01-2014 04:33, Gore, David W (David) skrev:
Crashes for us, RedHat 6.5 64-bit.

[xymon at xymon1 logs]$ uname -a
Linux xymon1 2.6.32-431.1.2.el6.x86_64 #1 SMP Sun Nov 24 09:37:37 EST
2013 x86_64 x86_64 x86_64 GNU/Linux

[xymon at xymon1 logs]$ tail alert.log
2014-01-27 01:25:49 Peer not up, flushing message queue
2014-01-27 01:25:49 Stale alert for iciomtw2:se dropped
2014-01-27 01:25:49 Stale alert for ipgpdcjbpm2:autom-cnt dropped
2014-01-27 02:06:01 Child process 6570 died: Signal 6
2014-01-27 02:06:02 Peer at 0.0.0.0:0 failed: Broken pipe
2014-01-27 02:06:02 Peer not up, flushing message queue
2014-01-27 02:06:02 Stale alert for iciompd2:se dropped

(gdb) bt
#0  0x0000003f39432925 in raise () from /lib64/libc.so.6
#1  0x0000003f39434105 in abort () from /lib64/libc.so.6
#2  0x00000000004117a3 in sigsegv_handler (signum=<value optimized
out>) at sig.c:57
#3  <signal handler called>
#4  next_alert (alert=0x1fbf210) at do_alert.c:708
#5  0x0000000000403985 in main (argc=<value optimized out>,
argv=<value optimized out>) at xymond_alert.c:925
well, that points the finger right at some code that was changed in
4.3.14 - so it makes sense.

I don't understand how it triggers, though - but the code before 4.3.14
would catch it. So let's try merging those two pieces.

Does this patch help?


Regards,
Henrik


news about this ?
▸ quoted from David W David Gore


Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
list Henrik Størner · Mon, 27 Jan 2014 17:24:46 +0100 · 
Den 27-01-2014 17:04, Robert Schetterer skrev:
Am 27.01.2014 07:09, schrieb Henrik Størner:
Does this patch help?
news about this ?
Did you try the patch?

I believe it is the correct fix, and after a closer look at the code I 
actually understand why it is necessary.

There will be a 4.3.15 release in a day or two, I just want to see if 
any other urgent problems show up.


Regards,
Henrik
list Robert Schetterer · Mon, 27 Jan 2014 18:10:49 +0100 · 
Am 27.01.2014 17:24, schrieb Henrik Størner:
▸ quoted from Robert Schetterer
Den 27-01-2014 17:04, Robert Schetterer skrev:
Am 27.01.2014 07:09, schrieb Henrik Størner:
Does this patch help?
news about this ?
Did you try the patch?
no, short in time ,sorry
▸ quoted from Henrik Størner
I believe it is the correct fix, and after a closer look at the code I
actually understand why it is necessary.

There will be a 4.3.15 release in a day or two, I just want to see if
any other urgent problems show up.
i will wait to this, thx for coding
▸ quoted from Robert Schetterer
Regards,
Henrik


Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
list David W David Gore · Mon, 27 Jan 2014 12:20:48 -0500 · 
So far so good.  Thanks Henrik for the quick response!


[xymon at xymon1 tmp]$ ls -lrt core*
-rw------- 1 xymon apache 15568896 Jan 27 01:11 core.15623
-rw------- 1 xymon apache 16306176 Jan 27 02:06 core.6570
-rw------- 1 xymon apache 14458880 Jan 27 08:04 core.21277
-rw------- 1 xymon apache 12234752 Jan 27 08:09 core.14197
-rw------- 1 xymon apache 13688832 Jan 27 10:51 core.19759

[xymon at xymon1 tmp]$ ps -fu xymon | grep launch
xymon     1143     1  0 12:33 ?        00:00:01 /home/xymon/server/bin/xymonlaunch --config=/home/xymon/server/etc/tasks.cfg --env=/home/xymon/server/etc/xymonserver.cfg --log=/home/xymon/server/logs/xymonlaunch.log --pidfile=/home/xymon/server/logs/xymonlaunch.pid
xymon     1174     1  0 12:33 ?        00:00:00 /home/xymon/client/bin/xymonlaunch --config=/home/xymon/client/etc/clientlaunch.cfg --log=/home/xymon/client/logs/clientlaunch.log --pidfile=/home/xymon/client/logs/clientlaunch.xymon1.pid

[xymon at xymon1 tmp]$ date
Mon Jan 27 17:19:08 UTC 2014
▸ quoted from Robert Schetterer

~David

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Robert Schetterer
Sent: Monday, January 27, 2014 11:05 AM
To: xymon at xymon.com
Subject: Re: [Xymon] Version 4.3.14 is out

Am 27.01.2014 07:09, schrieb Henrik Størner:
Hi,

Den 27-01-2014 04:33, Gore, David W (David) skrev:
Crashes for us, RedHat 6.5 64-bit.

[xymon at xymon1 logs]$ uname -a
Linux xymon1 2.6.32-431.1.2.el6.x86_64 #1 SMP Sun Nov 24 09:37:37 EST
2013 x86_64 x86_64 x86_64 GNU/Linux

[xymon at xymon1 logs]$ tail alert.log
2014-01-27 01:25:49 Peer not up, flushing message queue
2014-01-27 01:25:49 Stale alert for iciomtw2:se dropped
2014-01-27 01:25:49 Stale alert for ipgpdcjbpm2:autom-cnt dropped
2014-01-27 02:06:01 Child process 6570 died: Signal 6
2014-01-27 02:06:02 Peer at 0.0.0.0:0 failed: Broken pipe
2014-01-27 02:06:02 Peer not up, flushing message queue
2014-01-27 02:06:02 Stale alert for iciompd2:se dropped

(gdb) bt
#0  0x0000003f39432925 in raise () from /lib64/libc.so.6
#1  0x0000003f39434105 in abort () from /lib64/libc.so.6
#2  0x00000000004117a3 in sigsegv_handler (signum=<value optimized
out>) at sig.c:57
#3  <signal handler called>
#4  next_alert (alert=0x1fbf210) at do_alert.c:708
#5  0x0000000000403985 in main (argc=<value optimized out>,
argv=<value optimized out>) at xymond_alert.c:925
well, that points the finger right at some code that was changed in
4.3.14 - so it makes sense.

I don't understand how it triggers, though - but the code before 4.3.14
would catch it. So let's try merging those two pieces.

Does this patch help?


Regards,
Henrik


news about this ?


Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein