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 Dave, As per the email I sent outside of our inquiry tracking system, I believe that the problem you were seeing was, indeed, caused by the one hour clock error on the ECMWF LDM machine. Again, it is _CRITICAL_ that the clocks on machines used for LDM-LDM transfers to be accurate. > I'm wondering if you can help debug this problem with TIGGE. > > Baudouin first sent this message: > > Hi David, > it is true that we have not been feed the queue all night long (because > of the power failure), but there are 300000 products in the queue. > > ldm@tigge-ldm:~> pqmon > Mar 22 08:42:48 pqmon NOTE: Starting Up (9706) > Mar 22 08:42:48 pqmon NOTE: nprods nfree nempty nbytes maxprods maxfree > minempty maxext age > Mar 22 08:42:48 pqmon NOTE: 318717 1 97337532 137851373896 923672 3 > 96732578 262148626104 118737 > Mar 22 08:42:48 pqmon NOTE: Exiting > > Does that mean that you only get products which are push in the queue > after your subscription? > > Baudouin > > > Later he wrote that the tigge-ldm.ecmwf.int log files report the > following: > > Mar 22 12:09:45 tigge-ldm dataportal(noti)[5146] NOTE: topo: > dataportal.ucar.edu ANY > Mar 22 12:14:47 tigge-ldm dataportal(noti)[5146] ERROR: > nullproc5(dataportal.ucar.edu): RPC: Unable to receive > Mar 22 12:15:12 tigge-ldm dataportal(noti)[5183] NOTE: Starting > Up(6.4.5.1/5): 20060322203837.216 TS_ENDT {{ANY, ".*"}} > Mar 22 12:15:12 tigge-ldm dataportal(noti)[5183] NOTE: topo: > dataportal.ucar.edu ANY > Mar 22 12:20:13 tigge-ldm dataportal(noti)[5183] ERROR: > nullproc5(dataportal.ucar.edu): RPC: Unable to receive > Mar 22 12:20:38 tigge-ldm dataportal(noti)[5195] NOTE: Starting > Up(6.4.5.1/5): 20060322203837.216 TS_ENDT {{ANY, ".*"}} > Mar 22 12:20:38 tigge-ldm dataportal(noti)[5195] NOTE: topo: > dataportal.ucar.edu ANY > Mar 22 12:25:39 tigge-ldm dataportal(noti)[5195] ERROR: > nullproc5(dataportal.ucar.edu): RPC: Unable to receive > Mar 22 12:26:04 tigge-ldm dataportal(noti)[5694] NOTE: Starting > Up(6.4.5.1/5): 20060322203837.216 TS_ENDT {{ANY, ".*"}} > Mar 22 12:26:04 tigge-ldm dataportal(noti)[5694] NOTE: topo: > dataportal.ucar.edu ANY > > > Now he reports that the clock is wrong on tigge-ldm. Yesterday Tom had > me run the 'notifyme' program > as follows: > notifyme -vl- -o 10000 -h tigge-ldm.ecmwf.int > which reported only the following: > > Mar 23 21:56:27 notifyme[7931] NOTE: Starting Up: tigge-ldm.ecmwf.int: > 20060323190947.623 TS_ENDT {{ANY, ".*"}} > Mar 23 21:56:27 notifyme[7931] NOTE: LDM-5 desired product-class: > 20060323190947.623 TS_ENDT {{ANY, ".*"}} > Mar 23 21:56:27 notifyme[7931] NOTE: NOTIFYME(tigge-ldm.ecmwf.int): OK > > But today I tried adding a '0' to the time: > > notifyme -vl- -o 100000 -h tigge-ldm.ecmwf.int > > and suddenly I'm seeing products: > > Mar 23 21:57:14 notifyme[8116] NOTE: Starting Up: tigge-ldm.ecmwf.int: > 20060322181034.456 TS_ENDT {{ANY, ".*"}} > Mar 23 21:57:14 notifyme[8116] NOTE: LDM-5 desired product-class: > 20060322181034.456 TS_ENDT {{ANY, ".*"}} > Mar 23 21:57:14 notifyme[8116] NOTE: NOTIFYME(tigge-ldm.ecmwf.int): OK > Mar 23 21:57:15 notifyme[8116] INFO: 428963 20060322211420.593 > EXP 000 tigge_ecmf_cf_20060322_1200_102_0_10_meter_u_velocity_0.grib > Mar 23 21:57:15 notifyme[8116] INFO: 428963 20060322211420.686 > EXP 000 tigge_ecmf_cf_20060322_1200_102_0_10_meter_v_velocity_0.grib > Mar 23 21:57:16 notifyme[8116] INFO: 428963 20060322211420.734 > EXP 000 > tigge_ecmf_cf_20060322_1200_102_0_convective_available_potential_energy_ > 0.grib > > > Does this suggest the clock issue is the source of the problem? > -dave > > Cheers, Tom **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: PDA-304144 Department: Support IDD Priority: Normal Status: Closed