Otherwise everything went fine, but ssh service fails to start:
marras 01 22:51:14 xxx systemd[1]: ssh.service: Failed to set invocation ID on control group /system.slice/ssh.service, ignoring: Operation not supported
marras 01 22:51:14 xxx systemd[1]: Starting OpenBSD Secure Shell server...
marras 01 22:51:16 xxx systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a
marras 01 22:51:16 xxx systemd[1]: Failed to start OpenBSD Secure Shell server.
marras 01 22:51:16 xxx systemd[1]: ssh.service: Unit entered failed state.
marras 01 22:51:16 xxx systemd[1]: ssh.service: Failed with result 'exit-code'
Checked that there are no configuration issues using sudo /usr/sbin/sshd -T. Any ideas or anything else I could post here to resolve the issue?
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Problem after updating Jessie to Stretch
-
- Posts: 398
- Joined: 2011-10-02 08:00
Re: Problem after updating Jessie to Stretch
What others tried, several solutions:
https://serverfault.com/questions/53803 ... s-to-start
Sometimes just a reboot helps....
https://serverfault.com/questions/88809 ... d-to-start
https://serverfault.com/questions/53803 ... s-to-start
Sometimes just a reboot helps....
https://serverfault.com/questions/88809 ... d-to-start
Re: Problem after updating Jessie to Stretch
Actually got the ssh working. Now the next problem is, that we are getting messages from syslog, eg. kernel:[494231920]ssed1:mnd.evc:Scedd and after awhile certain services become unresponsive. Any ideas, how to start resolving this issue?