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

[Support #HDQ-517625]: Assistance requested for "Gap in packet sequence" log entries from noaaportIngester

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [Support #HDQ-517625]: Assistance requested for "Gap in packet sequence" log entries from noaaportIngester
  • Date: Wed, 24 Jun 2020 10:34:24 -0600


-------- Forwarded Message --------
Subject: New Client Reply - [Support !HDQ-517625]: Assistance requested 
for "Gap in packet sequence" log entries from noaaportIngester
Date: Wed, 24 Jun 2020 10:14:35 -0600
From: Gregory Grosshans <address@hidden>
To: address@hidden

New Client Reply: Assistance requested for "Gap in packet sequence" log 
entries from noaaportIngester

Hi Tom,

Sorry for the delayed response.  I just updated the LDM config and
restarted LDM and unfortunately see Gap errors.


[ldmcp@sbn1 ~/logs]$ grep Gap *.log

8.exp.log:20200624T161033.643115Z noaaportIngester[12944]
productMaker.c:pmStart:439          WARN  *Gap* in packet sequence: 851048
to 851758 [skipped 709]

8.exp.log:20200624T161033.668640Z noaaportIngester[12944]
productMaker.c:pmStart:439          WARN  *Gap* in packet sequence: 851758
to 851781 [skipped 22]

8.exp.log:20200624T161041.293238Z noaaportIngester[12944]
productMaker.c:pmStart:439          WARN  *Gap* in packet sequence: 851781
to 851834 [skipped 52]

8.exp.log:20200624T161045.071009Z noaaportIngester[12944]
productMaker.c:pmStart:439          WARN  *Gap* in packet sequence: 851834
to 851836 [skipped 1]

8.exp.log:20200624T161047.848035Z noaaportIngester[12944]
productMaker.c:pmStart:439          WARN  *Gap* in packet sequence: 851836
to 852438 [skipped 601]

8.exp.log:20200624T161053.771598Z noaaportIngester[12944]
productMaker.c:pmStart:439          WARN  *Gap* in packet sequence: 852438
to 853528 [skipped 1089]

[ldmcp@sbn1 ~/logs]$ cd

[ldmcp@sbn1 ~]$ ps -ef |grep noaa

root     12939 12935  5 16:10 ?        00:00:02 *noaa*portIngester -m
224.0.1.1 -n -l /home/ldmcp/logs/1.nmc.log

root     12940 12935  3 16:10 ?        00:00:01 *noaa*portIngester -m
224.0.1.2 -n -l /home/ldmcp/logs/2.goes.log

root     12941 12935 14 16:10 ?        00:00:05 *noaa*portIngester -m
224.0.1.3 -n -l /home/ldmcp/logs/3.nmc2.log

root     12942 12935  4 16:10 ?        00:00:01 *noaa*portIngester -m
224.0.1.4 -n -l /home/ldmcp/logs/4.nopt.log

root     12943 12935  4 16:10 ?        00:00:01 *noaa*portIngester -m
224.0.1.5 -n -l /home/ldmcp/logs/5.nmc3.log

root     12944 12935  3 16:10 ?        00:00:01 *noaa*portIngester -m
224.0.1.8 -n -l /home/ldmcp/logs/8.exp.log

root     12945 12935  5 16:10 ?        00:00:02 *noaa*portIngester -m
224.0.1.9 -n -l /home/ldmcp/logs/9.grw.log

root     12946 12935  4 16:10 ?        00:00:01 *noaa*portIngester -m
224.0.1.10 -n -l /home/ldmcp/logs/10.gre.log

ldmcp    13107 11940  0 16:11 pts/0    00:00:00 grep --color=auto *noaa*

[ldmcp@sbn1 ~]$

[ldmcp@sbn1 ~]$ cd etc

[ldmcp@sbn1 ~/etc]$ grep ^EXEC ldmd.conf |grep noaa

EXEC "*noaa*portIngester -m 224.0.1.1  -n -l /home/ldmcp/logs/1.nmc.log"

EXEC "*noaa*portIngester -m 224.0.1.2  -n -l /home/ldmcp/logs/2.goes.log"

EXEC "*noaa*portIngester -m 224.0.1.3  -n -l /home/ldmcp/logs/3.nmc2.log"

EXEC "*noaa*portIngester -m 224.0.1.4  -n -l /home/ldmcp/logs/4.nopt.log"

EXEC "*noaa*portIngester -m 224.0.1.5  -n -l /home/ldmcp/logs/5.nmc3.log"

EXEC "*noaa*portIngester -m 224.0.1.8  -n -l /home/ldmcp/logs/8.exp.log"

EXEC "*noaa*portIngester -m 224.0.1.9  -n -l /home/ldmcp/logs/9.grw.log"

EXEC "*noaa*portIngester -m 224.0.1.10 -n -l /home/ldmcp/logs/10.gre.log"

[ldmcp@sbn1 ~/etc]$



Gregg

address@hidden> wrote:

> See my response below.
>
> address@hidden> wrote:
>
>> Hi Jay and Gregg,
>>
>> re:
>> > sbn1 has been configured to support multicast routing:
>> >
>> > 224.0.1.1       0.0.0.0         255.255.255.255 UH        0 0
>> 0 em2
>> > 224.0.1.2       0.0.0.0         255.255.255.255 UH        0 0
>> 0 em2
>> > 224.0.1.3       0.0.0.0         255.255.255.255 UH        0 0
>> 0 em2
>> > 224.0.1.4       0.0.0.0         255.255.255.255 UH        0 0
>> 0 em2
>> > 224.0.1.5       0.0.0.0         255.255.255.255 UH        0 0
>> 0 em2
>> > 224.0.1.6       0.0.0.0         255.255.255.255 UH        0 0
>> 0 em2
>> > 224.0.1.7       0.0.0.0         255.255.255.255 UH        0 0
>> 0 em2
>> > 224.0.1.8       0.0.0.0         255.255.255.255 UH        0 0
>> 0 em2
>> > 224.0.1.9       0.0.0.0         255.255.255.255 UH        0 0
>> 0 em2
>> > 224.0.1.10      0.0.0.0         255.255.255.255 UH        0 0
>> 0 em2
>>
>> Sounds good!
>>
>> Out of curiosity and "for the files", was this done by creating a
>> route-em2 file in /etc/sysconfig/network-scripts and then bouncing
>> the em2 interface?
>>
>
> Yes.
>
>>
>> Gregg:
>>
>> Will you be able to change the LDM configuration file setup for
>> sbn1 today and let us now the results of the change?
>>
>> Thanks for the information!
>>
>> Cheers,
>>
>> Tom
>> --
>>
>> ****************************************************************************
>> Unidata User Support                                    UCAR Unidata
>> Program
>> (303) 497-8642                                                 P.O. Box
>> 3000
>> address@hidden                                   Boulder, CO
>> 80307
>>
>> ----------------------------------------------------------------------------
>> Unidata HomePage                       http://www.unidata.ucar.edu
>>
>> ****************************************************************************
>>
>>
>> Ticket Details
>> ===================
>> Ticket ID: HDQ-517625
>> 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.
>>
>>
>>
>
> --
> *Jay Liang*
> *Storm Prediction Center* <http://www.spc.noaa.gov/>
> *NWSSPC <https://fb.com/NWSSPC> @NWSSPC
> <https://www.twitter.com/NWSSPC> NWSSPC
> <https://www.youtube.com/user/NWSSPC>*
> *Office: +1.405.325.2184*
>


-- 
**********************
*I'm primarily telecommuting.  If you need to reach me, call my work cell
405-249-5310.*




*========================================================================Email
seems to be generating increasing inefficiencies in organizations.  I
learned from a manager a Stanford Computer Science professor no longer uses
email for communication, but uses SNAIL mail, telephone calls, and person
to person visits.  I'm considering the same.  405-325-2462*

*Storm Prediction Center*

*120 David L. Boren Blvd, Suite 2330Norman, OK 73072*



Ticket Details
===================
Ticket ID: HDQ-517625
Department: Support NOAAPORT
Priority: Normal
Status: Open
Link: 
https://andy.unidata.ucar.edu/staff/index.php?_m=tickets&_a=viewticket&ticketid=31436



Ticket Details
===================
Ticket ID: HDQ-517625
Department: Support NOAAPORT
Priority: Normal
Status: Open
===================
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.