From owner-freebsd-questions@freebsd.org Sat Oct 1 13:28:18 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 D7B11C0451C for ; Sat, 1 Oct 2016 13:28:18 +0000 (UTC) (envelope-from walkenhorst.benjamin@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (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 6E16B1E55 for ; Sat, 1 Oct 2016 13:28:18 +0000 (UTC) (envelope-from walkenhorst.benjamin@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id b184so7296915wma.3 for ; Sat, 01 Oct 2016 06:28:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=5f6yAWFpEjKvi/KmtBNQM0hALbjOJXRnMclbAHRM30c=; b=vkM0zhAsj6ybCuAYAWPY7kLECrve3tG42forVxjIHLaNx6vKzWd2x4OkelrKees6A4 n4iGs7yDBCpuofmglBP+8GxDP5vpC+LNd/AuS+bW2jw9ijBovdOPEB1pFITCrV02Cu7M tXjuzNKVQbfivTvfT/vuPuKa8zbMlpEKm9L9eY5IvFqJWmv/rAnv5WAk8+wgIC/Dki9Z TiIsJD57FRIJUunMgO9BbeKfp/U1DrJnvcjObpqn1ZIuSJum1hwNAxShp7r7/2aMKZJk k0+StMU7m5K2WaPFdJYin8610O/QB+wRhlbUJpK8PkNDAzG3zGGqAMcUlyNrLzsNrCL8 nFDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=5f6yAWFpEjKvi/KmtBNQM0hALbjOJXRnMclbAHRM30c=; b=hTlNSZeUPISwM59MxT2abiLBnmmn1QSNcaPWK2X8XC/con+A2TfgD3ccXkCu3CciN2 1oO8t+gF2pQYFoWVAX5/KjxwQf0Jrmj03aU04Ls62wvMzp/bvSJEerbCWS+E67kiEH2h /MiAgPzaWBsgC0vPlKYtoaW/Fdq8tD6wNxgBuVb+/0RHT//YsmFNjvvs7ESnRyzWPQyM hpq9m6x81bGFiMAPkfDH72YG71oXxfVgDVpbHllHLrTZ+74E2KpcBE5IBneOACBczsRp d+jyvSC2JGmJp+mOJHJZIJQcgkldi2U8lKd2z1Vn78InnAuuqvhvHWIExPC3+lzPH+67 iAqw== X-Gm-Message-State: AA6/9Rli2nXjfp35G2gZTMzRxgvS/Rwur9MSB3BTn5dr+SIJyTmSeYnI18KdtEWsug53Nw== X-Received: by 10.194.238.42 with SMTP id vh10mr10131220wjc.111.1475328496676; Sat, 01 Oct 2016 06:28:16 -0700 (PDT) Received: from julie.krylon.net ([84.139.251.99]) by smtp.gmail.com with ESMTPSA id ab9sm24721107wjc.7.2016.10.01.06.28.15 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 01 Oct 2016 06:28:16 -0700 (PDT) From: Benjamin Walkenhorst Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: sshd does not start after upgrade to 11 Message-Id: <7DC514C7-4597-4D72-8DE3-EFDD78A7C96D@gmail.com> Date: Sat, 1 Oct 2016 15:28:07 +0200 To: freebsd-questions@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) 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: Sat, 01 Oct 2016 13:28:18 -0000 Hello everyone, I just upgraded my VPS from 10.3 to 11, and the upgrade *mostly* worked = as 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.=20 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 = still 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 = grateful.=20 Kind regards, Benjamin=