[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20051209: logs from machines that stopped.

>From: Waldenio Almeida <address@hidden>
>Organization: INPE/CPTEC
>Keywords: 200512092024.jB9KOt7s008346 LDM assertion errors

Hi Waldenio,

>I have got problems with 2 machines here: moingobe and tume. I am
>checking the moingobe (FreeBSD under ldm 6.3.0)
>it was rebooted by the support people before I know about the
>problem.  I didnt problems with my linux machines under ldm 6.4.1

The mysterious LDM exits were caused by an assertion error in
the pq.c module.  The only way that assertions are enabled to work
is when the LDM is built with assertions turned on.  You can
check the LDM builds on your machines to see if assertions were
turned on as follows:

<as 'ldm'>
cd ~ldm/ldm-x.x.x/src           <- substitute x.x.x with your distribution
less macros.make

Look for the line containing CONFIGURE_CPPFLAGS.  A build where
assertions are turned on will look like:

CONFIGURE_CPPFLAGS      = -UNDEBUG

Assertions turned off will look like:

CONFIGURE_CPPFLAGS      = -DNDEBUG

If your LDM(s) were built with assertions turned on, you should
recompile them with assertions turned off.

>The tume (solaris under ldm 6.0.14) I just did a restart on the ldm. I
>am sending you the logs of tume. 

OK.  I found the assertion error in tume's ldmd.log.2 file:

>Dec 08 05:24:22 tume mombucu[25520]: assertion "n > 0" failed: file "pq.c", 
>line 2187

>I restarted the machine today (december, 9) in the morning between 11
>and 12 GMT
>
>I hope that this helps.

Yes, thank you for reporting this.

I recommend that you upgrade the old LDMs you have with the latest
release, LDM-6.4.4, -- OR -- wait until early next week (hopefully
Monday) and download the next LDM release.

>Cheers,

Again, thanks for your verifying that you experienced the same
assertion failure.

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.