Re: 20020421: LDM 5.1.2

HI Adam, 

Also, when we fix the DNS
> problem everything worked fine untill the ldm just stoped again.

What was the message from the log when it stopped?

If we
> ever try to restart the ldm once it has crashed like that without
> rebooting the system,


Prior to re-starting do you check to make sure ALL LDM processes have
stopped?

It is very hard to determine the source of this issue without the relevant
log files...otherwise I would be guessing. You can change the # of logs
you generate in ldmadmin.conf if that is becoming an issue...

Thank you,


-Jeff
____________________________                  _____________________
Jeff Weber                                    address@hidden
Unidata Support                               PH:303-497-8676 
NWS-COMET Case Study Library                  FX:303-497-8690
University Corp for Atmospheric Research      3300 Mitchell Ln
http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000
________________________________________      ______________________

On Fri, 26 Apr 2002, adam  taylor (994) wrote:

> Nope, not a Athlon CPU or athlon chipset.  All intel inside.  And as far
> as the logs, they have long been overwritten because of multiple restarts
> due to the access denied by remote server problem which we corrected.
> There was an error in the reverse DNS tables.  Also, when we fix the DNS
> problem everything worked fine untill the ldm just stoped again.  If we
> ever try to restart the ldm once it has crashed like that without
> rebooting the system, ldm will start and then the entire system freezes
> 100% and a hard reboot must be done which messes up the files systems on
> our data drive, and you get hte picture.
> 
> Adam Taylor
> 
> 
> On Mon, 22 Apr 2002, Jeff Weber wrote:
> 
> > Hi Adam, 
> > 
> > Athlon chip?
> > 
> > There's a known bug with RH 7.x and Athlon.
> > 
> > What's in the system logs?
> > 
> > Can you view the log that reports "child 21314 terminated by signal 7",
> > 
> > Please grep through it and see what process 21314 was.
> > 
> > 
> > It should be the one that starts up right after:
> > 
> > pqact[21313]
> > 
> > 
> > Thank you,
> > 
> > -Jeff
> > ____________________________                  _____________________
> > Jeff Weber                                    address@hidden
> > Unidata Support                               PH:303-497-8676 
> > NWS-COMET Case Study Library                  FX:303-497-8690
> > University Corp for Atmospheric Research      3300 Mitchell Ln
> > http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000
> > ________________________________________      ______________________
> > 
> > On Sun, 21 Apr 2002, Unidata Support wrote:
> > 
> > > 
> > > ------- Forwarded Message
> > > 
> > > >To: address@hidden
> > > >From: "adam taylor (994)" <address@hidden>
> > > >Subject: LDM 5.1.2
> > > >Organization: UCAR/Unidata
> > > >Keywords: 200204211924.g3LJOja26407
> > > 
> > > Computer:
> > > Dual PIII 933Mhz
> > > 1 Gig Ram
> > > Linux Redhat 7.2
> > > LDM queue = 700Mb
> > > 
> > > The LDM program on our computer refuses to stay running.  It will run fine
> > > for a while(anywhere from a day to a week), and then quit with out any
> > > notice.  All processes just quit that have anything to do with the LDM.
> > > Attached is the ends of the last two times that the LDM quit.
> > > 
> > > Last log:
> > > 
> > > Apr 21 09:32:05 tornado pnga2area[30659]: Starting Up 
> > > Apr 21 09:32:05 tornado pnga2area[30659]: unPNG::    72941    242720 
> > > 3.3276 
> > > Apr 21 09:32:05 tornado pnga2area[30659]: Exiting 
> > > Apr 21 09:32:48 tornado pnga2area[30662]: Starting Up 
> > > Apr 21 09:32:48 tornado pnga2area[30662]: unPNG::    59289    322320
> > > 5.4364 
> > > Apr 21 09:32:48 tornado pnga2area[30662]: Exiting 
> > > Apr 21 09:44:54 tornado rpc.ldmd[21311]: child 21314 terminated by signal
> > > 7 
> > > Apr 21 09:44:54 tornado rpc.ldmd[21311]: Killing (SIGINT) process group 
> > > Apr 21 09:44:54 tornado rpc.ldmd[21311]: Interrupt 
> > > Apr 21 09:44:54 tornado rpc.ldmd[21311]: Exiting 
> > > Apr 21 09:44:54 tornado pqact[21313]: Interrupt 
> > > Apr 21 09:44:54 tornado pqact[21313]: Exiting 
> > > Apr 21 09:44:54 tornado rpc.ldmd[21311]: Terminating process group 
> > > Apr 21 09:44:54 tornado striker[21315]: Interrupt 
> > > Apr 21 09:44:54 tornado pqbinstats[21312]: Interrupt 
> > > Apr 21 09:44:55 tornado striker[21315]: Exiting 
> > > Apr 21 09:44:55 tornado pqbinstats[21312]: Exiting 
> > > 
> > > Log before last:
> > > 
> > > Apr 20 23:04:57 tornado pnga2area[19939]: Starting Up 
> > > Apr 20 23:04:57 tornado pnga2area[19939]: unPNG::   106064    309200
> > > 2.9152 
> > > Apr 20 23:04:57 tornado pnga2area[19939]: Exiting 
> > > Apr 20 23:06:10 tornado pnga2area[19957]: Starting Up 
> > > Apr 20 23:06:10 tornado pnga2area[19957]: unPNG::    65726    242800
> > > 3.6941 
> > > Apr 20 23:06:10 tornado pnga2area[19957]: Exiting 
> > > Apr 20 23:07:12 tornado pnga2area[19961]: Starting Up 
> > > Apr 20 23:07:12 tornado pnga2area[19961]: unPNG::    66746    242720
> > > 3.6365 
> > > Apr 20 23:07:12 tornado pnga2area[19961]: Exiting 
> > > Apr 20 23:07:43 tornado pnga2area[19962]: Starting Up 
> > > Apr 20 23:07:43 tornado pnga2area[19962]: unPNG::    53363    322320
> > > 6.0401 
> > > Apr 20 23:07:43 tornado pnga2area[19962]: Exiting 
> > > Apr 20 23:11:02
> > > 
> > > As you can see by this log, the LDM died without even finishing writing
> > > the log as shown by the date without any information beside it.
> > > 
> > > Just trying to figure out that in the world is going on.  Also when it
> > > stops, it leaves the computer so unstable that a complete shutdown and
> > > reboot is needed.  If you try to clean, del the queue, and start it back
> > > up.  The computer just freezes and must be shut off.
> > > 
> > > Thanks in advance
> > > 
> > > Adam Taylor
> > > Department of Geosciences
> > > University of Louisiana at Mornoe
> > > 
> > > 
> > > 
> > > ------- End of Forwarded Message
> > > 
> > > 
> > 
> > 
> 
>