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.
Scott, Is there any chance that I could log onto your system as the LDM user? This would speed things up considerably. > [Re: modifying /etc/syslog.conf] > Changes made. Restarted LDM. I can't seem to restart the syslog service. I'll > dig around a bit. The syslog(8) daemon should have been running and shouldn't have stopped due to editing its configuration-file. What is the output from the command ps -ef | grep syslog > Oct 25 20:37:46 fetch1 arhdata.arh.nwsar.gov[22366] NOTE: Starting Up(6.4.6): > The only error or info I see on arhdata is this: > Oct 25 20:37:49 fetch1 160.0.2.11[22380] NOTE: nullproc_6 failure to > 160.0.2.11; > RPC: Program/version mismatch; low version = 4, high version = 5 I'll have to think about the "Program/version mismatch" message. > [Re: netstat(1) output] > [root@fetch1 ~]# netstat --inet -t -a -n -p | grep LISTEN > tcp 0 0 0.0.0.0:683 0.0.0.0:* > LISTEN 8136/MsqRequestord > tcp 0 0 0.0.0.0:111 0.0.0.0:* > LISTEN 2022/portmap > tcp 0 0 0.0.0.0:51540 0.0.0.0:* > LISTEN 22309/rpc.ldmd ... The netstat(1) output indicates that your LDM server is listening on port 51540 rather than on the well-known LDM port 388. This is why your downstream LDM-s can't connect. The LDM program must be owned by root and setuid. What is the output from the command ls -l $HOME/ldm-6.4.6/bin/rpc.ldmd Regards, Steve Emmerson Ticket Details =================== Ticket ID: SVU-966060 Department: Support LDM Priority: Normal Status: On Hold