Dave, > Do the errors occur at the same time every day or are they scattered > throughout the day? > > If the 6 digits following the âTâ in the first field of each ERROR > message is the hour, minute, and seconds associated with the message (and the > arrival of a product), They are. The timestamp is an ISO 8601 standard. > then it looks like errors are being generated anywhere from several per > minute to every few minutes, throughout the day. > I see that the utility /usr/local/bin/STRIP is used. Does it log? If not, can > you instrument it? > STRIP isnât logging, and I donât know off-hand how to make it log. > (Redirect standard error output to a file in the pqact.conf line that invokes > it?) However, as an alternative test, I commented out all but one of the > PIPEs in our pqact.conf file that PIPE to STRIP and reread the pqact.conf > file. After 15 minutes there have been zero ERROR messages. > > Good call. > > All but one of the products that we PIPE through STRIP are NWS forecast text > products from the WMO feed. I donât think that anyone is using the locally > stored versions of those products at SFSU any more, so a brute force tactic > for addressing the error messages is simply to stop trying to save these > products at all. That doesnât get to the heart of the problem, an > unsatisfying solution in an academic sense (and because Iâm curious about > it), but it probably won't matter in any practical sense. > > I donât remember any more where we got the STRIP program. (Itâs binary > code, but we didnât compile it locally. It appears that in January of 2017 > it replaced a c-shell script consisting of one line: "/usr/bin/tr -d > '\001\003\015' >! $1â) Interesting. That function (stripping out control characters) can be accomplished via the "-strip" option of the FILE and PIPE commands: there's no reason to use /usr/local/bin/STRIP. Regards, Steve Emmerson Ticket Details =================== Ticket ID: WIW-895985 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.
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.