major problem reached

[Paul Theodoropoulos]

have been running fine using tagged hash for a week or so now. yesterday 
evening, the server started having problems, returning the following error 
message:

Jan 11 17:24:39 nnrp innd: SERVER cant dbzstore 
[5896A8AD039F14210F44D65600BD43D
8]@0: Invalid argument
Jan 11 17:25:00 nnrp rnews: Reading config from /usr/local/news/etc/inn.conf
Jan 11 17:25:00 nnrp innd: localhost connected 23
Jan 11 17:25:00 nnrp innd: localhost:23 closed seconds 0 accepted 0 refused 
0 re
jected 0 duplicate 0 accepted size 0 duplicate size 0
Jan 11 17:25:01 nnrp innd: SERVER cant dbzstore 
[5896A8AD039F14210F44D65600BD43D
8]@0: Invalid argument
Jan 11 17:25:05 nnrp innd: SERVER cant dbzstore 
[5896A8AD039F14210F44D65600BD43D
8]@0: Invalid argument
Jan 11 17:25:07 nnrp last message repeated 1 time

eventually throttling about twenty minutes later.

here's where my history and history.pag are - note that history.pag is 
larger than 2gig. inn was built with largefiles support (this is solaris 7, 
64bit kernel).

-rw-rw-r--   1 news     news     1518704679 Jan 12 08:16 history
-rw-rw-r--   1 news     news     2082078872 Jan 12 08:16 history.pag

this morning i built the latest snapshot, and applied Mark Hittinger's 
suggested use of fseeko on his.c etc.

attempted to rebuild the .pag -

news-nnrp /usr/local/news/db% makedbz -s `wc -l <history.n` -f history.n
Can't store "[5896A8AD039F14210F44D65600BD43D8]", Invalid argument

here are the file sizes for history.pag and history.n.pag at that point:

-rw-r--r--   1 news     news     2082533984 Jan 12 09:06 history.n.pag
-rw-rw-r--   1 news     news     2082078872 Jan 12 08:16 history.pag

so now i'm stuck. i've no idea how to get out of this place. is that a bad 
entry in the history file? or is something more sinister going on?

help?
--
Paul Theodoropoulos                       Advanced TelCom Group, Inc.
Senior UNIX Systems Administrator                   Internet Services
Work: http://www.atgi.net             Play: http://www.anastrophe.com