[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 11:23:54 -0700
Hi All,

In addition to the Novra status information Tom requested, have you done 
any configuration or testing with the net.ipv4.ipfrag_max_dist kernel 
tunable as mentioned in the following Unidata NOAAport config web page?  

https://www.unidata.ucar.edu/software/noaaport/current/

It would be useful to know if there's a difference in the Boulder and 
College Park systems in that regard or if they are identical?
Actually, it would be useful if you let us know what value you're
using currently on all the systems in question?

mike

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.