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

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

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: [LDM #MFT-584849]: Errors from noaaportIngester process
  • Date: Fri, 09 Feb 2018 14:28:37 -0700
Carissa,

address@hidden> wrote:

> Bhagat just ran this for me....does this tell you something? The first
> one/green is my happy system, the second one/red is my angry system.
>

Is the "bad" system in Boulder?


> I should also note if it wasn't already we are running ldm-6.12.14.
>
> [sysadm@vm-lnx-sbn1 ~]$ sudo sysctl -a |grep ipfrag_max_dist
> [sudo] password for sysadm:
> *net.ipv4.ipfrag_max_dist = 4096*
>

Good system. Have a cookie.

You could also set the value to zero to disable sequence-checking of IP
fragments.


> [sysadm@vm-bldr-sbn1 ~]$ sudo sysctl -a |grep ipfrag_max_dist
> [sudo] password for sysadm:
> *net.ipv4.ipfrag_max_dist = 64*
>

Bad system! No cookie for you!

The value should be zero or 4096 or greater. A value of 64 is known to
cause reception problems.

If this value is changed, then the LDM system will need to be restarted. If
the problem persists, then the computer might have to be re-booted.

What about the other system parameter, net.ipv4.conf.default.rp_filter?

Regards,
Steve Emmerson



Ticket Details
===================
Ticket ID: MFT-584849
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.