[Exim] upgrade 3.36 -> 4.04, "sync error" ??

Kezdőlap
Üzenet törlése
Válasz az üzenetre
Szerző: Troy Engel
Dátum:  
Címzett: exim-users
Tárgy: [Exim] upgrade 3.36 -> 4.04, "sync error" ??
Hi guys,

Trying to upgrade from 3.36 to 4.04. Machine is RedHat 6.2, mailboxes
are {$home}/Maildir/ (on an NFS mount). Spooldir is /var/spool/mail/,
which is *also* a NFS mounted dir. 3.36 is working fine, even after
backgrading quickly.

Problem: after stopping 3.36, flipping the symlink to 4.04 (binaries are
in /opt/exim-{ver}/, with a simple single /opt/exim symlink to the
running version) I get this in my logs:

== snip ==
2002-05-09 15:30:26 exim 4.04 daemon started: pid=20697, -q30m,
listening for SMTP on port 25 (IPv4)
2002-05-09 15:30:26 Start queue run: pid=20698
2002-05-09 15:30:26 175HTs-0007X6-00 Message is frozen
2002-05-09 15:30:26 175dbU-0001zb-00 Message is frozen
2002-05-09 15:30:26 175JHe-0007ij-00 spool file directory sync error
while delivering: Invalid argument
2002-05-09 15:30:26 End queue run: pid=20698
2002-05-09 15:30:39 175wQp-0005Nw-00 Message abandoned: spool file
directory sync error while receiving from mia.fluid.com (fluid.com)
[63.76.105.182]: Invalid argument
2002-05-09 15:30:42 175wQs-0005Nx-00 Message abandoned: spool file
directory sync error while receiving from mta5.snfc21.pbi.net
[206.13.28.241]: Invalid argument
== snip ==

over and over, basically causing no mail to flow. Stop 4.04 and go back
to 3.36, everything flows as expected. I took great care in build 4.04
and it's new configure file (and even using the steps in Testing doc
section work fine, with temp spool set to "/var/tmp/exim/" -- mail flows
cool) so I'm sure that's fine.

Anyone have a clue what this error means, and what I can do to solve it?
(don't see any references, or I can't find them, in the archives and
docs. I'm assuming it's a NFS problem?)

thanks!
-te

--
Troy Engel, Systems Engineer
Hockey. Kinda like Figure Skating in a War Zone.