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

[NOAAPORT #VJU-931365]: Re: [noaaport] LDM crashed this morning on satellite ingesters



Rosie,

The latest LDM (6.11.7) should solve the problem.

> Hi Gilbert,
> 
> Yes, we saw the same here on both of ours, running ldm-6.11.4  and
> ldm-6.11.2.
> 
> Rosie
> 
> 
> 
> On 2/25/14 11:08 AM, Gilbert Sebenste wrote:
> > If you have an LDM that's attached directly to a satellite dish,
> > make sure it is working. The College of DuPage and AllisonHouse
> > are both reporting that their LDM's on their ingest servers
> > crashed at the same time this morning, at 15:41:54Z, when there
> > was a drop in satellite signal strength on both dishes:
> >
> > Feb 25 15:41:54 noaaport readnoaaport[1544] ERROR: [gb22gem.c:74] [GB 1]
> > Couldn't get parameter values
> > Feb 25 15:41:54 noaaport readnoaaport[1544] ERROR: [gb2param.c:89] [GB
> > -1] Couldn't get parameter info: disc=0, cat=2, id=3, pdtn=0
> > Feb 25 15:41:54 noaaport readnoaaport[1544] ERROR: [gb22gem.c:74] [GB 1]
> > Couldn't get parameter values
> > Feb 25 15:41:54 noaaport readnoaaport[1544] ERROR: [gb2param.c:89] [GB
> > -1] Couldn't get parameter info: disc=10, cat=0, id=5, pdtn=0
> > Feb 25 15:41:54 noaaport readnoaaport[1544] ERROR: [gb22gem.c:74] [GB 1]
> > Couldn't get parameter values
> > Feb 25 15:41:54 noaaport readnoaaport[1544] ERROR: [gb2param.c:89] [GB
> > -1] Couldn't get parameter info: disc=0, cat=2, id=0, pdtn=0
> > Feb 25 15:41:54 noaaport readnoaaport[1544] ERROR: [gb22gem.c:74] [GB 1]
> > Couldn't get parameter values
> > Feb 25 15:41:54 noaaport readnoaaport[1544] ERROR: [gb2param.c:89] [GB
> > -1] Couldn't get parameter info: disc=0, cat=3, id=5, pdtn=0
> > Feb 25 15:41:54 noaaport readnoaaport[1544] ERROR: [gb22gem.c:74] [GB 1]
> > Couldn't get parameter values
> > Feb 25 15:41:54 noaaport kernel: [3778565.459747] readnoaaport[1544]:
> > segfault at ffffffffffffffbc ip 00007fa19b50fa5b sp 00007fff7bab6810
> > error 4 in libldm.so.0.0.0
> > [7fa19b4bb000+83000]
> > Feb 25 15:41:54 noaaport kernel: [3778565.459747] readnoaaport[1544]:
> > segfault at ffffffffffffffbc ip 00007fa19b50fa5b sp 00007fff7bab6810
> > error 4 in libldm.so.0.0.0
> > [7fa19b4bb000+83000]
> > Feb 25 15:41:56 noaaport ldmd[1535] NOTE: child 1544 terminated by
> > signal 11: readnoaaport -m 224.0.1.3
> > Feb 25 15:41:56 noaaport ldmd[1535] NOTE: Killing (SIGTERM) process group
> > Feb 25 15:41:56 noaaport ldmd[1535] NOTE: Exiting
> >
> > A remake of the queues and a restart got them going again.
> >
> > Just FYI. Anyone else seeing this? They are both using LDM version 6.11.6.
> >
> > Gilbert
> >
> > *******************************************************************************
> >
> > Gilbert Sebenste
> > ********
> > (My opinions only!)                                                  ******
> > Staff Meteorologist, Northern Illinois University                      ****
> > E-mail: address@hidden                                  ***
> > web: http://weather.admin.niu.edu                                      **
> > Twitter: http://www.twitter.com/NIU_Weather                            **
> > Facebook: http://www.facebook.com/niu.weather                           *
> > *******************************************************************************
> >
> >
> > _______________________________________________
> > noaaport mailing list
> > address@hidden
> > For list information or to unsubscribe, visit:
> > http://www.unidata.ucar.edu/mailing_lists/
> 
> 
> --
> SSEC Data Center            Email:  address@hidden
> UW Madison                  Web:    http://www.ssec.wisc.edu/datacenter
> 1225 W. Dayton              Phone:  (608) 262-0502
> Madison, Wisconsin 53706    Fax:    (608) 263-6738
> 
> _______________________________________________
> noaaport mailing list
> address@hidden
> For list information or to unsubscribe, visit: 
> http://www.unidata.ucar.edu/mailing_lists/

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: VJU-931365
Department: Support NOAAPORT
Priority: Critical
Status: Closed


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.