Well, here's my first dumb question ;-) On my own little workstation I intended to set up an NNTPCache, since my inn2.2 is quite slow on overviews. System: Linux Redhat 6.0 with glibc update. Platform: PC (I-Celeron) RAM: Sufficient NNTPCache: 2.3.3 Here's the debug snippet (line numbering's mine): =============================================== 001 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:170: connected to NNTP server detebe.org.:8119 as DEFAULT 002 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:470: <= [detebe.org.:8119] 200 detebe.org InterNetNews NNRP server INN 2.2 23-Oct-1998 ready (posting ok). 003 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:470: <= [detebe.org.:8119] 200 detebe.org InterNetNews NNRP server INN 2.2 23-Oct-1998 ready (posting ok). 004 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:482: => [detebe.org.:8119] list overview.fmt 005 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:470: <= [detebe.org.:8119] 215 Order of fields in overview database. 006 Oct 22 13:21:06 chaos nntpcache-update[12021]: parsing 'overview.fmt' from detebe.org.:8119 007 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:470: <= [detebe.org.:8119] Subject: 008 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:470: <= [detebe.org.:8119] From: 009 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:470: <= [detebe.org.:8119] Date: 010 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:470: <= [detebe.org.:8119] Message-ID: 011 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:470: <= [detebe.org.:8119] References: 012 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:470: <= [detebe.org.:8119] Bytes: 013 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:470: <= [detebe.org.:8119] Lines: 014 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:470: <= [detebe.org.:8119] Xref:full 015 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:470: <= [detebe.org.:8119] . 016 Oct 22 13:21:06 chaos nntpcache-update[12021]: checking server detebe.org.:8119 for 'active' 017 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:482: => [detebe.org.:8119] list 018 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:470: <= [detebe.org.:8119] 215 Newsgroups in form "group high low flags". 019 Oct 22 13:21:06 chaos nntpcache-update[12021]: parsing 'active' from detebe.org.:8119 020 Oct 22 13:21:06 chaos nntpcache-update[12021]: sockets.c:470: <= [detebe.org.:8119] opera.test 0000000380 0000000096 y 021 Oct 22 13:21:06 chaos nntpcache-update[12021]: nntpcache.c:281: SIGSEGV! 022 Oct 22 13:21:06 chaos nntpcache-update[12021]: clean shutdown with error 1. dumping core for debug analysis =============================================== Everything seems to run ok until the active-reading nntpcache dies in line 021. The master process is still there and answering requests (but has no groups :-/ ). Has anybody seen this effect before? Should I provide more information? What would help? Regards, Elmi. PS: The same nntpcache installation ran quite nicely on my old 486 box... -- "Ingenieurin, Elektrikerin, Architektin und junger Mann mit Knackarsch zum Kaffee-Kochen gesucht" (von einem Plakat, zitiert von Princess) ........................................... whois -h whois.ripe.net ELMI-RIPE
