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.
EuiHyun, > I omitted to attach log message of my LDM machine > sorry..... > > I guess it is limitation of COSMIC. > Is it right? > Now, I am reading manual page of LDM processor. > > This is part of my log file. > > Dec 1 22:04:28 ssmgwdss cosmic-io.cosmic.ucar.edu[11594] ERROR: > Disconnecting due to LDM failure; nullproc_6 failure to > cosmic-io.cosmic.ucar.edu; RPC: Unable to receive; errno = Connection reset > by peer > Dec 1 22:04:58 ssmgwdss cosmic-io.cosmic.ucar.edu[11594] NOTE: LDM-6 > desired product-class: 20091201120458.328 TS_ENDT {{EXP, ".*"}} > Dec 1 22:04:58 ssmgwdss cosmic-io.cosmic.ucar.edu[11594] ERROR: > Disconnecting due to LDM failure; nullproc_6 failure to > cosmic-io.cosmic.ucar.edu; RPC: Unable to receive; errno = Connection reset > by peer > Dec 1 22:05:28 ssmgwdss cosmic-io.cosmic.ucar.edu[11594] NOTE: LDM-6 > desired product-class: 20091201120528.626 TS_ENDT {{EXP, ".*"}} > Dec 1 22:05:28 ssmgwdss cosmic-io.cosmic.ucar.edu[11594] ERROR: > Disconnecting due to LDM failure; nullproc_6 failure to > cosmic-io.cosmic.ucar.edu; RPC: Unable to receive; errno = Connection reset > by peer The error messages mean that the LDM on host "ssmgwdss" was able to connect to the LDM on host "cosmic-io.cosmic.ucar.edu" at the TCP level, but not at the LDM level. I suspect that the LDM configuration-file on "cosmic-io" doesn't have an ACCEPT entry that matches the request from "ssmgwdss". You can verify this by executing the following command on "ssmgwdss": notifyme -vl- -h cosmic-io.cosmic.ucar.edu -f EXP -o 3600 You should see the metadata from the last hours worth of products. If you don't, then you're not allowed to receive that data. It could be that the ACCEPT entry that should match the request from "ssmgwdss" is based on the fully-qualified domain-name of the host and that the reverse-DNS lookup (performed by the LDM on "cosmic-io" to convert the IP of address of "ssmgwdss" to the fully-qualified domain-name) is failing. This can be verified by executing the nslookup(1) or dig(1) utility on "cosmic-io". If that's the case, then another ACCEPT entry should be created that uses a pattern for the IP address of "ssmgwdss" rather than a pattern for the fully-qualified domain-name. > LDM process if difficult for me. > I aniticipate hopeful message from U. > > Thank you very much. > And Merry christmas! You too! > EuiHyun Regards, Steve Emmerson Ticket Details =================== Ticket ID: SQY-147149 Department: Support LDM Priority: Normal Status: Closed