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.
Hi Jeff, I cannot get to fujita: /local/ldm/etc% ldmping fujita.afit.edu Aug 14 15:01:15 State Elapsed Port Remote_Host rpc_stat Aug 14 15:01:15 NAMED 0.089255 0 fujita.afit.edu gethostbyname(fujita.afit.edu): lookup failed Aug 14 15:01:40 NAMED 0.005297 0 fujita.afit.edu gethostbyname(fujita.afit.edu): lookup failed Aug 14 15:02:05 NAMED 0.005196 0 fujita.afit.edu gethostbyname(fujita.afit.edu): lookup failed Aug 14 15:02:30 NAMED 0.005246 0 fujita.afit.edu gethostbyname(fujita.afit.edu): lookup failed Aug 14 15:02:55 NAMED 0.005200 0 fujita.afit.edu gethostbyname(fujita.afit.edu): lookup failed Aug 14 15:03:20 NAMED 0.005204 0 fujita.afit.edu gethostbyname(fujita.afit.edu): lookup failed ^C/local/ldm/etc% ssh fujita.afit.edu ssh: fujita.afit.edu: no address associated with hostname. /local/ldm/etc% telnet fujita.afit.edu fujita.afit.edu: Unknown host /local/ldm/etc% rlogin fujita.afit.edu fujita.afit.edu: unknown host /local/ldm/etc% So, we obviously have some DNS issues going on, and I suspect that is the problem with the ldm as well.. Have your sys admin check out how he has configured etc/hosts. Also, what is the IP# for fujita? Thanks! -Jeff ____________________________ _____________________ Jeff Weber address@hidden Unidata Support PH:303-497-8676 COMET Case Study Library FX:303-497-8690 University Corp for Atmospheric Research 3300 Mitchell Ln http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 ________________________________________ ______________________ On Wed, 14 Aug 2002, Sitler Jeffrey L Civ AFIT/ENP wrote: > > Jeff, > We still aren't getting data. > I am guessing the power outage changed something, and myself nor the "UNIX > GURUS" can figure out what is wrong. > Here is the ldmd.log right after we try to start things up. > > fujita{jsitler}79: more ldmd.log > Aug 14 14:33:01 fujita rpc.ldmd[2236]: Starting Up (built: Feb 28 2002 > 15:37:43) > Aug 14 14:33:02 fujita pqact[2238]: Starting Up > Aug 14 14:33:02 fujita pqact[2239]: Starting Up > Aug 14 14:33:02 fujita pqbinstats[2237]: Starting Up (2236) > Aug 14 14:33:02 fujita redwood[2240]: run_requester: Starting Up: > redwood.atmos. > albany.edu > Aug 14 14:33:02 fujita striker[2241]: run_requester: Starting Up: > striker.atmos. > albany.edu > Aug 14 14:33:02 fujita profhorn[2242]: run_requester: Starting Up: > profhorn.mete > or.wisc.edu > Aug 14 14:33:04 fujita localhost[2249]: Connection from localhost > Aug 14 14:33:04 fujita localhost[2249]: Connection reset by peer > Aug 14 14:33:04 fujita localhost[2249]: Exiting > > > Any guesses on what is going on here? > > We have tried to snoop fujita going out, we have tried to snoop port 388, > and even redwood. > Nothing is showing up on snoop in regards to ldm. > We can ping without a problem, but ldm just doesn't want to seem to get > going. > > thanks > Jeff > > ps > Those fires didn't get to close to you guys out there did they? > Hope not. >