[SOLVED] Systemd - console-kit-log-system-start.service FAILED

Hi!
i'm using systemd, and i removed initscripts and sysvinit.
I've now noticed this error, it seems that service failed to load.
By the way, i can systemctl restart it, and then it will be active and running. So, where is the problem? I found this, that seems to be my same problem, but it is 2 years old! https://bugzilla.redhat.com/show_bug.cgi?id=632714 .
Any idea?
thanks!
Last edited by nierro (2012-07-31 18:59:21)

Looking into the issue, i can't find a solution...
so, here there are :
systemctl status console-kit-log-system-start.service
console-kit-log-system-start.service - Console System Startup Logging
Loaded: loaded (/usr/lib/systemd/system/console-kit-log-system-start.service; static)
Active: failed (Result: exit-code) since Tue, 03 Jul 2012 09:34:45 +0200; 1 day and 3h ago
Process: 175 ExecStart=/usr/sbin/ck-log-system-start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/console-kit-log-system-start.service
and
journalctl -a | grep console-kit-log
Jul 03 09:34:45 arch systemd[1]: console-kit-log-system-start.service: main process exited, code=exited, status=1
Jul 03 09:34:45 arch systemd[1]: Unit console-kit-log-system-start.service entered failed state.
Any idea?
EDIT:as i said, i can restart it, without any sort of problem, so i guess the issue is related to the deps of this service (After=...). I left it untouched, never modified this service...
Last edited by nierro (2012-07-04 12:11:10)

Similar Messages

Error: missing ck-log-system-start file

Hi,
I'm on a fully updated Arch_X86-64/KDE system that works fine.
I occasionally check by boot log (journalctl -b) , and found the following error:
Failed at step EXEC spawning /usr/sbin/ck-log-system-start: No such file or directory
As said, my system works fine.
Should I fix it?
If Y, by creating the missing file (using touch) or otherwise.
Please advise!
Thnaks

Thanks Karol,
Here's the requested output:
# systemctl status ck-log-system-start
ck-log-system-start.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
As indicated by the following console-kit isn't running either.
# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
console-kit-daemon.service loaded failed failed Console Manager
console-kit-log-system-start.service loaded failed failed Console System Startup Logging

[Not solved]systemd-tmpfiles stat(/run/user/myuser/gvfs) failed: Perm

I get this error message since a couple of days and systemd-tmpfiles service is slow to start compared to before. I have no arch-units/initscripts anymore. I update everyday but I can see no updates that sticks out in pacman-log, on the day before this failure appeared. (systemd-tools was updated 3 days before this error)
Permissions;
/run/user
drwxr-xr-x 3 root root 60 7 jun 10.51 .
drwxr-xr-x 11 root root 340 7 jun 10.51 ..
drwx------ 3 myuser myuser 80 7 jun 10.51 myuser
/run/user/myuser
drwx------ 3 myuser myuser 80 7 jun 10.51 .
drwxr-xr-x 3 root root 60 7 jun 10.51 ..
dr-x------ 2 myuser myuser 0 7 jun 10.51 gvfs
lrwxrwxrwx 1 root root 17 7 jun 10.51 X11-display -> /tmp/.X11-unix/X0
/run/user/myuser/gvfs
dr-x------ 2 myuser myuser 0 7 jun 10.51 .
drwx------ 3 myuser myuser 80 7 jun 10.51 ..
EDIT: Now I've look at the files;
/usr/lib/tmpfiles.d
totalt 160K
drwxr-xr-x 2 root root 4,0K 2 jun 15.54 .
drwxr-xr-x 167 root root 128K 7 jun 07.34 ..
-rw-r--r-- 1 root root 30 1 jun 02.28 console.conf
-rw-r--r-- 1 root root 29 27 maj 06.29 consolekit.conf
-rw-r--r-- 1 root root 719 1 jun 02.28 legacy.conf
-rw-r--r-- 1 root root 729 1 jun 02.28 systemd.conf
-rw-r--r-- 1 root root 449 1 jun 02.28 tmp.conf
-rw-r--r-- 1 root root 622 1 jun 02.28 x11.conf
And the only thing possibly close is; d /run/user 0755 root root 10d
from systemd.conf.
Last edited by swanson (2012-06-08 07:20:28)

Nope, error still there and no clue what's happening. It occurs without me trying to mount anything, no usb's, no phones and no disks.

System Start Up Fails Windows 7

HELP!!!! Please anyone out there it's my laptop when I turn it on it goes as far as the Windows Logo and then just a blank screen. I have my System Recovery CD and also my Boot Manager CD so I have installed both and still nothing.

