Hello:
We have been running NNTPcached 2.3.3 to my
knowledge since the first quarter of 2000 without any major
incidents.
The server is a Sun Ultra Enterprise, using Solaris
2.6, and pull news from a commercial service Newsfeeds.com.
Sometime on Saturday, NNTPcached died, and although
it will restart, it dies shortly after (within 5 minutes). It is
generating an Interrupted System call error. Here is a typical log excerpt
immediately after a restart:
May 6 15:11:53 Virginia
nntpcache-update[521]: sockets.c:482: => [corp.newsfeeds.com] list
overview.fmt
May 6 15:11:54 Virginia nntpcache-update[521]: sockets.c:482: => [corp.newsfeeds.com] list May 6 15:14:26 Virginia nntpcache-update[521]: sockets.c:482: => [corp.newsfeeds.com] list active.times May 6 15:14:28 Virginia nntpcache-update[521]: nmalloc.c:14: XMcalloc call from list.c:__LINE__ for 6 bytes failed May 6 15:15:34 Virginia nntpcache-client[530]: sockets.c:482: => [corp.newsfeeds.com] xover 4391-4408 May 6 15:15:43 Virginia nntpcache-client[530]: sockets.c:482: => [corp.newsfeeds.com] xover 100198-104036 May 6 15:16:18 Virginia nntpcache-client[530]: sockets.c:482: => [corp.newsfeeds.com] ARTICLE 103266 May 6 15:16:20 Virginia nntpcached[520]: history.c:44:No such file or directory: missing history file 'cache.history' May 6 15:16:20 Virginia nntpcached[520]: history.c:50:No such file or directory: missing history file 'cache.history.dir' May 6 15:16:20 Virginia nntpcached[520]: history.c:56:No such file or directory: missing history file 'cache.history.pag' May 6 15:17:13 Virginia nntpcache-client[544]: sockets.c:482: => [corp.newsfeeds.com] xover 96415-96415 May 6 15:17:29 Virginia nntpcache-client[544]: sockets.c:482: => [corp.newsfeeds.com] ARTICLE 96117 May 6 15:17:37 Virginia nntpcache-client[530]: sockets.c:482: => [corp.newsfeeds.com] xover 498936-501589 May 6 15:18:03 Virginia nntpcache-client[544]: sockets.c:482: => [corp.newsfeeds.com] ARTICLE 96376 May 6 15:18:16 Virginia nntpcache-client[544]: sockets.c:482: => [corp.newsfeeds.com] ARTICLE 96379 May 6 15:18:19 Virginia nntpcache-client[530]: sockets.c:482: => [corp.newsfeeds.com] ARTICLE 500102 May 6 15:19:14 Virginia nntpcache-client[530]: sockets.c:482: => [corp.newsfeeds.com] ARTICLE 499729 May 6 15:19:15 Virginia nntpcache-client[544]: sockets.c:482: => [corp.newsfeeds.com] ARTICLE 96385 May 6 15:23:11 Virginia nntpcached[520]: nmalloc.c:25:Interrupted system call: XMcalloc call from nntpcache.c:__LINE__ for 1 bytes failed Does anyone have any idea why this would suddenly
start occuring? Is it a known bug we have just not experienced before now?
Is there a fix I should already know about?
I have not been able to contact our news provider
to see if they have made any changes over the weekend. However, there is
always the XMcalloc error after the active.times log entry.
Any assistance will be greatly appreciated.
Our formerly trouble free service is down until this is resolved.
Best Regards,
Bryan Guest
sys admin |