Hide Forgot
It seems that even though the openssh server is installed, it is not started on boot. I need to run "service sshd start" everytime.
You maybe know that that systemd is not supported in f15, maybe not. If you really want to test the systemd units for sshd you may get it from rawhide's srpm and manually put them to the correct place. There is no will to add them to f15 rpms. But if you test it, pleasse report the bugs. It will be useful when the switch to sytemd will take place.
Ok, but be it by systemd or some other thing, I presume sshd should be started on boot, right?
(In reply to comment #2) > Ok, but be it by systemd or some other thing, I presume sshd should be started > on boot, right? yes but not by systemd, only upstart is supported in f15. The essential service should not support systemd in f15.
(In reply to comment #3) > (In reply to comment #2) > > Ok, but be it by systemd or some other thing, I presume sshd should be started > > on boot, right? > > yes but not by systemd, only upstart is supported in f15. The essential service > should not support systemd in f15. I think you meant SysV init script in the sentences above. Also s/should not/do not have to/.
What openssh package version do you have? Also have you installed F15 from scratch or by some upgrade method?
This is openssh-server 5.6p1-31. I installed Fedora from the F15 beta livecd, not by upgrading from a previous release.
That's really weird. The package has regular SysV init script that contains the default runlevels for starting. I thought that F15 still has support for it. Also I cannot reproduce it in F15 beta install (network install, no livecd). Maybe it is some problem in the livecd install? If you call 'chkconfig --add sshd' and restart the computer, does the sshd start up automatically?
I ran "chkconfig --add sshd", restarted the computer, and it did not work. I could not ssh into the machine until I manually ran "service sshd start".
Can you try to update the systemd package and try the chkconfig --add sshd again? I think this must be some bug in the systemd support for SysV init scripts.
How do I "update" the systemd package, given that "yum update" says there are no updates available today?
Well I just wanted you to try to update if there are updates... I don't really think this is openssh bug - it is either problem of systemd or the livecd installer. You can also try chkconfig --del sshd ; chkconfig --add sshd - that might fix it.
For the record, "chkconfig --del sshd && chkconfig --add sshd" did "fix" my affected computer... but like avahi and cherokee and others, I'm left wondering how many systems are affected like this.
I tried the solution in comment #11, but it did not work. systemctl status sshd.servicesshd.service - LSB: Start up the OpenSSH server daemon Loaded: loaded (/etc/rc.d/init.d/sshd) Active: failed since Sat, 09 Jul 2011 14:27:52 -0400; 7min ago Process: 1531 ExecStart=/etc/rc.d/init.d/sshd start (code=exited, status=255) CGroup: name=systemd:/system/sshd.service systemctl start sshd.service Job failed. See system logs and 'systemctl status' for details. When I execute ls /lib/systemd/system/*.service /etc/systemd/system/*.service, sshd is not in the list of services able to be started. My system is F15, x86_64 upgraded by wiping and reinstalling but kept /home partition by creating new encrypted /home and copying all folders/files over via rsync from the old unencrypted /home. Sshd used to work on F14, but I am at a loss of how to get it to work now. Linux XXXXXXX.XXXXXX 2.6.38.8-32.fc15.x86_64 #1 SMP Mon Jun 13 19:49:05 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux openssh-5.6p1-31.fc15.1.x86_64 All updates have been applied.
Update: I found where sshd resides in /usr/sbin and tried to manually start it. That pointed me to a line in the sshd_config file that was causing the start to fail. After eliminating what it viewed as "garbage characters," it started up.
(In reply to comment #14) > Update: I found where sshd resides in /usr/sbin and tried to manually start > it. That pointed me to a line in the sshd_config file that was causing the > start to fail. Can you tell me which line it is? After eliminating what it viewed as "garbage characters," it > started up.
It was the Banner line (line # 129). I had used spaces and punctuation in the line. Once I eliminated them, sshd started right up.
(In reply to comment #16) > It was the Banner line (line # 129). I had used spaces and punctuation in the > line. Once I eliminated them, sshd started right up. This was not the default installation? Is it?
It started as default. I modified the sshd_config file to change ports, disallow root login, and add a banner. It was in adding the banner that the problem occurred. I guess I don't really need a banner, but I wanted something to verify I had the correct machine.
The Banner is a filename of the file containing the banner.
Okay. I did not realize that. In my defense, it was not really clear in the default sshd_config file about that and the man page assumed that I already knew how to do this (took a bit too much for granted about my experience level with servers). # no default banner path #Banner none I appreciate your pointer in the right direction. I going to fix this properly as soon as I finish this note. I am not setting up a public server but just setting it up so I can access my home machine and files while I am traveling.
It seems to me that there is no bug.