Hi,
Shut down the notebook. Tap away at f10 as you start the notebook to enter the bios menu. Under the Advanced or Diagnostic tab you should find the facility to run tests on both the Hard Drive and Memory. Post back with the details of any error messages.
Regards,
DP-K
****Click the White thumb to say thanks****
****Please mark Accept As Solution if it solves your problem****
****I don't work for HP****
Microsoft MVP - Windows Experience

Error source CAPI2 id 513 - Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object

Running Windows 8.1 PRO RTM x64 upgraded from Win 8 PRO. Updates to 8.1 as of 17 October installed
Event viewer still shows newly triggered Error(s) CAPI2 event id 513.
I can trigger this error by manually creating a restore point invoking VSS.
The VSS System Writer is listed and is error free.
Log Name:      Application
Source:        Microsoft-Windows-CAPI2
Date:          17/10/2013 20:32:19
Event ID:      513
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Machine -Name
Description:
Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.
Details:
AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol.
System Error:
Access is denied.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-CAPI2" Guid="{5bbca4a8-b209-48dc-a8c7-b23d3e5216fb}" EventSourceName="Microsoft-Windows-CAPI2" />
    <EventID Qualifiers="0">513</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2013-10-17T19:32:19.935384000Z" />
    <EventRecordID>89898</EventRecordID>
    <Correlation />
    <Execution ProcessID="1404" ThreadID="2104" />
    <Channel>Application</Channel>
    <Computer>Machine-Name</Computer>
    <Security />
</System>
<EventData>
    <Data>
Details:
AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol.
System Error:
Access is denied.
</Data>
</EventData>
</Event>

Thank you excellent post! I confirmed this fix worked for my situation as well. Below is more detailed post since it did not jump out for me the first time.
############################ Details ##############################
My operating system is Windows 8.1 after installing Visual Studio 2013 when Symantec System recover 2013 ran started seeing
the following errors in event logs.
################## Example event log errors #######################
Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.
Details:
AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol.
System Error:
Access is denied.
################## Example event log errors #######################
Note: Confirmed this fix resolved my issue.
Step 1. Download and unzip accesschk.exe to C:\Temp http://download.sysinternals.com/files/AccessChk.zip
Step 2. Run cmd.exe prompt as Administrator go to Temp directory
C:\>cd Temp
Step 3. Run accesschk.exe
C:\Temp>accesschk.exe -c mslldp
################# Example output 1 #################################
Accesschk v5.10 - Reports effective permissions for securable objects
Copyright (C) 2006-2012 Mark Russinovich
Sysinternals - www.sysinternals.com
mslldp
RW NT AUTHORITY\SYSTEM
RW BUILTIN\Administrators
RW S-1-5-32-549
R NT SERVICE\NlaSvc
################# Example output 1 #################################
Step 4. Run following command.
C:\Temp>SC sdshow MSLLDP <---- Example text 1.
################# Example output 2 #################################
D:(D;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BG)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SY)(A;;CCDCLCSWRPDTLOCRSDRCWDWO;;;BA)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SO)(A;;LCRPWP;;;S-1
-5-80-3141615172-2057878085-1754447212-2405740020-3916490453)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)
################# Example output 2 #################################
Step 5. Run following command.
C:\Temp>SC sdshow MUP
################# Example output 3 #################################
D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;IU)
(A;;CCLCSWLOCRRC;;;SU) ######## <--- Example text 2. Grab this value. #######
S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)
################# Example output 3 #################################
Step 6.
C:\Temp>
### Copy and past Example 1. line in notepad in command promt you can select all then copy the paste the text into notepad.
MSLLDP D:(D;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BG)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SY)(A;;CCDCLCSWRPDTLOCRSDRCWDWO;;;BA)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SO)(A;;LCRPWP;;;S-1-5-80-3141615172-2057878085-1754447212-2405740020-3916490453)
(A;;CCLCSWLOCRRC;;;SU) ######## <--- Insert Example text 2. here #######
S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)
Run this command. (Note: Make sure its all one line no wordwrap that the webpage could be showing this text.)
C:\Temp> sc sdset MSLLDP D:(D;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BG)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SY)(A;;CCDCLCSWRPDTLOCRSDRCWDWO;;;BA)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SO)(A;;LCRPWP;;;S-1-5-80-3141615172-2057878085-1754447212-2405740020-3916490453)(A;;CCLCSWLOCRRC;;;SU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)
Step 7.
##### Check the result #####
C:\Temp>accesschk.exe -c mslldp
################# Example output 4 #################################
Accesschk v5.10 - Reports effective permissions for securable objects
Copyright (C) 2006-2012 Mark Russinovich
Sysinternals - www.sysinternals.com
mslldp
RW NT AUTHORITY\SYSTEM
RW BUILTIN\Administrators
RW S-1-5-32-549
R NT SERVICE\NlaSvc
R NT AUTHORITY\SERVICE <--- You should now see this line.
################# Example output 4 #################################
Step 8.
Ran backup using Symantect System Recovery 2013 the event errors did not return after this fix. Great post again!
############################ Details ##############################

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

