[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

19990603: File corruption

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.

  • Subject: 19990603: File corruption
  • Date: Thu, 03 Jun 1999 13:01:32 -0600
>From: Geff Underwood <address@hidden>
>Organization: .
>Keywords: 199906031854.MAA25141

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>We're having an odd problem with Gempak upper air data:  00Z data comes
>in, and can be used for a while, but eventually becomes unavailable.  I
>get the impression that bad data may be confusing dcuair.
>
>Here's the relevant part of pqact.conf:
>
>DDS|IDS ^U[GJKLMQS][ABCGHJMPSU][ACFKMNRSUWX].* .... ([0-3][0-9])
>        PIPE    dcuair
>                data/gempak/upperair/(\1:yy)(\1:mm)\1_upa.gem
>
>We're running ldm 5.0.6 under IRIX 6.5.2m, in case that matters.
>
>-----BEGIN PGP SIGNATURE-----
>Version: PGPfreeware 5.0i for non-commercial use
>Charset: noconv
>
>iQA/AwUBN1bPRsXnbEgeKlfEEQL4mQCgu8vvVHfL7eLLzBjF+fId11TXgcUAoIPD
>IMRKzzWQ1dbaZZ+vxGSjKHRO
>=aKHv
>-----END PGP SIGNATURE-----
>

Geff,

We don't see any problems with the upperair files here. This sounds like
the same problem you are having with dchrly. I did not hear whether
the dchrly binary I posted for you resolved your problems, but if it did
then you might want to grab my dcuair at:
~gbuddy/nawips-5.4/binary/irix/dcuair

If both of these work for you, then the problem is likely a bug that
got fixed somewhere down the line. Otherwise, you might need to check
for disk full messages in your /usr/adm/SYSLOG file.

Steve Chiswell