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

[LDM #FDB-239245]: ldm running out of space

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 #FDB-239245]: ldm running out of space
  • Date: Mon, 05 May 2014 14:44:18 -0600
Donald,

pqact(1) processes have as their working directory the value of the LDM 
registry parameter "/pqact/datadir-path". You can see the value of this 
parameter with the command "regutil /pqact/datadir-path". A relative path in a 
pqact(1) FILE entry will be resolved against this directory. You should ensure 
that the resulting absolute pathname is the one you want.

> We are running ldm 6.11.6 on castor.rcac.purdue.edu.  We are currently
> running out of space in the ldm filesystem.  We made /ldm its own filesystem.
> We made /opt/ldm/var/data a symbolic link pointing to "../../../ldm/data"
> so data would be in the /ldm filesystem.
> 
> Right now pqact is complaining (via syslog) messages like the following:
> May  5 16:00:44 castor pqact[12026] ERROR: [filel.c:307] Deleting failed FILE 
> entry "data/gempak/nexrad/craft/KDFX/KDFX_20140505_1954"
> 
> I see that there is no file named
> /ldm/data/gempak/nexrad/craft/KDFX/KDFX_20140505_1954
> 
> However, there is a file named
> /ldm/data/data/gempak/nexrad/craft/KDFX/KDFX_20140505_1954
> 
> Do you have any idea what we have configured improperly to cause this issue?
> 
> Thanks,
> --Don
> 
> Don Kindred
> ITAP, Research Systems Group
> Purdue University
> ph: (765)496-1486

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: FDB-239245
Department: Support LDM
Priority: Normal
Status: Closed