From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: exim-4.76-1 fails to remove lock from spooler on delivery
Date: Thu, 27 Oct 2011 07:48:00 -0000 [thread overview]
Message-ID: <20111027074719.GN18409@calimero.vinschen.de> (raw)
In-Reply-To: <00af01cc941e$760e9a60$622bcf20$@ieee.org>
On Oct 26 16:33, Pierre A. Humblet wrote:
> > -----Original Message-----
> > From: Zdzislaw Meglicki
> > Sent: Wednesday, October 26, 2011 13:43 PM
> >
> > Hello Pierre,
> >
> > We are getting somewhere. First, the system went down, because it was
> > patching itself and needed to reboot. Normal for Windows.
> >
> > I'm now sitting in front of the machine. I have stopped exim and cleaned
> all
> > logs in /var/log/exim. Then restarted it. Then I e-mailed a message from
> > perth.ovpit.indiana.edu to gusta at yanchep.ovpit.indiana.edu to reproduce
> > the problem and inspected he logs.
> >
> > Here's what I find:
> >
> > 1. In the /var/spool/mail directory, the message has been written on the
> > destination file "gustav".
> > 2. The lock file, /var/spool/mail/gustav.lock, which wasn't there
> originally, is
> > there now and remains unremoved.
> > 3. There is an entry in /var/log/exim/exim_panic.log that looks as
> follows:
> >
> > root@yanchep $ cat exim_panic.log
> > 2011-10-26 13:33:46 LTOOS9-0002MK-LW failed to read delivery status for
> > gustav@yanchep.ovpit.indiana.edu from delivery subprocess
> > 2011-10-26 13:33:46 LTOOS9-0002MK-LW appendfile transport process
> > returned non-zero status 0x0001: terminated by signal 1 root@yanchep $
>
> I was able to replicate the problem on Windows 7:
> The delivery process crashes because it can't load winmm.dll
>
> 16:06:33 3572 writing data block fd=6 size=1 timeout=0
> 6 [main] exim 3572 C:\Program Files\cygwin\bin\exim-4.76-1.exe: ***
> fatal error - unable to load C:\Windows\system32\winmm.dll, Win32 error 1114
> 16:06:33 5620 LOG: MAIN PANIC
> 16:06:33 5620 failed to read delivery status for phumblet@phumblet-lap01w
> from delivery subprocess
>
> So it's a Cygwin issue... I think it has been discussed before but I am not
> sure if there is a solution.
Cygwin from CVS doesn't use winmm anymore, unless you need access to
the audio I/O. Try the latest developer snapshot from
http://cygwin.com/snapshots/
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-10-27 7:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 21:30 Zdzislaw Meglicki
2011-10-26 14:34 ` Pierre A. Humblet
[not found] ` <1319650967.20592.YahooMailRC@web80704.mail.mud.yahoo.com>
2011-10-26 20:33 ` Pierre A. Humblet
2011-10-26 22:13 ` Zdzislaw Meglicki
2011-10-27 7:48 ` Corinna Vinschen [this message]
2011-10-27 16:38 ` Pierre A. Humblet
2011-10-26 18:06 Zdzislaw Meglicki
[not found] ` <008d01cc940f$dd265940$97730bc0$@ieee.org>
2011-10-26 19:25 ` Zdzislaw Meglicki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111027074719.GN18409@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).