[SOLVED] systemd adsl service does not start

After the today's upgrade of my system I get lines like this in my journal, as the adsl service does not want to start.
# router systemd[522]: Failed at step EXEC spawning /usr/sbin/pppoe-start: No such file or directory
The problem is, that pppoe-start is in /usr/bin/ and not in /usr/sbin. According to pacman (pacman-Ql rp-pppoe) /usr/bin/ is the correct location.
I really don't know, why systemd is trying to launch it, because even the service file (/usr/lib/systemd/system/adsl.service) points to the correct location.
[Unit]
Description=ADSL Deamon
[Service]
Type=forking
ExecStart=/usr/bin/pppoe-start
ExecStop=/usr/bin/pppoe-stop
[Install]
WantedBy=multi-user.target
The service is launching and stopping with pppoe-start and pppoe-stop.
When launched, it also shuts down fine when stopping it by
systemctl stop adsl
Why the hell is it trying to launch from /usr/sbin/?
Last edited by scar (2013-06-04 13:07:23)

It goes definitely against any logic.
The service file looks good, but I've copied it to /usr/lib/systemd/system/bdsl.service. Same contents - and the new one launches succesfully.
I've deleted the original ...adsl.service file, verified that it disappeared, copied it back from the new bdsl.service file, and it still does not launch.
[EDIT]
I've erased the drive, restored the system from a 1 week old backup, started it - everything worked. Then I'v updated the whole system, including the rp-pppoe package, and the adsl service is failing again.
Downgrading solves the problem. Should I file a bug report?
Last edited by scar (2013-06-01 10:14:41)

[SOLVED] systemd service not starting

Hi,
Been using Arch for just over a week now moving from Ubuntu and loving it. Achieved so much more on Arch in this short time until this evening.
I am trying to run a shell script at startup. I added the service file under /etc/systemd/system/myapp.service
With the following content:
[Unit]
Description=Notification
[Service]
ExecStart=/usr/bin/myscript
[Install]
WantedBy=multi-user.target
As it is I can run "systemctl restart myapp.service" and the script execute flawlessly however on reboot it does nothing and I get this error when I run systemctl status myapp.service:
systemctl status myapp.service
myapp.service - Notification
Loaded: loaded (/etc/systemd/system/myapp.service; enabled)
Active: failed (Result: exit-code) since Thu 1970-01-01 10:00:08 EST; 14s ago
Process: 116 ExecStart=/usr/bin/myscript (code=exited, status=6)
Other info:
Script starts with #!/bin/sh
Script permissions 755
Tried adding After=network.target under unit.
Tried Type=oneshot and forking
O yes /var/log/messages.log | grep myapp
Sep 6 14:25:56 alarm systemd[1]: [/etc/systemd/system/myapp.service:1] Unknown section 'unit'. Ignoring.
Sep 6 14:25:56 alarm systemd[1]: [/etc/systemd/system/myapp.service:2] Assignment outside of section. Ignoring.
Jan 1 01:00:11 alarm systemd[1]: myapp.service: main process exited, code=exited, status=6/NOTCONFIGURED
Jan 1 01:00:11 alarm systemd[1]: Unit myapp.service entered failed state.
Jan 1 01:00:11 alarm [ 3.243318] systemd[1]: [/etc/systemd/system/myapp.service:1] Unknown section 'unit'. Ignoring.
Jan 1 01:00:11 alarm [ 3.243490] systemd[1]: [/etc/systemd/system/myapp.service:2] Assignment outside of section. Ignoring.
Only thing I dont get is the date difference? I have set the timezone correctly..
Any suggestions?
thanks
Last edited by blueteq (2013-09-10 10:01:11)

Reaching the network.target does not necessarily mean that an active connection has been reached. For example, if you use wicd or netctl-auto, it will report the stating of the service as successful after the daemon itself has started, but starting the daemon simply means that it is ready to start scanning for wireless networks and then connect.
If you want to be absolutely sure that there is a network connection before the service starts, you should use NetworkManager.service. That will also pull in the NetworkManager-wait-online.service which will not complete until a full connection has been reached. At that point the startup will have reached the network-online.target. So you should order the service after that instead. In reality, you should order it after that anyway, no matter what netowrk connection service you use, as that is a built in target to systemd.
Even though you have the RestartSec=35 and Restart=on-failure (which is a sane thing to do IMO), it is probably a good idea to order it After=netowrk-online.target anyway, as that will cause the service to start a bit later and at least attempt to order itself correctly. That way it will also ensure that the service is stopped before the network is taken down as well, hopefully ensuring a clean disconnect as well.

