Henning Westerholt пишет:
> 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?
It happend 3-d time. Someone (not customer) just send the incorrect message.
>
> 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?
This was the last message. I think it kill the openser:
REGISTER
sip:ipshka.com SIP/2.0\015\012
From: 111111
<sip:[EMAIL PROTECTED]>;tag=45e2159efbfb18109476942d2bc2e735\015\012
To: 111111 <sip:[EMAIL PROTECTED]>\015\012
Via: SIP/2.0/UDP
91.124.211.246:5060;iid=1293;branch=z9hG4bK3319169efbfb18109477942d2bc2e735;uas-addr=193.28.184.13;rport\015\012
CSeq: 2 REGISTER\015\012
Call-ID: [EMAIL PROTECTED]
Contact: "111111" <sip:[EMAIL PROTECTED]:5060;transport=udp>\015\012
User-Agent: \015\012
Expires: 3600\015\012
Max-Forwards: 69\015\012
Authorization: Digest username="\354\361\350\361", realm="ipshka.com",
nonce="48727b20f8dd8c3afabc4a12dfd06dc5ba4c473b", uri="sip:ipshka.com",
response="05c2e6604a1a38432fbd57e9deb9a9dc", opaque="",
algorithm=MD5\015\012
Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO, NOTIFY, OPTIONS,
PRACK\015\012
Content-Length: 0\015\012\015\012"
>
> - version of openser (openser -V)
version: openser 1.3.0-notls (x86_64/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM,
SHM_MMAP, PKG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
svnrevision: unknown
@(#) $Id: main.c 3304 2007-12-11 12:55:11Z bogdan_iancu $
main.c compiled on 13:19:56 Jun 5 2008 with gcc 4.1.2
> - server architecture and OS
[EMAIL PROTECTED] etc]# cat /proc/version
Linux version 2.6.23.8-63.fc8
([EMAIL PROTECTED]) (gcc version 4.1.2
20070925 (Red Hat 4.1.2-33)) #1 SMP Wed Nov 21 17:56:40 EST 2007
Intel MB S3000 series. Intel Pentium Core 2 Duo 2GB memory, software
SATA Raid.
> - version of postgres server and client libraries
[EMAIL PROTECTED] ~]# postgres --version
postgres (PostgreSQL) 8.2.6
-------------------------
postgresql-8.2.6-1.fc8.i386.rpm
postgresql-contrib-8.2.6-1.fc8.i386.rpm
postgresql-dbi-link-2.0.0-3.fc7.noarch.rpm
postgresql-libs-8.2.6-1.fc8.i386.rpm
postgresql-python-8.2.6-1.fc8.i386.rpm
postgresql-server-8.2.6-1.fc8.i386.rpm
> - perhaps some details about the content of the database
-- Database: openser
-- DROP DATABASE openser;
CREATE DATABASE openser
WITH OWNER = postgres
ENCODING = 'UTF8';
>
> Did you get a core dump from the crash? Inspecting the backtrace could lead
> to
> further informations why this causes a crash.
Yes. Sent directly.
>
> Cheers,
>
> Henning
>
_______________________________________________
Devel mailing list
Devel@lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/devel
