Re: cygwin ver 1.5.12-1 on win2k3

[Igor Pechtchanski <pechtcha at cs dot nyu dot edu>]

On Tue, 19 Jul 2005, Etienne Mbuyi wrote:

> We are trying to run Cron on some our win2k3 servers but without
> success.

First off, cygwin-1.5.12 is ancient!  I'd recommend upgrading.

> If we assigned the domain administrator the right to logon as a service,
> Cron service doesn't start. The service only start when using the local
> system account.

This may be an indication of restricted permissions on the log file -- the
domain admin cannot write to the log, so the service won't start.  Try
chown'ing /var/log/cron.log to the domain admin, or even simply "chmod
666"ing it.

> Even if the service is running, the job doesn't seem to work.

Which job?

> Attached you will find the cygchect.out file. Below is the
> cron_diagnose.sh output.

Looks to me like you didn't actually *read* the output.

> $ cron_diagnose.sh
> cron_diagnose.sh 1.10
>
> The owner and the Administrators need
> to have ..x permission to /usr/sbin/sendmail.
> Here are the current permissions:
>
> ls: /usr/sbin/sendmail: No such file or directory
>
> Please change the user and/or group ownership and
> permissions of /usr/sbin/sendmail, and then run this script again.
>      ssmtp and exim are suitable mailers.

This looks like one problem.

> This script did not find any errors in your cron setup.
>
> If you are running cron as yourself,
> /usr/sbin/sendmail should point to an executable mailer
>
> If you are still unable to get cron to work, then try
> shutting down the cron service, uninstalling it,
> reinstalling it, and restarting it.
>
> The following commands will do that:
>   $ cygrunsrv --stop cron
>   $ cygrunsrv --remove cron
>   $ cygrunsrv --install cron -p /usr/sbin/cron -a -D
>       (You can also add a -u switch)
>   $ cygrunsrv --start cron
>
> If the cron service does not start, try deleting the file
> /var/run/cron.pid and then repeating the commands above.
>
> Also, examine the log file for cron, /var/log/cron.log, for
> information that it might give you about the problem cron is
> having.
>
> If none of this fixes the problem, then report your problem
> to cygwin@cygwin.com.

Did you try all of the above?

> Please include a copy of your crontab, ('crontab -l')

Well, where is it?

> and the output of 'cygcheck -srv > cygcheck.txt'.
>
> Please include the generated file 'cygcheck.txt' *as an attachment*,
> and NOT in the body of the mail message.

Please alleviate the above omissions and we may be able to help you.

You could also try some simple crontab commands, e.g., '/usr/bin/date >>
/tmp/cron.date.out', and see if that runs (check the file for the latest
date).
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA

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