[Solved] Mismatch on GID and shadow.service fails

Hi, randomly the shadow.service fails on loading and it gives me this output:
$ systemctl status shadow.service
● 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 sab 2015-03-28 14:54:50 CET; 13min ago
Process: 1988 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
Main PID: 1988 (code=exited, status=2)
mar 28 14:54:50 vivopicenin pwck[1988]: user 'git': no group 999
mar 28 14:54:50 vivopicenin pwck[1988]: user 'systemd-journal-remote': no group 998
mar 28 14:54:50 vivopicenin pwck[1988]: user 'systemd-journal-upload': no group 997
mar 28 14:54:50 vivopicenin pwck[1988]: user 'sddm': no group 996
mar 28 14:54:50 vivopicenin pwck[1988]: user 'rtkit': no group 133
mar 28 14:54:50 vivopicenin pwck[1988]: pwck: nessuna modifica
mar 28 14:54:50 vivopicenin systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
mar 28 14:54:50 vivopicenin systemd[1]: Failed to start Verify integrity of password and group files.
mar 28 14:54:50 vivopicenin systemd[1]: Unit shadow.service entered failed state.
mar 28 14:54:50 vivopicenin systemd[1]: shadow.service failed.
The output instead of pwck is:
$ sudo pwck
user 'polkitd': no group 102
user 'avahi': no group 84
user 'colord': no group 124
user 'git': no group 999
user 'systemd-journal-remote': no group 998
user 'systemd-journal-upload': no group 997
user 'sddm': no group 996
user 'rtkit': no group 133
pwck: nessuna modifica
So for example for sddm group it requires a 996 GID, but on my /etc/group file i have this content:
$ cat /etc/group
root:x:0:root
bin:x:1:root,bin,daemon
daemon:x:2:root,bin,daemon
sys:x:3:root,bin
adm:x:4:root,daemon
tty:x:5:
disk:x:6:root
lp:x:7:daemon
mem:x:8:
kmem:x:9:
wheel:x:10:root,marco
ftp:x:11:
mail:x:12:
uucp:x:14:
log:x:19:root
utmp:x:20:
locate:x:21:
rfkill:x:24:
smmsp:x:25:
proc:x:26:
http:x:33:
games:x:50:
lock:x:54:
uuidd:x:68:
dbus:x:81:
network:x:90:
video:x:91:
audio:x:92:
optical:x:93:
floppy:x:94:
storage:x:95:
scanner:x:96:
input:x:97:
power:x:98:
nobody:x:99:
users:x:100:
systemd-journal:x:190:
systemd-journal-gateway:x:191:
systemd-timesync:x:192:
systemd-network:x:193:
systemd-bus-proxy:x:194:
systemd-resolve:x:195:
systemd-journal-upload:x:994:
systemd-journal-remote:x:995:
ntp:x:87:
mysql:x:89:
git:x:993:
usbmux:x:140:
vboxusers:x:108:
sddm:x:992:
There are some mismatches, for example on sddm group which requires 996 GID but on my system i have GID 992.
What should i do in oder to fix it?
Thanks!
P.s. sudo gpwck gives me no output and i don't have any .pacnew on my system.
Last edited by toketin (2015-03-29 17:18:03)

Hi thanks for the reply, i've fixed fot the half of the groups' errors, for the others it gives me that the group X doesn't exist. This the output:
# groupmod --gid 102 polkitd
groupmod: group 'polkitd' does not exist
# groupmod --gid 84 avahi
groupmod: group 'avahi' does not exist
# groupmod --gid 124 colord
groupmod: group 'colord' does not exist
# groupmod --gid 133 rtkit
groupmod: group 'rtkit' does not exist
I had tried to re-install yesterday for example git and sddm packages but it didn't fix the issue.
Last edited by toketin (2015-03-29 12:38:01)

Similar Messages

[SOLVED] shadow.service fails

