SSHD Service shuts down after a while after latest library updates

SSHD Service shuts down after a while after latest library updates

[Enrico.Bertram]

I want to report an issue I see after updating the libraries to the
latest versions. Some of them were security related (CA Certificates,
crypto policies,...)
Unfortunately I do not remember, which exact ones and if that may be a hint.


OS: Win10 1809, Build 17763.475
Issue: CYGWIN sshd service shuts down after a while (~couple of hours)


The service is configured to start automatically and does so on each reboot.
The event viewer does not show any event (for example the "stopped" on
normal shutdowns) - the service is just in shut down state every now and
then and I have to manually start it again.

Logging is unchanged until now in the sshd_config, and uses default
settings:
#SyslogFacility AUTH
#LogLevel INFO

Are there any hints on extended log settings to be able analyse further?

Thanks,
Enrico Bertram.

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

Re: SSHD Service shuts down after a while after latest library updates

[L A Walsh]

On 5/12/2019 6:35 AM, Enrico.Bertram wrote:
> \
>
> The service is configured to start automatically and does so on each reboot.
> The event viewer does not show any event (for example the "stopped" on
> normal shutdowns) - the service is just in shut down state every now and
> then and I have to manually start it again.
>   
This has been a feature of Windows since win98.  Not officially, mind
you, but any scheduled task in windows would eventually become
unscheduled and stop running with out any notification.

The only way I found to get round this is by having a job login from
a reliable server (like linux) multiple times/hour with a control
login that attempts to remain logged in so that problems can be
solved by the already logged in process.

For the first time since Win98, I'm starting to get error reports when
there are problems as well as notifications if there was a problem
resetting my basic state.

I may have to extend my monitoring and corrections since some are more
involved,
but sadly it was the only way I found out how to get prompt errors when
things stopped working because Windows philosophy is to not report
things in hope that the problem or need for the report will go away.

Part of this stems from, for example in tools to regulate resources
given to programs, only servers are allowed to do so, with the
regulating software not running on Windows.

There are some unsatisfactory third party options (Process Lasso) that
do things
like keep processes running or restart if they die  -- things that the
Windows service manager claims to do, but not always work.

Windows on my machine hasn't been able to start the system log function
for about 2-3 years -- with MS having no clue and only recommendation
being to upgrade to win10.  I have a few problem the MS was unable to
solve for more than 3 years with similar outcomes.  Very often the
problems aren't fixed, but appear
to be so because some do not trigger frequently.

So if you want reliable debug and monitoring, use another OS like linux to
monitor the flakey windows.

(my 2 cents)....
Linda






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

Re: SSHD Service shuts down after a while after latest library updates

[Bill Stewart]

On Sun, May 12, 2019 at 8:31 AM L A Walsh wrote:

> This has been a feature of Windows since win98. Not officially, mind
> you, but any scheduled task in windows would eventually become
> unscheduled and stop running with out any notification.

I've never seen this behavior on any Windows machine (a scheduled task
becoming unscheduled by itself), but in any case, this is irrelevant
to the current question because scheduled tasks are not the same as
Windows services (daemons).

What we need to know is what is happening that would cause the service
to stop running. As a test, you can stop the service (if it's not
stopped already), and do the following:

1. Open Cygwin shell as administrator (right-click, "Run as administrator")

2. Run: cd /usr/sbin

3. Run: sshd -d -d -d

This will run the service "interactively" and you can see what error occurs.

Bill

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