[arch-general] (no subject)
Hello! I was investigating this boot up error message : "failed to start verify of integrity of password and group files" It turned out to be due (apparently) to a faulty (re)installation of mariadb, which I seem to have fixed. Fine. But in the process, I came across this in my system: [localuser@localhost ~]$ systemctl status shadow shadow.service - Verify integrity of password and group files Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled) Active: inactive (dead) I am having some difficulty trying to find information on this. Bottom line: is this a problem, that I need to fix, or is it something that is normal and can just be ignored?
On Tue, 2015-06-09 at 14:39 -0500, Francis Gerund wrote:
failed to start verify of integrity of password and group files
I noticed it a long time ago and ignored it, however, when searching the web with startpage for "failed to start verify of integrity of password and group files", the first hit I get starts with [SOLVED]: https://bbs.archlinux.org/viewtopic.php?id=180203 Id it's important for your security, you should read such threads. I didn't read this or any other thread.
What Jens pointed out is what the link I posted and several others say too. I noticed it without reading the whole thread ;). I for example get $ sudo pwck -r user 'sagemath': directory '/opt/sage' does not exist pwck: no changes I don't care about it, I don't guess it's a security hole. Am I mistaken?
Hi. I actuallly did see that, but that seems to talk about the shadow.service "failing" to start or run properly. the terminal message I was getting said: shadow.service - Verify integrity of password and group files Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled) Active: inactive (dead) So it was like, "what do that mean"? And since it mentioned checking the password file, I figured I'd best check into it. I don't know what the shadow.service is, and am new to systemd. On Tue, Jun 9, 2015 at 2:47 PM, Ralf Mardorf <ralf.mardorf@rocketmail.com> wrote:
On Tue, 2015-06-09 at 14:39 -0500, Francis Gerund wrote:
failed to start verify of integrity of password and group files
I noticed it a long time ago and ignored it, however, when searching the web with startpage for "failed to start verify of integrity of password and group files", the first hit I get starts with [SOLVED]:
https://bbs.archlinux.org/viewtopic.php?id=180203
Id it's important for your security, you should read such threads. I didn't read this or any other thread.
On Tue, Jun 9, 2015 at 10:07 PM, Francis Gerund <ranrund@gmail.com> wrote:
Hi.
I actuallly did see that, but that seems to talk about the shadow.service "failing" to start or run properly.
the terminal message I was getting said:
shadow.service - Verify integrity of password and group files Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled) Active: inactive (dead)
So it was like, "what do that mean"? And since it mentioned checking the password file, I figured I'd best check into it.
I don't know what the shadow.service is, and am new to systemd.
The shadow.service comes from the `shadow` package, and it’s responsible for checking and testing your /etc/passwd, /etc/group, /etc/shadow and /etc/gshadow files (which is what the name already tells you). The output you pasted means your files are correct and there is nothing to worry about. If they weren’t, you would get different output (and should run the ExecStart command manually without `-r` to resolve the issues): ● shadow.service - Verify integrity of password and group files Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2015-06-10 17:17:30 CEST; 9s ago Process: 9420 ExecStart=/usr/bin/pwck -r (code=exited, status=2) Main PID: 9420 (code=exited, status=2) Jun 10 17:17:30 kw-cassandra systemd[1]: Starting Verify integrity of password and group files... Jun 10 17:17:30 kw-cassandra systemd[1]: shadow.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Jun 10 17:17:30 kw-cassandra systemd[1]: Failed to start Verify integrity of password and group files. Jun 10 17:17:30 kw-cassandra systemd[1]: shadow.service: Unit entered failed state. Jun 10 17:17:30 kw-cassandra systemd[1]: shadow.service: Failed with result 'exit-code'. Jun 10 17:17:30 kw-cassandra pwck[9420]: duplicate password entry Jun 10 17:17:30 kw-cassandra pwck[9420]: delete line 'bin:x:1:1:bin:/bin:/usr/bin/nologin'? No Jun 10 17:17:30 kw-cassandra pwck[9420]: duplicate password entry Jun 10 17:17:30 kw-cassandra pwck[9420]: delete line 'bin:x:1:1:bin:/bin:/usr/bin/nologin'? No Jun 10 17:17:30 kw-cassandra pwck[9420]: pwck: no changes -- Chris Warrick <https://chriswarrick.com/> PGP: 5EAAEA16
Okay, thanks for the information. System working okay now. : ) On Wed, Jun 10, 2015 at 10:23 AM, Chris Warrick <kwpolska@gmail.com> wrote:
On Tue, Jun 9, 2015 at 10:07 PM, Francis Gerund <ranrund@gmail.com> wrote:
Hi.
I actuallly did see that, but that seems to talk about the shadow.service "failing" to start or run properly.
the terminal message I was getting said:
shadow.service - Verify integrity of password and group files Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled) Active: inactive (dead)
So it was like, "what do that mean"? And since it mentioned checking the password file, I figured I'd best check into it.
I don't know what the shadow.service is, and am new to systemd.
The shadow.service comes from the `shadow` package, and it’s responsible for checking and testing your /etc/passwd, /etc/group, /etc/shadow and /etc/gshadow files (which is what the name already tells you). The output you pasted means your files are correct and there is nothing to worry about. If they weren’t, you would get different output (and should run the ExecStart command manually without `-r` to resolve the issues):
● shadow.service - Verify integrity of password and group files Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2015-06-10 17:17:30 CEST; 9s ago Process: 9420 ExecStart=/usr/bin/pwck -r (code=exited, status=2) Main PID: 9420 (code=exited, status=2)
Jun 10 17:17:30 kw-cassandra systemd[1]: Starting Verify integrity of password and group files... Jun 10 17:17:30 kw-cassandra systemd[1]: shadow.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Jun 10 17:17:30 kw-cassandra systemd[1]: Failed to start Verify integrity of password and group files. Jun 10 17:17:30 kw-cassandra systemd[1]: shadow.service: Unit entered failed state. Jun 10 17:17:30 kw-cassandra systemd[1]: shadow.service: Failed with result 'exit-code'. Jun 10 17:17:30 kw-cassandra pwck[9420]: duplicate password entry Jun 10 17:17:30 kw-cassandra pwck[9420]: delete line 'bin:x:1:1:bin:/bin:/usr/bin/nologin'? No Jun 10 17:17:30 kw-cassandra pwck[9420]: duplicate password entry Jun 10 17:17:30 kw-cassandra pwck[9420]: delete line 'bin:x:1:1:bin:/bin:/usr/bin/nologin'? No Jun 10 17:17:30 kw-cassandra pwck[9420]: pwck: no changes
-- Chris Warrick <https://chriswarrick.com/> PGP: 5EAAEA16
Tue, 9 Jun 2015 14:39:24 -0500 Francis Gerund <ranrund@gmail.com>:
[localuser@localhost ~]$ systemctl status shadow shadow.service - Verify integrity of password and group files Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled) Active: inactive (dead)
I am having some difficulty trying to find information on this. Bottom line: is this a problem, that I need to fix, or is it something that is normal and can just be ignored?
The information is in /usr/lib/systemd/system/shadow.* It's a daily OneShot service (replacing a daily cronjob from pre-systemd-times) running 'pwck -r' and 'grpck -r', so run these commands manually and see what they're complaining about. --byte
Hi. While investigating the original error, I did research (and use) both pwck and grpck. Indeed, pwck was complaining about ab missing lib directory for mysql, which did lead to discovering the problem with mariadb. After the bug fix, no problems from either pwck -r or grpck -r. Thanks for the pointer to /usr/lib/systemd/system/shadow.service. I was assuming that it might be something that runs on startup and then goes away. But, you know what happens when you "assume". Thanks again. On Tue, Jun 9, 2015 at 2:51 PM, Jens Adam <jra@byte.cx> wrote:
Tue, 9 Jun 2015 14:39:24 -0500 Francis Gerund <ranrund@gmail.com>:
[localuser@localhost ~]$ systemctl status shadow shadow.service - Verify integrity of password and group files Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled) Active: inactive (dead)
I am having some difficulty trying to find information on this. Bottom line: is this a problem, that I need to fix, or is it something that is normal and can just be ignored?
The information is in /usr/lib/systemd/system/shadow.* It's a daily OneShot service (replacing a daily cronjob from pre-systemd-times) running 'pwck -r' and 'grpck -r', so run these commands manually and see what they're complaining about.
--byte
participants (4)
-
Chris Warrick
-
Francis Gerund
-
Jens Adam
-
Ralf Mardorf