I haven't been tweaking my system much lately, both because it is set up the way I like it and because I haven't been actively interested in it lately. Today I noticed at boot that shadow.service failed. I have updated systemd yesterday and I'm pretty sure this issue popped up only now. It does not seem to cause problems with logging in.
Further inquiry gives me:
systemctl status 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 Thu 2014-04-17 09:50:07 CEST; 6min ago
Process: 5847 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
Main PID: 5847 (code=exited, status=2)
Apr 17 09:50:07 hostname pwck[5847]: duplicate password entry
Apr 17 09:50:07 hostname pwck[5847]: delete line 'uuidd:x:68:68:uuidd:/:/sbin/nologin'? No
Apr 17 09:50:07 hostname pwck[5847]: user 'uuidd': no group 68
Apr 17 09:50:07 hostname pwck[5847]: duplicate password entry
Apr 17 09:50:07 hostname pwck[5847]: delete line 'uuidd:x:998:998::/:/sbin/nologin'? No
Apr 17 09:50:07 hostname pwck[5847]: pwck: no changes
Apr 17 09:50:07 hostname systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 09:50:07 hostname systemd[1]: Failed to start Verify integrity of password and group files.
Apr 17 09:50:07 hostname systemd[1]: Unit shadow.service entered failed state.
journalctl -xn
Apr 17 09:23:57 hostname systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
-- Subject: Unit shadow.service has failed
-- Unit shadow.service has failed.
Apr 17 09:23:57 hostname systemd[1]: Unit shadow.service entered failed state.
Apr 17 09:27:28 hostname dbus[352]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.15" (uid=1000 pid=5525 comm="systemctl start shadow.service ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
Apr 17 09:27:31 hostname sudo[5527]: username : TTY=pts/0 ; PWD=/home/username ; USER=root ; COMMAND=/usr/bin/systemctl start shadow.service
-- Subject: Unit shadow.service has begun with start-up
-- Unit shadow.service has begun starting up.
Apr 17 09:27:31 hostname systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
-- Subject: Unit shadow.service has failed
-- Unit shadow.service has failed.
Apr 17 09:27:31 hostname systemd[1]: Unit shadow.service entered failed state.
I'm not sure what I'm doing in this field and can't seem to find topics with similar problems to this.
Last edited by D. (2014-04-17 13:04:01)

I've got a similar problem with shadow.service not starting due to invalid password file integrity:
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-04-19 07:40:53 NZST; 22min ago
Process: 289 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
Main PID: 289 (code=exited, status=2)
Apr 19 07:40:53 taniwha-folio13 pwck[289]: user 'rtkit': no group 133
Apr 19 07:40:53 taniwha-folio13 pwck[289]: user 'git': no group 998
Apr 19 07:40:53 taniwha-folio13 pwck[289]: user 'transmission': no group 169
Apr 19 07:40:53 taniwha-folio13 pwck[289]: user 'ntp': no group 87
Apr 19 07:40:53 taniwha-folio13 pwck[289]: user 'uuidd': no group 997
Apr 19 07:40:53 taniwha-folio13 pwck[289]: user 'rpc': no group 32
Apr 19 07:40:53 taniwha-folio13 pwck[289]: pwck: no changes
Apr 19 07:40:53 taniwha-folio13 systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 19 07:40:54 taniwha-folio13 systemd[1]: Failed to start Verify integrity of password and group files.
Apr 19 07:40:54 taniwha-folio13 systemd[1]: Unit shadow.service entered failed state.
In my case, the error message indicates users without groups. How do I address this?
ps similar problem, so not sure if I should start a new thread or not

Shadow.service fails after LightDM uninstall

Hi,
Since I've uninstalled Light-locker (and LightDM as a dependency) I receive the following error:
● 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 di 2015-03-24 19:43:48 CET; 45min ago
Process: 315 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
Main PID: 315 (code=exited, status=2)
mrt 24 19:43:47 zeus pwck[315]: user 'lightdm': directory '/var/lib/lightdm' does not exist
mrt 24 19:43:48 zeus pwck[315]: pwck: no changes
mrt 24 19:43:48 zeus systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
mrt 24 19:43:48 zeus systemd[1]: Failed to start Verify integrity of password and group files.
mrt 24 19:43:48 zeus systemd[1]: Unit shadow.service entered failed state.
mrt 24 19:43:48 zeus systemd[1]: shadow.service failed.
Can anyone help me fix this?
Thanks in advance!
Last edited by VenomGameworld (2015-03-24 18:35:15)

Spider.007 wrote:It's interesting the package creates the user on install, but doesn't remove it on uninstallation. I wonder if this is intended by the maintainer.
https://projects.archlinux.org/svntogit … de9766105a is the change that removed user and group deletion.

Shadow.service fails to start

I've gotten a notification upon startup at least twice at this point - something along the lines of "shadow.service failed". systemctl --failed confirms that it's the only service failing.
I found https://bbs.archlinux.org/viewtopic.php?id=180203 - which addresses the same topic, but I'm unsure of how to go about applying the fixes mentioned here. Where can I find the new uuid value that I need for the files that are listed in the first reply? Do I need to edit each of those files? Are there any other files that would affect shadow.service's operation, or any other files that need to be updated with the appropriate uuid value?
The other thing I don't understand is why the service would fail. If the uuid value in the files it checks is invalid, shouldn't it return an error message stating that the checked files failed validation?
Thanks in advance for any help you can provide!

