random shadow.service failed on boot up

FenrirAB · 2014-06-06 23:24:05

ever since i installed xampp (for apache and mysql use) there seems to be a random shadow.service failed... during start up... there are a few solve here and there but im too weary about deleting anything without understanding whats going on... im not even sure if xampp IS the culptrit but i know that ever since i installed it, the shadow.service started to failed... any help would be available and i will provided any needed info to solve it if asked..

THANKS IN ADVANCE!

jasonwryan · 2014-06-07 00:46:40

xampp has nothing to do with it: it was the filesystem upgrade. There are a couple of threads here already with details of how to fix it. Read your journal and then search on the terms for the thread here.

loqs · 2014-06-07 11:41:12

systemctl status -l shadow.service

this should be roughly equivalent to (see man pwck for details)

pwck -r

With the list of all inconsistencies you can research which entries need to be added / amended / removed from /etc/group /etc/passwd /etc/shadow

FenrirAB · 2014-06-07 20:25:55

the reason why i kept thinking its xammp is because it kept pulling up mysql, ~~NOW i know this is stupid but DOES creating that mysql directory in the home folder will solve this?~~

i do have a directory /home/mysql.

[fenrirab@thegrid ~]$ systemctl status -l shadow.service
● shadow.service - Verify integrity of password and group files
   Loaded: loaded (/usr/lib/systemd/system/shadow.service; static)
   Active: failed (Result: exit-code) since Sat 2014-06-07 13:18:51 PDT; 3min 4s ago
  Process: 257 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
 Main PID: 257 (code=exited, status=2)

Jun 07 13:18:57 thegrid pwck[257]: user 'mysql': directory '/home/mysql' does not exist
Jun 07 13:18:57 thegrid pwck[257]: pwck: no changes

THANKS IN ADVANCE

Last edited by FenrirAB (2014-06-07 20:30:53)

FenrirAB · 2014-06-20 21:49:58

still no luck... im not confident enough to write or deletes something in the shadow file without knowing what im suppose to be doing ... here is the list in my journal

Job for shadow.service failed. See 'systemctl status shadow.service' and 'journalctl -xn' for details.
[fenrirab@thegrid ~]$ journalctl -xn
-- Logs begin at Sat 2014-04-26 09:42:42 PDT, end at Fri 2014-06-20 14:39:50 PDT
Jun 20 14:39:42 thegrid dbus[249]: [system] Rejected send message, 2 matched rul
Jun 20 14:39:50 thegrid sudo[774]: fenrirab : TTY=pts/0 ; PWD=/home/fenrirab ; U
Jun 20 14:39:50 thegrid sudo[774]: pam_unix(sudo:session): session opened for us
Jun 20 14:39:50 thegrid systemd[1]: Starting Verify integrity of password and gr
-- Subject: Unit shadow.service has begun with start-up
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- 
-- Unit shadow.service has begun starting up.
Jun 20 14:39:50 thegrid pwck[777]: user 'mysql': directory '/home/mysql' does no
Jun 20 14:39:50 thegrid pwck[777]: pwck: no changes
Jun 20 14:39:50 thegrid systemd[1]: shadow.service: main process exited, code=ex
Jun 20 14:39:50 thegrid systemd[1]: Failed to start Verify integrity of password
-- Subject: Unit shadow.service has failed
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- 
-- Unit shadow.service has failed.
-- 
-- The result is failed.
Jun 20 14:39:50 thegrid systemd[1]: Unit shadow.service entered failed state.
Jun 20 14:39:50 thegrid sudo[774]: pam_unix(sudo:session): session closed for us
lines 1-23...skipping...
-- Logs begin at Sat 2014-04-26 09:42:42 PDT, end at Fri 2014-06-20 14:39:50 PDT. --
Jun 20 14:39:42 thegrid dbus[249]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.58" (uid=1000 pid=772 comm="systemc
Jun 20 14:39:50 thegrid sudo[774]: fenrirab : TTY=pts/0 ; PWD=/home/fenrirab ; USER=root ; COMMAND=/usr/bin/systemctl start -l shadow.service
Jun 20 14:39:50 thegrid sudo[774]: pam_unix(sudo:session): session opened for user root by fenrirab(uid=0)
Jun 20 14:39:50 thegrid systemd[1]: Starting Verify integrity of password and group files...
-- Subject: Unit shadow.service has begun with start-up
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- 
-- Unit shadow.service has begun starting up.
Jun 20 14:39:50 thegrid pwck[777]: user 'mysql': directory '/home/mysql' does not exist
Jun 20 14:39:50 thegrid pwck[777]: pwck: no changes
Jun 20 14:39:50 thegrid systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Jun 20 14:39:50 thegrid systemd[1]: Failed to start Verify integrity of password and group files.
-- Subject: Unit shadow.service has failed
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- 
-- Unit shadow.service has failed.
-- 
-- The result is failed.
Jun 20 14:39:50 thegrid systemd[1]: Unit shadow.service entered failed state.
Jun 20 14:39:50 thegrid sudo[774]: pam_unix(sudo:session): session closed for user root
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-23/23 (END)

