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

20040615: Quick update on weather3.admin.niu.edu... (cont.)

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20040615: Quick update on weather3.admin.niu.edu... (cont.)
  • Date: Tue, 15 Jun 2004 12:50:28 -0600
>From: Gilbert Sebenste <address@hidden>
>Organization:  NIU
>Keywords:  200406150354.i5F3sOtK011267 LDM Fedora Core Linux

Gilbert,

re: possible bad RAM, etc.

>Guess what. One of the clips on one of the memory banks was open, and my 
>techie guru says it may not have been touching properly. I sent a note out 
>to ldm-users about it.

I saw your note.

>He pushed it in (or made sure it was in), and then 
>clipped it on tight. Think that would cause it?

Yes, absolutely.

>He says yes.

I agree.

So, I would go for broke by:

- stop the LDM
- delete the existing queue
- make a 1 GB queue
- start the LDM

Your earlier notes seemed to indicate that things would fail quickly
unless your queue was less than a certain size.  Making a queue that
is significantly larger than that minimun size should force the issue
quickly.

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically 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.

>From address@hidden  Tue Jun 15 14:31:11 2004

Tom,

re: recommendation to go to a large queue to force the sigbus error

>Welllll, I went to my standard 400 MB. :-) I forgot to mention I did that 
>in my post to ldm-users.
 
re: your earlier notes suggested an LDM queue size dependency on crashes

>True. However, I had it set to 300 MB each time. At 400 MB, it tended to 
>crash within a few hours, if not minutes. So far, so good.

>And...how the hook popped off, I'll never know.

*******************************************************************************
Gilbert Sebenste                                                     ********
(My opinions only!)                                                  ******
Staff Meteorologist, Northern Illinois University                      ****
E-mail: address@hidden                                               ***
web: http://weather.admin.niu.edu                                      **
Work phone: 815-753-5492                                                *
*******************************************************************************