X-Spam-Check-By: sourceware.org X-YMail-OSG: xYJSRnMVM1nKVZTDaOOftPGNyFQ6T9p_Fd7I75GLYssdyIWXsntO8ZsnxPf7M3rww7_Nxlcq8kq10VtgM5LwCt76u88hz1JUi4mhrZXU73gTwWz8aA1Dyo.034lg_I.94DRyit6aYzTZwu2DeT_WasXff7fuQYOrtx6_ONH_hY_bFIphtbMKW4c1Tg-- Date: Tue, 23 Jan 2007 10:38:29 +0100 (CET) From: Marco Atzeri Subject: Re: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2 To: cygwin AT cygwin DOT com In-Reply-To: <17845.36409.265000.733500@sanofi-aventis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Message-ID: <915416.7728.qm@web25011.mail.ukl.yahoo.com> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com --- Steve Rowley ha scritto: > >Date: Mon, 22 Jan 2007 15:16:19 -0800 > >From: Brian Dessent > > > >Steve Rowley wrote: > >> >In case of problem, examine the log file for > cron, > >> >/var/log/cron.log, and the Windows event log > >> >for information about the problem cron is > having. > > > >This is the key thing to look at, the actual reason > for why it can't > >start should be in one of those two locations. > > Excellent points. Here are the results: > > (1) There is no /var/log/cron.log. Since this is > the first time I've > tried to bring up cron on this machine, I take > it to indicate that > the daemon never got as far as creating its log > file. > > (2) Windows event log: yes, there are some > cron-related events there. > Had I read the message as carefully as you did, > I would have > found Application events like this: > > >Event Type: Error > >Event Source: cron > >Event Category: None > >Event ID: 0 > >Date: 1/22/2007 > >Time: 11:00:27 PM > >User: NT AUTHORITY\SYSTEM > >Computer: CBDWB00033 > >Description: > >The description for Event ID ( 0 ) in Source ( > cron ) cannot be found. The local computer may not > have the necessary registry information or message > DLL files to display messages from a remote > computer. You may be able to use the /AUXSOURCE= > flag to retrieve this description; see Help and > Support for details. The following information is > part of the event: cron: PID 304: starting service > `cron' failed: fork: 11, Resource temporarily > unavailable. > > Any idea what to make of that? > > >> >/usr/bin/cygrunsrv: Error enumerating > services: OpenService: Win32 error 5: > >> >Access is denied. > > > >This usually just means there's a registry key for > a service that has an > >ACL that returns an error when cygrunsrv tries to > query its information > >to find out if it's a Cygwin service. Most of the > time this can be > >ignored [...] > > Good, then we'll all happily ignore it. > > >> [ATTACHMENT ~/My Documents/cygcheck_output.txt, > text/plain] > > > >You didn't actually attach anything, just this > text. > > Silly me. I actually understand why that happened, > but won't bore you > with the reason, unless I can think of an > entertaining way to tell it. > In any case, I've reattached the output of cygchek > to this message. possible issue: the user SYSTEM has no enough permission to execute or to write in certain directories. use ls -l or getfacl to check permissions of the involved file/directories. For me, some changes of permission from 700 to 755 or 750 solved a similar problem with OpenSSH and NFS . SYSTEM belongs to the administrators group but it is not admin/root $ grep SYSTEM /etc/passwd SYSTEM:*:18:544:,S-1-5-18:: $ grep 544 /etc/group Administrators:S-1-5-32-544:544: Regards Marco ___________________________________ Vinci i biglietti per FIFA World Cup in Germania! yahoo.it/concorso_messenger -- 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/