Just read the mentioned thread because the answer is in it and duplicating that seems useless. Don't make it seem like you want the answer to be presented on a silver plate

DHCP and SMB service failing

We have a X server with 10.5.5 installed.
This server is our main server with active settings for OD, SMB, DNS, DHCP and AFP.
At variable intervals the DHCP and SMB service gets corrupt.
here's excerpt from the server log:
Nov 15 04:19:59 FileServer servermgrd[54]: pipe(status) error: 24
Nov 15 04:19:59 FileServer servermgrd[54]: servermgrd: readFile File /etc/ipfilter/ipaddressgroups.plist is not a valid plist
Nov 15 04:19:59 FileServer servermgrd[54]: Exception in doCommand: couldn't spawn task: path = /usr/sbin/sso_util, errno 24
Nov 15 04:19:59 FileServer Server Admin[81743]: * -[ServiceEntry sessionHost]: unrecognized selector sent to instance 0x2a9040
Nov 15 04:20:29: --- last message repeated 1 time ---
Nov 15 04:23:30 FileServer servermgrd[54]: pipe(stdout) error: 24
Nov 15 04:23:30 FileServer servermgrd[54]: Exception in doCommand: couldn't spawn task: path = /usr/bin/smbstatus, errno 24
Nov 15 04:24:08 FileServer servermgrd[54]: pipe(stdout) error: 24
Nov 15 04:24:08 FileServer servermgrd[54]: Exception in doCommand: couldn't spawn task: path = /usr/bin/smbstatus, errno 24
Nov 15 04:24:08 FileServer servermgrd[54]: pipe(status) error: 24
Nov 15 04:24:08 FileServer servermgrd[54]: Exception in doCommand: couldn't spawn task: path = /usr/bin/smbstatus, errno 24
Now this only happens when we leave the server admin app open on the specific server.
If we close the application the server seems to be working fine (for at least 3 weeks...).
We even reinstalled the server from scratch, but this problem is persistent...
Is this a bug en the Server Admin app?

Hi
Get into the habit of not leaving either of the two applications (Server Admin and WorkGroup Manager) open. Especially Server Admin. When you've done with the application quit out of it. If you can develop your command line skills (man serveradmin is useful), try and use these where possible instead. Best advice I can give you.
If your server is not configured as Advanced please ignore this advice.
Tony

[SOLVED]Systemd and Crashplan service failed.

Hello,
Crashplan service won't start.
systemctl status crashplan.service
crashplan.service - CrashPlan Backup Engine
Loaded: loaded (/usr/lib/systemd/system/crashplan.service; enabled)
Active: failed (Result: exit-code) since Wed, 17 Oct 2012 11:21:39 -0600; 1h 11min ago
Process: 922 ExecStop=/opt/crashplan/bin/CrashPlanEngine stop (code=exited, status=0/SUCCESS)
Process: 527 ExecStart=/opt/crashplan/bin/CrashPlanEngine start (code=exited, status=0/SUCCESS)
Main PID: 920 (code=exited, status=127)
CGroup: name=systemd:/system/crashplan.service
Oct 17 11:21:29 arch CrashPlanEngine[527]: Starting CrashPlan Engine ... Using standard startup
Oct 17 11:21:29 arch CrashPlanEngine[527]: OK
Oct 17 11:21:29 arch systemd[1]: Started CrashPlan Backup Engine.
Oct 17 11:21:29 arch CrashPlanEngine[922]: Stopping CrashPlan Engine ... /opt/crashplan/bin/CrashPlanEngine: line 144: kill: (920) - No such process
Oct 17 11:21:39 arch CrashPlanEngine[922]: OK
Please let me know what information can I provide to sort out this issue.
Thanks.
Last edited by donniezazen (2012-10-18 07:04:11)

/usr/lib/systemd/system/crashplan.service
[Unit]
Description=CrashPlan Backup Engine
After=network.target
[Service]
Type=forking
PIDFile=/opt/crashplan/CrashPlanEngine.pid
EnvironmentFile=/opt/crashplan/bin/run.conf
WorkingDirectory=/opt/crashplan
ExecStart=/opt/crashplan/bin/CrashPlanEngine start
ExecStop=/opt/crashplan/bin/CrashPlanEngine stop
[Install]
WantedBy=multi-user.target

[Solved] Suspend to Disk: systemd-hibernate.service Fails