[SOLVED] systemd not alway starts dnsmasq and minidlna service

Hi!
After I've annoyed some of you (and hopefully helped others) with my threads on systemd I got systemd working. But; I still have one problem. Systemd seems to have trouble starting dnsmasq and minidlna.
dnsmasq.service loaded failed failed A lightweight DHCP and caching DNS server
[email protected] loaded active running Getty on tty1
httpd.service loaded active running Apache Web Server
logitechmediaserver.service loaded active running Logitech Media Server Daemon
lvm.service loaded active exited LVM activation
minidlna.service loaded failed failed minidlna server
Sometimes they do load, sometimes not. Is there a way to find out why a service could not be started?
btw
systemctl start minidlna dnsmasq
does start them perfectly
Last edited by theking2 (2012-12-13 18:50:35)

Yes, there is such a command systemctl status and it says
Dec 11 20:54:44 janus systemd[1]: Starting A lightweight DHCP and caching DNS server...
Dec 11 20:54:45 janus dnsmasq[308]: dnsmasq: syntax check OK.
Dec 11 20:54:45 janus dnsmasq[335]: dnsmasq: failed to create listening socket for 172.16.0.8: Cannot assign requested address
Dec 11 20:54:45 janus systemd[1]: dnsmasq.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Dec 11 20:54:45 janus systemd[1]: Failed to start A lightweight DHCP and caching DNS server.
Dec 11 20:54:45 janus systemd[1]: Unit dnsmasq.service entered failed state
and
minidlna.service - minidlna server
Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled)
Active: failed (Result: exit-code) since Tue, 2012-12-11 20:54:45 CET; 46s ago
Process: 303 ExecStart=/usr/sbin/minidlna -P /var/run/minidlna/minidlna.pid (code=exited, status=255)
CGroup: name=systemd:/system/minidlna.service

[solved] systemd services not starting at boot (or at all)

On my router, some systemd services fail to start at boot.
The services are :
adsl (pppoe connetction on the wan interface)
shorewall (funny again for a router)
logind (brings up only tty1, and not the others with a 'timeout' error)
adsl starts fine manually after booting up
the others don't work, I have to launch shorewall with the old sysvinit rc script (and it works)
I really don't know, what happened to logind...
Last edited by scar (2012-11-30 10:20:44)

cups: avahi client failed
adsl: timeout (ppp0 running on eth0, the service did not found eth0)
shorewall: did not work by the systemctl command, only with the old rc script
I'm not sure if there was an error with logind, but I've had only tty1, not all the others (I have not touched /etc/inittab)
since this was a very old install (but up to date), I've decided to reinstall the whole thing,
Everything works
(But reinstalling does not solve any problem, it erases the problems...)
Last edited by scar (2012-11-30 10:21:20)

Systemd and console-kit - "active = FALSE" how to fix it?

After an upgrade I have a small problem witch console-kit:
└─[21:24 wto,15 maj 12:$]→ ck-list-sessions
Session1:
unix-user = '1000'
realname = '(null)'
seat = 'Seat2'
session-type = ''
active = FALSE
x11-display = ':0'
x11-display-device = '/dev/tty2'
display-device = ''
remote-host-name = ''
is-local = FALSE
on-since = '2012-05-15T19:17:31.558072Z'
login-session-id = '4294967295'
I am using systemd and start the X server witch a deamon in it:
└─[21:36 wto,15 maj 12:$]→ cat /lib/systemd/system/xinit.service
[Unit]
Description=Direct login to X
Requires=dev-tty7.device
After=dev-tty7.device systemd-user-sessions.service
[Service]
ExecStart=/bin/su dragonn -l -c "/bin/bash --login -c startx"
[Install]
WantedBy=graphical.target
My .xinitrc looks:
└─[21:41 wto,15 maj 12:$]→ cat .xinitrc
#!/bin/sh
exec ck-launch-session dbus-launch wm-manager
Why is my console kit session "active = FALSE"?

dragonn wrote:Thanks for info, is there any way to fix it without using a login manager? I really don't need it - it will only slow down the boot process.
Not yet, but it seems to be the planned:
http://freedesktop.org/wiki/Software/sy … imizations (point 10 in the second list)
see also http://lists.freedesktop.org/archives/s … 04974.html
btw. I added a note about this in the wiki. I didn't want to remove it because there are a few people who don't use ConsoleKit anyway and won't care about this problem.

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

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)

[SOLVED]systemd-tmpfiles-setup.service failure

Hi guys,
I just reinstalled arch with the following partitions:
[root@arch_vinnom vinnom]# gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.0
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 625142448 sectors, 298.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): BD3CA679-FA08-4F60-9BAD-B845DE9FF7EB
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 625142414
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 4095 1024.0 KiB EF02 BIOS
2 4096 52432895 25.0 GiB 8300 ROOT
3 52432896 53481471 512.0 MiB 8300 BOOT
4 53481472 74452991 10.0 GiB 8300 TMP
5 74452992 95424511 10.0 GiB 8300 VAR
6 95424512 602935295 242.0 GiB 8300 HOME
7 602935296 625142414 10.6 GiB 8200 SWAP
The problem is that tmpfs is mounted at '/tmp' through '/usr/lib/systemd/system/tmp.mount'
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
[Unit]
Description=Temporary Directory
Documentation=man:hier(7)
Documentation=http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
ConditionPathIsSymbolicLink=!/tmp
DefaultDependencies=no
Conflicts=umount.target
Before=local-fs.target umount.target
[Mount]
What=tmpfs
Where=/tmp
Type=tmpfs
Options=mode=1777,strictatime
Because of this, I'm always getting:
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Dom 2015-05-03 03:29:58 BRT; 27min ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 278 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
Main PID: 278 (code=exited, status=1/FAILURE)
Then I tried to change '/tmp' to '/run/tmpfs', folder that I created for this, using tmpfs wiki as reference.
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
[Unit]
Description=Temporary Directory
Documentation=man:hier(7)
Documentation=http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
ConditionPathIsSymbolicLink=!/run/tmpfs
DefaultDependencies=no
Conflicts=umount.target
Before=local-fs.target umount.target
[Mount]
What=tmpfs
Where=/run/tmpfs
Type=tmpfs
Options=mode=1777,strictatime,nodev,nosuid,size=1536M
But the error persists. What I'm missing?
Last edited by vinnom (2015-05-03 16:51:38)

ooo wrote:Couldn't you just mask the tmp.mount service? (as mentioned in the wiki page you linked)
Then your /tmp partition would be mounted according to your fstab
Raynman wrote:
The tmp.mount generated from your fstab should override the tmp.mount in /usr/lib/systemd/system. You say
The problem is that tmpfs is mounted at '/tmp' through '/usr/lib/systemd/system/tmp.mount'
If that is true (could you show output of mount and your fstab?) that is worth investigating.
However, your original problem seems to be that systemd-tmpfiles-setup.service fails. If something is wrong with your mounts, that could be related, but it might very well be something else. Is there any more information in the journal to indicate why the service fails (maybe even mentioning a tmpfiles.d config file that is responsible)? Did you create any config files for tmpfiles.d yourself?
Sorry guys, I tried to be concise, but ended up that I didn't make myself clear.
My '/tmp' is mounting fine as it takes priority over systemd. In fact, what I wanted to say is that '/tmp' mounts fine, systemd tried to mount tmpfs at '/tmp' and fails and I want to point tmpfs to mount at '/run/tmpfs' which I created for this, but just editing '/usr/lib/systemd/system/tmp.mount' didn't solve.
As for journalctl, it repeats several times this message:
Mai 02 22:43:32 arch_vinnom systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
Mai 02 22:43:32 arch_vinnom systemd[1]: Failed to start Create Volatile Files and Directories.
Mai 02 22:43:32 arch_vinnom systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
Mai 02 22:43:32 arch_vinnom systemd[1]: systemd-tmpfiles-setup.service failed.
foutrelis wrote:
Depending on how your '/var' file system is created/mounted, you might need to enable ACL on it:
https://wiki.archlinux.org/index.php/Sy … rt_at_boot
hmm
I created my /var during arch installation, with mkfs.reiserfs.
Using
tune2fs -l /dev/sdXY | grep "Default mount options:"
To check if acl was already enabled, I got:
[root@arch_vinnom vinnom]# tune2fs -l /dev/sda5 | grep "Default mount options:"
tune2fs: Bad magic number in super-block while trying to open /dev/sda5
Couldn't find valid filesystem superblock.
Then I searched a bit and noted that reiserfs isn't compatible with acl =/
Last edited by vinnom (2015-05-03 15:12:18)

[SOLVED] Systemd - console-kit-log-system-start.service FAILED

Similar Messages

Maybe you are looking for