Re: [Exim] Bug in Exim 4.41: "Cannot lock: Invalid Argument"

Top Page
Delete this message
Reply to this message
Author: John Dalbec
Date:  
To: Marc Langer, Exim-Users Mailing List
Subject: Re: [Exim] Bug in Exim 4.41: "Cannot lock: Invalid Argument"
Marc Langer wrote:

> Hi,
>
> after upgrading from Exim 4.10 to 4.41 every incoming mail produces
> the following output:
>
> 2004-08-01 14:37:03 1BrFaI-0001y0-PD Cannot lock /var/spool/exim/input//1BrFaI-0001y0-PD-D (22): Invalid argument
>
> strace shows:
>
> [pid  7540] open("/var/spool/exim/input//1BrFaI-0001y0-PD-D", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0640) = 1
> [pid  7540] fchown(1, 8, 12)            = 0
> [pid  7540] fchmod(1, 0640)             = 0
> [pid  7540] fcntl(1, F_GETFL)           = 0x8002 (flags O_RDWR|O_LARGEFILE)
> [pid  7540] fstat(1, {st_mode=S_IFREG|0640, st_size=0, ...}) = 0
> [pid  7540] old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40019000
> [pid  7540] _llseek(1, 0, [0], SEEK_CUR) = 0
> [pid  7540] fcntl(1, 0xd /* F_??? */, 0xbfffee90) = -1 EINVAL (Invalid argument)


0xd is F_SETLK64. It looks like your kernel and/or glibc do(es)n't support
64-bit file access. Exim compiles with 64-bit file access enabled by default.
Red Hat 7.0 is very old and will have accumulated a large number of security
holes by now. Your best bet would be to upgrade to Red Hat 7.3 (which is
supported by the Fedora-Legacy project at www.fedoralegacy.org). If you can't
upgrade, try removing -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE from
OS/Makefile-Linux.
HTH,
John
>
> permissions are correct and empty spool files are created.
>
> System: Redhat 7.0, glibc 2.1.92, gcc version 2.96 20000731 (Red Hat Linux 7.0)
>
> I had to downgrade to 4.10 to get it working again.
>
> Marc
>
> --
>
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>
>
>