bad_history
John Newman
jnn at jump.net
Thu Nov 9 02:25:27 UTC 2000
> > 64-bit Solaris 2.8. Inn 2.3.0, CNFS, tradindexed. My original
> > problem, in case you didn't catch it, was log entries like this:
>
> Did you specify largefiles at ./configure time? Also, I presume
> you didn't specify tagged-hash and are using the same md5 where I've
> seen the below problem.
I did specify largefiles. I did not use tagged-hash. What do you mean
by same md5?
> Just for some more info, could you `ls -l' your /news/db dir, to give
> the timestamps on your history, .index, and .hash files, as well as
> the sizes?
Wed Nov 8 19:18:24 CST 2000
news2/News/db# ls -l
total 3219688
-rw-rw-r-- 1 news news 1274580 Nov 8 19:15 active
-rw-rw-r-- 1 news news 1274518 Nov 8 11:15 active.old
-rw-r--r-- 1 news news 3256 Nov 8 11:15 active.times
-rw-rw-r-- 1 news news 1394750357 Nov 8 19:15 history
-rw-rw-r-- 1 news news 120 Nov 8 19:15 history.dir
-rw-rw-r-- 1 news news 258166512 Nov 8 19:15 history.hash
-rw-rw-r-- 1 news news 172111008 Nov 8 19:15 history.index
-rwxr-xr-x 1 news news 139 Oct 4 18:11 mvhist
-rw-r--r-- 1 news news 1404773 Nov 8 09:02 newsgroups
> Also, a `cat history.dir' in this directory will show me if the sizes
> are to be expected, and confirm that you have an 8-byte of_t.
news2/News/db# cat history.dir
dbz 6 24789609 10 66
16521811 16526406 16077766 15624639 15341703 15081849 14438106 13904323 13341693 12712715 12213521
> Also, `grep MMAP' in your source include/config.h file, to see if there
> are any changes in Slowaris 8 from 7, or if you get the same as I see
> with NetBSD.
#define HAVE_MMAP 1
/* #undef MMAP_MISSES_WRITES */
/* #undef MMAP_NEEDS_MSYNC */
> Can you grab a couple message IDs from the beginning of your logfile
> /news/log/news or equivalent, and see how they appear? Likewise, the
> first few messages from /news/log/OLD/news.1.gz (gzip -dc that | head )
> and see if they are present... Using grephistory,of course
They all show up as first entry..
>
> Then, for more fun,
> ctlinnd pause 'no reason at all'
> ctlinnd go 'no reason at all'
> and see if my message from earlier today now shows up, if it still
> is invisible with grephistory before the ctlinnd pause.
>
> If still no result, ctlinnd throttle and then go, just in case there
> might be some difference between throttling and pausing for some
> reason (calls the same source though)
grephistory always returns the first entry from the history file, even after
pausing or throttling...
--
John
More information about the inn-workers
mailing list