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.
>From: William C Klein <address@hidden> >Organization: Valparaiso >Keywords: 200207191908.g6JJ8H908347 data feeds Bill, >weather.valpo.edu is the same as aeolus.valpo.edu. It's just an alias. OK, that explains everything. >Our weather dept just sent me an email saying that they are not getting >data once again. Help! > >[ aeolus : ldm : ~/logs ] >[ 3 ] > ps -u ldm > PID TTY TIME CMD > 7408 ? 0:00 ingetext > 7399 ? 1:23 pqact > 7431 ? 0:00 startxcd > 7430 ? 0:47 ingetext > 7406 ? 0:08 rpc.ldmd > 7432 ? 0:31 ingebin. > 7402 ? 26:47 rpc.ldmd > 7410 ? 0:00 ingebin. > 7405 ? 1:51 rpc.ldmd > 7397 ? 0:00 rpc.ldmd > 7401 ? 2:41 pqbinsta > 22248 ? 0:00 dmsyn.k > 22246 ? 0:00 dmraob.k > 7400 ? 2:53 pqact > 7398 ? 0:00 startxcd > 22249 ? 0:00 dmsfc.k > 7403 ? 27:23 rpc.ldmd > 22247 ? 0:00 dmmisc.k > 7437 ? 17:10 dmgrid.k > 26663 pts/2 0:00 tcsh OK, so the McIDAS decoders are ready to decode data if/when it arrives. The LDM rpc.ldmd processes are running trying to get data, so the problem must be elsewhere. >[ aeolus : ldm : ~/logs ] >[ 4 ] > > >So, ldm is running. Yup. >-rw-rw-r-- 1 ldm vumcidas 673174 Jul 22 13:49 ldmd.log > >That's within the past 2 minutes. > >Most recent error message: > >Jul 22 18:49:22 aeolus nldn2md[26669]: changing to directory >/var/data/mcidas >Jul 22 18:49:22 aeolus nldn2md[26669]: NLDN2MD -- BEGIN >Jul 22 18:49:22 aeolus nldn2md[26669]: PRODUCT CODE=LD 2002203 >184200 >Jul 22 18:49:22 aeolus nldn2md[26669]: nldninput(): Product header record >found >Jul 22 18:49:22 aeolus nldn2md[26669]: Appending to MD file: 73 >Jul 22 18:49:22 aeolus nldn2md[26669]: nldninput(): EOF on stdin >Jul 22 18:49:22 aeolus nldn2md[26669]: NLDN2MD - Flash events in file: >160206 >Jul 22 18:49:22 aeolus nldn2md[26669]: NLDN2MD -- DONE >Jul 22 18:49:22 aeolus nldn2md[26669]: Exiting >Jul 22 18:49:39 aeolus papagayo[7402]: FEEDME(papagayo.unl.edu): >h_clnt_create(papagayo.unl.edu): Timed out while creating connection > > >Does that mean that papagayo is not sending out data? Yes, it does. I just checked to see if papagayo was up and running an LDM: ldmping papagayo.unl.edu Jul 22 19:20:28 State Elapsed Port Remote_Host rpc_stat Jul 22 19:20:38 SVC_UNAVAIL 9.997358 0 papagayo.unl.edu h_clnt_create(papagayo.unl.edu): Timed out while creating connection I then tried a ping to papagayo: ping papagayo.unl.edu PING papagayo.unl.edu (129.93.52.150): 56 data bytes and got nothing. Looks like papagayo is not up! Time to switch over to your failover feed site. A quick check of the page that lists site's upstream feed hosts: http://www.unidata.ucar.edu/projects/idd/sitelist.html shows that you should be able to feed from either of the following: ldm.meteo.psu.edu weather.cod.edu To verify this before changing your ~ldm/etc/ldmd.conf file, run ldmping and notifyme to each of the hosts. For example: <login as 'ldm'> ldmping ldm.meteo.psu.edu If this returns back something like: ldmping ldm.meteo.psu.edu Jul 22 19:24:05 State Elapsed Port Remote_Host rpc_stat Jul 22 19:24:05 RESPONDING 0.114401 388 ldm.meteo.psu.edu then try: notifyme -vxl- -o 3600 -f ANY -h ldm.meteo.psu.edu This will either show you products that ldm.meteo.psu.edu is receiving or give you an error indicating that you have not been allowed by they system to request data. If neither of these sites responds to your probes, please let us know and we will arrange a different failover feed site for you. By the way, Simon Kissler is still listed as the LDM point of contact at Valparaiso. Is this correct, or should the contact information be changed to be you? Tom