Howdy-ha, folks. I know this looks pretty mundane, but for the life of me I can't get hibernation to work. Each time I run systemctl hibernate the screen will go blank as though preparing to suspend, then come back on; journalctl shows the same error messages:
PM: Cannot find swap device, try swapon -a.
PM: Cannot get swap writer
Failed to start Hibernate.
Dependency failed for Hibernate.
Service sleep.target is not needed anymore. Stopping.
Unit systemd-hibernate.service entered failed state.
This happens when swap is mounted, and "swapon" says as much. I've been working on this for about four hours now, and none of what I've found seems to pertain to my situation (most of the "solutions" were "Increase partition size').
What I've tried:
- Three different kernels---linux-ck custom build and linux-ck-sandybridge from graysky's repo (both with BFQ and CFQ: see below), as well as the stock Arch kernel
- A 2 Gb swap file at /swapfile on my SSD;
- A 4 Gb swap partition on /dev/mmcblk0 (an SD card, and my preferred method/location, if possible);
- An 8 Gb swap partition on HDD /dev/sdb2
Reasons for wanting hibernate rather than suspend-to-RAM:
- Maximize battery life.
- There's some kind of issue with Linux-ck and suspending to RAM; it'll work once, then freeze in a kernel panic the second time, forcing a hard reset. The stock kernel suspends to RAM, but still won't hibernate
- I put a lot of time into building a custom Linux-ck kernel, and would rather not have to start the configuration over with the stock kernel if possible.
I'm working with limited space on my boot drive and, as mentioned, increasing the amount of swap has no bearing on this. The resulting phenomenon and error messages are the same, regardless of size and medium. I've exhausted my ideas on where to look, and what to even look for. Thanks a lot to everyone in advance (especially you,karol; don't think I don't see you lurking back there )
Last edited by ANOKNUSA (2013-11-17 05:32:14)

I rebooted, so trying to recreate the same situation:
$ free -h
total used free shared buffers cached
Mem: 7.7G 7.2G 525M 0B 32M 2.3G
-/+ buffers/cache: 4.8G 2.9G
Swap: 3.7G 0B 3.7G
top reports nearly the same thing:
top - 20:00:13 up 22 min, 1 user, load average: 0.12, 0.22, 0.14
Tasks: 155 total, 1 running, 154 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.1 us, 0.3 sy, 0.1 ni, 99.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem: 8061380 total, 7500096 used, 561284 free, 34432 buffers
KiB Swap: 3872236 total, 0 used, 3872236 free, 2417172 cached
htop, however, reports about 1.5 Gb more free RAM. After reboot, swappiness is still set to 100 with the same results.
EDIT:
ANOKNUSA wrote: I'll test it again with the other locations mentioned in the OP, and get back to you.
Even though I rebooted, I haven't done this yet, so ignore it for the moment.
Last edited by ANOKNUSA (2013-08-28 01:06:10)

Cannot log into CMS and all services fail to load on installation.

A trial version of Crystal Server XI r2 was installed due to problems with the license key for our purchased version of XI. The r2 has since expired and I have uninstalled it. I have now tried to install XI several times, but I am having a problem with the installation where it is Starting Services. I get errors for each server Error 1920 Service Destination and server failed to start. Please can you advise why this is occurring and what I can do to fix it?
I keep getting the log in for the CMS, but no matter what I enter it fails. Possibly I have selected something wrong in the installation. I do not believe we had to log into the CMS previously.
It comes up with
System: CrystalReports (no other options) User Name: Administrator
Password:
Authentication: Enterprise (other options LDAP, Windows NT, Windows AD - all these come up with error that there is no plug-in). I have entered the server password which failed, tried it blank which failed. I do not know what is required here.
I have tried all our passwords, but no users or passwords work. I have tried selecting different options, but have mostly tried New with the Create new or use existing, java and iis both selected as default, SQL Server and entered sa + password,
I think probably an old version of the CMS exists from the original installation, but I have tried complete uninstall.
In the event viewer there is error:
Event Type:     Error
Event Source:     Application Error
Event Category:     (100)
Event ID:     1000
Date:          18/08/2010
Time:          14:16:24
User:          N/A
Computer:     CRYSTALREPORTS
Description:
Faulting application cacheserver.exe, version 11.0.0.1282, faulting module unknown, version 0.0.0.0, fault address 0x7ff2fbfc.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 63 61 63   ure cac
0018: 68 65 73 65 72 76 65 72   heserver
0020: 2e 65 78 65 20 31 31 2e   .exe 11.
0028: 30 2e 30 2e 31 32 38 32   0.0.1282
0030: 20 69 6e 20 75 6e 6b 6e    in unkn
0038: 6f 77 6e 20 30 2e 30 2e   own 0.0.
0040: 30 2e 30 20 61 74 20 6f   0.0 at o
0048: 66 66 73 65 74 20 37 66   ffset 7f
0050: 66 32 66 62 66 63         f2fbfc
Please can someone help? I am almost suicidal!
Georgie

Moved to BOE forums where CRS is supported.

Obejct key mismatch between webservice and entity service

Hi
I created one web service using entity service in one caf project. Now i created another project. I have one entity service in this project which is using the previous web service. when i am testing my second project using service browser, I am getting object key values which are different from what i am getting using web service browser.
Anyone has any idea regarding this?
Regards
Saurabh

Hi Sauragb,
the different object keys is normal, because even when you apply remote persistency caf core stores the "startup" attributes in an database. So when using a entity service you will always have attributes like key, createdBy, lastChangedBy... stored in lokal CAF Database.
And that's why you have different keys.
best Regards,
Rene

[solved] shadow.service load fail Verify integrity password&group file

My system Arch with KDE 5 boot OK but in log I have: "shadow.service loaded failed failed Verify integrity of password and group files"
I make upgrade KDE 4 to next 5. I now not have installed package kdebase-workspace with KDM.
KDE start with edit boot file ~/.xinitrc - in Pantheon desktop environment https://wiki.archlinux.org/index.php/Pantheon
#!/bin/sh
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
gsettings-data-convert &
xdg-user-dirs-gtk-update &
/usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 &
/usr/lib/gnome-settings-daemon/gnome-settings-daemon &
/usr/lib/gnome-user-share/gnome-user-share &
eval $(gnome-keyring-daemon --start --components=pkcs11,secrets,ssh,gpg)
export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT_INFO SSH_AUTH_SOCK
########## exec dbus-launch gala &
# exec cerbere
# start kde 5
exec startkde
[root@arch-linux ~]# systemctl status shadow.service
● 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 śro 2015-05-27 07:55:12 CEST; 4min 41s ago
Process: 285 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
Main PID: 285 (code=exited, status=2)
maj 27 07:55:11 arch-linux systemd[1]: Starting Verify integrity of password and group files...
maj 27 07:55:12 arch-linux pwck[285]: user 'kdm': directory '/var/lib/kdm' does not exist
maj 27 07:55:12 arch-linux pwck[285]: pwck: bez zmian
maj 27 07:55:12 arch-linux systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
maj 27 07:55:12 arch-linux systemd[1]: Failed to start Verify integrity of password and group files.
maj 27 07:55:12 arch-linux systemd[1]: Unit shadow.service entered failed state.
maj 27 07:55:12 arch-linux systemd[1]: shadow.service failed.
[root@arch-linux ~]# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● shadow.service loaded failed failed Verify integrity of password and group files
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Last edited by hackintosh1984pl (2015-05-27 19:18:57)

I help me this information https://bbs.archlinux.org/viewtopic.php?id=193624
Remove line with "kdm" in file: /etc/passwd and reboot and OK is now:
[root@arch-linux ~]# systemctl --failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
I make also backup: cp /etc/passwd /etc/passwd.backup

Pwck Complaining about homeless users, causing shadow.service to fail

I was looking through my journal and noticed the following error:
Jul 08 00:00:00 raspberry_pi systemd[1]: Failed to start Verify integrity of password and group files.
Checking the status of shadow.service produces this output:
~ $ sudo 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 Tue 2014-07-08 00:00:00 PDT; 5min ago
Process: 11736 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
Main PID: 11736 (code=exited, status=2)
Jul 08 00:00:00 raspberry_pi systemd[1]: Starting Verify integrity of password and group files...
Jul 08 00:00:00 raspberry_pi pwck[11736]: user 'remote': directory '/home/remote' does not exist
Jul 08 00:00:00 raspberry_pi systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Jul 08 00:00:00 raspberry_pi systemd[1]: Failed to start Verify integrity of password and group files.
Jul 08 00:00:00 raspberry_pi systemd[1]: Unit shadow.service entered failed state.
Jul 08 00:00:01 raspberry_pi pwck[11736]: pwck: no changes
The passwd entry for this user is
~ $ cat /etc/passwd
remote:x:1001:100::/home/remote:/bin/nologin
I guess this explains why pwck is complaining and causing shadow.service to fail. However, this user was created a long time ago, explicitly without a home directory, so I am not sure why a home path is specified in the passwd file. I also feel certain that this error is relatively new.
So, using the following command I created a test user without a home directory so that I could at least see what a passwd line for a user without a home directory is supposed to look like, but to my surprise a home path was specified in the passwd file and pwck complained about the new user in the same way.
~ $ sudo useradd -M -g users -s /bin/bash testuser
~ $ cat /etc/passwd
testuser:x:1002:100::/home/testuser:/bin/bash
~ $ sudo pwck -r
user 'remote': directory '/home/remote' does not exist
user 'testuser': directory '/home/testuser' does not exist
pwck: no changes
I also created a throwaway user on my x86 notebook to see if this happens, and it does, so this does not appear to be related to the architecture.
Is there anything I could do short of creating a home directory for this user, or does this look like a bug?

Hope it's not too late to answer this.
Changing the home directory to /dev/null seems to have solved the issue for me.
Still don't know what negative effects that might have for me, but shadow.service runs normally as far as I can tell.
Edit:
Performing
userdel -r <user>
throws
userdel: /dev/null not owned by <user>, not removing
, so setting /dev/null as the home directory is relatively "safe"
Last edited by zomernifalt (2014-11-05 15:55:36)

Sync problem on iPhone4 IOS5 and iTunes 10.5: Sync service failed to start

After painful upgrade to IOS 5.0 on my iPone 4 which suffer from er 3014 unt I do full restore in other computer. Now two new problems cropped up again:
A.
When I sync IPhone with iTunes, the sync process started and freeze at "waing f sync service to start" and for 5 minutes or so, it end up with a dialog stated that the iPhone could not be synced because sync service failed to start
To remedy, I have to click t start Sync again, and thios time, it will be completed.
To solve tjhis, I have done the following, and the probelm still persist:
a. Reinstal,l to repair iTunes
b. Delete the Lockup folder
c. Reset sync history
d. reboot iPhone
All cannot solve the problem. Help please, how to solve this problem?
Also, when I backup my iPhone, it freeze at "Backing up iPhone" fr about 10-15 minutes, then start backup, until nearly finished, then it restart backup process again by itself, and again, freezing at "Backing up iPhone" for another 5 minutes, then it start backup and complete. I check the backup time in Preferences, it's correct.
To solve this, I delete the backup, and start new backup, the process went OK. But when I start backup again, the above symptom (backing up, and restart backup again to complete) persist
I have quite a rough experiences with iTunes-iPhone-iPad sync and backup all the times. Can the sync and backup process mad better and real trouble free Apple?
Help and suggestion please. I sync iPhone and iPad2 with WIndow XP PC. iPad2 do not have problem. The problem is with iPhone4 IOS 5 32 GB (less than 2 GB free space on iPhone remains)

I have very similar problems with my brand new iPhone and iTunes. iTunes is virtually unusable even after multiple installs, uniinstalls, and reinstalls. Sync fails silently. Drop-down menus won't stay visible long enough to click any options. Phone-support blames it on the fact that I use Windows XP however the iTunes page says right there: "iTunes 10.5 for Windows XP, Vista or Windows 7". The only program I have problems with is iTunes.
He said I have to revert to iOS 4 but he also said he thought that was impossible. What does the OS on my phone have to do with the behavior of iTunes running on my computer? iTunes crashed and had failures both before and after I updated to iOS 5. Typical bad tech support just like every other company. I thought Apple was different. Apple really stepped in it this time and it stinks. I've seen a huge number of new problem reports here and elsewhere.

[SOLVED]shadow.service won't start

I noticed something wrong during boot and it was shadow.service. Here's some log:
systemctl status 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 Mon 2014-05-12 15:28:32 CST; 6min ago
Process: 20614 ExecStart=/usr/bin/pwck -r (code=exited, status=2)
Main PID: 20614 (code=exited, status=2)
journalctl -xn
-- Logs begin at Thu 2014-03-06 17:45:00 CST, end at Mon 2014-05-12 15:25:19 CST. --
May 12 15:09:10 wangchong-work org.a11y.atspi.Registry[15916]: ** (at-spi2-registryd:15919): WARNING **: Unable to register client with session manager
May 12 15:09:13 wangchong-work org.freedesktop.thumbnails.Thumbnailer1[15877]: (tumblerd:15949): tumbler-WARNING **: Failed to load plugin "tumbler-poppler-thumbnailer.so": libpoppler-glib.so.8: cannot open shared object file: No such file or directory
May 12 15:09:13 wangchong-work org.freedesktop.thumbnails.Thumbnailer1[15877]: (tumblerd:15949): tumbler-WARNING **: Failed to load plugin "tumbler-ffmpeg-thumbnailer.so": libffmpegthumbnailer.so.4: cannot open shared object file: No such file or directory
May 12 15:09:13 wangchong-work org.freedesktop.thumbnails.Thumbnailer1[15877]: (tumblerd:15949): tumbler-WARNING **: Failed to load plugin "tumbler-raw-thumbnailer.so": libopenrawgnome.so.1: cannot open shared object file: No such file or directory
May 12 15:09:13 wangchong-work org.freedesktop.thumbnails.Thumbnailer1[15877]: (tumblerd:15949): tumbler-WARNING **: Failed to load plugin "tumbler-odf-thumbnailer.so": libgsf-1.so.114: cannot open shared object file: No such file or directory
May 12 15:09:14 wangchong-work org.gtk.Private.UDisks2VolumeMonitor[15877]: libbluray/bdnav/index_parse.c:162: indx_parse(): error opening /home/wangchong/FILES/BDMV/index.bdmv
May 12 15:09:14 wangchong-work org.gtk.Private.UDisks2VolumeMonitor[15877]: libbluray/bdnav/index_parse.c:162: indx_parse(): error opening /home/wangchong/FILES/BDMV/BACKUP/index.bdmv
May 12 15:09:14 wangchong-work org.gtk.Private.UDisks2VolumeMonitor[15877]: libbluray/bdnav/index_parse.c:162: indx_parse(): error opening /home/wangchong/TEMP/BDMV/index.bdmv
May 12 15:09:14 wangchong-work org.gtk.Private.UDisks2VolumeMonitor[15877]: libbluray/bdnav/index_parse.c:162: indx_parse(): error opening /home/wangchong/TEMP/BDMV/BACKUP/index.bdmv
May 12 15:25:19 wangchong-work org.gtk.vfs.Daemon[15877]: ** (process:16065): WARNING **: send_done_cb: No such interface 'org.gtk.vfs.Enumerator' on object at path /org/gtk/vfs/client/enumerator/1 (g-dbus-error-quark, 19)
I seached this bbs and found several similar problem and they all have something to do with /etc/group file, but I don't have any clue that my problem is also caused by the file. Here's the file:
root:x:0:root
bin:x:1:root,bin,daemon
daemon:x:2:root,bin,daemon
sys:x:3:root,bin
adm:x:4:root,daemon
tty:x:5:
disk:x:6:root
lp:x:7:daemon
mem:x:8:
kmem:x:9:
wheel:x:10:root
ftp:x:11:
mail:x:12:
uucp:x:14:
log:x:19:root
utmp:x:20:
locate:x:21:
rfkill:x:24:
smmsp:x:25:
http:x:33:
games:x:50:
lock:x:54:
uuidd:x:68:
dbus:x:81:
network:x:90:
video:x:91:
audio:x:92:
optical:x:93:
floppy:x:94:
storage:x:95:
scanner:x:96:
power:x:98:
nobody:x:99:
users:x:100:
systemd-journal:x:190:
polkitd:x:102:
avahi:x:84:
gdm:x:120:
wangchong:x:1000:
vboxusers:x:108:wangchong
transmission:x:169:
git:x:999:
sagemath:x:998:
colord:x:124:
mysql:x:89:
Last edited by wangchong (2014-05-12 10:09:29)

I used to be affected by this as well. But you should run
systemctl status shadow.service
as root. That will give is exactly why it failed. It could be missing lines in /etc/passwd or missing home directory's / shells etc etc.

[SOLVED] Unable to hibernate (and garbles the screen when it fails)

Hello, I'm unable to hibernate (but I can suspend fine).
When I run
sudo systemctl hibernate
it will run the command, turn off the screen and come back all garbled (like static from a tv), with the computer still on but the processes stopped.
I followed all the instructions on the hibernation wiki.
I rebuilt grub adding the swap partition and added the resume hook to mkinitcpio.
My swap partition is 23.4GB and my ram is 16gb, so that shouldn't be an issue.
I've had a look at my xorg logs, run systemctl --all | grep errors with nothing, and nothing came up from the system journal ( I forgot the command as it was deleted from my bash history).
What other logs can I provide to help determine the error?
Thanks
edit:
It's been solved now, I believe an update to the kernel has done the trick. I can suspend to disk fine now.
For those googling, I'm running 3.11.6-1-ARCH
Last edited by lugubrious (2013-11-13 00:21:27)

Still nothing unfortunately.
I masked alsa90 under /etc/pm/sleep.d to be -x. That was the only file out of the pm directories. (I only have it for KDE too).
I've also double checked my grub config to add resume, and mkinitcpio which has the resume hook.
This is the relevant part of journalctl, this is when I run sudo systemlctl hibernate
Oct 16 15:36:08 arch64 sudo[2228]: lugub : TTY=pts/0 ; PWD=/home/lugub ; USER=root ; COMMAND=/usr/bin/systemctl hibernate
Oct 16 15:36:08 arch64 sudo[2228]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 16 15:36:08 arch64 systemd[1]: Cannot add dependency job for unit xscreensaver.service, ignoring: Unit xscreensaver.service failed to load: No such file or directory.
Oct 16 15:36:08 arch64 systemd[1]: Starting Sleep.
Oct 16 15:36:08 arch64 systemd[1]: Reached target Sleep.
Oct 16 15:36:08 arch64 systemd[1]: Starting Hibernate...
Oct 16 15:36:08 arch64 kernel: PM: Hibernation mode set to 'platform'
Oct 16 15:36:08 arch64 systemd-sleep[2231]: Suspending system...
Oct 16 15:36:08 arch64 slim[340]: (II) AIGLX: Suspending AIGLX clients for VT switch
Oct 16 15:36:08 arch64 kernel: PM: Marking nosave pages: [mem 0x00092000-0x000fffff]
Oct 16 15:36:08 arch64 kernel: PM: Marking nosave pages: [mem 0xcfda0000-0xffffffff]
Oct 16 15:36:08 arch64 kernel: PM: Marking nosave pages: [mem 0xc4000000-0xc7ffffff]
Oct 16 15:36:08 arch64 kernel: PM: Basic memory bitmaps created
The error with xscreensaver service comes up when I sleep, (and run xscreensaver lock && suspend), but I can sleep fine with it.
Oct 16 15:57:07 arch64 systemd[1]: Cannot add dependency job for unit xscreensaver.service, ignoring: Unit xscreensaver.service failed to load: No such file or directory.
Oct 16 15:57:07 arch64 systemd[1]: Starting Sleep.
Oct 16 15:57:07 arch64 systemd[1]: Reached target Sleep.
Oct 16 15:57:07 arch64 systemd[1]: Starting Suspend...
Oct 16 15:57:07 arch64 systemd-sleep[559]: Suspending system...
Oct 16 15:57:07 arch64 kernel: PM: Syncing filesystems ... done.
Oct 16 15:57:07 arch64 kernel: PM: Preparing system for mem sleep
Oct 16 15:57:08 arch64 slim[341]: (II) AIGLX: Suspending AIGLX clients for VT switch
Oct 16 15:57:17 arch64 kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Oct 16 15:57:17 arch64 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Oct 16 15:57:17 arch64 systemd[1]: Time has been changed
Oct 16 15:57:17 arch64 systemd[446]: Time has been changed
Oct 16 15:57:17 arch64 systemd-sleep[559]: System resumed.
When I ran pm-hibernate as suggested above it didn't suspend either, but this came up on journalctl
Oct 16 14:37:03 arch64 kernel: PM: Cannot find swap device, try swapon -a.
Oct 16 14:37:03 arch64 kernel: PM: Cannot get swap writer
Any ideas? Thanks
Last edited by lugubrious (2013-10-16 03:28:19)

[SOLVED]sensord.service fails to start

Hi there!
I made a clean Arch install a couple of days ago and I've had problems trying to get sensord to work apropriately. I've went through the troubleshooting of this particular service and googled a lot the last couple of days about this topic but I found nothing really useful (or nothing that I could really understand. Maybe my search terms are not so effective ).
# systemctl status sensord -l
[sudo] password for daniel:
● sensord.service - Log hardware monitoring data
Loaded: loaded (/usr/lib/systemd/system/sensord.service; enabled)
Active: failed (Result: exit-code) since mié 2014-09-03 09:14:04 CLT; 7min ago
Process: 4231 ExecStart=/usr/sbin/sensord -i $INTERVAL -l $LOG_INTERVAL -f daemon (code=exited, status=127)
sep 03 09:14:04 Ophiel sensord[4231]: /usr/sbin/sensord: error while loading shared libraries: librrd.so.4: cannot open shared object file: No such file or directory
sep 03 09:14:04 Ophiel systemd[1]: sensord.service: control process exited, code=exited status=127
sep 03 09:14:04 Ophiel systemd[1]: Failed to start Log hardware monitoring data.
sep 03 09:14:04 Ophiel systemd[1]: Unit sensord.service entered failed state.
This is just a minor annoyance. My system performs great and I have no issues with it. It just annoys the heck out of me to see a service failing in my start up screen.
I don't know if hardware specs or other logs are useful. But if you need more info, just let me know
Thanks in advance.
Last edited by Silex89 (2014-09-03 14:16:15)

Silex89 wrote:My system performs great and I have no issues with it
Hmmm ...
Silex89 wrote:This thread is SOLVED.
Really ? Maybe there are services working but unrequested, have a look here:
https://bbs.archlinux.org/viewtopic.php?id=186244
I thought, that you explicitly installed sensord. Do you need a round robin database to visualize graphically your measured values in Nagios e.g. ?
Last edited by midixinga (2014-09-03 18:06:06)

[Solved] Mismatch on GID and shadow.service fails

Similar Messages

Maybe you are looking for