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

Jan Janak jan at iptel.org
Sat Feb 12 00:47:52 CET 2005


On 11-02 16:29, Karl A. Krueger wrote:
> 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.

  That means SER crashed. Could you enable core generation using
  ulimit -c unlimited, it would write the core even if there is one
  hanging process.

  Then, please, use gdb to display the backtrace and send it to me.
  

     Jan.




More information about the sr-users mailing list