From owner-freebsd-bugs@freebsd.org Thu Feb 11 09:27:46 2021 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7D877540DA6 for ; Thu, 11 Feb 2021 09:27:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4Dbrrf2yqsz3FBZ for ; Thu, 11 Feb 2021 09:27:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 65CF6540F12; Thu, 11 Feb 2021 09:27:46 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6595E540C4E for ; Thu, 11 Feb 2021 09:27:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Dbrrf2Npjz3F6R for ; Thu, 11 Feb 2021 09:27:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 3AC19671C for ; Thu, 11 Feb 2021 09:27:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 11B9RkEo068959 for ; Thu, 11 Feb 2021 09:27:46 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 11B9Rknk068958 for bugs@FreeBSD.org; Thu, 11 Feb 2021 09:27:46 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 253429] Failed invocation of /usr/sbin/service when going multi-user Date: Thu, 11 Feb 2021 09:27:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: se@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2021 09:27:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253429 Bug ID: 253429 Summary: Failed invocation of /usr/sbin/service when going multi-user Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: conf Assignee: bugs@FreeBSD.org Reporter: se@FreeBSD.org A few weeks ago I noticed that cron is no longer started on my system after= a reboot. This is caused by /usr being on a separate ZFS file system that has not been mounted at the time when the rc script tries to start cron, despite it havi= ng a REQUIRE: FILESYSTEMS condition: # PROVIDE: cron # REQUIRE: LOGIN FILESYSTEMS # BEFORE: securelevel # KEYWORD: shutdown According to "service -e", cron is one of the last few services to be start= ed: $ service -e /etc/rc.d/rctl /etc/rc.d/hostid /etc/rc.d/zpool /etc/rc.d/zvol /etc/rc.d/hostid_save /usr/local/etc/rc.d/microcode_update /etc/rc.d/zfsbe /etc/rc.d/zfs ... /etc/rc.d/cron /usr/local/etc/rc.d/sa-spamd /usr/local/etc/rc.d/dovecot /usr/local/etc/rc.d/postfix /etc/rc.d/bgfsck But in fact, starting cron is the first action when going multi-user and be= fore local file systems (beyond / and /dev) have been mounted: ... ugen0.6: at usbus0 ukbd0 on uhub3 ukbd0: on usbus0 kbd2 at ukbd0 hidraw1 on uhub3 hidraw1: on usbus0 /etc/rc.d/cron: service: not found /etc/rc: WARNING: run_rc_command: cannot run /usr/sbin/cron Setting hostuuid: 1e0028e0-008c-4300-13a1-f46d04d87842. Setting hostid: 0x3c3b54d6. Starting file system checks: Mounting local filesystems:. The log shows, that the /usr/sbin/service command is not available, yet. The same is of course true for /usr/sbin/cron. Before mounting the essential file systems, commands like service are not available and I understand that this is a contradiction to file systems bei= ng mounted when going multi-user as directed by the output of "service -e". I'm not aware on any local modifications of my start-up scripts, but I guess that having a separate /usr partition is not common, anymore. Moving the "service" command to /sbin might fix this issue (to be verified). --=20 You are receiving this mail because: You are the assignee for the bug.=