[Serusers] Over-long fields can crash SER with PostgreSQL

Karl A. Krueger kkrueger at whoi.edu
Fri Feb 11 22:29:40 CET 2005


On Fri, Feb 11, 2005 at 10:26:39PM +0100, Jan Janak wrote:
> Did ser crash or locked up ? Usrloc has been designed to overcome
> database issues, thus if a database operation fails, usrloc should
> continue using internal memory cache.

When this happens, it appears to me that all the ser child processes
die, but one locked-up one remains.  This one has to be killed with
"kill -9" before ser can be restarted.


> If it crashed, could you, please, provide me with more information ?
> Especially SER coredump along with compiled sources would be handy.

I do not have the core, but here's the log entries from the database
error forward.  ser was running at debug level 4.

Feb 10 13:39:32 mabell /usr/sbin/ser[13053]: PG[360] submit_query query 'insert
into location (user_id,contact,expires,q,callid,cseq,replicate,flags,state,user_
agent ) values ('agaylord','sip:agaylord at 128.128.64.20:8456','2005-02-10 14:39:2
3 -0500',0.00      ,'196b2f63db33fc68',2,0,0,0,'eyeBeam release 9100a stamp 1646
0 (sn:37067be159c1a125f54c)')', result 'ERROR:  value too long for type characte
r varying(50) '
Feb 10 13:39:32 mabell /usr/sbin/ser[13057]: DBG: tcp_main_loop: dead child 5 (s
hutting down?)
Feb 10 13:39:32 mabell /usr/sbin/ser[13035]: child process 13053 exited by a sig
nal 11
Feb 10 13:39:32 mabell /usr/sbin/ser[13035]: core was not generated
Feb 10 13:39:32 mabell /usr/sbin/ser[13035]: INFO: terminating due to SIGCHLD
Feb 10 13:39:32 mabell /usr/sbin/ser[13039]: INFO: signal 15 received
Feb 10 13:39:32 mabell /usr/sbin/ser[13038]: INFO: signal 15 received
Feb 10 13:39:32 mabell /usr/sbin/ser[13037]: INFO: signal 15 received
Feb 10 13:39:32 mabell /usr/sbin/ser[13044]: INFO: signal 15 received
Feb 10 13:39:32 mabell /usr/sbin/ser[13054]: INFO: signal 15 received
Feb 10 13:39:32 mabell /usr/sbin/ser[13055]: INFO: signal 15 received
Feb 10 13:39:32 mabell /usr/sbin/ser[13056]: INFO: signal 15 received
Feb 10 13:39:32 mabell /usr/sbin/ser[13057]: INFO: signal 15 received
Feb 10 13:39:32 mabell /usr/sbin/ser[13035]: PG[272] db_close entry
Feb 10 13:39:32 mabell /usr/sbin/ser[13035]: PG[272] db_close entry

After this point ser is entirely unresponsive.


I am running version 0.8.14 with no source modifications other than to
install the PostgreSQL module.

-- 
Karl A. Krueger <kkrueger at whoi.edu>
Network Security -- Linux/Unix Systems Support -- Etc.
Woods Hole Oceanographic Institution




More information about the sr-users mailing list