From owner-freebsd-questions@freebsd.org Tue Oct 11 03:58:36 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCEC4C075E3 for ; Tue, 11 Oct 2016 03:58:36 +0000 (UTC) (envelope-from gobble.wa@gmail.com) Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 78E5BB40 for ; Tue, 11 Oct 2016 03:58:36 +0000 (UTC) (envelope-from gobble.wa@gmail.com) Received: by mail-qk0-x230.google.com with SMTP id z190so12045297qkc.2 for ; Mon, 10 Oct 2016 20:58:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=z9iYkW6SoAeaRmYy1sNIS+USgGjodm2xjBu2ClkLLx8=; b=kfkn0rITigPgqn6ODb4kRdGo0FUtmU/x9Q6AhTl8EK1jvmMGK1eYXMeezoeQiyLflX tYMOeT6zlxNylmRyy9E960p5YhJYcFBWRRJbFgllD5AoOSJQYUDKjahF7kH0ctphlhSP K07KdfPS3vUrWtG2+h4W5yd78MvE/21g4U+pjJcuNqk9RaSOa/Mg53QoQyAlsCsu4kUq B7mt4YEjFkOQ/IV+oJ3RGbOchjg1SYtRi29NjYqhQrPAYx1ImcaZF8MK2Vyn7UtXhHkb uwe7zpyDETXFUESNphJ/DwoHLkikeuBzC3efZV/Yutf4Rt4c6fsoHhpgbfV40aa8pRBl bgzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=z9iYkW6SoAeaRmYy1sNIS+USgGjodm2xjBu2ClkLLx8=; b=chgUVNz8aCleq2ar+bY82WNZxgFkgmwMWw8vc/ZTptwQ2xcTt5G9aa1XyIqCz9y8u2 +nRN6i2kskv6Wccs7LuC3KZx/upHCb2ngNWuuDn6bwSB6pAlAYt9CJyqHRlvi+DFAUNY bDlC49Hm/FIVDPMIrjVSPxPkoUwCHKJD7YZRAbEh7L5yXV2EWzLtrBj7olyo+BzrDOdq v37SQdnuGH0lnWesfY8h61j9GTs2CTRMMrmZkdKNRAEZThnU8Q2ScM+bjpLaTUXY5MWF PG9B6vQl+X/Q2sNPjYy/Brhu7zqRIzo1JwaN+XVJqNTHFEgim5VpTRdsRnZXJ2tgl+Ac 1cGw== X-Gm-Message-State: AA6/9RknJ3xODL+llj/w8pDXSJ5DK2wh5+N40lMU5AEUaWhYUFroD9c5scdWQtG20oqLWIeblkgm6Ti0PRCoQQ== X-Received: by 10.55.121.67 with SMTP id u64mr1735375qkc.114.1476158315622; Mon, 10 Oct 2016 20:58:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.34.142 with HTTP; Mon, 10 Oct 2016 20:58:35 -0700 (PDT) In-Reply-To: <7DC514C7-4597-4D72-8DE3-EFDD78A7C96D@gmail.com> References: <7DC514C7-4597-4D72-8DE3-EFDD78A7C96D@gmail.com> From: Waitman Gobble Date: Mon, 10 Oct 2016 20:58:35 -0700 Message-ID: Subject: Re: sshd does not start after upgrade to 11 To: "freebsd-questions@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Oct 2016 03:58:36 -0000 On Sat, Oct 1, 2016 at 6:28 AM, Benjamin Walkenhorst 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