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

Re: synoptic decoder went crazy?

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: Re: synoptic decoder went crazy?
  • Date: Tue, 4 Apr 2006 16:13:42 -0600 (MDT)
On Tue, 4 Apr 2006, Tom Baltzer wrote:

> Hi Robb,
>
>
>
> The synoptic decoder on lead4 seemed to go crazy today and started logging
> huge volumes to it's process log file.
>
>
>
> The messages looked like this:
>
>
>
> Malformed UTF-8 character (unexpected continuation byte 0xb0, with no
> preceding start byte) in index at decoders/syn2nc line 620, <STDIN> chunk
> 1662.
>
> Malformed UTF-8 character (unexpected non-continuation byte 0xfb,
> immediately after start byte 0xf3) in index at decoders/syn2nc line 620,
> <STDIN> chunk 1662.

Hey Tom,


yea, some folks are starting to use uni chars consisting of 2 bytes
instead of one.  i need to look it up, but there are some flags that need
to be in the decoder and they only work with newer versions of perl. so
shut it down until i figure it out. i would keep tabs on the other perl
decoders cuz they could have the same problem.

thanks,
robb...


>
> Malformed UTF-8 character (unexpected non-continuation byte 0x36,
> immediately after start byte 0xfb) in index at decoders/syn2nc line 620,
> <STDIN> chunk 1662.
>
> Malformed UTF-8 character (unexpected continuation byte 0xb0, with no
> preceding start byte) in index at decoders/syn2nc line 620, <STDIN> chunk
> 1662.
>
> Malformed UTF-8 character (unexpected non-continuation byte 0xfb,
> immediately after start byte 0xf3) in index at decoders/syn2nc line 620,
> <STDIN> chunk 1662.
>
> Malformed UTF-8 character (unexpected non-continuation byte 0x36,
> immediately after start byte 0xfb) in index at decoders/syn2nc line 620,
> <STDIN> chunk 1662.
>
>
>
>
>
>
>
> We've shut her down and restarted - thus far no synoptic data appears to
> have come across the wire.
>
>
>
> Any thoughts on this?
>
>
>
> Thanks,
> Tom.
>
>
>
> Tom Baltzer
>
> Software Engineer
>
> UCAR Office of Programs
> Unidata Program Center
> P.O. Box 3000
> Boulder, CO 80307-3000
>
>
>
> E-mail: address@hidden
>
> Phone: 303-497-8637
>
>
>
>

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================