Re: [ldm-users] Problems ingesting Noaaport DB

I am running Unidata NOAAPORT v1.3.0 along with LDM. I suspect most people
using the Unidata NOAAPORT code are running 1.3.0, since it was the latest
version and
was released in 2007.  

What happens is that readnoaaport shuts down and this cascades and shuts
down the whole LDM system.

>From my log file from the most recent shutdown.

Oct 07 22:16:54 noaaport2 rpc.ldmd[5549] NOTE: child 5557 terminated by
signal 11: readnoaaport -m 224.0.1.3 
Oct 07 22:16:54 noaaport2 rpc.ldmd[5549] NOTE: Killing (SIGTERM) process
group 
Oct 07 22:16:54 noaaport2 rtstats[5559] NOTE: Exiting 
Oct 07 22:16:54 noaaport2 rpc.ldmd[5549] NOTE: Exiting 
Oct 07 22:16:54 noaaport2 rpc.ldmd[5549] NOTE: Terminating process group



Maybe a termination signal 11 from the readnoaaport exe might provide a
clue?

-Mike

 
-----Original Message-----
From: ldm-users-bounces@xxxxxxxxxxxxxxxx
[mailto:ldm-users-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Stonie R. Cooper
Sent: Wednesday, October 07, 2009 5:49 PM
To: Dan Vietor
Cc: LDM Users
Subject: Re: [ldm-users] Problems ingesting Noaaport DB

I concur with Dan . . . we have seen no major issues and have no reports
of issues from the users of our software.  NCF has not indicated any
major issues other than the massive retransmits due to the solar ephemeris.

Is everyone that is having a problem using the same software?  If so, I
would look closer at that as a probably cause.

Stonie

Dan Vietor wrote:
> On Wed, 2009-10-07 at 16:20 -0500, Gilbert Sebenste wrote:
>> On Wed, 7 Oct 2009, Dan Vietor wrote:
>>
>> > Also, the only outage I've seen is the eclipse outage about 1845Z which
>> > caused about a 3 minute outage and a loss of about 38000 frames.
>>
>> I just got off the phone with the NCF again...they gave me incorrect 
>> information. They are looking into it right now...
> 
> I did see a slight dropoff around 1655Z:
> 
> prods-071600.log:09/10/07 16:00:29 BPD sid: 10101 pid:   257 len: 
> 203721 comp:     0 flen: 32
> prods-071600.log:09/10/07 16:03:28 BPD sid: 10101 pid:   200 len:
> 1029297 comp:     0 flen: 32
> prods-071605.log:09/10/07 16:06:28 BPD sid: 10101 pid:   203 len: 
> 554605 comp:     0 flen: 32
> prods-071605.log:09/10/07 16:09:28 BPD sid: 10101 pid:   206 len: 
> 642922 comp:     0 flen: 32
> prods-071610.log:09/10/07 16:12:32 BPD sid: 10101 pid:   209 len:
> 1654766 comp:     0 flen: 32
> prods-071615.log:09/10/07 16:15:32 BPD sid: 10101 pid:   212 len:
> 1174893 comp:     0 flen: 32
> prods-071615.log:09/10/07 16:18:31 BPD sid: 10101 pid:   215 len: 
> 517288 comp:     0 flen: 32
> prods-071620.log:09/10/07 16:21:32 BPD sid: 10101 pid:   218 len: 
> 431808 comp:     0 flen: 32
> prods-071620.log:09/10/07 16:24:32 BPD sid: 10101 pid:   221 len: 
> 386567 comp:     0 flen: 32
> prods-071625.log:09/10/07 16:27:33 BPD sid: 10101 pid:   224 len: 
> 366895 comp:     0 flen: 32
> prods-071630.log:09/10/07 16:31:04 BPD sid: 10101 pid:   227 len: 
> 224709 comp:     0 flen: 32
> prods-071630.log:09/10/07 16:33:34 BPD sid: 10101 pid:   230 len: 
> 314953 comp:     0 flen: 32
> prods-071635.log:09/10/07 16:36:36 BPD sid: 10101 pid:   233 len: 
> 349749 comp:     0 flen: 32
> prods-071635.log:09/10/07 16:39:34 BPD sid: 10101 pid:   236 len: 
> 257671 comp:     0 flen: 32
> prods-071640.log:09/10/07 16:42:33 BPD sid: 10101 pid:   239 len: 
> 353943 comp:     0 flen: 32
> prods-071645.log:09/10/07 16:45:32 BPD sid: 10101 pid:   242 len: 
> 232083 comp:     0 flen: 32
> prods-071645.log:09/10/07 16:48:32 BPD sid: 10101 pid:   245 len: 
> 222060 comp:     0 flen: 32
> prods-071650.log:09/10/07 16:51:33 BPD sid: 10101 pid:   248 len: 
> 175297 comp:     0 flen: 32
> prods-071650.log:09/10/07 16:54:35 BPD sid: 10101 pid:   251 len: 
> 178272 comp:     0 flen: 32
> prods-071655.log:09/10/07 16:57:32 BPD sid: 10101 pid:   257 len:    
> 962 comp:     0 flen: 32
> prods-071655.log:09/10/07 16:57:32 BPD sid: 10101 pid:   254 len: 
> 405373 comp:     0 flen: 32
> 
> But I was getting old PPS type data:
> 
> prods-071600.log:09/10/07 16:00:29 BPD sid: 10101 pid:   157 len:  
> 57792 comp:     0 flen: 32
> prods-071600.log:09/10/07 16:03:27 BPD sid: 10101 pid:   100 len: 
> 119940 comp:     0 flen: 32
> prods-071605.log:09/10/07 16:06:26 BPD sid: 10101 pid:   103 len:  
> 76228 comp:     0 flen: 32
> prods-071605.log:09/10/07 16:09:26 BPD sid: 10101 pid:   106 len:  
> 61508 comp:     0 flen: 32
> prods-071610.log:09/10/07 16:12:27 BPD sid: 10101 pid:   109 len: 
> 158783 comp:     0 flen: 32
> prods-071615.log:09/10/07 16:15:27 BPD sid: 10101 pid:   112 len:  
> 55805 comp:     0 flen: 32
> prods-071615.log:09/10/07 16:18:26 BPD sid: 10101 pid:   115 len:  
> 87806 comp:     0 flen: 32
> prods-071620.log:09/10/07 16:21:27 BPD sid: 10101 pid:   118 len:  
> 49946 comp:     0 flen: 32
> prods-071620.log:09/10/07 16:24:30 BPD sid: 10101 pid:   121 len:  
> 30185 comp:     0 flen: 32
> prods-071625.log:09/10/07 16:27:26 BPD sid: 10101 pid:   124 len:  
> 37219 comp:     0 flen: 32
> prods-071630.log:09/10/07 16:30:56 BPD sid: 10101 pid:   127 len:  
> 31263 comp:     0 flen: 32
> prods-071630.log:09/10/07 16:34:03 BPD sid: 10101 pid:   130 len: 
> 132983 comp:     0 flen: 32
> prods-071635.log:09/10/07 16:36:28 BPD sid: 10101 pid:   133 len:  
> 31118 comp:     0 flen: 32
> prods-071635.log:09/10/07 16:39:29 BPD sid: 10101 pid:   136 len:  
> 82890 comp:     0 flen: 32
> prods-071640.log:09/10/07 16:42:28 BPD sid: 10101 pid:   139 len:  
> 23053 comp:     0 flen: 32
> prods-071645.log:09/10/07 16:45:28 BPD sid: 10101 pid:   142 len: 
> 549767 comp:     0 flen: 32
> prods-071645.log:09/10/07 16:48:28 BPD sid: 10101 pid:   145 len:  
> 32711 comp:     0 flen: 32
> prods-071650.log:09/10/07 16:51:29 BPD sid: 10101 pid:   148 len:  
> 19473 comp:     0 flen: 32
> prods-071650.log:09/10/07 16:54:28 BPD sid: 10101 pid:   151 len: 
> 100656 comp:     0 flen: 32
> prods-071655.log:09/10/07 16:57:28 BPD sid: 10101 pid:   154 len:  
> 58287 comp:     0 flen: 32
> 
> I see an outage of radar data on NOAAPORT where we didn't get any Nexrad
> single site data for about 2 minutes around 1536Z.
> 
> I've yet to find anything on my end of any significance.
> 
> 
> ------------------------------------------------------------------------
> 
> 
> *Daniel Vietor*       *Mail:* devo@xxxxxxxxxxxxx
<mailto:devo@xxxxxxxxxxxxx>
> Unisys Corp   *Title:* Engineer/Meteorologist
> 2476 Swedesford Rd    *Phone:* 610-648-3623
> Malvern PA 19355      *Fax:* 610-695-5524
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe,  visit:
http://www.unidata.ucar.edu/mailing_lists/ 

_______________________________________________
ldm-users mailing list
ldm-users@xxxxxxxxxxxxxxxx
For list information or to unsubscribe,  visit:
http://www.unidata.ucar.edu/mailing_lists/ 



  • 2009 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the ldm-users archives: