[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

Similar Messages

[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)

[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

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

[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]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] systemd : services failing to start on boot

I have removed sysvinit completely as per the systemd wiki pages.
I don't usually re-boot very often so I'm not sure exactly when the problem started.
I only noticed this problem about 4 or 5 days ago.
But now whenever I reboot my machine 2 services fail consistently.
adsl.service
colord.service
They both start flawlessly once I can log in at a console.
I'm using kde and in the last couple of days, while trying to fix my problem, the kdm service has failed to start a couple of times too - saying there is no X server.
Before switching to systemd I never had any of these problems using the old rc.conf method. My DAEMONS array had the adsl service start after the network service.
I need some help and advice to find out what is causing the problem and how to fix it.
Last edited by bhrgunatha (2012-10-25 05:44:22)

Thanks. That seems plausible. So I've been snooping at the journal.
journalctl -ab
Oct 25 17:06:13 starch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
Oct 25 17:06:14 starch systemd[1]: Started Recreate Volatile Files and Directories.
Oct 25 17:06:14 starch systemd[1]: Starting System Initialization.
Oct 25 17:06:14 starch systemd[1]: Reached target System Initialization.
Oct 25 17:06:14 starch systemd[1]: Starting CUPS Printing Service Sockets.
Oct 25 17:06:14 starch systemd[1]: Listening on CUPS Printing Service Sockets.
Oct 25 17:06:14 starch systemd[1]: Starting Console System Startup Logging...
Oct 25 17:06:14 starch systemd[1]: Starting Restore Sound Card State...
Oct 25 17:06:14 starch systemd[1]: Starting CUPS Printer Service Spool.
Oct 25 17:06:14 starch systemd[1]: Started CUPS Printer Service Spool.
Oct 25 17:06:14 starch systemd[1]: Starting D-Bus System Message Bus Socket.
Oct 25 17:06:16 starch ntpd[381]: ntpd [email protected] Tue Aug 21 15:06:24 UTC 2012 (1)
Oct 25 17:06:16 starch ntpd[413]: proto: precision = 0.156 usec
Oct 25 17:06:17 starch ntpd[413]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Oct 25 17:06:17 starch ntpd[413]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Oct 25 17:06:18 starch ntpd[413]: Listen and drop on 1 v6wildcard :: UDP 123
Oct 25 17:06:18 starch ntpd[413]: Listen normally on 2 lo 127.0.0.1 UDP 123
Oct 25 17:06:18 starch ntpd[413]: Listen normally on 3 lo ::1 UDP 123
Oct 25 17:06:18 starch ntpd[413]: peers refreshed
Oct 25 17:06:18 starch ntpd[413]: Listening on routing socket on fd #20 for interface updates
Oct 25 17:06:18 starch dbus[384]: [system] Activating systemd to hand-off: service name='org.freedesktop.ColorManager' unit='colord.service'
Oct 25 17:06:18 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.systemd1'
Oct 25 17:07:03 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Oct 25 17:07:03 starch dbus[384]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Oct 25 17:07:03 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link down
Oct 25 17:07:03 starch systemd[1]: Starting Manage, Install and Generate Color Profiles...
Oct 25 17:07:03 starch systemd[1]: Started Manage, Install and Generate Color Profiles.
Oct 25 17:07:03 starch systemd[1]: colord.service: main process exited, code=killed, status=6
Oct 25 17:07:03 starch systemd[1]: Unit colord.service entered failed state.
Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link down
Oct 25 17:07:04 starch kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct 25 17:07:04 starch kernel: PPP generic driver version 2.4.2
Oct 25 17:07:04 starch cupsd[380]: Unknown directive DefaultAuthType on line 26.
Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link up
Oct 25 17:07:04 starch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 25 17:07:04 starch pppoe-start[382]: TIMED OUT
Oct 25 17:07:04 starch kernel: NET: Registered protocol family 24
Oct 25 17:07:04 starch pppoe-start[382]: /usr/sbin/pppoe-start: line 193: 394 Terminated $CONNECT "$@" > /dev/null 2>&1
That seems to confirm your theory.
eth0 link is not up when attempting to start colord and adsl
So the $64,000 question:
How do I defer them until eth0 is ready?
Or how can I force the eth0 link to be up before colord or adsl try to use it?
Last edited by bhrgunatha (2012-10-25 01:33:36)

[Solved] mpd.service fails to start

hello, i've switched to arch recently,
love it so far.
I've been trying to start mpd, with no success :
systemctl status mpd.service
mpd.service - Music Player Daemon
Loaded: loaded (/usr/lib/systemd/system/mpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2015-02-21 12:52:02 CET; 3s ago
Process: 1924 ExecStart=/usr/bin/mpd --no-daemon (code=exited, status=1/FAILURE)
Main PID: 1924 (code=exited, status=1/FAILURE)
I cant really see what goes wrong, I get no error message on "systemctl start mpd.service", and I dont see anything in "journalctl" :
Feb 21 12:30:42 SGC cantata[1694]: libpng warning: iCCP: known incorrect sRGB profile
Feb 21 12:30:42 SGC cantata[1694]: libpng warning: iCCP: known incorrect sRGB profile
Feb 21 12:30:42 SGC cantata[1694]: QStringList Solid::Backends::UDisks::UDisksManager::allDevicesInternal() error: "org.freedesktop.DBus.Error.ServiceUnknown"
Feb 21 12:35:01 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:35:01 SGC baloo_file[507]: Normal
Feb 21 12:35:44 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:35:44 SGC baloo_file[507]: Normal
Feb 21 12:36:50 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:36:50 SGC baloo_file[507]: Normal
Feb 21 12:39:45 SGC konsole[659]: org.kde.kurlfilter-ikws: "d2a291c6bf4fad8aaf7442433364ab6bfb2eecd969885543bfd1e4071db8633b"
Feb 21 12:40:26 SGC konsole[659]: org.kde.kurlfilter-ikws: "d2a291c6bf4fad8aaf7442433364ab6bfb2eecd969885543bfd1e4071db8633b"
Feb 21 12:42:48 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:42:48 SGC baloo_file[507]: Normal
Feb 21 12:43:43 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:43:43 SGC baloo_file[507]: Normal
Feb 21 12:43:52 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:43:52 SGC baloo_file[507]: Normal
Feb 21 12:45:45 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:45:45 SGC baloo_file[507]: Normal
Feb 21 12:45:48 SGC konsole[659]: org.kde.kurlfilter-ikws: "systemctl status mpd.service ● mpd.service - Music Player Daemon Loaded: loaded (/usr/lib/systemd/system/mpd.serv
Feb 21 12:45:56 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:45:56 SGC baloo_file[507]: Normal
Feb 21 12:46:07 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:46:07 SGC baloo_file[507]: Normal
Feb 21 12:48:52 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:48:52 SGC baloo_file[507]: Normal
Feb 21 12:49:07 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:49:07 SGC baloo_file[507]: Normal
Feb 21 12:49:40 SGC konsole[659]: org.kde.kurlfilter-ikws: "Feb 21 12:45:56 SGC baloo_file[507]: Normal Feb 21 12:46:07 SGC baloo_file[507]: "/home/demo/.xsession-errors" Fe
Feb 21 12:49:44 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:49:44 SGC baloo_file[507]: Normal
Feb 21 12:50:04 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:50:04 SGC baloo_file[507]: Normal
Feb 21 12:50:28 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:50:28 SGC baloo_file[507]: Normal
Feb 21 12:51:00 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:51:00 SGC baloo_file[507]: Normal
Feb 21 12:53:49 SGC konsole[659]: org.kde.kurlfilter-ikws: "Feb 21 12:14:12 SGC kded5[480]: kf5.kservice.sycoca: Trying to open ksycoca from "/home/demo/.cache/ksycoca5" Feb
Feb 21 12:54:03 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:54:03 SGC baloo_file[507]: Normal
Feb 21 12:54:56 SGC konsole[659]: org.kde.kurlfilter-ikws: "systemctl status mpd.service ● mpd.service - Music Player Daemon Loaded: loaded (/usr/lib/systemd/system/mpd.serv
Feb 21 12:55:01 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:55:01 SGC baloo_file[507]: Normal
Feb 21 12:55:17 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:55:17 SGC baloo_file[507]: Normal
Feb 21 12:55:36 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:55:36 SGC baloo_file[507]: Normal
Feb 21 12:55:48 SGC baloo_file[507]: "/home/demo/.xsession-errors"
Feb 21 12:55:48 SGC baloo_file[507]: Normal
Here's my /etc/mpd.conf :
# See: /usr/share/doc/mpd/mpdconf.example
music_directory "~/Music"
playlist_directory "~/.mpd/playlists"
db_file "~/.mpd/mpd.db"
log_file "~/.mpd/mpd.log"
pid_file "~/.mpd/mpd.pid"
state_file "~/.mpd/mpdstate"
bind_to_address "127.0.0.1"
port "6600"
audio_output {
type "alsa"
name "Output"
#pid_file "/run/mpd/mpd.pid"
#db_file "/var/lib/mpd/mpd.db"
#state_file "/var/lib/mpd/mpdstate"
#playlist_directory "/var/lib/mpd/playlists"
Thanks in advance,
Last edited by demo (2015-02-21 13:14:00)

Raynman wrote:
Spider.007 wrote:Mpd runs as a system service
In this case the system service is indeed the one that failed, but mpd also provides a user service file and all the paths in demo's /etc/mpd.conf (even though that is the default config for the system service) seem to indicate a user service might be more appropriate.
Indeed, I've made the appropriate change to run it as user service
(put my mdp.conf in ~/.mpd, and add "mpd ~/.mpd/mpd.conf" to my home ".profile")
Last edited by demo (2015-02-21 13:13:41)

[solved] mpd service fails

So I'm trying to run mpd globaly (prefer to run it as seperate user) and it keeps failing (listed as failed in the list of daemons produced by systemctl) I checked and rechecked the file permessions and it seems like everything is correct so I figured maybe I made mistake in the config or maybe it's something else
my config
# See: /usr/share/doc/mpd/mpdconf.example
user "mpd"
pid_file "/run/mpd/mpd.pid"
db_file "/var/lib/mpd/mpd.db"
state_file "/var/lib/mpd/mpdstate"
playlist_directory "/var/lib/mpd/playlists"
music_directory "/multimedia/Music"
log_file "/var/lib/mpd/log"
sticker_file "/var/lib/mpd/sticker.sql"
mixer_type "software"
restore_paused "yes"
auto_update "yes"
audio_outpot {
type "pulse"
name "Local Music Player Daemon"
server "127.0.0.1"
BTW I've got a couple of unrelated issues should I mention them in the same thread or is it OK to start a thread for each seperately?
Last edited by nashod (2014-10-15 22:19:20)

bstaletic wrote:Take a look at "audio_outpot {" line. You have a typo.
Thank you! I can't believe I missed that *run away in shame*

[Solved] kdm.service fails to start X with systemd 185-4

Hello
After updating systemd yesterday to 185-4 and booting my pc in the morning I found out that either the boot stops in the middle giving me just black screen or it would throw me to console prompt after some time.
systemctl status kdm.service shows two errors
Jul 1 11:20:57 pc kdm[285]: X server startup timeout, terminating
Jul 1 11:21:08 pc kdm[285]: X server for display :0 cannot be started, session disabled
The same can be observed in logs. However, there are no errors in Xorg.0.log.
Moreover when I do
systemctl stop kdm.service
systemctl start kdm.service
kdm loads fine and I can login to kde.
I have temporarily reverted to 185-3 and the problem seems to be gone.
Does anybody experience a similar issue?
thanks
Last edited by aya (2012-07-02 14:05:53)

~ $ ls -l /etc/systemd/system/graphical.target.wants/kdm.service
lrwxrwxrwx 1 root root 35 мая 31 20:33 /etc/systemd/system/graphical.target.wants/kdm.service -> /usr/lib/systemd/system/kdm.service
~ $ cat /usr/lib/systemd/system/kdm.service
cat: /usr/lib/systemd/system/kdm.service: No such file or directory.
Also read - https://projects.archlinux.org/svntogit … 833ee7a0c8

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)

Systemd-remount-fs.service fails [SOLVED]

After a fresh install on a brandnew laptop, my root partition is being mounted read only, and I see that systemd-remount-fs.service fails:
[root@anton ~]# systemctl status systemd-remount-fs.service
systemd-remount-fs.service - Remount Root and Kernel File Systems
Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; static)
Active: failed (Result: exit-code) since Sat, 2012-12-01 21:00:05 MST; 18min ago
Docs: man:systemd-remount-fs.service(8)
Process: 186 ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/systemd-remount-fs.service
Dec 01 21:00:05 anton systemd-remount-fs[186]: mount: / not mounted or bad option
Dec 01 21:00:05 anton systemd-remount-fs[186]: In some cases useful info is found in syslog - try
Dec 01 21:00:05 anton systemd-remount-fs[186]: dmesg | tail or so
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
I have no idea why this is happening, or what to do to try and fix it - any help/advice would be greatly appreciated. Following is the information I think is necessary for assistance:
Note that I have /usr on a separate partition, which I suspect is possibly involved in the issue somehow.
Here's my fstab:
[root@anton ~]# cat /etc/fstab
# /dev/sda5
#UUID=a09ff37e-ce60-4173-b95a-4b71a53c01d3 / ext4 defaults,rw,noatime,discard,data=writeback 0 1
# /dev/sda6
UUID=f4ab3551-c4f8-4e77-97bb-cc754c81af24 /usr ext4 defaults,noatime,discard,data=writeback 0 0
# /dev/sda7
UUID=c8d2776b-faaa-4a9d-ad49-4b09489faaaa /var ext4 defaults,rw,noatime,discard 0 2
# /dev/sda8
UUID=3dff3fa5-3291-4227-907a-258f12e1b3cf /home ext4 defaults,rw,relatime,discard 0 2
Here's the relevant output from mount (note that my root (sda5) partition is not being mount with the options I specified in fstab):
[root@anton ~]# mount | grep sda
/dev/sda5 on / type ext4 (ro,relatime,data=ordered)
/dev/sda6 on /usr type ext4 (rw,noatime,discard,data=writeback)
/dev/sda7 on /var type ext4 (rw,noatime,discard,data=ordered)
/dev/sda8 on /home type ext4 (rw,relatime,discard,data=ordered)
Relavant snippet from /boot/grub/grub.cfg:
menuentry 'Arch GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-a09ff37e-ce60-4173-b95a-4b71a53c01d3' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 a09ff37e-ce60-4173-b95a-4b71a53c01d3
else
search --no-floppy --fs-uuid --set=root a09ff37e-ce60-4173-b95a-4b71a53c01d3
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=a09ff37e-ce60-4173-b95a-4b71a53c01d3 ro init=/usr/lib/systemd/systemd
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
Finally, here's my mkinitcpio.cfg:
[root@anton ~]# cat /etc/mkinitcpio.conf
MODULES=""
BINARIES=""
FILES=""
HOOKS="base udev autodetect sata filesystems usbinput usr fsck shutdown"
Last edited by corey_s (2012-12-02 08:57:35)

Thanks for the quick response, WonderWoofy ( by the way, great username! )!
When I removed or modified the the mount options in the bootloader kernel command line, there was no change to the status of the fs after boot-up. I had changed it at one point from 'ro', to 'rw'; but doing so had no affect on the output of the mount command.
However, I did finally identify the cause: turns out if I specify 'data=writeback', in fstab for the root partition, then systemd-remount-fs.service fails, as per my OP - leaving me with a 'ro'-mounted root filesystem. Simply removing that, or changing it to 'data=ordered', solved the issue: when I rebooted, the root partition was mounted as per my fstab config.
So, my fstab now looks like this:
# /dev/sda5
UUID=a09ff37e-ce60-4173-b95a-4b71a53c01d3 / ext4 rw,noatime,discard 0 1
# /dev/sda6
UUID=f4ab3551-c4f8-4e77-97bb-cc754c81af24 /usr ext4 defaults,ro,noatime,discard,data=writeback 0 0
# /dev/sda7
UUID=c8d2776b-faaa-4a9d-ad49-4b09489faaaa /var ext4 defaults,rw,noatime,discard 0 2
# /dev/sda8
UUID=3dff3fa5-3291-4227-907a-258f12e1b3cf /home ext4 defaults,rw,relatime,discard 0 2
... and all is now well.
I'll mark this as solved, but I'll also ask: why does specifying 'data=writeback' on my root partition cause the systemd-remount-fs.service to fail? Any experts out there know?
Last edited by corey_s (2012-12-02 06:46:32)

Ntp-once.service fails [solved]

I'm trying to set up the oneshot ntp time sync as described in the arch wiki https://wiki.archlinux.org/index.php/Ne … col_daemon
I believe I have /etc/ntp.conf configured correctly, because when I manually run
>sudo ntpd -gq
I get:
ntpd: time set -7.226927s
However, when I try to start the service, either enabled at boot or started manually afterwards, I get:
>sudo systemctl start ntp-once.service
Job for ntp-once.service failed. See 'systemctl status ntp-once.service' and 'journalctl -xn' for details.
The suggested links give:
>sudo systemctl status ntp-once.service
ntp-once.service - Network Time Service (once)
   Loaded: loaded (/etc/systemd/system/ntp-once.service; disabled)
   Active: failed (Result: exit-code) since Sat 2013-03-30 05:48:56 EDT; 2min 13s ago
   Process: 939 ExecStart=/usr/bin/ntpd -q -g -u ntp:ntp (code=exited, status=255)
Mar 30 05:48:55 arch ntpd[939]: Listen and drop on 1 v6wildcard :: UDP 123
Mar 30 05:48:55 arch ntpd[939]: Listen normally on 2 lo 127.0.0.1 UDP 123
Mar 30 05:48:55 arch ntpd[939]: Listen normally on 3 eth0 192.168.0.110 UDP 123
Mar 30 05:48:55 arch ntpd[939]: Listen normally on 4 lo ::1 UDP 123
Mar 30 05:48:55 arch ntpd[939]: Listen normally on 5 eth0 fe80::f66d:4ff:fe40:3c9b UDP 123
Mar 30 05:48:55 arch ntpd[939]: peers refreshed
Mar 30 05:48:55 arch ntpd[939]: Listening on routing socket on fd #22 for interface updates
Mar 30 05:48:56 arch systemd[1]: ntp-once.service: main process exited, code=exited, status=255/n/a
Mar 30 05:48:56 arch systemd[1]: Failed to start Network Time Service (once).
Mar 30 05:48:56 arch systemd[1]: Unit ntp-once.service entered failed state
>sudo journalctl -xn
-- Logs begin at Sun 2012-10-28 09:25:15 EDT, end at Sat 2013-03-30 05:53:07 EDT. --
Mar 30 05:48:55 arch ntpd[939]: Listening on routing socket on fd #22 for interface updates
Mar 30 05:48:56 arch systemd[1]: ntp-once.service: main process exited, code=exited, status=255/n/a
Mar 30 05:48:56 arch systemd[1]: Failed to start Network Time Service (once).
-- Subject: Unit ntp-once.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Documentation: http://www.freedesktop.org/wiki/Softwar … 8ba40df7e9
-- Unit ntp-once.service has failed.
-- The result is failed.
Mar 30 05:48:56 arch systemd[1]: Unit ntp-once.service entered failed state
Mar 30 05:48:56 arch sudo[936]: pam_unix(sudo:session): session closed for user root
Mar 30 05:51:10 arch sudo[941]: bp : TTY=pts/0 ; PWD=/home/bp ; USER=root ; COMMAND=/usr/bin/system
Mar 30 05:51:10 arch sudo[941]: pam_unix(sudo:session): session opened for user root by bp(uid=0)
Mar 30 05:51:10 arch sudo[941]: pam_unix(/etc/systemd/system/ntp-once.servicesudo:session): session closed for user root
Mar 30 05:53:07 arch sudo[946]: bp : TTY=pts/0 ; PWD=/home/bp ; USER=root ; COMMAND=/usr/bin/journa
Mar 30 05:53:07 arch sudo[946]: pam_unix(sudo:session): session opened for user root by bp(uid=0)
My /etc/systemd/system/ntp-once.service looks like this:
[Unit]
Description=Network Time Service (once)
After=network.target nss-lookup.target
[Service]
Type=oneshot
ExecStart=/usr/bin/ntpd -q -g -u ntp:ntp ; /sbin/hwclock -w
[Install]
WantedBy=multi-user.target
And my /etc/ntp.conf like this:
# Associate to public NTP pool servers; see http://www.pool.ntp.org/
server 0.north-america.pool.ntp.org iburst
server 1.north-america.pool.ntp.org iburst
server 2.north-america.pool.ntp.org iburst
server 3.north-america.pool.ntp.org iburst
# Only allow read-only access from localhost
restrict default noquery nopeer
restrict 127.0.0.1
restrict ::1
# Location of drift file
driftfile /var/lib/ntp/ntp.drift
logfile /var/log/ntp.log
Last edited by bpeary (2013-03-31 23:12:20)

Thanks for the suggestions. I tried breaking that line up into
ExecStart=/usr/bin/ntpd -q -g -u ntp:ntp
ExecStart=/sbin/hwclock -w
but got the same fail error. Then I thought about how it worked manually, and I had used ntpd -gq. I don't know what the ntp:ntp means, or the 'u', but decided to try it with the format that worked manually. So I put in:
ExecStart=/usr/bin/ntpd -qg ; /sbin/hwclock -w
and now it is working.

[solved] What makes systemd-logind.service fail?

After last update made yesterday I was unable to reboot. With the help of an installation cd and chrooting I disabled my graphical login manager lxdm which, when started, seems to do nothing and the system is stuck.
Without lxdm service enabled, I can start xfce4 with
startxfce4
from commandline and everything seems to run fine.
But the booting process gives me several messages telling that the service systemd-logind failed. Apart from the virtual console created while booting and the one running X11 there is no other one (no login prompt when pressing strg+alt f3 e.g.)
[root@amd64-archlinux ~]# systemctl status systemd-logind
● systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: failed (Result: start-limit) since Sun 2014-06-08 19:09:24 CEST; 5min ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/logind
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Process: 336 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
Main PID: 336 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
Jun 08 19:09:24 amd64-archlinux systemd[1]: Failed to start Login Service.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Unit systemd-logind.service entered failed state.
Jun 08 19:09:24 amd64-archlinux systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Stopping Login Service...
Jun 08 19:09:24 amd64-archlinux systemd[1]: Starting Login Service...
Jun 08 19:09:24 amd64-archlinux systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Failed to start Login Service.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Unit systemd-logind.service entered failed state.
Has anyone an idea where to lead me?
Last edited by bernd_b (2014-06-09 11:20:21)

I don't know if I got you point - but here is a try:
I am running X11 started manually with "startxfce4". So firing up a konsole in X11 I do and get
root@amd64-archlinux pkg]# systemctl stop systemd-logind
[root@amd64-archlinux pkg]# systemctl start systemd-logind
Job for systemd-logind.service failed. See 'systemctl status systemd-logind.service' and 'journalctl -xn' for details.
journalctl -xn:
-- Unit systemd-logind.service has begun shutting down.
Jun 08 21:38:18 amd64-archlinux systemd[1]: Starting Login Service...
-- Subject: Unit systemd-logind.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-logind.service has begun starting up.
Jun 08 21:38:18 amd64-archlinux systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start.
Jun 08 21:38:18 amd64-archlinux systemd[1]: Failed to start Login Service.
-- Subject: Unit systemd-logind.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-logind.service has failed.
-- The result is failed.
I ran the service directly I get:
[root@amd64-archlinux pkg]# /usr/lib/systemd/systemd-logind
Failed to connect to system bus: No such file or directory
Failed to fully start up daemon: No such file or directory
What I figured out so far is this in addition:
- krusader does not start- there is no response or message in the konsole when firing up this application.
- I can only mount nfs-shares with the option "-o nolock" otherwise I get, e.g.
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
Last edited by bernd_b (2014-06-08 19:48:43)

[SOLVED] shadow.service fails

Similar Messages

Maybe you are looking for