Thanks for that too. I did need to run that because it found several duplicate entries as well as one that shouldn't have been in there anymore. All I had to do was answer yes to everything to fix it.
]]>`sudo grpck` - Worked for me! Thanks. I normally don't bother with pacnew files, but when I do, I let pacmatic handle them. I made the mistake of telling it to replace shadow because I didn't know what it was and so knew I had not edited it. I then had to boot into another Arch install I luckily had on another drive in my computer and revert shadow to an older version. That's when I started getting this error, and `grpck` knew exactly how to fix it.
This worked perfectly for me. I have the habit of manually editing my /etc/passwd and /etc/group files on testing computers.
I guess it's time for me to adopt preferred methods, or at least run grpck after manually editing. Have a look at pwck as well.
]]># grpck
I had some groups duplicated due to a merge of the shadow.pacnew file.
]]>Reinstalling avahi did not correct the error.
Same for me here, as well as for polkitd. In fact there are no groups for those two :
# grep avahi passwd* group*
passwd:avahi:x:84:84:avahi:/:/bin/false
passwd-:avahi:x:84:84:avahi:/:/bin/false
# grep polkitd passwd* group*
passwd:polkitd:x:102:102:Policy Kit Daemon:/:/bin/false
passwd-:polkitd:x:102:102:Policy Kit Daemon:/:/bin/false
I know I messed up merging the .pacnew files
Would creating the groups with groupadd solve the problem ? Something like this :
# groupadd -g 84 avahi
# groupadd -g 102 polkitd
Or am I missing something important here ?
]]>/etc $ sudo pwck
user 'addeduser': no group 1001
user 'avahi': no group 84
pwck: no changes
/etc $ sudo grep avahi passwd* group*
passwd:avahi:x:84:84:avahi:/:/bin/false
passwd-:avahi:x:84:84:avahi:/:/bin/false
group:avahi:x:85:
group-:avahi:x:85:
group.bak:avahi:x:84:
What happens if I change avahi:x:85 to avahi:x:84 in /etc/group? Is anything messed up?
After the last update, I used passwd.pacnew, group.pacnew, shadow.pacnew and gshadow.pacnew for a short time, and then I moved them to *.bak's and reverted to the old ones. I don't know what is this mess.
Worse, even the group of an added user is missing. The system is working smoothly.
bpeary - shadow service is new, that is why you are receiving that message only now. simply reinstalling ntp & avahi should be the easiest way to fix it.
AFAIK the only way arch packages would make shadow. service fail was this:
https://bbs.archlinux.org/viewtopic.php … 2#p1171272
Don't overwrite your group file with a .pacnew one without merging them.
]]>I too am newly receiving this message, and have made no changes to users, groups, or passwords for at least a year.
shadow.service - Verify integrity of password and group files
Loaded: loaded (/usr/lib/systemd/system/shadow.service; static)
Active: failed (Result: exit-code) since Wed 2014-04-23 16:01:13 EDT; 7min ago
Process: 300 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
Main PID: 300 (code=exited, status=2)
Apr 23 16:01:13 arch pwck[300]: user 'avahi': no group 84
Apr 23 16:01:13 arch pwck[300]: user 'ntp': no group 87
Apr 23 16:01:13 arch pwck[300]: pwck: no changes
Apr 23 16:01:13 arch systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 23 16:01:13 arch systemd[1]: Failed to start Verify integrity of password and group files.
Apr 23 16:01:13 arch systemd[1]: Unit shadow.service entered failed state.
Is it simply a matter of adding these to /etc/group?
]]># systemctl status -l shadow
● shadow.service - Verify integrity of password and group files
Loaded: loaded (/usr/lib/systemd/system/shadow.service; static)
Active: failed (Result: exit-code) since Wed 2014-04-23 12:28:32 IDT; 2s ago
Process: 1017 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
Main PID: 1017 (code=exited, status=2)
Apr 23 12:28:32 Host pwck[1017]: user 'mysql': directory '/home/mysql' does not exist
Apr 23 12:28:32 Host pwck[1017]: pwck: no changes
Apr 23 12:28:32 Host systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 23 12:28:32 Host systemd[1]: Failed to start Verify integrity of password and group files.
Apr 23 12:28:32 Host systemd[1]: Unit shadow.service entered failed state.
How can i fix it?
]]>