Something similar has happened to me, I'm still trying to recover my EC2
instance ..
In Upstart config file ,
instead of
-- exec /usr/sbin/sshd -D
inside scricpt block
doing a config test with -t parameter
and revert to a backup config like /etc/ssh/sshd_config.bk if config test
fa
Hi, I had the exact same error on my syslog because my config wasn't
valid.
I had at the end of my config.
Match Group sftp
Subsystem sftp internal-sftp
ChrootDirectory %h
ForceCommand internal-sftp
AllowTcpForwarding no
The problem was Subsystem has to be placed outside (before) Match's
Subsys
Thanks for taking the time to submit this bug. Certainly it would be
nice if there were a meaningful error message in syslog explaining why
ssh failed to start.
** Changed in: openssh (Ubuntu)
Status: New => Confirmed
** Changed in: openssh (Ubuntu)
Importance: Undecided => Low
--
Yo
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/911753
Title:
Wrong directive in config file cause server to crash
To manage notifications about this bug go to:
https://bugs.launchpa
