Date: Mon, 10 Oct 2016 20:58:35 -0700 From: Waitman Gobble <gobble.wa@gmail.com> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: sshd does not start after upgrade to 11 Message-ID: <CAFuo_fxxtCrxYErJ00ZdOSDjh1bs_LHjeWM_0xwZuXomdgDNXA@mail.gmail.com> In-Reply-To: <7DC514C7-4597-4D72-8DE3-EFDD78A7C96D@gmail.com> References: <7DC514C7-4597-4D72-8DE3-EFDD78A7C96D@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Oct 1, 2016 at 6:28 AM, Benjamin Walkenhorst <walkenhorst.benjamin@gmail.com> wrote: > Hello everyone, > > > I just upgraded my VPS from 10.3 to 11, and the upgrade *mostly* worked a= s I had hoped, except that now sshd is not started automatically. Which is = kind of annoying for a remote system. ;-) > > When I login through the console and say (as root) =E2=80=9Eservice sshd = start=E2=80=9C, I get the following output: > 14:59|root@straylight:/var/log]# service sshd restart > Performing sanity check on sshd configuration. > Stopping sshd. > Performing sanity check on sshd configuration. > Starting sshd. > login class '/usr/sbin/sshd' non-existent, using default > Resource limits for class default: > cputime infinity secs > filesize infinity kB > datasize infinity kB > stacksize infinity kB > coredumpsize infinity kB > memoryuse infinity kB > memorylocked 64 kB > maxprocesses infinity > openfiles infinity > sbsize infinity bytes > vmemoryuse infinity kB > pseudo-terminals infinity > swapuse infinity kB > kqueues infinity > umtxp infinity > > Afterwards, =E2=80=9Epgrep ssh=E2=80=9C does not show any processes. > There are no error messages in syslog, either. > > When I run (again, as root) /usr/sbin/sshd manually, it works. > > Did I mess something up during the upgrade inadvertently? Since I can sti= ll start sshd manually, I suspect the problem is not with sshd itself, but = the way it is started by the init system. > > If anyone could give me a hint on how to proceed, I would be very gratefu= l. > Kind regards, > Benjamin > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" The upgrade process of files in /etc is perhaps a bit 'screwy' IMHO. At minimum it's error-prone. I'm not sure it's common to edit rc.subr anyway? This should fix. root@fbsf:/etc # mv rc.subr rc.subr.back root@fbsf:/etc # wget "https://raw.githubusercontent.com/freebsd/freebsd/master/etc/rc.subr" --2016-10-11 03:50:59-- https://raw.githubusercontent.com/freebsd/freebsd/master/etc/rc.subr Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.44.133 Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.44.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 48643 (48K) [text/plain] Saving to: 'rc.subr' rc.subr 100%[=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= >] 47.50K --.-KB/s in 0.1s 2016-10-11 03:50:59 (418 KB/s) - 'rc.subr' saved [48643/48643] root@fbsf:/etc # service sshd restart Performing sanity check on sshd configuration. sshd not running? (check /var/run/sshd.pid). Performing sanity check on sshd configuration. Starting sshd. root@fbsf:/etc # --=20 Waitman Gobble Los Altos California USA 650-900-8557
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFuo_fxxtCrxYErJ00ZdOSDjh1bs_LHjeWM_0xwZuXomdgDNXA>