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

[LDM #TCW-702523]: downstream LDM server not receiving all data (e.g. nexrad) from local LDM/NOAAPORT ingest systems

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 #TCW-702523]: downstream LDM server not receiving all data (e.g. nexrad) from local LDM/NOAAPORT ingest systems
  • Date: Fri, 04 Sep 2020 11:54:34 -0600
HI Gregg,

You might also try resetting the real-time scheduling parameter to 950000 *and* 
setting the hard real-time priority limit for the LDM user in file 
"/etc/security/limits.conf":

    ldm hard rtprio 99

You'll have to reboot the computer.

> Some more nuances on the RHEL OS SPC is using.
> 
> *The two SPC* servers SBN1 and SBN2 are *running RHEL 7.8:*
> which became available 3/31/2020, Kernel 3.10.0-1127, redhat-release Errata
> Date: 2020-03-31 RHBA-2020:1033
> <https://access.redhat.com/errata/RHBA-2020:1033>
> 
> there are some subtle differences between the two servers (see bold section
> in uname -a in prior email).

I noticed that. Interesting what a difference a small change can make.

> *The AWC *server for SBN ingest is *running RHEL 7.7:*
> which became available 8/16/2019, Kernel 3.10.0-1062, redhat-release Errata
> Date: 2019-08-06 RHBA-2019:2351
> <https://access.redhat.com/errata/RHBA-2019:2351>

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: TCW-702523
Department: Support LDM
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.