upgrading from inn 2.2.1 -> 2.4.1

[Jason]

> If the new server isn't already running, I think you'd be better off at
> this point just starting clean.  Delete the spool, the overview, and the
> history from the new server, start with an empty history file, and then
> feed all the articles from the old server using innxmit.  When you use
> innxmit, you do *not* need to run makehistory.

agreed.. I started fresh on the new server. removed the articles, the overview, initialized the 
database. and started the innxmit process.
and after awhile of successfully transmitting articles, the innxmit crashes on the old server with

[jawelsh at shogun outgoing]$ innxmit kendo list
Can't send "japan/crash-archive2/34", Broken pipe
Rewriting batch file and exiting.
[jawelsh at shogun outgoing]$ 

trying to restart it yields...
[jawelsh at shogun outgoing]$ innxmit kendo list
Can't connect to kendo, 400 File exists writing SMstore file -- throttling
[jawelsh at shogun outgoing]$

I restarted innd on the new server and retried, and I got 
[jawelsh at shogun outgoing]$ innxmit kendo list
No reply to check, Broken pipe
Rewriting batch file and exiting.
[jawelsh at shogun outgoing]$

shogun=old server,  kendo = new server

regards,
Jason



> 
> -- 
> Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>
> 
>     Please send questions to the list rather than mailing me directly.
>      <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
> 

-- 
================================================
|    Jason Welsh   jason at monsterjam.org        |
| http://monsterjam.org    DSS PGP: 0x5E30CC98 |
|    gpg key: http://monsterjam.org/gpg/       |
================================================