[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 19991103: LDM 5.0.8 and 'expanding input buffer size' problemwithAFOS feed
- Subject: Re: 19991103: LDM 5.0.8 and 'expanding input buffer size' problemwithAFOS feed
- Date: Thu, 4 Nov 1999 10:37:14 -0700 (MST)
Gregory,
At this point, I'm really starting to speculate. Is it possible to install
the ldm on another box that's not IRIX? My thinking is some library/etc
has changed to make the ldm behave abnormal. If we could duplicate this on
another platform then it's definitely a bug in the ldm. Could be OS
specific.
Robb...
On Thu, 4 Nov 1999, Gregory Grosshans wrote:
> On the machine in question the only feeds are DDS, PPS and AFOS. On this
> machine
> I've had a LDM queue of 25 MB for three years and it worked fine with all
> three
> feed types.
>
> There is a seperate machine with LDM ingesting NOAAPORT and on this machine
> the
> queue is 700+ MB since I'm ingesting three
> channels of NOAAPORT data.
>
> I've actually set the size of the ldm queue in the $LDMHOME/bin/ldmadmin
> script to
> 250000000. I've verified several times that the queue is of sufficient
> length.
> When I switch back to 5.0.2 I change the queue back to 25 MB and everything
> works
> fine.
>
> I tried commenting out the PPS and DDS feed types, leaving only AFOS on and
> starting 5.0.8 and still received the 'expanding input buffer size'. While
> LDM
> was running with just the AFOS feed I tried pqcat. PQCAT started and exited
> right
> away and indicated the number of products were 0.
>
> Gilbert, If I were able to have the routers and firewall changed to allow
> your LDM
> access to this machine I don't understand how the AFOS
> data would be able to get to you. Right now there are no AFOS products
> entering
> the queue, the only thing occurring is the 'Expanding input buffer size.' If
> there were AFOS products entering the queue they would also show up in one of
> the
> three other LDM machines here.
>
> Actually, that may be a key, the buffer is expanding. Robb, do you know how
> the
> buffer plays into the LDM? Does LDM load a product
> into a new dynamic buffer prior to placing it in the queue and then does it
> free
> the memory?\
>
> Thanks for your timely responses.
>
> Gregg
>
>
> Gilbert Sebenste wrote:
>
> > On Thu, 4 Nov 1999, Robb Kambic wrote:
> >
> > > Gregory,
> > >
> > > After looking at the log messages, it doesn't appear your queue is 250
> > > megabytes. Look in the data dir, what's the:
> > >
> > > % ls -l ldm.pq
> > >
> > > If it's 250 megabytes then up it again. There might be other products
> > > coming in on your afos stream, etc. If it isn't then change it in the
> > > bin/ldmadmin file to 250. Then the standard
> > >
> > > % ldmadmin stop
> > > % ldmadmin delqueue
> > > % ldmadmin mkqueue
> > > % ldmadmin start
> > >
> > > I just put the commands here for my sanity sake.
> >
> > DUH! I forgot he was also ingesting NOAAPORT. Whoa, that's 175 MB right
> > there. Up, up and away! Use 400 MB at least.
> >
> > > Also, if you comment out the dds and pps does it make any difference?
> > >
> > > Robb...
> >
> > I think that's the key here. NOAAPORT takes up 150 MB of my queue/hour,
> > and of course, we filter out scrambled NIDS and other stuff. Give it a go,
> > and then let us know!
> >
> > *******************************************************************************
> > Gilbert Sebenste
> > ********
> > Internet: address@hidden (My opinions only!) ******
> > Staff Meteorologist, Northern Illinois University ****
> > Work phone: 815-753-5492 ***
> > *******************************************************************************
> >
>
===============================================================================
Robb Kambic Unidata Program Center
Software Engineer III Univ. Corp for Atmospheric Research
address@hidden WWW: http://www.unidata.ucar.edu/
===============================================================================