Gilbert-
We’ve been seeing this too. We’re running 6.12.7. I haven’t tracked the problem
down but have not noticed any issues with the usual IR and VIS stuff we
operationally use.
Rodger
Rodger R. Getz, President and CEO
AWIS Weather Services
1735 East University Drive, Suite 101
Auburn, AL 36830-5204
Website: http://www.awis.com
Facebook: https://www.facebook.com/AWISWeatherServices
Twitter: https://twitter.com/AWISweather
Phone: (334) 826-2149 ext 1004
Toll-free: (888) 798-9955 ext 1004
Toll-free Fax: (888) 374-8027
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or legally privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.
If you received this in error, please contact the sender and delete the
material from any computer.
> On Jun 6, 2015, at 11:39 AM, Gilbert Sebenste
> <sebenste@xxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Hello everyone,
>
> Over the past few months, I have noticed an issue over at the College of
> DuPage, and at a company I work for on the side. In our ldmd.logs, on our
> NOAAport satellite ingesters only, we see something like this every 15 or 30
> minutes:
>
> Jun 6 15:46:57 sat noaaportIngester[5561] WARN: Gap in packet
> sequence: 29680041 to 29680050 [skipped 8]
> Jun 6 15:46:57 sat noaaportIngester[5561] WARN: Gap in packet
> sequence: 29680041 to 29680050 [skipped 8]
> Jun 6 15:46:57 sat noaaportIngester[5561] ERROR: Missing GOES fragment
> in sequence, last 37/169677 this 46/169677
> Jun 6 15:46:57 sat noaaportIngester[5561] ERROR: Missing GOES fragment
> in sequence, last 37/169677 this 46/169677
> Jun 6 15:46:57 sat noaaportIngester[5561] WARN: Gap in packet
> sequence: 29680050 to 29680055 [skipped 4]
> Jun 6 15:46:57 sat noaaportIngester[5561] WARN: Gap in packet
> sequence: 29680050 to 29680055 [skipped 4]
>
> It only happens with satellite imagery, as I see no other data losses in
> both receiver's logs. This happens on LDM 6.12.6, and also on 6.12.13. It
> is not consistent; that is, quite a few times the images will come in
> fine. On both sites, the C/N is above 17, and signal strength is
> excellent, around -37 to -39 dB. Is anyone else seeing this? I wish when
> this happens, and if it's possible to parse it, we would be able to see
> the WMO headers of the offending data to track this down better.
>
> Gilbert
>
> *******************************************************************************
> Gilbert Sebenste ********
> (My opinions only!) ******
> Staff Meteorologist, Northern Illinois University ****
> E-mail: sebenste@xxxxxxxxxxxxxxxxxxxxx ***
> web: http://weather.admin.niu.edu **
> Twitter: http://www.twitter.com/NIU_Weather **
> Facebook: http://www.facebook.com/niu.weather *
> *******************************************************************************
>
> _______________________________________________
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/
