Date: Fri, 14 Dec 2018 15:59:38 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 234014] chown: ntpd: illegal user name -- after freebsd-update to 12.0 Message-ID: <bug-234014-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234014 Bug ID: 234014 Summary: chown: ntpd: illegal user name -- after freebsd-update to 12.0 Product: Base System Version: 12.0-RELEASE Hardware: i386 OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: vangyzen@FreeBSD.org I just updated an i386 machine (not amd64) from 11.2-RELEASE to 12.0-RELEASE using freebsd-update. On boot, the console says: chown: ntpd: illegal user name Sure enough, the ntpd user was in /etc/*passwd but _not_ in /etc/*pwd.db. # getent passwd ntpd # grep ntp master.passwd ntpd:*:123:123::0:0:NTP Daemon:/var/db/ntp:/usr/sbin/nologin # strings spwd.db | grep ntp # strings pwd.db | grep ntp Also, ntpd is running as root. The pwd db files were newer than the plain text files, so pwd_mkdb did run during the upgrade: # stat -x master.passwd passwd spwd.db pwd.db File: "master.passwd" Size: 3019 FileType: Regular File Mode: (0600/-rw-------) Uid: ( 0/ root) Gid: ( 0/ wheel) Device: 0,70 Inode: 1036545 Links: 1 Access: Fri Dec 14 09:30:48 2018 Modify: Fri Dec 14 09:30:48 2018 Change: Fri Dec 14 09:32:39 2018 File: "passwd" Size: 2509 FileType: Regular File Mode: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ wheel) Device: 0,70 Inode: 1036629 Links: 1 Access: Fri Dec 14 09:30:48 2018 Modify: Fri Dec 14 09:30:48 2018 Change: Fri Dec 14 09:32:39 2018 File: "spwd.db" Size: 40960 FileType: Regular File Mode: (0600/-rw-------) Uid: ( 0/ root) Gid: ( 0/ wheel) Device: 0,70 Inode: 1036680 Links: 1 Access: Fri Dec 14 09:48:57 2018 Modify: Fri Dec 14 09:30:50 2018 Change: Fri Dec 14 09:32:40 2018 File: "pwd.db" Size: 40960 FileType: Regular File Mode: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ wheel) Device: 0,70 Inode: 1036668 Links: 1 Access: Fri Dec 14 09:48:38 2018 Modify: Fri Dec 14 09:30:49 2018 Change: Fri Dec 14 09:32:40 2018 I wonder if pwd_mkdb ran against the wrong/old master.passwd file? Simply running pwd_mkdb worked around the problem. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234014-227>