delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/01/09/14:00:59

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Sun, 9 Jan 2005 13:55:20 -0500
From: "Pierre A. Humblet" <pierre DOT humblet AT ieee DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: Is Cygwin cron supposed to send e-mail reports?
Message-ID: <20050109185520.GA745387@hpn5170>
Mime-Version: 1.0
User-Agent: Mutt/1.4.1i

On Sun, Jan 09, 2005 at 09:32:08AM -0800, David Christensen wrote:
> Cygwin:
> 
> I have a Debian box and several Cygwin boxes that back themselves up
> every night and rsync the tarballs to a central Cygwin/XP backup server.
> It all works, with the exception that I can't figure out how to get the
> Cygwin boxes to send me e-mail reports (the Debian box does this, and
> it's very useful).  I've downloaded, installed, and configured Cygwin
> exim (and opened up the Windows Firewall SMTP port) expecting that cron
> would send messages via the /usr/sbin/sendmail symbolic link, but that
> didn't seem to do the trick.  I downloaded, installed, and fumbled
> around with everything else available under the Cygwin Setup "Mail"
> category, plus some manual command-line tests, looking at logs, etc.,
> but couldn't figure it out.  I searched the Cygwin FAQ, User's Guide,
> and mailing list, and searched Google for permutations on "Cygwin cron
> mail", but I didn't find anything that looked like it addressed this
> specific issue.
> 
> 
> Is Cygwin cron supposed to send e-mail reports?  

Yes.

According to your logs below, you seem to have two problems: 
1) queue runner fork problems, probably due to a rebase issue.
   (I am not an expert, not having been a victim)
2) a mail delivery issue:
>         2005-01-09 09:18:21 IA282L-00030G-88 <= dpchrist AT p42800e U=dpchr
> ist P=local S=716
>         2005-01-09 09:18:21 IA282L-00030G-88 cloud.he.net [65.19.145.2]:
>  Software caused connection abort
>         2005-01-09 09:18:21 IA282L-00030G-88 == dpchrist AT holgerdanske DOT co
> m R=dnslookup T=remote_smtp defer (113): Software caused connection abort
  This shows that a mail was generated locally (from cron, I assume).
  The delivery failed, apparently because of an issue at the remote end,
  but perhaps with a local root cause (rebase?).
  (I grep'ed "Software caused" in the exim source and didn't find it.)
  You could try to find details by running "exim -d dpchrist AT holgerdanske DOT com"
  from the command line (type CR + a few words + CR when exim seems to wait for
  input).
  ssmtp is less likely to suffer rebase issue. Use ssmtp-config. 

 Pierre

> 
> 
> p.s.  Here is a command line test of Debian mail:
> 
>           dpchrist AT p166d302:~$ mail -s test dpchrist AT holgerdanske DOT com
>           This is a test of Debian mail invoked as follows:
>           mail -s test dpchrist AT holgerdanske DOT com
>           .
>           Cc:
>           dpchrist AT p166d302:~$
> 
>     It worked -- e.g. the Debian box sent it via SMTP to the recipient.
> 
> 
> p.p.s.  Here is a command line test using Cygwin email:
> 
>           dpchrist AT p42800e:~$ email -s test dpchrist AT holgerdanske DOT com
>           Sending  "test"  |****************************************  \ 
>  96% of 569 Bytes
>           E-Mail Sent
> 
>     It didn't work.  Looking at the logs:
> 
>         dpchrist AT p42800e:~$ tail -n 6 /var/log/exim/exim_main.log
>         2005-01-09 08:45:41 daemon: fork of queue-runner process failed:
>  Resource temporarily unavailable
>         2005-01-09 09:00:41 daemon: fork of queue-runner process failed:
>  Resource temporarily unavailable
>         2005-01-09 09:15:41 daemon: fork of queue-runner process failed:
>  Resource temporarily unavailable
>         2005-01-09 09:18:21 IA282L-00030G-88 <= dpchrist AT p42800e U=dpchr
> ist P=local S=716
>         2005-01-09 09:18:21 IA282L-00030G-88 cloud.he.net [65.19.145.2]:
>  Software caused connection abort
>         2005-01-09 09:18:21 IA282L-00030G-88 == dpchrist AT holgerdanske DOT co
> m R=dnslookup T=remote_smtp defer (113): Software caused connection abor
> t
> 
>         dpchrist AT p42800e:~$ tail -n 3 /var/log/exim/exim_panic.log
>         2005-01-09 08:45:41 daemon: fork of queue-runner process failed:
>  Resource temporarily unavailable
>         2005-01-09 09:00:41 daemon: fork of queue-runner process failed:
>  Resource temporarily unavailable
>         2005-01-09 09:15:41 daemon: fork of queue-runner process failed:
>  Resource temporarily unavailable
> 
>     Is this the Cygwin rebase issue?  I don't see "rebase" in the
>     Cygwin FAQ or User's Guide.  Is there something that explains the
>     Cygwin rebase issue?


> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019