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.
Daniella, > I'm trying start LDM and some problems happens: > > First when I did "ldmadmin start" that's apear: > > Couldn't get time from time-server at otc1.psu.edu using the ntpdate(1) > utility, "/usr/sbin/ntpdate". If the utility is valid and this happens > often, then remove otc1.psu.edu from variable "@time_servers" in the > configuration-file, /usr/local/ldm/etc/ldmadmin-pl.conf. > > Couldn't get time from time-server at ntppub.tamu.edu using the ntpdate(1) > utility, "/usr/sbin/ntpdate". If the utility is valid and this happens > often, then remove ntppub.tamu.edu from variable "@time_servers" in the > configuration-file, /usr/local/ldm/etc/ldmadmin-pl.conf. > > Couldn't get time from time-server at ntp1.cs.wisc.edu using the > ntpdate(1) utility, "/usr/sbin/ntpdate". If the utility is valid and this > happens often, then remove ntp1.cs.wisc.edu from variable "@time_servers" > in the configuration-file, /usr/local/ldm/etc/ldmadmin-pl.conf. > > Couldn't get time from time-server at timeserver.unidata.ucar.edu using > the ntpdate(1) utility, "/usr/sbin/ntpdate". If the utility is valid > and this happens often, then remove timeserver.unidata.ucar.edu > from variable "@time_servers" in the configuration-file, > /usr/local/ldm/etc/ldmadmin-pl.conf. > > Couldn't get time from time-server at ntp.ucsd.edu using the ntpdate(1) > utility, "/usr/sbin/ntpdate". If the utility is valid and this happens > often, then remove ntp.ucsd.edu from variable "@time_servers" in the > configuration-file, /usr/local/ldm/etc/ldmadmin-pl.conf. > > You should either fix the problem (recommended) or disable time-checking > by setting the variable "$check_time" to 0 in the configuration-file, > /usr/local/ldm/etc/ldmadmin-pl.conf, (not recommended). For some reason, your computer couldn't contact any of the time-serving computers. This might indicate a problem with your networking. > The product-queue is OK. > Checking pqact(1) configuration-file(s)... > /usr/local/ldm/etc/pqact.conf: syntactically correct > /home/gempak/GEMPAK5.11.4/ldm/etc/pqact.gempak: syntactically correct > etc/pqact.gempak_decoders: syntactically correct > etc/pqact.gempak_nwx: syntactically correct > etc/pqact.gempak_images: syntactically correct > etc/pqact.gempak_nexrad: syntactically correct > etc/pqact.gempak_craft: syntactically correct > etc/pqact.conf_mcidasA: syntactically correct > etc/pqact.conf_mcidasB: syntactically correct > Checking LDM configuration-file (/usr/local/ldm/etc/ldmd.conf)... > Starting the LDM server... > > "feedme" > and then no data arrive here. > I know ldmd.conf is right because data arrive in other computer. > > That's my ldmd.log: The log file contained this error-message: > Sep 2 08:20:41 jason pqact[558] ERROR: Couldn't exec(decoders/dcnldn): No > such file or directory This indicates that the GEMPAK decoder $HOME/decoders/dcnldn doesn't exist. I suspect that you need to change the pathname of the decoder to reference the GEMPAK installation. The following error-message were also in the log file: > Sep 2 08:20:41 jason idd.cptec.inpe.br[555] ERROR: Disconnecting due to LDM > failure; Couldn't get IP address of host idd.cptec.inpe.br; no such host is > known > Sep 2 08:20:41 jason idd.cptec.inpe.br[557] ERROR: Disconnecting due to LDM > failure; Couldn't get IP address of host idd.cptec.inpe.br; no such host is > known > Sep 2 08:20:41 jason idd.cptec.inpe.br[554] ERROR: Disconnecting due to LDM > failure; Couldn't get IP address of host idd.cptec.inpe.br; no such host is > known > Sep 2 08:20:41 jason idd.cptec.inpe.br[556] ERROR: Disconnecting due to LDM > failure; Couldn't get IP address of host idd.cptec.inpe.br; no such host is > known They indicate that your computer couldn't convert the hostname idd.cptec.inpe.br to an IP address. This indicates that either the hostname is incorrect or that there's something wrong with your domain name service. You can verify this by the command "ping idd.cptec.inpe.br". I recommend showing this to your network administrator. > I'm runnig LDM in Ubuntu. > > Thank you for your help, > > Daniella Bourguinon Regards, Steve Emmerson Ticket Details =================== Ticket ID: AOS-951017 Department: Support LDM Priority: Normal Status: Closed