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.
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.
I agree with Mike. If the LDM is running, you should be able to ping it if there are no firewalls blocking port 388. Gilbert On Jun 5, 2016, at 6:01 PM, Michael Dross <mdross@xxxxxxxxxxxxxxxxxx<mailto:mdross@xxxxxxxxxxxxxxxxxx>> wrote: What I do to rule ipables in/out is to turn off iptables for a minute and run a ldmping test. If successful you know iptables is the issue. Allow port 388. Sent from my iPhone On Jun 5, 2016, at 3:53 PM, Donna Cote <d-cote@xxxxxxxx<mailto:d-cote@xxxxxxxx>> wrote: I thought that was for logging properly - which is working fine. I'm wondering about the iptables. I will run the setuid in a little while (stepping away from the computer to mow the lawn...might not be able to mow tomorrow). On Jun 5, 2016 2:45 PM, "Patrick L. Francis" <wxprofessor@xxxxxxxxx<mailto:wxprofessor@xxxxxxxxx>> wrote: That sounds like your setuids did not execute ☺ Goto your source directory and: su root -c ‘make root-actions’ cheers, --patrick ………………………………………………………… Patrick L. Francis PhD DMin Vice President of Research & Dev Aeris Weather http://aerisweather.com/ http://facebook.com/wxprofessor/ ………………………………………………………… .. From: ldm-users-bounces@xxxxxxxxxxxxxxxx<mailto:ldm-users-bounces@xxxxxxxxxxxxxxxx> [mailto:ldm-users-bounces@xxxxxxxxxxxxxxxx<mailto:ldm-users-bounces@xxxxxxxxxxxxxxxx>] On Behalf Of Donna Cote Sent: Sunday, June 5, 2016 3:41 PM To: LDM <ldm-users@xxxxxxxxxxxxxxxx<mailto:ldm-users@xxxxxxxxxxxxxxxx>> Subject: [ldm-users] diagnosing problem when ldmping works one-way (not both ways) I have recently started up an LDM server for the sole purpose of gathering and holding rtstats data for our relay, cluster and storage LDM systems. The new LDM is on our host called earthdata. Now, I can ssh, scp, and ping just fine between our systems but ldmping on any of our LDM servers gives me a "SVC_UNAVAIL" message. All of our LDM is version 6.12.14. I have checked the exec entry in the ldmd.conf file. I have checked the allow and request entries. I have restarted LDM on each system. Still, curoi - to - earthdata is "SVC_UNAVAIL" while earthdata - to - curoi is "RESPONDING" just fine. With the notifyme utility, I see no rtstats data getting to earthdata. Any ideas on what to check for and how I could fix this? Thanks, Donna > [ldm@curoi ~]$ ldmping earthdata > Jun 05 04:03:46 ulog INFO: State Elapsed Port Remote_Host > rpc_stat > Jun 05 04:03:46 ulog INFO: Resolving earthdata to 128.194.165.79 took > 0.000851 seconds > Jun 05 04:03:56 ulog ERROR: SVC_UNAVAIL 10.000997 0 earthdata > h_clnt_create(earthdata): Timed out while creating connection > Jun 05 04:04:21 ulog ERROR: ADDRESSED 0.000002 0 earthdata > h_clnt_create(earthdata): Timed out while creating connection > ^C > > [ldm@curoi ~]$ grep -w earthdata etc/ldmd.conf > exec "rtstats -f ANY -h earthdata.tamu.edu<http://earthdata.tamu.edu>" > allow ANY ^((earthdata)|(earthdata\.tamu\.edu))$ > [ldm@curoi ~]$ > > ---------------------------------- > > [ldm@earthdata ~]$ ldmping curoi > Jun 05 04:03:23 ulog INFO: State Elapsed Port Remote_Host > rpc_stat > Jun 05 04:03:23 ulog INFO: Resolving curoi to 128.194.165.100 took 0.001789 > seconds > Jun 05 04:03:23 ulog INFO: RESPONDING 0.004038 388 curoi > Jun 05 04:03:48 ulog INFO: RESPONDING 0.000335 388 curoi > ^C > > > > [ldm@earthdata ~]$ > grep curoi etc/ldmd.conf > > request ANY "^rtstats" curoi.tamu.edu<http://curoi.tamu.edu> > > allow ANY ^((curoi)|(curoi\.tamu\.edu))$ > > [ldm@earthdata ~]$ _______________________________________________ NOTE: All exchanges posted to Unidata maintained email lists are recorded in the Unidata inquiry tracking system and made publicly available through the web. Users who post to any of the lists we maintain are reminded to remove any personal information that they do not want to be made public. ldm-users mailing list ldm-users@xxxxxxxxxxxxxxxx<mailto:ldm-users@xxxxxxxxxxxxxxxx> For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/ _______________________________________________ NOTE: All exchanges posted to Unidata maintained email lists are recorded in the Unidata inquiry tracking system and made publicly available through the web. Users who post to any of the lists we maintain are reminded to remove any personal information that they do not want to be made public. ldm-users mailing list ldm-users@xxxxxxxxxxxxxxxx<mailto:ldm-users@xxxxxxxxxxxxxxxx> For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
ldm-users archives: