X-Spam-Check-By: sourceware.org Message-ID: <455D28AA.5020905@cygwin.com> Date: Thu, 16 Nov 2006 22:12:42 -0500 From: "Larry Hall (Cygwin)" Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060916 Fedora/1.5.0.7-1.fc4.remi Thunderbird/1.5.0.7 Mnenhy/0.7.4.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: 1.5.21-1: sshd occasionally fails to start References: In-Reply-To: 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: 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 Tom Mount wrote: > On new installations of Cygwin 1.5.21-1, I've noticed that after > installation I have to try starting the sshd service upwards of a > dozen times before it will actually start. If I use "net start sshd" I > get the following: > > The CYGWIN sshd service is starting. > The CYGWIN sshd service could not be started. > > A system error has occurred. > > System error 1067 has occurred. > > The process terminated unexpectedly. > > If I use "cygrunsrv -S sshd" I get the following: > > cygrunsrv: Error starting a service: QueryServiceStatus: Win32 error 1062: > The service has not been started. > > I can go back and forth for five minutes or so before one or the other > will work. I get the 1067 error when I try to use the windows service > manager to start it manually. > > I know there's lots out here on 1062 and 1067 errors; but in the cases > I read they all seemed to be permanently fatal errors - no matter how > many times one tried to start the service it would always fail. This > one doesn't seem to be permanent - it will eventually work, but if I > shut it down again it's anyone's guess if it'll come back up again. > > I've attached the cygcheck file. Is there a configuration issue that's > preventing sshd from starting up until it's had a chance to sit for > five to ten minutes? I'm surprised it will start at all but no it's not a configuration issue. It's an installation issue. You have an extremely old cygwin1.dll installed in c:/Tools/Foundstone, whatever that is. You've been caught by a . Seems to be a trend lately with these sorts of questions. Delete this old DLL. The current one is binary compatible. If you still have problems after that, add tcp as a dependency to the sshd service. This will make sure that sshd doesn't start before tcp does, in case that's a problem for you. -- 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/