Odd history error messages

bill davidsen davidsen at tmr.com
Wed Jul 10 19:19:15 UTC 2002


I'm getting this:

 SERVER cant write history <3d2c7d2a$0$13929$edfadb0f at dspool01.news.t
ele.dk> Success
Jul 10 14:49:19 newsmst01 innd: dbz not open for this history file /usr/local/news/db/history
Jul 10 14:49:19 newsmst01 innd: dbz not open for this history file /usr/local/news/db/history
Jul 10 14:49:19 newsmst01 innd: SERVER cant write history <aghj91$f1k$3 at binnews2.kornet.net> Success
Jul 10 14:49:19 newsmst01 innd: dbz not open for this history file /usr/local/news/db/history
Jul 10 14:49:19 newsmst01 innd: dbz not open for this history file /usr/local/news/db/history
Jul 10 14:49:19 newsmst01 innd: SERVER cant write history <3D2C535C.E47F506C at removethis.com> Success
Jul 10 14:49:19 newsmst01 innd: dbz not open for this history file /usr/local/news/db/history
Jul 10 14:49:19 newsmst01 innd: dbz not open for this history file /usr/local/news/db/history
Jul 10 14:49:19 newsmst01 innd: SERVER cant write history <3d2c8114.11527199 at news.xs4all.nl> Success
Jul 10 14:49:19 newsmst01 innd: dbz not open for this history file /usr/local/news/db/history
Jul 10 14:49:19 newsmst01 innd: SERVER cant write history <cancel.c31f.PSkymCWXl$D1uc.03274 at news.gom
mu.com> Success

with inn-CURRENT-20020611

The server was up for 2+ weeks before I put it in production, now it
keeps stopping. Ring a bell with anyone?
-- 
bill davidsen <davidsen at tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.


More information about the inn-workers mailing list