RE: NNTPC: nntpcache has stopped!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This happened to me today, too.
Here´s what I found in warn.log:

Dec  8 23:08:16 linux1 nntpcached[466]: nntpcache.c:281:Interrupted system call: SIGSEGV!
Dec  8 23:25:22 linux1 nntpcached[8231]: nntpcache.c:281:Bad file descriptor: SIGSEGV!
Dec  8 23:30:18 linux1 nntpcached[467]: nntpcache.c:281:Bad file descriptor: SIGSEGV!
Dec  8 23:45:39 linux1 nntpcached[773]: nntpcache.c:281:Bad file descriptor: SIGSEGV!
Dec  8 23:46:47 linux1 nntpcached[795]: nntpcache.c:281:Bad file descriptor: SIGSEGV!
Dec  8 23:52:18 linux1 nntpcache-update[838]: sockets.c:373: saw more than one '\r'
Dec  8 23:52:40 linux1 nntpcache-update[838]: sockets.c:373: saw more than one '\r'

After deleting cache.mmap, nntpcached starts again.

I saw another message several times:

Dec  8 23:54:20 linux1 nntpcache-nocem[912]: nocem.c:325:No child processes: group change to 'news.lists.filters' failed

What does that mean?

Thanks!
Bodo





-----Original Message-----
From: Anthony Perry [mailto:aperry@cisco.com]
Sent: Wednesday, December 08, 1999 3:48 AM
To: nntpcache-users@suburbia.net
Subject: NNTPC: nntpcache has stopped!



What I found with this is that the /usr/local/var/nntpcache/mmap files were
becoming corrupted and causing the nnntpcached deamon to crash and burn.
When I rm the mmap files (all of them), nntpcached seemed much happied.

Occationally I had to remove the entire content of
/usr/local/var/nntpcache/* and/or reboot the box.

Very annoying.

Anthony


>
>
> Hiya good people.
>
> I've had a very weird thing happen with nntpcache. It stopped
> running on our
> slackware box last night, and is refusing to start up again. Everything
> looks normal, no files have been altered, but the process is not
> running and
> there is NO debug information being passed to syslog other than:
>
>     syslog: clean shutdown with error 1. dumping core for debug analysis
>
> I've modified to nntpcache.config file to include:
>
>     logDebug                yes
>     logInfo                 yes
>     logWarnings             yes
>     logErrors               yes
>
> But there is nothing logged that is offering any help.
>
> Anyone know about this? Any help would be really appreciated!!!
>
> Oh, its VERSION file contains 2.3.1 (dunno how recent it is, we just paid
> the money, got it running and forgot about it).
>
> Many thanks
> Anthony
>
>
>





[Index of Archives]     [Yosemite]     [Yosemite Campsites]     [Bugtraq]     [Linux]     [Trn]

Powered by Linux