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

[LDM #MFT-584849]: Errors from noaaportIngester process

Hi Justin,

It looks like NOAAPort reception at the Boulder campus isn't as good as others.

Unfortunately, the fellow who can help you the most, Tom Yoksas, is out skiing 
today. He'll be back in the office tomorrow, at which time we'll confab on what 
can be done.

Setting up a cross-feed between College Park and Boulder is a good idea and not 
just a workaround.

If we need to talk to you, is that possible?

> We run four RedHat 6 Linux systems that receive data from a SBN dishes via
> a DVB signal, 2 are in College Park, MD and the other 2 are in Boulder CO.
> 
> We have found that our systems in Boulder are missing over 100,000 products
> a day compared to our College Park system. Looking at our noaaportIngester
> log on one of the Boulder systems for channel 1 we are seeing these types
> of errors:
> 
> Feb 06 17:59:30 noaaportIngester[9189] WARN: Gap in packet sequence:
> 130361016 to 130361019 [skipped 2]
> Feb 06 17:59:30 noaaportIngester[9189] ERROR: OOPS, start of new product
> [10174607 ] with unfinished product 10174606
> Feb 06 17:59:30 noaaportIngester[9189] ERROR: Product definition header
> version 1 pdhlen 16
> Feb 06 17:59:30 noaaportIngester[9189] ERROR: PDH transfer type 71
> Feb 06 17:59:30 noaaportIngester[9189] ERROR: header length 52 [pshlen = 36]
> Feb 06 17:59:30 noaaportIngester[9189] ERROR: blocks per record 1 records
> per block 1
> Feb 06 17:59:30 noaaportIngester[9189] ERROR: product seqnumber 10174607
> block number 0 data block size 1761
> Feb 06 17:59:30 noaaportIngester[9189] ERROR: product header flag 1
> Feb 06 17:59:30 noaaportIngester[9189] ERROR: prodspecific data length 0
> Feb 06 17:59:30 noaaportIngester[9189] ERROR: bytes per record 0
> Feb 06 17:59:30 noaaportIngester[9189] ERROR: Fragments = 0 category 1
> Feb 06 17:59:30 noaaportIngester[9189] ERROR: next header offset 0
> Feb 06 17:59:30 noaaportIngester[9189] ERROR: original seq number 0
> Feb 06 17:59:30 noaaportIngester[9189] ERROR: receive time 1517939967
> Feb 06 17:59:30 noaaportIngester[9189] ERROR: transmit time 1517939969
> Feb 06 17:59:30 noaaportIngester[9189] ERROR: run ID 0
> Feb 06 17:59:30 noaaportIngester[9189] ERROR: original run id 0
> 
> We are seeing over 100,000 of these types of error messages in Boulder
> compared to College Park which sees a few thousand and both of our systems
> in Boulder are seeing the same number of errors, over 100,000.
> 
> There seems to be some problem with the DVB signal being broadcast which
> our virtual systems in Boulder are listening to (we are also running these
> over a virtual system in College Park). I've included one of our network
> administrators (Anuj) who is familiar with the actual physical equipment
> configuration. Do you know of, or have you seen, what can cause this type
> of behavior/performance? Loosing over 100k products has had quite an impact
> to our processing in Boulder and we've set up cross feeding the LDM systems
> between College Park and Boulder to not lose any data.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: MFT-584849
Department: Support NOAAPORT
Priority: Normal
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.