[opensuse-factory] Milestone 2 sshd being launched in non-deamon mode
After upgrading to Milestone 2 I wasn't able to ssh into the box after a reboot. /lib/systemd/system/sshd.service had the "-D" option so connections were being refused. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 21/03/12 21:58, Sid Boyce escribió:
After upgrading to Milestone 2 I wasn't able to ssh into the box after a reboot. /lib/systemd/system/sshd.service had the "-D" option so connections were being refused.
and what is the problem ? "-D When this option is specified, sshd will not detach and does not become a daemon. This allows easy monitoring of sshd. " Unless there is something else wrong, -D does exactly what instructed to.. does not fork()... systemd documentation discourages forking daemons and documentation recommends using the current mode instead. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 22/03/12 18:13, Cristian Rodríguez wrote:
El 21/03/12 21:58, Sid Boyce escribió:
After upgrading to Milestone 2 I wasn't able to ssh into the box after a reboot. /lib/systemd/system/sshd.service had the "-D" option so connections were being refused.
and what is the problem ?
"-D When this option is specified, sshd will not detach and does not become a daemon. This allows easy monitoring of sshd. "
Unless there is something else wrong, -D does exactly what instructed to.. does not fork()... systemd documentation discourages forking daemons and documentation recommends using the current mode instead.
The behaviour I saw was returns of "Connection refused". Removed "-D" and restarted sshd and all logins since have been successful. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 22/03/12 17:02, Sid Boyce escribió:
On 22/03/12 18:13, Cristian Rodríguez wrote:
El 21/03/12 21:58, Sid Boyce escribió:
After upgrading to Milestone 2 I wasn't able to ssh into the box after a reboot. /lib/systemd/system/sshd.service had the "-D" option so connections were being refused.
and what is the problem ?
"-D When this option is specified, sshd will not detach and does not become a daemon. This allows easy monitoring of sshd. "
Unless there is something else wrong, -D does exactly what instructed to.. does not fork()... systemd documentation discourages forking daemons and documentation recommends using the current mode instead.
The behaviour I saw was returns of "Connection refused". Removed "-D" and restarted sshd and all logins since have been successful. Regards Sid.
No !, if you modify /lib/systemd/system/sshd.service it will be overwritten at any time, if you do such change, you most copy /lib/systemd/system/sshd.service to /etc/systemd/system and edit there. if you remove the "-D" (which is not a fix either) you must set Type=forking on the [Service] section. The service must have failed due to other reason, does the log say something relevant ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 23/03/12 00:03, Cristian Rodríguez wrote:
El 22/03/12 17:02, Sid Boyce escribió:
On 22/03/12 18:13, Cristian Rodríguez wrote:
El 21/03/12 21:58, Sid Boyce escribió:
After upgrading to Milestone 2 I wasn't able to ssh into the box after a reboot. /lib/systemd/system/sshd.service had the "-D" option so connections were being refused.
and what is the problem ?
"-D When this option is specified, sshd will not detach and does not become a daemon. This allows easy monitoring of sshd. "
Unless there is something else wrong, -D does exactly what instructed to.. does not fork()... systemd documentation discourages forking daemons and documentation recommends using the current mode instead.
The behaviour I saw was returns of "Connection refused". Removed "-D" and restarted sshd and all logins since have been successful. Regards Sid.
No !, if you modify /lib/systemd/system/sshd.service it will be overwritten at any time, if you do such change, you most copy /lib/systemd/system/sshd.service to /etc/systemd/system and edit there.
if you remove the "-D" (which is not a fix either) you must set
Type=forking
on the [Service] section.
The service must have failed due to other reason, does the log say something relevant ?
Thanks, I shall have a look. regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 23/03/12 00:03, Cristian Rodríguez wrote:
El 22/03/12 17:02, Sid Boyce escribió:
On 22/03/12 18:13, Cristian Rodríguez wrote:
El 21/03/12 21:58, Sid Boyce escribió:
After upgrading to Milestone 2 I wasn't able to ssh into the box after a reboot. /lib/systemd/system/sshd.service had the "-D" option so connections were being refused.
and what is the problem ?
"-D When this option is specified, sshd will not detach and does not become a daemon. This allows easy monitoring of sshd. "
Unless there is something else wrong, -D does exactly what instructed to.. does not fork()... systemd documentation discourages forking daemons and documentation recommends using the current mode instead.
The behaviour I saw was returns of "Connection refused". Removed "-D" and restarted sshd and all logins since have been successful. Regards Sid.
No !, if you modify /lib/systemd/system/sshd.service it will be overwritten at any time, if you do such change, you most copy /lib/systemd/system/sshd.service to /etc/systemd/system and edit there.
if you remove the "-D" (which is not a fix either) you must set
Type=forking
on the [Service] section.
The service must have failed due to other reason, does the log say something relevant ?
Absolutely nothing in the logs on either side. I shall file a bug later. On a new build Milestone 2 box with or without -D ssh fails. Times out after about 2 minutes. lancelot@tindog:~> ssh -X semado ssh: connect to host semado port 22: Connection timed out lancelot@tindog:~> ssh semado ssh: connect to host semado port 22: Connection timed out lancelot@tindog:~> Remote side, from /var/log/messages, no failures reported in any logs.. Mar 26 17:53:41 semado systemd[1]: sshd.service start request repeated too quickly, refusing to start. Mar 26 17:56:20 semado sshd[15863]: Server listening on 0.0.0.0 port 22. Mar 26 17:56:20 semado sshd[15863]: Server listening on :: port 22. Mar 27 00:12:54 semado avahi-daemon[893]: Loading service file /etc/avahi/services/sftp-ssh.service. Mar 27 00:12:54 semado avahi-daemon[893]: Loading service file /etc/avahi/services/ssh.service. Mar 27 00:12:54 semado avahi-daemon[893]: Service "semado" (/etc/avahi/services/ssh.service) successfully established. Mar 27 00:12:54 semado avahi-daemon[893]: Service "semado" (/etc/avahi/services/sftp-ssh.service) successfully established. Mar 27 00:13:19 semado sshd[3484]: Server listening on 0.0.0.0 port 22. Mar 27 00:13:19 semado sshd[3484]: Server listening on :: port 22. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Cristian Rodríguez -
Sid Boyce