NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Harry, >Date: Mon, 24 Mar 2003 11:55:29 -0800 >From: "Harry Chen" <address@hidden> >Organization: CWB&NSSL >To: Steve Emmerson <address@hidden> >Subject: Re: 20030320: ldmsend The above message contained the following: ldmd.conf: ... # send anything to your own machine #allow ANY # ^((localhost|loopback)|(127\.0\.0\.1\.?$)|([a-z].*\.unidata\.ucar\.edu\.?$)) The above entry is disabled. This will prevent the LDM from connecting to itself, which it must do in order to work correctly. Please enable the above entry in your "ldmd.conf" file by changing it to the following: # send anything to your own machine allow ANY ^((localhost|loopback)|(127\.0\.0\.1\.?$)|([a-z].*\.unidata\.ucar\.edu\.?$)) I can't diagnose the problem between host kucrain03 and host wfldm because the log file entries that you sent me don't overlap in time. The time-interval of kucrain03's logfile is Mar 21 22:44:49 through Mar 21 22:44:51 but the time-interval of wfldm's logfile is Mar 21 07:40:27 through Mar 21 22:40:52 The LDM system requires that the system clocks be accurate. This is typically done by using the free-available "ntpd" utility. As I said before, troubleshooting an LDM system can be difficult. Is there any way that I can log onto hosts kucrain03 and wfldm as the LDM user? Regards, Steve Emmerson