Xymon Mailing List Archive search

Snapshot 17/7 client-test went purple

3 messages in this thread

list Lars Ebeling · Tue, 18 Jul 2006 05:45:22 +0200 ·
Hi,

Nothing in logfiles, no core. Running on HP-UX 11.11


Regards
Lars Ebeling
Hobbithobbyist
http://leopg9.no-ip.org

¤ "The trouble with the world is that the stupid are cocksure and the intelligent are full of doubt."
--Bertrand Russell
list Lars Ebeling · Tue, 18 Jul 2006 06:02:51 +0200 ·
Think this is my problem

Regards
Lars

----- Original Message ----- 
From: "Henrik Stoerner" <user-ce4a2c883f75@xymon.invalid>
To: <user-ae9b8668bcde@xymon.invalid>
Sent: Monday, July 17, 2006 11:24 AM
Subject: Re: [hobbit] logfetch broken

On Mon, Jul 17, 2006 at 11:14:42AM +0200, Dominique Frise wrote:
logfetch of today's snapshot (4.2-RC-20060712.1) eats a lot of CPU while
blocking the rest of local tests.
Yes, there is a problem with logfetch. Thought I had it solved,
but I got reports yesterday that it wasn't fixed entirely. So it's
back on the "known problems" list for the rel. candidate.
How can I force it to generate a core file?
kill -ABRT <pid-of-logfetch>


Regards,
Henrik

list Lars Ebeling · Tue, 18 Jul 2006 07:19:02 +0200 ·
Installed todays (18/7) snapshot. Client-tests still purple.

Regards
Lars
quoted from Lars Ebeling

----- Original Message ----- 
From: "lars ebeling" <user-1fecd3eafd52@xymon.invalid>
To: <user-ae9b8668bcde@xymon.invalid>
Sent: Tuesday, July 18, 2006 6:02 AM
Subject: [hobbit] Snapshot 17/7 client-test went purple

Think this is my problem

Regards
Lars

----- Original Message ----- 
From: "Henrik Stoerner" <user-ce4a2c883f75@xymon.invalid>
To: <user-ae9b8668bcde@xymon.invalid>
Sent: Monday, July 17, 2006 11:24 AM
Subject: Re: [hobbit] logfetch broken

On Mon, Jul 17, 2006 at 11:14:42AM +0200, Dominique Frise wrote:
logfetch of today's snapshot (4.2-RC-20060712.1) eats a lot of CPU while
blocking the rest of local tests.
Yes, there is a problem with logfetch. Thought I had it solved,
but I got reports yesterday that it wasn't fixed entirely. So it's
back on the "known problems" list for the rel. candidate.
How can I force it to generate a core file?
kill -ABRT <pid-of-logfetch>


Regards,
Henrik