Stefan,
I don't know if this is your problem. I just suggested it as a
possibility for you to consider. I originally saw random lockups on a
BB system after upgrading from Redhat 7 to (8 or 9, I don't remember).
I thought this might be possible on other versions or distributions as
well.
The solution in my case was to either:
1) Down-grade the compiler to match the OS .
2) Recompile the kernel.
3) Change OS versions (sounds like you may have tried this).
I hope this helps in some way. Good luck on your problem.
Jeff
-----Original Message-----
From: Stefan Loos [mailto:user-dea24d965402@xymon.invalid] Sent: Monday, July 11, 2005 8:24 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: RE: [hobbit] Status Unavailable - again
Hello Jeffery,
do you think we see this issue because the kernel was built with a
different compiler than I was using for building the hobbit server?
@Henrik - do you think this could be the problem?
Regards,
Stefan
<br><br><br>>From: "Reif Jeffery M" <user-e9cc5d6c2490@xymon.invalid><br>>Reply-To: user-ae9b8668bcde@xymon.invalid<br>>To: user-ae9b8668bcde@xymon.invalid<br>>Subject: RE: [hobbit]
Status Unavailable - again<br>>Date: Mon, 11 Jul 2005 07:20:12 -0500<br>><br>>This is a shot in the dark - I had a lockup problem
on a BB system where<br>>the kernel was compiled with a different
version compiler than was<br>>included with the system and there were some IPC-related changes in<br>>compiler versions.<br>><br>>-----Original Message-----<br>>From: Stefan
Loos [mailto:user-dea24d965402@xymon.invalid]<br>>Sent: Monday, July 11, 2005 7:12
AM<br>>To: user-ae9b8668bcde@xymon.invalid<br>>Subject: Re: [hobbit] Status
Unavailable - again<br>><br>>Hi Henrik,<br>><br>>we have several
own-written scripts (mostly in perl) which monitor<br>>oracle<br>>instances,
bea weblogic servers. There is one for hardware monitoring -<br>>HP<br>>(Intel) and Sun Servers (prtdiag based) and some are
just the output of<br>>a<br>>http request to the software running on
that weblogic servers.<br>>I have just one server for testing, it's a HP
DL 360. We are running<br>>Redhat<br>>Enterprise Server 3 but I've
tried it with a SuSE 9.3 too.<br>><br>>Regards,<br>><br>>Stefan<br>><br>><br
><br><br>&gt;From: user-ce4a2c883f75@xymon.invalid (Henrik Stoerner)<br>&gt;Reply-To:<br>>user-ae9b8668bcde@xymon.invalid<br>&
;gt;To: user-ae9b8668bcde@xymon.invalid<br>&gt;Subject: Re: [hobbit]<br>>Status<br>>Unavailable - again<br>&gt;Date:
Mon, 11 Jul 2005
13:08:59<br>>+0200<br>&gt;<br>&gt;Hi Stefan,<br>&gt;<br>&gt;On Mon, Jul 11, 2005 at<br>>09:36:42AM +0000, Stefan Loos wrote:<br>&gt;
&gt; It would be great if<br>>you<br>>can put me in cc. If you want I can
try to assist<br>&gt; &gt; you. I'm<br>>at a<br>>point
where I don't know what to try anymore. I think it<br>&gt; &gt;<br>>isn't<br>>easy for Henrik to find this issue - I have
no coredumps and<br>>nothing<br>&gt;<br>>&gt; in the logfile what could help.<br>&gt;<br>&gt;Yes, this is
a<br>>really<br>>nasty problem. Vernon and I though we had it<br>&gt;nailed down by the<br>>end<br>>of last week,
but there's more to it than<br>&gt;what we found<br>>then.<br>&gt;<br>&gt;What kind of
external scripts run on your clients,<br>>apart from the BB<br>&gt;client ? The current suspicion is that this is<br>>triggered by a status<br>&gt;message that is handled
badly by Hobbit<br>>causing<br>>this lock-up. So I'm<br>&gt;trying to see if there might be something in<br>><br>>common between your setups.<br>&gt;<br>&gt;And what kind of system are<br>>you<br>>running Hobbit on ? If Linux, which<br>&gt;distribution ? Another<br>>suspicion<br>>I
have is that this might be a<br>&gt;problem with the implementation
of<br>><br>>SysV IPC<br>>semaphores.<br>&gt;<br>&gt;<br>&
;gt;Regards,<br>&gt;Henrik<br>&gt;<br>&gt<
br>>;<br>&gt;To<br>>unsubscribe from the hobbit list, send an e-mail<br>>to<br>&gt;user-095ef1c764a2@xymon.invalid<br>&a
mp;gt;<br>&gt;<br><br>><br>><br>><br>>To unsubscribe from the hobbit list, send an e-mail to<br>>user-095ef1c764a2@xymon.invalid<br>><br>><br>><br>><br>
><br>>To unsubscribe from the hobbit list, send an e-mail to<br>>user-095ef1c764a2@xymon.invalid<br>><br>><br>