[SOLVED] systemd: autostart service last, at login screen

hi
I don't use X, so no .xinitrc, but I'd like to run a script after boot when it reaches the terminal login.
In particular, the script is a simple beep command to play a sound.
I tried this
[Unit]
Description=welcome
After=multi-user.target
[Service]
Type=oneshot
ExecStart=/usr/bin/beep -f 1000 -l 200 -n -f 1200 -l 200 -n -f 2000 -l 120
[Install]
but can't even enable it
any suggestions? thanks
Last edited by v43 (2014-01-19 13:50:56)

because of the empty [Install] section
EDIT:
I tried adding the regular WantedBy=multi-user.target in the [Install], and it works!!
but why? how can this service be required by the multi-user.target and also be called after it?
[Unit]
Description=welcome
After=multi-user.target
[Service]
Type=oneshot
ExecStart=/usr/bin/beep -f 1000 -l 200 -n -f 1200 -l 200 -n -f 2000 -l 120
[Install]
WantedBy=multi-user.target
Last edited by v43 (2014-01-19 13:49:31)

Similar Messages

[Solved] systemd-sysctl.service failed to set parameters from 99-sy...

$ cat /etc/sysctl.d/99-sysctl.conf
# Protection from the SYN flood attack.
net.ipv4.tcp_syncookies = 1
# Disable packet forwarding.
net.ipv4.ip_forward = 0
# Tweak those values to alter disk syncing and swap behavior.
vm.vfs_cache_pressure = 1000
vm.swappiness = 0
# USB Speed
vm.dirty_ratio = 5
vm.dirty_background_ratio = 3
# KDE
fs.inotify.max_user_watches = 524288
$ cat /proc/sys/vm/dirty_ratio
10
$ cat /proc/sys/vm/dirty_background_ratio
5
but
$ cat /proc/sys/vm/swappiness
0
$ cat /proc/sys/vm/vfs_cache_pressure
1000
Only restarting of systemd-systct.service helps.
$ sudo systemctl restart systemd-sysctl.service
$ cat /proc/sys/vm/dirty_ratio
5
$ cat /proc/sys/vm/dirty_background_ratio
3
what am i doing wrong?
Solved with - % sudo chmod -x /usr/lib/pm-utils/power.d/laptop-mode
Last edited by Perfect Gentleman (2013-09-20 00:34:44)

Perfect Gentleman wrote:Solved with - % sudo chmod -x /usr/lib/pm-utils/power.d/laptop-mode
A more permanent solution is to mask that file
mkdir -p /etc/pm/power.d
touch /etc/pm/power.d/laptop-mode
which will not get written on update or reinstall. (Not than an update to this package seems at all likely but just in case.)

[SOLVED] Systemd fluidsynth service tries to load / fluidsynth removed

I recently moved to a pure systemd configuration and have been trying to familiarise myself with it.
I subsequently noticed that I had fluidsynth installed, and a pacman -Qi said that it was installed as a dependency for another package, but that no other packages currently required it. So I removed it.
Now when I run systemctl --failed I get the following output:
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
fluidsynth.service loaded failed failed FluidSynth Daemon
I can stop the service without any errors, but disabling it results in this:
$ sudo systemctl disable fluidsynth.service
Failed to issue method call: No such file or directory
I'm not really sure what this means. It doesn't seem to be causing any problems, but I'd like to understand what's going on and get everything working as it should. Can anyone suggest what I should do?
Last edited by esuhl (2012-10-16 01:38:21)

Cheers. But I can't see one there:
$ sudo ls -al /etc/systemd/system
total 32
drwxr-xr-x 8 root root 4096 Oct 14 02:50 .
drwxr-xr-x 5 root root 4096 Oct 14 02:50 ..
drwxr-xr-x 2 root root 4096 Aug 30 20:13 getty.target.wants
drwxr-xr-x 2 root root 4096 Oct 12 20:13 local-fs.target.wants
drwxr-xr-x 2 root root 4096 Oct 14 02:50 multi-user.target.wants
drwxr-xr-x 2 root root 4096 Oct 9 05:01 printer.target.wants
drwxr-xr-x 2 root root 4096 Oct 9 05:01 sockets.target.wants
drwxr-xr-x 2 root root 4096 Oct 12 20:13 sysinit.target.wants
lrwxrwxrwx 1 root root 41 Oct 9 04:55 syslog.service -> /usr/lib/systemd/system/syslog-ng.service
Last edited by esuhl (2012-10-16 00:04:22)

