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.
David, > Oops, I accidentally killed process 7671 instead of sending SIGUSR2. So I > restarted the edex server and sent SIGUSR2 to pid 21215, which is the process > requesting NOTHER. Looks like the time is a problem. Here is what I get: > > 20180206T194717.003320Z idd.unidata.ucar.edu[21215] INFO > error.c:236:err_log() Ignoring too-old product: 427861 > 20180206183258.799160 NOTHER 641563 TISI15 KNES 061832 PAA > 20180206T194726.472098Z idd.unidata.ucar.edu[21215] INFO > error.c:236:err_log() Ignoring too-old product: 1486903 > 20180206183259.532239 NOTHER 641564 TISI01 KNES 061832 PAA > 20180206T194726.596793Z idd.unidata.ucar.edu[21215] INFO > error.c:236:err_log() Ignoring too-old product: 20632 > 20180206183259.534551 NOTHER 641565 TISI03 KNES 061832 PAB > > My system time looks correct on my end. Don't worry about it. That's just your system catching-up and, somehow, getting too-old data-products initially. If you send a SIGUSR2 to 21215, does it log the same products as a notifyme(1) in another window? Regards, Steve Emmerson Ticket Details =================== Ticket ID: ORN-677013 Department: Support LDM Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.