upgrading from inn 2.2.1 -> 2.4.1

[Bill Davidsen]

Jason wrote:
> hey, im migrating an inn server from a very old redhat install to a solaris box. 
> On the solaris box, I have installed inn 2.4.1 and have gotten it to work with a freshly initialized database.
> but now I need to migrate the news db from this old 2.2.1 box and cant seem to get it to work.
> 
> If i do nothing to the database files and just copy them over to the 2.4.1, upon starting  inn, I get the dreaded:
> innd: SERVER can't open history /local/news/db/history: Argument out of domain
> innd: can't dbzinit /local/news/db/history Argument out of domain
> innd: can't dbzclose /local/news/db/history Argument out of domain
> innd: SERVER can't open history /local/news/db/history: Argument out of domain
> innd: can't dbzinit /local/news/db/history Argument out of domain
> 
> so reading the FAQ, I didnt see anything relevant. but reading the NEWS file,
> I see theres a section on upgrading from 2.2 to 2.3 and there are obviously database changes, but I have run the commands 
> listed in that section and cant get my history file converted correctly.
> 
> when I run the makehistory, I get:
> 
> [news at kendo]$ ls -al   (old database before doing anything)
> total 29905
> drwxr-xr-x   4 news         1024 Jul 10 01:25 .
> drwxr-xr-x  13 news         1024 Jul  9 23:50 ..
> -rw-r--r--   1 news         4135 Jul 10 01:25 active
> -rw-r--r--   1 news         4102 Jul 10 01:25 active.old
> -rw-r--r--   1 news         3238 Jul 10 01:25 active.times
> -rw-r--r--   1 news           72 Jul 10 01:25 distributions
> -rw-r--r--   1 news     28755860 Jul 10 01:25 history
> -rw-r--r--   1 news          207 Jul 10 01:25 history.dir
> -rw-r--r--   1 news      1845652 Jul 10 01:25 history.pag
> -rw-r--r--   1 news          249 Jul 10 01:25 newsgroups
> -rw-r--r--   1 news            0 Jul 10 01:25 subscriptions
> [news at kendo]$ ../bin/makehistory -b -f history.n -O  -T/local/news/tmp -l 600000
> [news at kendo]$ ls -al
> total 29906
> drwxr-xr-x   4 news         1024 Jul 10 01:34 .
> drwxr-xr-x  13 news         1024 Jul  9 23:50 ..
> -rw-r--r--   1 news         4135 Jul 10 01:25 active
> -rw-r--r--   1 news         4102 Jul 10 01:25 active.old
> -rw-r--r--   1 news         3238 Jul 10 01:25 active.times
> -rw-r--r--   1 news           72 Jul 10 01:25 distributions
> -rw-r--r--   1 news     28755860 Jul 10 01:25 history
> -rw-r--r--   1 news          207 Jul 10 01:25 history.dir
> -rw-r--r--   1 news            0 Jul 10 01:34 history.n
> -rw-r--r--   1 news           43 Jul 10 01:34 history.n.dir
> -rw-r--r--   1 news            0 Jul 10 01:34 history.n.hash
> -rw-r--r--   1 news            0 Jul 10 01:34 history.n.index
> -rw-r--r--   1 news      1845652 Jul 10 01:25 history.pag
> -rw-r--r--   1 news          249 Jul 10 01:25 newsgroups
> -rw-r--r--   1 news            0 Jul 10 01:25 subscriptions
> [news at kendo]$ 
> 
> any ideas?

The only thing which remotely comes to mind is that you don't have 
config correct and it's not seeing the articles to build the 
makehistory. On the other hand, that makes it run very quickly ;-) 
Running quickly is usually a clue it isn't doing what you expect.

-- 
    -bill davidsen (davidsen at tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me