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.
Unidata Support wrote: > > ------- Forwarded Message > > >To: "Unidata Support" <address@hidden>, > >To: <address@hidden>, > >To: <address@hidden> > >cc: "Edward Hindman" <address@hidden> > >From: "Xiaodong Yan" <address@hidden> > >Subject: halo in City College of New York > >Organization: UCAR/Unidata > >Keywords: 200110021825.f92IPw115168 > > Dear Unidata support Personal, > I am sending this email, asking for help with the weather station at City > College. > The host here halo.sci.ccny.cuny.edu isn't getting new data since last week. > I checked the ldmd.log files. It keeps on saying" can't contact portmapper. > .." > > Can you guys give me a clue, what I can do with the current situation? > > There is a possibility that the school's firewall is not keep the proper > ports opened for halo since they are actively making modification recently > few days. But I can't give a conclusion based on my knowledge. If you guys > found out that's the problem I will work with school's central network > administration to deal with the problem. > > best regards, > Xiaodong Yan > ================================= > Mr. Xiaodong Yan > System Administrator, Science Computing > Room: Marshak Science Building, J-302 > City College of City University of New York > New York, NY 10031 > Tel: 212.650.7885 > Email: address@hidden > ================================= > > ------- End of Forwarded Message Hi Xiaodong, I did both an ldmping and a traceroute to your machine. Here are the results: (anne) imogene:/opt/news/man 195 % ldmping halo.sci.ccny.cuny.edu Oct 02 19:56:46 State Elapsed Port Remote_Host rpc_stat Oct 02 19:56:56 SVC_UNAVAIL 10.008482 0 halo.sci.ccny.cuny.edu h_clnt_create(halo.sci.ccny.cuny.edu): Timed out while creating connection Oct 02 19:57:21 ADDRESSED 0.000006 0 halo.sci.ccny.cuny.edu h_clnt_create(halo.sci.ccny.cuny.edu): Timed out while creating connection ^P (anne) imogene:/opt/news/man 196 % ldmping halo.sci.ccny.cuny.edu -i5 Oct 02 19:57:50 State Elapsed Port Remote_Host rpc_stat Oct 02 19:58:00 SVC_UNAVAIL 10.003324 0 halo.sci.ccny.cuny.edu h_clnt_create(halo.sci.ccny.cuny.edu): Timed out while creating connection Oct 02 19:58:05 ADDRESSED 0.000006 0 halo.sci.ccny.cuny.edu h_clnt_create(halo.sci.ccny.cuny.edu): Timed out while creating connection Oct 02 19:58:20 NAMED 10.019987 0 halo.sci.ccny.cuny.edu can't contact portmapper: RPC: Timed out Oct 02 19:58:35 SVC_UNAVAIL 9.999896 0 halo.sci.ccny.cuny.edu h_clnt_create(halo.sci.ccny.cuny.edu): Timed out while creating connection Oct 02 19:58:40 ADDRESSED 0.000006 0 halo.sci.ccny.cuny.edu h_clnt_create(halo.sci.ccny.cuny.edu): Timed out while creating connection Oct 02 19:58:55 NAMED 10.029887 0 halo.sci.ccny.cuny.edu can't contact portmapper: RPC: Timed out Oct 02 19:59:10 SVC_UNAVAIL 10.009776 0 halo.sci.ccny.cuny.edu h_clnt_create(halo.sci.ccny.cuny.edu): Timed out while creating connection This ldmping tells me that two things are happening. One is a slow connection, but we knew that was a problem for you, right? The second is that my LDM can't get to port 388 and is thus trying to contact the portmapper. (anne) imogene:/opt/news/man 197 % traceroute halo.sci.ccny.cuny.edu traceroute to halo.sci.ccny.cuny.edu (134.74.52.189), 30 hops max, 38 byte packets 1 flra-n140 (128.117.140.252) 2.615 ms 0.478 ms 0.267 ms 2 vbnsr-n2.ucar.edu (128.117.2.252) 0.824 ms 0.771 ms 0.646 ms 3 internetr-n243-104.ucar.edu (128.117.243.106) 1.365 ms 0.977 ms 0.832 ms 4 frgp-gw-1.ucar.edu (128.117.243.114) 2.032 ms 2.893 ms 1.963 ms 5 12.124.158.13 (12.124.158.13) 2.031 ms 1.971 ms 1.775 ms 6 gbr2-p60.dvmco.ip.att.net (12.123.36.142) 3.894 ms 2.743 ms 2.600 ms 7 gbr4-p80.dvmco.ip.att.net (12.122.5.29) 3.580 ms 2.848 ms 1.986 ms 8 gbr4-p80.dlstx.ip.att.net (12.122.2.101) 23.099 ms 22.853 ms 22.493 ms 9 gbr3-p60.dlstx.ip.att.net (12.122.1.137) 23.771 ms 22.875 ms 23.437 ms 10 gbr4-p20.attga.ip.att.net (12.122.2.90) 36.449 ms 37.105 ms 36.671 ms 11 gbr4-p80.wswdc.ip.att.net (12.122.2.178) 51.837 ms 51.245 ms 51.613 ms 12 gbr3-p60.wswdc.ip.att.net (12.122.1.129) 50.285 ms 50.091 ms 49.909 ms 13 gbr3-p80.n54ny.ip.att.net (12.122.2.165) 58.421 ms 57.189 ms 57.961 ms 14 gbr1-p100.n54ny.ip.att.net (12.122.1.150) 57.119 ms 56.107 ms 55.928 ms 15 gar1-p360.n54ny.ip.att.net (12.123.1.129) 57.475 ms 57.759 ms 57.427 ms 16 12.125.51.210 (12.125.51.210) 71.332 ms 69.256 ms 69.652 ms 17 at-gsr2-nyc-1-2-cuny-1.appliedtheory.net (169.130.253.130) 77.741 ms 77.208 ms 74.209 ms 18 128.228.179.67 (128.228.179.67) 74.474 ms 70.033 ms 68.761 ms 19 128.228.179.20 (128.228.179.20) 68.087 ms 69.043 ms 70.522 ms 20 128.228.92.38 (128.228.92.38) 144.028 ms 170.672 ms 121.928 ms 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * This traceroute shows either very slow connections or a firewall (or firewalls) at your end. I recommend that you contact the network people and ensure that they have opened port 388. Let me know when this has happened, and I'll try the ldmping again to confirm that your machine is accessible. Also, make sure that the portmapper is running on your machine. Currently, the LDM requires that the portmapper be running on the localhost in order to start up. To check this, just do "ps -ef | grep portmap". You should see a process called portmap or rpcbind running. Anne -- *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://www.unidata.ucar.edu/ ****************************************************