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.
Hi Ron, re: > Here is the result of that line. Sorry, since ~ldm/bin is a link to ~ldm/runtime/bin, the 'ls' invocation that needs to be run (and output examined and sent back to us) is: <as 'ldm'> cd ~ldm ls -alt bin/ What we are looking for is the permissions on 'hupsyslog' and 'ldmd'... both need to be owned by 'root' and 'setuid root'. For example, here is the listing for these routines from the LDM v6.12.14 installation on one of my development machines: -rwsr-xr-x 1 root ldm 108515 Dec 12 2015 ldmd -rwsr-xr-x 1 root ldm 12412 Dec 12 2015 hupsyslog re: > I have rebooted my computer a few times and that doesn't help. After a reboot (e.g., now assuming you just rebooted), does the PID reported in the 'hupsyslog' error match the value in the rsyslogd PID file, /var/run/syslogd.pid? The reason I suggested that rebooting might be the fix was that those two values did not match in the listings that you had sent previously. One comment: - I noticed that the PATH defined for your 'ldm' user (as listed by 'ldmadmin config') has the ~ldm/ldm-6.9.8/bin directory hardcoded at the beginning of PATH: PATH: /home/ldm/ldm-6.9.8/bin:/home/ldm/decoders:/home/ldm/util:/home/ldm/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/ldm/.local/bin:/home/ldm/bin The best way to include the LDM 'bin' directory is through inclusion of the runtime linked bin directory, ~ldm/bin (/home/ldm/bin in your case). You should remove /home/ldm/ldm-6.9.8/bin from your PATH and move /home/ldm/decoders and /home/ldm/util to the end of your PATH definition. After the changes, your PATH should look like: PATH: /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/ldm/.local/bin:/home/ldm/bin:/home/ldm/decoders:/home/ldm/util OR, depending on if /home/ldm/.local/bin has anything that is needed AND does not contain old LDM bin content: PATH: /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/ldm/bin:/home/ldm/decoders:/home/ldm/util:/home/ldm/.local/bin OR even: PATH: /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/ldm/bin:/home/ldm/decoders:/home/ldm/util After making the changes to PATH, please make sure that the changes are active (in scope) before trying to start the LDM again. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: HZS-503248 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.