falconindy · 2014-06-20 22:17:34

user 'mysql': directory '/home/mysql' does not exist

This seems pretty clear, and the fix has nothing to do with editing shadow DB files...

FenrirAB · 2014-07-29 07:54:23

sorry guys but i still dont understand...

went to etc/group and deleted this line:
mysql:x:998:

went to etc/passwd and deleted the line with mysql in it.

and this is the result after i restarted

[fenrirab@thegrid ~]$ sudo systemctl start -l shadow.service
[sudo] password for fenrirab: 
Job for shadow.service failed. See 'systemctl status shadow.service' and 'journalctl -xn' for details.
[fenrirab@thegrid ~]$ systemctl start -l shadow.service
Failed to start shadow.service: Access denied
[fenrirab@thegrid ~]$ sudo systemctl start -l shadow.service
Job for shadow.service failed. See 'systemctl status shadow.service' and 'journalctl -xn' for details.
[fenrirab@thegrid ~]$ systemctl status -l shadow.service
● shadow.service - Verify integrity of password and group files
   Loaded: loaded (/usr/lib/systemd/system/shadow.service; static)
   Active: failed (Result: exit-code) since Tue 2014-07-29 00:49:54 PDT; 4s ago
  Process: 790 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
 Main PID: 790 (code=exited, status=2)

Jul 29 00:49:54 thegrid pwck[790]: no matching password file entry in /etc/passwd
Jul 29 00:49:54 thegrid pwck[790]: delete line 'mysql:!:16208::::::'? No
Jul 29 00:49:54 thegrid pwck[790]: pwck: no changes
Jul 29 00:49:54 thegrid systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Jul 29 00:49:54 thegrid systemd[1]: Failed to start Verify integrity of password and group files.
Jul 29 00:49:54 thegrid systemd[1]: Unit shadow.service entered failed state.
[fenrirab@thegrid ~]$

Last edited by FenrirAB (2014-07-29 07:55:58)

FenrirAB · 2014-07-29 08:12:23

seem to have fixed it by

sudo pwck
delete line 'mysql:!:16208::::::'? Yes

type Yes

then

sudo grpck
delete line 'mysql:!:16208::::::'? Yes

type Yes

will mark as SOLVE after a few days of testing...
restart computer

Arch Linux

#1 2014-06-06 23:24:05

random shadow.service failed on boot up

#2 2014-06-07 00:46:40

Re: random shadow.service failed on boot up

#3 2014-06-07 11:41:12

Re: random shadow.service failed on boot up

#4 2014-06-07 20:25:55

Re: random shadow.service failed on boot up

#5 2014-06-20 21:49:58

Re: random shadow.service failed on boot up

#6 2014-06-20 22:17:34

Re: random shadow.service failed on boot up

#7 2014-07-29 07:54:23

Re: random shadow.service failed on boot up

#8 2014-07-29 08:12:23

Re: random shadow.service failed on boot up

Board footer