[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: Thu, 02 Jul 2020 12:12:40 -0600
Hi Gregg,

> Yes, the "elimination" of the second NOVRA multicasting on 140.90.173.x was
> the only thing that changed.  More details below.  The invocation of the
> noaaportIngestor has been the following, since you, Tom and I had the
> Google Meet call over a week ago:
> 
> *SBN1:*
> 
> [ldmcp@*sbn1* ~/logs]$ ps -ef | grep Ingest |grep -v grep
> 
> root      3132  3128  3 Jun26 ?        04:21:23 noaaportIngester -m
> 224.0.1.1 -n -l /home/ldmcp/logs/1.nmc.log
> 
> root      3133  3128  0 Jun26 ?        00:00:04 noaaportIngester -m
> 224.0.1.2 -n -l /home/ldmcp/logs/2.goes.log
> 
> root      3134  3128  6 Jun26 ?        09:46:24 noaaportIngester -m
> 224.0.1.3 -n -l /home/ldmcp/logs/3.nmc2.log
> 
> root      3135  3128  0 Jun26 ?        00:15:12 noaaportIngester -m
> 224.0.1.4 -n -l /home/ldmcp/logs/4.nopt.log
> 
> root      3136  3128  0 Jun26 ?        00:22:58 noaaportIngester -m
> 224.0.1.5 -n -l /home/ldmcp/logs/5.nmc3.log
> 
> root      3137  3128  0 Jun26 ?        00:11:05 noaaportIngester -m
> 224.0.1.8 -n -l /home/ldmcp/logs/8.exp.log
> 
> root      3138  3128  2 Jun26 ?        03:33:45 noaaportIngester -m
> 224.0.1.9 -n -l /home/ldmcp/logs/9.grw.log
> 
> root      3139  3128  2 Jun26 ?        03:18:33 noaaportIngester -m
> 224.0.1.10 -n -l /home/ldmcp/logs/10.gre.log
> 
> [ldmcp@sbn1 ~/logs]$

So, the noaaportIngester(1) processes on SBN1 didn't have an interface 
specified. This would cause them to receive every multicast packet sent to the 
proper group address *regardless of which interface it arrive on*.

Mystery solved?

Regards,
Steve Emmerson

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.