[OpenSER-Devel] Crash on unicode registration
Henning Westerholt
henning.westerholt at 1und1.de
Wed Jul 9 10:38:41 CEST 2008
On Tuesday 08 July 2008, Andrew O. Zhukov wrote:
> Again the same trouble
> comlete memory debug log at
>
> http://web.ipshka.com/core/
>
> Jul 7 23:17:56 ipshka openser[1980]: ERROR:postgres:val2str:
> PQescapeStringConn failed
> Jul 7 23:17:56 ipshka openser[1980]: WARNING:postgres:pg_get_result:
> 0x776080 Probable invalid query
> Jul 7 23:17:56 ipshka openser[1980]: WARNING:postgres:pg_get_result:
> 0x776080: PGRES_FATAL_ERROR
> Jul 7 23:17:56 ipshka openser[1980]: WARNING:postgres:pg_get_result:
> 0x776080: ERROR: invalid byte sequence for encoding "UTF8":
> 0xecf1e8#012HINT: This error can also happen if the byte sequence does
> not match the encoding expected by the server, which is controlled by
> "client_encoding".#012
> Jul 7 23:17:56 ipshka openser[1991]: CRITICAL:core:receive_fd: EOF on 7
Hi Andrew,
the crash is at least related to a problem with the postgres query. Does it
happens all the time, or only in some cases? Can you source this problem to
some specific record in the DB?
The error is caused from some data in your DB that is apparently not UTF-8
encoded. Even if this produce a query error, it should not crash the server.
Can you perhaps give some more details?
- version of openser (openser -V)
- server architecture and OS
- version of postgres server and client libraries
- perhaps some details about the content of the database
Did you get a core dump from the crash? Inspecting the backtrace could lead to
further informations why this causes a crash.
Cheers,
Henning
More information about the Devel
mailing list