INN 2.5.4 strange crash

[Petr Novopashenniy]

Good day, All!

I have INN 2.5.4 on old FreeBSD box.
After upgrade from 2.4.3, innd sometimes began to segfault.

This happens when news.daily is running.
This is gdb output from some crashes:

1)
Program terminated with signal 11, Segmentation fault.

(gdb) bt
#0  0x0 in ?? ()
#1  0x8057477 in CHANreadloop () at chan.c:1284
#2  0x8059100 in KEYgenerate (header=0x2, body=0xbfbfed98 "\220П©©╘П©©", 
bodylen=3217026468) at innd.c:750
#3  0x804d8de in _start ()

2)
(gdb) bt
#0  0x0 in ?? ()
#1  0x8057477 in CHANreadloop () at chan.c:1284
#2  0x8059100 in KEYgenerate (header=0x1, body=0xbfbfeda0 "\224П©©", 
bodylen=3217026472) at innd.c:750
#3  0x804d8de in _start ()

3)
(gdb) bt
#0  0x0 in ?? ()
#1  0x8057477 in CHANreadloop () at chan.c:1284
#2  0x8059100 in KEYgenerate (header=0x1, body=0xbfbfeda0 "\224П©©", 
bodylen=3217026472) at innd.c:750
#3  0x804d8de in _start ()

Nothing useful for me. ;(

In "Daily Usenet report" mail, I see that innstat from news.daily is 
working fine, but after that something goes wrong:

###
[dd]

news.etla.org                         1  (152)

TOTAL: 40                           121


ctlinnd: cannot send "logmode" command (dead server failure): No such 
process
ctlinnd: cannot send "go" command (dead server failure): No such process
Error log:
innd: innfeed-neva2!:25:proc:53280 blocked sleeping 5
innd: innfeed-neva1!:24:proc:53279 blocked sleeping 5
---------

[dd]
###

Last core creation time is Oct 29 03:20:19 2014, and looks like this is 
scanlogs problem. (I have no DOGROUPBASEEXPIRY=true, and I see sleep 30 in 
line 349 of news.daily, "news.daily noexpireover" start at 3:20 by cron)

Command "ctlinnd -s pause "Flushing log and syslog files" from line 114 
looks like work fine, and I see this message in news.notice. But I suspect 
that "ctlinnd flushlogs" from line 118 is crash innd.

Result of next commands "ctlinnd -s logmode" (line 141) and "ctlinnd -s 
go "Flushing log and syslog files" (line 177) we can see from the above 
example.

But I not see "Cannot flush logs" message.

Has anyone have such problem?

Petr Novopashenniy
RUSnet