X-Spam-Check-By: sourceware.org
Message-ID: <44D7FE7F.8020309@cygwin.com>
Date: Mon, 07 Aug 2006 23:01:19 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060112 Fedora/1.5-1.fc4.remi Thunderbird/1.5 Mnenhy/0.7.4.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.18-1: incorrect cron "script not found" message (Win2k).
References: <D3DA8E9DB543364DB6DE9B5964BA8EEA0EDF9C AT auntm231 DOT apac DOT corp DOT eds DOT com>
In-Reply-To: <D3DA8E9DB543364DB6DE9B5964BA8EEA0EDF9C@auntm231.apac.corp.eds.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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

Irwin, Doug wrote:
> Hi All,
> 
> I hate difficult-to-reproduce issues :(  It makes accurate reporting
> difficult...
> 
> We have a crontab which runs scripts that check whether a DBMS is
> accessible, doesn't have inappropriate locks in certain DBs, dumps
> databases, etc.
> 
> During the time database dumps are running some of our scripts
> occasionally raise "not found" messages, which are emailed to us.
> Here's an example:
>> -----Original Message-----
>> From: Cron Daemon [mailto:root AT server2]
>> Sent: Sunday, 6 August 2006 9:51 PM
>> To: Database Admin
>> Subject: Cron <sybase AT server2>
> /apps/sybase/sysdba/scripts/syblocks.scr -dPROD_COPY -sSERVER2 >
> /apps/sybase/sysdba/logs/SERVER2/syblocks.err
>> /apps/sybase/sysdba/scripts/syblocks.scr: not found
> 
> It's the same message we get if we schedule something that doesn't
> exist... But the script DOES exist.  And it ran three minutes ago and
> runs three minutes hence (crontab is
> 0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 7-22 * * *).
> 
> Sometimes it's this script.  Sometimes it's a different script.  It does
> not happen every night.
> 
> We have two other servers running the same DBMS/Cygwin/script/crontab
> config (names are obviously a little different).  Some of those other
> servers deal with bigger databases.  The main difference between the
> servers is that server2 runs Windows 2000, while server1 and server3 run
> Windows 2003.
> 
> I've spent some serious time searching Cygwin.com and the web in general
> but can't seem to find any cases where this happens (i.e., where the
> script DOES exist and usually runs OK).
> 
> If there's any more info I can provide to clarify things, please let me
> know.  Sorry that I can't outline how to reproduce this... Wish I could.
> 
> Has anyone comes across this kind of thing before?
> 
> Thanks in advance for any assistance anyone can provide.


Looks like you sent the cygcheck output for ZIGGY rather than server2...

-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

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