[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: Thu, 03 Sep 2020 12:34:14 -0600
Hi Gregg,

> Here is the output you requested.
> 
> I think the OS was patched based on the differences in the uname output
> between SBN1 and SBN2 in my earlier email.  I'll ask Jay for specifics and
> let you know.
> 
> [ldmcp@sbn2 ~]$ df ~ldm
> Filesystem                    1K-blocks       Used Available Use% Mounted on
> nfsusers:/vol/vol1/users/ldm 1825361152 1650555200 174805952  91% /users/ldm
> [ldmcp@sbn2 ~]$
> [ldmcp@sbn2 ~]$ df ~ldmcp
> Filesystem                 1K-blocks     Used Available Use% Mounted on
> /dev/mapper/rhel_sbn2-home 183534020 48725128 134808892  27% /home
> [ldmcp@sbn2 ~]$

What's is user "ldmcp?"

> [ldmcp@sbn2 ~]$ mount | grep setuid
> [ldmcp@sbn2 ~]$

grep(1) for "suid"; not "setuid".

And would you please send me the output of "df ~ldm/bin".

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.