X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=0.0 required=5.0 	tests=BAYES_50,FB_WORD1_END_DOLLAR
X-Spam-Check-By: sourceware.org
Message-ID: <786453.44646.qm@web1111.biz.mail.sk1.yahoo.com>
References: <24395640.post@talk.nabble.com> <002301ca000f$242cb6a0$8e0410ac@wirelessworld.airvananet.com>
Date: Wed, 8 Jul 2009 14:47:45 -0700 (PDT)
From: Rajiv Garg <rajiv@rajivgarg.com>
Subject: Re: Intermittent Cron Errors
To: "Pierre A. Humblet" <Pierre.Humblet@ieee.org>, cygwin@cygwin.com
In-Reply-To: <002301ca000f$242cb6a0$8e0410ac@wirelessworld.airvananet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com


Pierre,

Thanks for your reply.  

Yes, both the job and service are running under the same account (orderworker).  I was looking into this a bit more, and found that we are getting the following event in our security event log at the exact time of the cron "can't switch user context" error.

Event Type:       Failure Audit
Event Source:    Security
Event Category: Privilege Use 
Event ID:           577
Date:               7/8/2009
Time:              4:30:17 PM
User:              <domain>\orderworker
Computer:      OMS1
Description:
Privileged Service Called:
Server:                       NT Local Security Authority / Authentication Service
Service:                      LsaRegisterLogonProcess()
Primary User Name:    OMS1$
Primary Domain:         <domain>
Primary Logon ID:       (0x0,0x3E7)
Client User Name:      orderworker
Client Domain:      
Client Logon ID:         (0x0,0xF1C649B8)
Privileges:                 SeTcbPrivilege

This seems to confirm that it's an sporadic authentication issue between our server and our domain controllers, not cron or cygwin-related.  I'm going to try to track this issue down and failing that, may try building a special version of cron to bypass setuid per your suggestion.  I should be able to handle that, but if I have trouble, I may drop you a line.

Thanks again!
Rajiv

--
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