[Solved] systemd-hostnamed.service broken in systemd 212?

Can someone confirm by checking
hostnamectl status
and
systemctl --failed
Thanks!
Last edited by gedgon (2014-04-03 20:30:03)

teateawhy wrote:Works for me.
Hmm, interesting. In v.212 systemd-hostnamed.service failing for me, and hostnamectl timing out. Works fine after downgrading.
Edit: Problem caused by wrong /var/tmp permission. Thanks, teateawhy.
Last edited by gedgon (2014-04-03 20:29:47)

[SOLVED]Systemd autostart conky

Hi guys, as a new Arch user I tried to play a bit with systemd to have it automatically start Conky after logon. When I try to start conky manually from the terminal it all works perfectly but when systemd needs to do it as a unit (service) it's not possible as Conky doesn't accept the rc file it's been given. It seems that the variable $HOME or %h is unknown to systemd. Below some details
Starting my 2 Conky files from the Gnome terminal is no problem:
conky -d -c $HOME/.Conky/ConkyToprc
conky -d -c $HOME/.Conky/ConkyLogrc
cat /etc/systemd/system/conky.service:
[Unit]
Description=Conky system monitor
Documentation=man:conky(1)
[Service]
Type=forking
ExecStart=/usr/bin/conky -d -c /home/viper/.Conky/ConkyToprc
[Install]
WantedBy=xinitrc.target
[root@Arch viper]# systemctl status conky.service
● conky.service - Conky system monitor
Loaded: loaded (/etc/systemd/system/conky.service; disabled)
Active: failed (Result: core-dump) since Fri 2014-05-16 18:39:51 CEST; 10min ago
Docs: man:conky(1)
Process: 4833 ExecStart=/usr/bin/conky -d -c /home/viper/.Conky/ConkyToprc (code=dumped, signal=ABRT)
May 16 18:39:51 Arch conky[4833]: Conky: $HOME environment variable doesn't exist
May 16 18:39:51 Arch conky[4833]: conky: malloc.c:2369: sysmalloc: Assertion `(old_top == (((mbinptr) (((char *) &((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct malloc_chunk, fd)))) && old_size == ...
May 16 18:39:51 Arch systemd-coredump[4834]: Process 4833 (conky) dumped core.
May 16 18:39:51 Arch systemd[1]: conky.service: control process exited, code=dumped status=6
May 16 18:39:51 Arch systemd[1]: Failed to start Conky system monitor.
May 16 18:39:51 Arch systemd[1]: Unit conky.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
So even after changing the systemd unit file to use the full path /home/viper/.Conky/ConkyToprc it's still not working. I think after changing $HOME or %h Conky did accept the config file but doesn't recognize the $HOME variable in the config file anymore. Or maybe I'm missing something here... And I'm not even trying to load the second conky file Anyone an idea as where I need to look? Any help is highly appreciated. Thank you in advance.
It seems to be a bit related to this: http://lists.freedesktop.org/archives/s … 06217.html
Last edited by DarkLite1 (2014-05-17 16:48:04)

Thank you everyone for your feedback, I really appreciate it Some things I would still like to clarify although I fully agree with your reasoning of not using systemd for my 'conky' idea here.
@ANOKNUSA: Yes you are right, systemd starts everything simultaneously at boot time. The way I did my test was to start the unit manually from the Gnome terminal after already being logged on to Gnome. So in my point of view the $HOME variable did already exist at that point and there was no need to wait for the X server... So in theory, it should've been able to get the job done.
@twelveeighty: So yes, I do believe you are right. systemd doesn't know $HOME at all.
Than my final question to have this solved for me. What is the best way to have 2 instances of Conky running with each it's own config file? I tried the following already, but it was unsuccessful:
cat /etc/profile.d/autostart.sh
Exec=/usr/sbin/conky -d -c /home/viper/.Conky/ConkyToprc
Exec=/usr/sbin/conky -d -c /home/viper/.Conky/ConkyLogrc
cat /usr/share/gnome/autostart/conky.desktop
[Desktop Entry]
Type=Application
Name=Conky
Comment=Start conky script
Exec=/usr/sbin/conky -d -c /home/viper/.Conky/ConkyToprc
Exec=/usr/sbin/conky -d -c /home/viper/.Conky/ConkyLogrc
OnlyShowIn=GNOME;
X-GNOME-Autostart-Phase=Application
When trying to follow the proposed solution found here https://wiki.archlinux.org/index.php/xinitrc there is no example file availble for .xinitrc in /etc/skel as suggested 'Copy the sample /etc/skel/.xinitrc file to your home directory' And if there was, how would the syntax be for 2 instances of Conky? Because when I read the Note it's not possible to add 2 lines of EXEC:
Note: Make sure to uncomment only one exec line, since that will be the last command run from the script; all the following lines will just be ignored. Do NOT attempt to background your WM by appending a `&` to the line.
/again: thanks for still helping me out and reading my jibber/jabber. I sometimes really feel like a noob here between all you pro's. But the only way of getting there is by falling and learning how to get up? Right Bruce?
Last edited by DarkLite1 (2014-05-17 16:18:43)

[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 user service and timer dbus error

I have installed arch recently and added a few of my own services, for example the acpi_call commands and such. Now I want to create a systemd service that runs every 5 minutes and execute a script.
I searched a lot and I found that I must use timers. I got the thing with the timers working, but because my script has to do with a specific user, I want it to run only every 5 minutes when i am logged in as that user.
I tried to put the files in /etc/systemd/users, .config/local/users and all the possibilities but everytime i want to enable it, it says dbus connection refused.
Can somebody please provide me a way to execute a systemd service every 5 minutes while I am logged in as a specific user?
I did follow the wiki and created a dbus service and all. Everything works on that side but i can't enable my user service.
thanks!
Last edited by nopemopes (2015-03-25 11:10:06)

jasonwryan wrote:
What errors are you getting? https://bbs.archlinux.org/viewtopic.php?id=57855
Not a Sysadmin issue, moving to NC...
sorry, didn't mean to be incomplete.
The error says "Failed to get D-Bus connection: Connection refused".
I did what the wiki said: Create the dbus files, enable them and such.
No i put my service files + timer in the places mentioned by the wiki but everytime i try to enable them, that error shows up.
systemctl status dbus gives me all good
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
Active: active (running) since ma 2015-03-23 19:39:24 CET; 1h 18min ago
Docs: man:dbus-daemon(1)
Main PID: 246 (dbus-daemon)
CGroup: /system.slice/dbus.service
└─246 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='...ervice'
mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1....ectory.
mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='...ervice'
mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1....ectory.
mrt 23 19:39:39 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
mrt 23 19:39:39 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
mrt 23 19:47:01 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
mrt 23 19:47:01 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
mrt 23 20:51:38 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
mrt 23 20:51:38 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
that's the log for dbus and these are my files:
drive_sync.service
[Unit]
Description=Drive sync
[Service]
Type=simple
ExecStart=drive_script.sh
drive_sync.timer
[Unit]
Description=Drive sync
[Service]
Type=simple
ExecStart=drive_script.sh
these files are located in ~/.config/systemd/user
Last edited by nopemopes (2015-03-23 20:00:55)

[solved] systemd dhcpcd service

Not sure what is failing with this output, a service file start dependency?
Mar 12 10:08:53 yrch systemd[1]: Timed out waiting for device sys-subsystem-net-devices-eth0.device.
Mar 12 10:08:53 yrch systemd[1]: Dependency failed for dhcpcd on eth0.
This is the dhcpcd service file
[root@yrch multi-user.target.wants]# cat dh*
[Unit]
Description=dhcpcd on %I
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
[Service]
Type=forking
PIDFile=/run/dhcpcd-%I.pid
ExecStart=/usr/sbin/dhcpcd -q -w %I
ExecStop=/usr/sbin/dhcpcd -x %I
[Install]
WantedBy=multi-user.target
Also running dhcpcd standalone fails first attempt, works correctly second attempt.
Last edited by ackt1c (2014-11-23 08:36:28)

Is your device eth0? The interface naming scheme has changed, it's no longet eth0, eth1 and so on, but udev gives names to devices based on the MAC address now. Unless you manually changed config files, you will have this new naming scheme in effect. Check with ip link.
Last edited by elkoraco (2013-03-13 09:18:50)

How to change the order of users in appearance of login screen?

Hello!
Because we often switch to a user,
which is listed last in login screen,
we want move them to the second place.
How to change the order of users in appearance of login screen?
Thank you for a tip
Erhy

The order users show up on the login screen is the way they are ordered under the
C:/Users directory. This is usually alphabetical, AFAIK there is no other way to change the order other than to change the username to something that starts with a letter that will be higher alphabetically.

Cannot start systemd-logind.service when booting.

The boot sequence had a logind.service fail, and then was stuck when trying to open the Gnome Display Manager. The output was:
Starting Login Service...
[FAILED] Failed to start Login Service.
See "systemctl status systemd-logind.service" for details.
Stopping Login Service...
[ OK ] Stopped Login Service.
Starting Login Service...
[FAILED] Failed to start Login Service.
See "systemctl status systemd-logind.service" for
Stopping Login Service...
[ OK ] Stopped Login Service.
Starting Login Service...
[FAILED] Failed to start Login Service.
See "systemctl status systemd-logind.service" for details.
[ OK ] Started dhcpd on enp4s0.
[ OK ] Reached target Network.
Starting Network Time Service...
[ OK ] Started Network Time Service.
[ OK ] Reached target Multi-User System.
[FAILED] Failed to start GNOME Display Manager.
See "systemctl status gdm.service" for details.
[ OK ] Reached target Graphical Interface.
I have disabled the gdm.service using an installation disk with chroot in order to login, and after the restart I tried `sudo systemctl status systemd-logind.service`. The output is:
● systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static; vendor preset: disabled)
Active: failed (Result: start-limit) since 月 2015-04-06 17:59:52 JST; 56s 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: 249 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
Main PID: 249 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
4月 06 17:59:52 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 06 17:59:52 masasin-arch systemd[1]: Stopping Login Service...
4月 06 17:59:52 masasin-arch systemd[1]: Starting Login Service...
4月 06 17:59:52 masasin-arch systemd[1]: start request repeated too quickly for systemd-logind.service
4月 06 17:59:52 masasin-arch systemd[1]: Failed to start Login Service.
4月 06 17:59:52 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 06 17:59:52 masasin-arch systemd[1]: systemd-logind.service failed.
At the moment, I cannot get into any graphical environments, but I do have access to the shell.
Let me know if you need more information.

I ran
journalctl -b -u systemd-logind
right after a reboot, and the output is as follows:
-- Logs begin at 水 2013-08-21 08:01:49 JST, end at 水 2015-04-08 18:26:45 JST. --
4月 08 18:26:14 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:14 masasin-arch systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
4月 08 18:26:14 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:14 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:14 masasin-arch systemd[1]: Unit systemd-logind.service failed.
4月 08 18:26:14 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 08 18:26:14 masasin-arch systemd[1]: Stopping Login Service...
4月 08 18:26:14 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
4月 08 18:26:15 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service failed.
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 08 18:26:15 masasin-arch systemd[1]: Stopping Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
4月 08 18:26:15 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service failed.
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 08 18:26:15 masasin-arch systemd[1]: Stopping Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:15 masasin-arch systemd-logind[257]: Failed to connect to system bus: No such file or directory
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
4月 08 18:26:15 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service failed.
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 08 18:26:15 masasin-arch systemd[1]: Stopping Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:15 masasin-arch systemd-logind[257]: Failed to connect to system bus: No such file or directory
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
4月 08 18:26:15 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service failed.
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 08 18:26:15 masasin-arch systemd[1]: Stopping Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: start request repeated too quickly for systemd-logind.service
4月 08 18:26:15 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service failed.

[SOLVED] Trouble with running systemd user service on login

I'm trying to get emacs to run as a systemd/user service so that it will start up faster, as suggested in the wiki article, but I'm having some problems.
I can't get the service to run as soon as I log in. I can run the service with
systemctl --user start emacs
and it will run for the rest of my session, but if I try to run
systemctl --user enable emacs
I get the following error:
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
I ran
systemctl --user is-enabled emacs
and that returned
static
but I'm not sure what that means. Any help would be greatly appreciated.
Last edited by whitebrice (2014-06-28 17:20:13)

Are you sure there isn't a typo in your unit file? The example you linked to in the wiki does have an [Install] section.
Post your ~/.config/systemd/user/emacs.service file here so we can take a look.

[SOLVED] defect dbus service, systemd is unable to create socket

Hi,
I am experiencing serious problems with systemd & dbus.
I want to setup a gateway in a KVM VM, all was working fine till i applied my shorewall config & set to autostart (systemctl enable shorewall).
If I reboot the machine after this step one or two times, then I get a broken dbus service.
What I did than: reinstalled archlinux again (x86_x64) and setup same -> got issue again.
installed arch linux as x86 and setup same -> issue again
installed arch as x86 and configured nothing else shorewall and got this issue again after maximum of two reboots.
i found in log:
Feb 13 15:45:56 pactor systemd[1]: Failed to open private bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
I've checked this directory by hand and found that only /var/run is existing. /var/run/dbus is already not existing.
logs:
journalctl -b: http://nopaste.info/685f4c6192.html
-be aware of systemd-logind, this needs dbus and i experience same problem with other services which require dbus as dnsmasq
root@pactor ~]# systemctl status dbus
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Mi 2013-02-13 15:45:56 CET; 9min ago
Main PID: 169 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
└─169 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
[root@pactor ~]# systemctl status dbus.socket
dbus.socket - D-Bus System Message Bus Socket
Loaded: loaded (/usr/lib/systemd/system/dbus.socket; static)
Active: active (running) since Mi 2013-02-13 15:45:56 CET; 9min ago
Feb 13 15:45:56 pactor systemd[1]: Listening on D-Bus System Message Bus Socket.
systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: activating (start) since Mi 2013-02-13 16:00:56 CET; 48s ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Main PID: 338 (systemd-logind)
CGroup: name=systemd:/system/systemd-logind.service
└─338 /usr/lib/systemd/systemd-logind
Feb 13 16:00:56 pactor systemd[1]: Failed to start Login Service.
Feb 13 16:00:56 pactor systemd[1]: Unit systemd-logind.service entered failed state
Feb 13 16:00:56 pactor systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Feb 13 16:00:56 pactor systemd[1]: Stopping Login Service...
Feb 13 16:00:56 pactor systemd[1]: Starting Login Service...
installed packages: http://nopaste.info/1d1be9adad.html
shorewall config: shorewall_conf.tar
Last edited by debijan (2013-02-20 20:13:47)

oh man... found the reason due to help of some guys on systemd irc... big thx to falconindy and alxchk.
shorewall's SUBSYSLOCK option in shorewall.conf is by default set to /var/lock/shorewall.
but the arch wiki point that it should be set to /var/run: https://wiki.archlinux.org/index.php/Router
definitely wrong! that deletes the /var/run symlink and created a directory intstead.
to set the SUBSYSLOCK on default is working like a charm.
look also for this: https://bbs.archlinux.org/viewtopic.php?id=151285
could somebody modify the wiki in the meantime, i will hold this thread on -not-solved in the meantime
edit:/ oh man this wrong info in wiki did cost me a lot of time :-/
Last edited by debijan (2013-02-13 22:09:35)

Systemd logind.service reports an error: Failed to start login service

Hello,
I found this error in /var/log/errors.log and /var/log/daemon.log although my system functions normally.
It's been written there every 90 seconds!!!!:
Dec 19 23:52:59 localhost systemd[1]: Failed to start Login Service.
Dec 19 23:54:29 localhost systemd[1]: Failed to start Login Service.
Dec 19 23:55:59 localhost systemd[1]: Failed to start Login Service.
Dec 19 23:57:29 localhost systemd[1]: Failed to start Login Service.
Dec 19 23:58:59 localhost systemd[1]: Failed to start Login Service.
the process: systemd-logind.service seems to be working fine:
[xxx@archbox ~]$ sudo systemctl status systemd-logind.service
[sudo] password for xxx:
systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: activating (start) since Wed, 2012-12-19 23:49:59 CET; 49s ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Main PID: 11822 (systemd-logind)
CGroup: name=systemd:/system/systemd-logind.service
└─11822 /usr/lib/systemd/systemd-logind
Dec 19 23:49:59 archbox systemd[1]: Starting Login Service...
Dec 19 23:49:59 archbox systemd-logind[11822]: New seat seat0.
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event6 (P...on)
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event7 (V...us)
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event4 (L...ch)
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event5 (S...on)
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event3 (T...ns)
Dec 19 23:49:59 archbox systemd-logind[11822]: New session 1 of user xxx.
Dec 19 23:49:59 archbox systemd-logind[11822]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-...ay.
and journalctl _PID=11822 returns:
Dec 19 23:38:01 archbox sudo[21335]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:38:01 archbox sudo[21335]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:38:01 archbox sudo[21335]: pam_unix(sudo:session): session closed for user root
Dec 19 23:38:44 archbox sudo[22682]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:38:44 archbox sudo[22682]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:38:44 archbox sudo[22682]: pam_unix(sudo:session): session closed for user root
Dec 19 23:39:10 archbox sudo[23516]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:39:10 archbox sudo[23516]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:39:29 archbox systemd[1]: systemd-logind.service operation timed out. Terminating.
Dec 19 23:39:29 archbox systemd[1]: Failed to start Login Service.
Dec 19 23:39:29 archbox systemd[1]: Unit systemd-logind.service entered failed state
Dec 19 23:39:29 archbox systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Dec 19 23:39:29 archbox systemd[1]: Stopping Login Service...
Dec 19 23:39:29 archbox systemd[1]: Starting Login Service...
Dec 19 23:39:29 archbox systemd-logind[24096]: New seat seat0.
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event6 (Power B
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event7 (Video B
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event4 (Lid Swi
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event5 (Sleep B
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event3 (ThinkPa
Dec 19 23:39:29 archbox systemd-logind[24096]: New session 1 of user xxx.
Dec 19 23:39:29 archbox systemd-logind[24096]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-displa
Dec 19 23:39:30 archbox sudo[23516]: pam_unix(sudo:session): session closed for user root
Dec 19 23:40:08 archbox sudo[25314]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:40:08 archbox sudo[25314]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:40:09 archbox sudo[25314]: pam_unix(sudo:session): session closed for user root
Dec 19 23:40:43 archbox slim[641]: error 8: BadMatch (invalid parameter attributes) request 142 mino
Dec 19 23:40:43 archbox slim[641]: error 9: BadDrawable (invalid Pixmap or Window parameter) request
Dec 19 23:40:43 archbox slim[641]: error 4: BadPixmap (invalid Pixmap parameter) request 54 minor 0
Dec 19 23:40:56 archbox sudo[26739]: xxx : TTY=pts/0 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:40:56 archbox sudo[26739]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:40:59 archbox systemd[1]: systemd-logind.service operation timed out. Terminating.
Dec 19 23:40:59 archbox systemd[1]: Failed to start Login Service.
Dec 19 23:40:59 archbox systemd[1]: Unit systemd-logind.service entered failed state
Dec 19 23:40:59 archbox systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Dec 19 23:40:59 archbox systemd[1]: Stopping Login Service...
Dec 19 23:40:59 archbox systemd[1]: Starting Login Service...
Dec 19 23:40:59 archbox systemd-logind[26935]: New seat seat0.
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event6 (Power B
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event7 (Video B
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event4 (Lid Swi
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event5 (Sleep B
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event3 (ThinkPa
Dec 19 23:40:59 archbox systemd-logind[26935]: New session 1 of user xxx.
Dec 19 23:40:59 archbox systemd-logind[26935]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-displa
Updating system with pacman didn't solve it.
Did I miss something out while migrating to systemd, is it a problem with SLiM or user session maybe ? Do you guys have any ideas where to start ? Thanks.
Last edited by nastycino (2012-12-30 17:46:43)

My /etc/systemd/logind.conf:
# 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.
# See logind.conf(5) for details
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#Controllers=
#ResetControllers=cpu
#InhibitDelayMaxSec=5
HandlePowerKey=poweroff
HandleSuspendKey=suspend
HandleHibernateKey=hibernate
HandleLidSwitch=suspend
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
Is there any way of reinstalling parts of systemd like logind.service?

[Solved] Login Screen Dim on Boot-Up

I was having a problem with my new Arch Enlightenment 18 install using the SLiM login manager on my Lenovo X220. The login screen was dim, but once logged in, the screen was normal brightness. I don't think SLiM itself was causing the dim login screen, but I found the solution!
# systemctl mask systemd-backlight@acpi_video0.service
Actually I stopped the service first, then disabled it, then masked it, however It was the masking of the systemd service that was required.
Found tip from following thread.
https://bbs.archlinux.org/viewtopic.php?id=171227

iTwenty wrote:Have you tried setting own_window to no?
When I do, I conky doesn't load at all.
EDIT: It works, but it's hidden by my PCManFM Wallpaper. I have to not set a wallpaper to see it...
KingX wrote:Are you using double buffer for conky? This is a good topic where users using different DE and WM are sharing their conkyrc files. You should take a look and compare your conkyrc.
Nope, not using double buffer. I've tried different settings here and there to no avail.
Last edited by Ward (2011-11-26 14:50:23)

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

[SOLVED] systemd: autostart service last, at login screen

Similar Messages

Maybe you are looking for