[SOLVED] systemd/User, starting a Dependent service

I am missing something simple here.  I have two services.  Once is dependent on the other.
I got the first service to start with:
$ cat ~/.config/systemd/user/[email protected]
[Unit]
Description=Syncthing - Open Source Continuous File Synchronization for %I
Documentation=https://github.com/syncthing/syncthing/wiki
After=network.target
[Service]
#User=%i
Environment=STNORESTART=yes
ExecStart=/usr/bin/syncthing -no-browser -logflags=0
Restart=on-failure
SuccessExitStatus=2 3 4
RestartForceExitStatus=3 4
[Install]
#WantedBy=multi-user.target
WantedBy=default.target
This autostarts upon logging in with i3 and gnome.  No problem (now).
The problem I have is with the notifier/watcher:
$ cat ~/.config/systemd/user/[email protected]
[Unit]
Description=Syncthing Inotify File Watcher for %I
Documentation=https://github.com/syncthing/syncthing-inotify/blob/master/README.md
After=network.target [email protected]
[email protected]
[Service]
#User=%i
ExecStart=/usr/bin/syncthing-inotify -logflags=0
SuccessExitStatus=2
Restart=on-failure
ProtectSystem=full
ProtectHome=read-only
[Install]
#WantedBy=multi-user.target
WantedBy=default.target
Installed it into my namespace, like I did with the parent service:
$ systemctl --user enable [email protected]
On system startup/login, the service is "Dead (inactive)."
But, I can start it manually:
$ systemctl --user start [email protected]
And the status of the service shows it logging and working, picking up changes, etc.
I must be missing a configuration parameter in the service file.
Last edited by eduncan911 (2015-05-25 14:39:38)

mauritiusdadd wrote:
Just a shot in the dark, but try to change the After= and Requires= lines in [email protected] to
After=network.target syncthing@%i.service
Requires=syncthing@%i.service
You know how you stay up late and everything you do right seems to be wrong?
When I ran:
systemctl status [email protected]
...it showed inactive (dead) and is the reason I made this thread. 
Changed it to this:
systemctl --user status [email protected]
Allowed me to see it started.  *head smack*
And btw, I tried "syncthing@%i.service" and it worked too!  I reverted back to "[email protected]" to verify %i fixed it, but it started as well as before.  So "%i" seems agnostic and would work as well.

Similar Messages

  • [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-user-session: Best way to pass global ENV vars?

    Hey guys,
    So when using the [email protected] from the user-session-units what's the best / cleanest way to set global environment variables for that systemd --user instance (and thus, all programs spawned from it)?
    What I'm talking about is /etc/profile and $HOME/.profile.
    For example, I usally configure my XDG_CONFIG_HOME and XDG_CACHE_HOME in my ~/.profile. But since systemd --user is being started by systemd --session none of these environment variables are loaded.
    The solution I've come up is to change the ExecStart in the [email protected] file to something like this:
    ExecStart=/usr/bin/sh -c "source /etc/profile; source $HOME/.config/bash/environment; exec /usr/lib/systemd/systemd --user"
    I know I could use the `EnvironmentFile` option to load the environment variables from a file, but it's not as flexable as a bash script.
    Am I thinking about this problem wrong? Is there a more "systemd --user"-y way of solving the problem?
    Last edited by EvanPurkhiser (2013-08-12 03:02:48)

    I've more or less solved this using my own user-session units. I still don't know if my method would really be considered the proper way or not though.
    Last edited by EvanPurkhiser (2013-08-12 03:02:19)

  • [SOLVED] systemd --user: "Failed to open private bus connection:"

    EDIT: The solution was to set DBUS_SESSION_BUS_ADDRESS, as suggested by gtmanfred in irc.  By putting the following before executing systemd --user, the error vanished:
    export DBUS_SESSION_BUS_ADDRESS=/run/user/$(id -u)/dbus/user_bus_socket
    ===================
    Original problem:
    Everything on my box appears to be working ok, but I'm getting this error consistently in tty1 and at the top of journalctl (as user) whenever I start systemd --user:
    systemd[3975]: Failed to open private bus connection: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
    I roughly have my system setup per this wiki section https://wiki.archlinux.org/index.php/Sy … ur_Session.  I start systemd --user via a small script in my .bash_profile. Here are my relevant dbus{.service,socket} files, from the package user-session-units mentioned in the wiki:  (Edit: xorg is started through xorg-launch-helper, also from that wiki page)  Edit2: I'm not using autologin.  I noticed that under the autologin section of that page, DBUS_SESSION_BUS_ADDRESS is set to some path.  In my setup that isn't set anywhere, so I may try to copy that later but I don't have time to play with it right now.  Will post back later.
    =====/usr/lib/systemd/user/dbus.service=====
    [Unit]
    Description=D-Bus System Message Bus
    Requires=dbus.socket
    [Service]
    ExecStart=/usr/bin/dbus-daemon --session --address=systemd: --nofork --systemd-activation
    ExecReload=/usr/bin/dbus-send --print-reply --session --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig
    =====/usr/lib/systemd/user/dbus.socket=====
    [Unit]
    Description=D-Bus System Message Bus Socket
    [Socket]
    ListenStream=%t/dbus/user_bus_socket
    And the output of sudo systemctl status dbus:
    dbus.service - D-Bus System Message Bus
    Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
    Active: active (running) since Tue 2013-02-05 14:50:30 EST; 22min ago
    Main PID: 369 (dbus-daemon)
    CGroup: name=systemd:/system/dbus.service
    └─369 /usr/bin/dbus-daemon --system --address=systemd: --no...
    Feb 05 14:50:30 sellers-laptop systemd[1]: Starting D-Bus System Message Bus...
    Feb 05 14:50:30 sellers-laptop systemd[1]: Started D-Bus System Message Bus.
    Feb 05 14:51:18 sellers-laptop dbus-daemon[369]: dbus[369]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Feb 05 14:51:18 sellers-laptop dbus[369]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Feb 05 14:51:18 sellers-laptop dbus[369]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
    Feb 05 14:51:18 sellers-laptop dbus-daemon[369]: dbus[369]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
    I'm not sure what the error even means or how to go about debugging it.  Any suggestions would be appreciated.
    Last edited by Feynman (2013-02-05 22:07:23)

    NVM...didn't notice it was already solved.
    Last edited by the sad clown (2013-02-05 22:33:10)

  • [SOLVED] systemd user unit for lsyncd

    After following the the systemd/User - Basic setup wiki article I have successfully setup user services for systemd.  I've also setup a systemd user "unit" to run lsyncd.  The user unit appears to start successfully based on the unit status shown below.  Only problem is lsyncd isn't running and I'm not seeing any relevant errors or info with journalctl.  If I run the script defined in ExecStart on the command line lsyncd starts as expected.  Any ideas or pointers?
    OUTPUT from "systemctl --user lsyncd.service":
    lsyncd.service - lsyncd
    Loaded: loaded (/home/maseone/.config/systemd/user/lsyncd.service; enabled)
    Active: inactive (dead) since Thu 2014-08-28 18:14:50 PDT; 21min ago
    Process: 630 ExecStart=/home/maseone/.lsyncd/start_lsyncd_simple.sh (code=exited, status=0/SUCCESS)
    Main PID: 630 (code=exited, status=0/SUCCESS)
    Aug 28 18:14:50 archie230x systemd[610]: Starting lsyncd...
    Aug 28 18:14:50 archie230x systemd[610]: Started lsyncd.
    UNIT for lsyncd:
    [Unit]
    Description=lsyncd
    [Service]
    ExecStart=/home/maseone/.lsyncd/start_lsyncd_simple.sh
    [Install]
    WantedBy=default.target
    SCRIPT defined in ExecStart:
    #! /bin/sh
    /bin/lsyncd -log all /home/maseone/.lsyncd/lsyncd.lua
    Last edited by maseone (2014-08-29 04:07:58)

    firecat53 wrote:
    Try changing the service type to forking instead of simple. Or look for an lsycd option that keeps it running in the foreground.
    Scott
    Thanks for the pointer, it worked!  After reading in detail the different types available "forking" does seem the most appropriate type for a daemon written as lsyncd.  I believe using an lsyncd option named "detach" would have worked with the "simple" type but forking seemd more appropriate in my case.
    Also as an update to my original post I have completely removed the use of the shell script and am now calling lsyncd directly in my defined systemd unit.  Also using the %h variable for the home directory now.
    REVISED unit file:
    [Unit]
    Description=lsyncd
    [Service]
    Type=forking
    ExecStart=/bin/lsyncd -log scarce %h/.lsyncd/lsyncd.lua
    [Install]
    WantedBy=default.target

  • [Solved] systemd - Auto starting programs under specific tty

    Is there any way to start a program on an empty tty?
    Currently i run htop on tty11 and a log on tty12 using the default startup scripts with something like this,
    htop:2345:respawn:/usr/bin/htop -d=10 > /dev/tty11
    I've tried played around with systemd for a while but can't get it working. There doesn't seem to any documentation for launching anything except additional gettys, so i tried to modify one of the .service file for htop but didn't make any progress.
    Does anyone else know how to get this working?
    Thanks
    Last edited by CaseMonster (2011-11-02 23:34:20)

    Okay I figured out how to properly run services on systemd, here's the newest .service file
    [Unit]
    Description=htop on tty11
    After=dev-tty11.device systemd-user-sessions.service
    [Service]
    ExecStart=/usr/bin/htop -d=100 > /dev/tty11 < /dev/tty11
    Type=oneshot
    [Install]
    WantedBy=multi-user.target
    And when running i get this
    systemctl status htop.service
    htop.service - htop on tty11
          Loaded: loaded (/lib/systemd/system/htop.service; enabled)
          Active: failed since Wed, 02 Nov 2011 02:57:08 -0500; 1s ago
         Process: 1452 ExecStart=/usr/bin/htop -d=100 > /dev/tty11 < /dev/tty11 (code=exited, status=1/FAILURE)
          CGroup: name=systemd:/system/htop.service

  • [SOLVED] systemd times out stopping transmission.service

    After a recent update, systemd takes really long to shut transmission down either manually or while the computer is turning off.
    Both systemd and transmission were update at the same time so I don't know which one has caused this issue.
    I'm pretty sure it is systemd because starting and killing transmission-daemon manually works as usual.
    I suffer from this problem on two of my machines, one of which runs a fresh install (today).
    Any workarounds?
    Last edited by bel3atar (2013-09-26 01:02:22)

    jjacky wrote:https://bugs.archlinux.org/task/37007 ?
    This must be it. There's a patch to fix the issue.

  • [SOLVED] systemd/user interface not working

    I cannot use user service files, because systemctl gives me this error:
    $ systemctl --user status
    Failed to get D-Bus connection: No such file or directory
    It's been a while since I used a user service file, so I don't know when it started exactly.
    How can I further diagnose this? I've done everything in the wiki related pages, so I'm clueless right now...
    Thanks in advance
    Last edited by hermes (2014-04-20 17:24:31)

    t3kk3n wrote:I would verify dbus is running by 'ps aux | grep dbus' and, if so, check your logs in journalctl. You can grep journalctl using the '--no-pager' option if you desire, otherwise just use less/more. I'd look at the boot logs and see if it spit any errors out about creating the session, etc.
    Thanks for your reply!
    DBus is running. The following processes are active:
    /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
    dbus-launch --sh-syntax --exit-with-session
    /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
    Here's the output of journalctl --this-boot --no-pager | grep -i dbus:
    apr 16 21:03:29 archlinux dbus[546]: [system] Activating systemd to hand-off: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
    apr 16 21:03:29 archlinux dbus[546]: [system] Successfully activated service 'org.freedesktop.systemd1'
    apr 16 21:03:29 archlinux dbus[546]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
    apr 16 21:03:29 archlinux dbus[546]: [system] Successfully activated service 'org.freedesktop.ColorManager'
    apr 16 21:03:29 archlinux dbus[546]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
    apr 16 21:03:30 archlinux dbus[546]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
    apr 16 21:03:30 archlinux dbus[546]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
    apr 16 21:03:30 archlinux dbus[546]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
    apr 16 21:03:30 archlinux dbus[546]: [system] Successfully activated service 'org.bluez'
    apr 16 21:03:30 archlinux dbus[546]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
    apr 16 21:03:30 archlinux dbus[546]: [system] Successfully activated service 'org.freedesktop.hostname1'
    apr 16 21:03:38 archlinux dbus[546]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
    apr 16 21:03:38 archlinux dbus[546]: [system] Successfully activated service 'org.freedesktop.UPower'
    apr 16 21:03:38 archlinux dbus[546]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
    apr 16 21:03:38 archlinux dbus[546]: [system] Successfully activated service 'org.freedesktop.UDisks2'
    apr 16 21:03:41 archlinux org.kde.kuiserver[2061]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    apr 16 21:03:41 archlinux org.kde.kuiserver[2061]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    apr 16 21:03:46 archlinux dbus[546]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
    apr 16 21:03:46 archlinux dbus[546]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
    apr 16 23:50:46 archlinux org.a11y.atspi.Registry[13309]: ** (at-spi2-registryd:13312): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
    apr 17 12:05:00 archlinux dbus[546]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.19" (uid=0 pid=2237 comm="/usr/lib/udisks2/udisksd --no-debug ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.20" (uid=1000 pid=2262 comm="kdeinit4: plasma-desktop [kdeinit] ")
    apr 17 16:50:15 archlinux dbus[546]: [system] Reloaded configuration
    apr 17 16:50:15 archlinux dbus[546]: [system] Reloaded configuration
    apr 17 16:52:06 archlinux dbus[546]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.24" (uid=1000 pid=2332 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.11" (uid=0 pid=1771 comm="/usr/lib/bluetooth/bluetoothd ")
    apr 17 16:52:06 archlinux dbus[546]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.24" (uid=1000 pid=2332 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.11" (uid=0 pid=1771 comm="/usr/lib/bluetooth/bluetoothd ")
    apr 17 16:52:06 archlinux dbus[546]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.24" (uid=1000 pid=2332 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.11" (uid=0 pid=1771 comm="/usr/lib/bluetooth/bluetoothd ")
    apr 17 16:52:06 archlinux dbus[546]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.24" (uid=1000 pid=2332 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.11" (uid=0 pid=1771 comm="/usr/lib/bluetooth/bluetoothd ")
    apr 17 16:52:06 archlinux dbus[546]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.37" (uid=1000 pid=2720 comm="/usr/lib/bluetooth/obexd ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.11" (uid=0 pid=1771 comm="/usr/lib/bluetooth/bluetoothd ")
    apr 17 16:52:06 archlinux dbus[546]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.37" (uid=1000 pid=2720 comm="/usr/lib/bluetooth/obexd ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.11" (uid=0 pid=1771 comm="/usr/lib/bluetooth/bluetoothd ")
    apr 17 16:52:06 archlinux dbus[546]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.37" (uid=1000 pid=2720 comm="/usr/lib/bluetooth/obexd ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.11" (uid=0 pid=1771 comm="/usr/lib/bluetooth/bluetoothd ")
    apr 17 16:52:06 archlinux dbus[546]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.37" (uid=1000 pid=2720 comm="/usr/lib/bluetooth/obexd ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.11" (uid=0 pid=1771 comm="/usr/lib/bluetooth/bluetoothd ")
    apr 17 16:52:06 archlinux dbus[546]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.37" (uid=1000 pid=2720 comm="/usr/lib/bluetooth/obexd ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.11" (uid=0 pid=1771 comm="/usr/lib/bluetooth/bluetoothd ")
    apr 17 16:52:06 archlinux dbus[546]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.37" (uid=1000 pid=2720 comm="/usr/lib/bluetooth/obexd ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.11" (uid=0 pid=1771 comm="/usr/lib/bluetooth/bluetoothd ")
    apr 17 16:52:06 archlinux dbus[546]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
    apr 17 16:52:07 archlinux dbus[546]: [system] Successfully activated service 'org.bluez'
    apr 18 12:26:24 archlinux org.gtk.vfs.Daemon[2061]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    apr 18 12:26:24 archlinux org.gtk.Private.GPhoto2VolumeMonitor[2061]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    apr 18 12:26:24 archlinux org.a11y.Bus[2061]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    apr 18 12:26:24 archlinux org.gtk.vfs.Daemon[2061]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    apr 18 12:26:24 archlinux org.gtk.Private.UDisks2VolumeMonitor[2061]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    apr 18 12:26:24 archlinux ca.desrt.dconf[2061]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-wimax: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.58': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.network-control: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.58': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.58': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.58': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.settings.modify.system: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.58': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.settings.modify.own: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.58': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.settings.modify.hostname: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.58': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-network: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.33': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.sleep-wake: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.33': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-wifi: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.33': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-wwan: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.33': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-wimax: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.33': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.network-control: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.33': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.33': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.33': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.settings.modify.system: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.33': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.settings.modify.own: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.33': no such name
    apr 18 12:26:24 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.settings.modify.hostname: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.33': no such name
    apr 18 12:26:33 archlinux org.kde.kuiserver[31022]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    apr 18 12:26:33 archlinux org.kde.kuiserver[31022]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    apr 18 12:26:38 archlinux org.a11y.atspi.Registry[31238]: ** (at-spi2-registryd:31241): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
    apr 18 12:26:42 archlinux polkitd[1292]: Error converting subject to JS object: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name ':1.141': no such name
    apr 18 12:26:42 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.sleep-wake: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.141': no such name
    apr 18 12:26:42 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-wifi: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.141': no such name
    apr 18 12:26:42 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-wwan: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.141': no such name
    apr 18 12:26:42 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-wimax: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.141': no such name
    apr 18 12:26:42 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.network-control: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.141': no such name
    apr 18 12:26:42 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.141': no such name
    apr 18 12:26:42 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.141': no such name
    apr 18 12:26:42 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.settings.modify.system: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.141': no such name
    apr 18 12:26:42 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.settings.modify.own: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.141': no such name
    apr 18 12:26:42 archlinux NetworkManager[1247]: <warn> error requesting auth for org.freedesktop.NetworkManager.settings.modify.hostname: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.141': no such name
    apr 19 03:28:20 archlinux org.gtk.vfs.Daemon[31022]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    apr 19 03:28:20 archlinux org.a11y.Bus[31022]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    apr 19 03:28:20 archlinux org.gtk.Private.GPhoto2VolumeMonitor[31022]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    apr 19 03:28:20 archlinux org.gtk.Private.UDisks2VolumeMonitor[31022]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
    apr 19 03:30:18 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:30:18 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:30:24 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:30:24 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:30:40 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:30:41 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:30:41 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:30:42 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:30:51 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:30:51 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:30:51 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:30:54 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:30:54 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:30:54 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:30:54 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:30:55 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:30:55 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:31:37 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:31:37 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:31:37 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:31:37 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:31:39 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:31:39 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:31:39 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:31:39 archlinux dbus[546]: [system] Reloaded configuration
    apr 19 03:33:20 archlinux org.kde.kuiserver[23937]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    apr 19 03:33:20 archlinux org.kde.kuiserver[23937]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
    I can't tell if these errors are significant regarding my issue though, they don't mean a lot to me.

  • [Solved] systemd/user : how to exit window manager & stop X?

    Solution: Jump to https://bbs.archlinux.org/viewtopic.php … 6#p1262166
    I have set up my system to user systemd units to start my environment (roughly following the wiki).
    My problem is that I cannot exit my window manager (using “io (exitWith ExitSuccess)” in Xmonad): the service file starting the WM (xmonad) stops/exits with success, but the xorg.service keeps
    running. I need to switch to TTY2, systemctl --user stop xorg.service by hand, then switch to TTY1, execute Ctrl-C, and then I finally get my login
    prompt back.
    This is a bit annoying, and I don't know how to fix it.
    Here are the relevant (I think) unit files:
    # xmonad.target
    [Unit]
    Description=XMonad
    Wants=xorg.target
    Wants=xinit.target
    Requires=dbus.socket
    AllowIsolate=true
    [Install]
    Alias=default.target
    # xmonad.service
    [Unit]
    Description=Starts Xmonad
    Before=xinitrc.target
    After=xorg.target
    Requires=xorg.target
    [Service]
    ExecStart=/usr/bin/xmonad
    Environment=DISPLAY=:0
    Restart=no
    [Install]
    WantedBy=xmonad.target
    RequiredBy=xorg.service
    As you can see, I have added the RequiredBy=xorg.service line at the bottom, hoping that if xmonad.service exits, so should xorg.service - but to
    no avail.
    What do I have to do in order to completely stop X and get my login prompt on TTY1 back?
    EDIT: I am of course using the user-session-units.
    Last edited by Stalafin (2013-04-22 13:54:45)

    I know it's an old thread (not really old) but I have the same problem. The question is your solution doesnt work with me. It just give me an error like this:
    Failed to issue method call: The name org.freedesktop.login1 was not provided by any .service files
    Failed to issue method call: Process /bin/false exited with status 1

  • [Solved] Starting systemd --user as a systemd --system process?

    Hey guys,
    I would like to run systemd --user as a system service using this .service file I wrote:
    $ cat [email protected]
    [Unit]
    Description=Systemd --user instance for %I
    Documentation=man:systemd
    [Service]
    User=%I
    ExecStart=/usr/lib/systemd/systemd --user --log-level=debug
    [Install]
    WantedBy=multi-user.target
    I enabled it for my user using `systemctl enable systemd-user@evan`, however, when starting it it fails with the following errors:
    Jul 21 21:14:42 desktop systemd[12920]: systemd 204 running in user mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
    Jul 21 21:14:42 desktop systemd[12920]: Using cgroup controller name=systemd. File system hierarchy is at /sys/fs/cgroup/systemd/system/[email protected]/[email protected]/systemd-12920.
    Jul 21 21:14:42 desktop systemd[12920]: Failed to create root cgroup hierarchy: Permission denied
    Jul 21 21:14:42 desktop systemd[12920]: Failed to allocate manager object: Permission denied
    Is it possible to run systemd --user like this? Do I need to add something to my [email protected]?
    Last edited by EvanPurkhiser (2013-07-22 02:10:10)

    EDIT: I just realized that the systemd-user-session-units package will only include specific units at build-time weather I have have the programs or not. You're right, I should just use this package!
    Well, to be honest, maybe I'm trying to hack around a problem that doesn't even really exist, but I don't think the systemd-user-sessions-units package meets my needs.
    The way I would like to have my user sessions setup is something like this:
    I would like to have an instance of systemd --user always running under my user so I can keep things like transmission-daemon always running, even when I don't have a user session open. When I do start my user session (via logging into getty) I want to bring my systemd instance up to a certain target. For example, logging in via tty1 should bring up graphical.target, which will start X11 and all that, while logging into any other tty will start console.target (for stuff like ssh-agent etc).
    Thinking more about this I suppose there's really no reason I couldn't use the [email protected] from systemd-user-session-units, but since I won't use most of the other user units included, I would rather just not use it.
    Here's what my .profile looks like:
    if systemctl -q is-active systemd-user@evan
    then
    # Default systemd to the console target
    target="console"
    # If we're logging in from VT1 start the graphical target
    if [[ $XDG_VTNR == 1 ]] && ! systemctl --user -q is-active graphical.target &> /dev/null
    then
    export DISPLAY=:0
    target="graphical"
    fi
    # Set all environment variables in the systemd --user instance (still working on this)
    env | systemctl --user set-environment -
    # Bring up systemd --user to the specified target
    systemctl --user start ${target}.target
    fi
    source "$HOME/.bashrc"
    Last edited by EvanPurkhiser (2013-07-22 03:56:13)

  • [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] systemd and ntpd.service

    I've just converted to pure systemd according to the wiki. Everything went remarkably well, with just a little blemish. While I'm not notified of any error at startup, when I check systemctl I find that ntpd.service's LOAD/ACTIVE/SUB is loaded/failed/failed.
    systemctl status ntpd.service gives me this:
    ntpd.service - Network Time Service
    Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled)
    Active: failed (Result: exit-code) since Thu, 18 Oct 2012 04:16:56 +0200; 6s ago
    Process: 1397 ExecStart=/usr/bin/ntpd -g -u ntp:ntp (code=exited, status=0/SUCCESS)
    Main PID: 1398 (code=exited, status=255)
    CGroup: name=systemd:/system/ntpd.service
    Oct 18 04:16:56 mike ntpd[1398]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
    Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 1 v6wildcard :: UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 2 lo 127.0.0.1 UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 3 eth0 192.168.0.2 UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 4 lo ::1 UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 5 eth0 fe80::224:1dff:fec4:aebe UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: peers refreshed
    Oct 18 04:16:56 mike ntpd[1398]: Listening on routing socket on fd #22 for interface updates
    Oct 18 04:16:56 mike systemd[1]: Started Network Time Service.
    and journalctl pretty much more of the same:
    Oct 18 04:16:56 mike ntpd[1397]: ntpd [email protected] Tue Aug 21 15:06:24 UTC 2012 (1)
    Oct 18 04:16:56 mike ntpd[1398]: proto: precision = 0.106 usec
    Oct 18 04:16:56 mike ntpd[1398]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
    Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
    Oct 18 04:16:56 mike sudo[1394]: pam_unix(sudo:session): session closed for user root
    Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 1 v6wildcard :: UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 2 lo 127.0.0.1 UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 3 eth0 192.168.0.2 UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 4 lo ::1 UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 5 eth0 fe80::224:1dff:fec4:aebe UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: peers refreshed
    Oct 18 04:16:56 mike ntpd[1398]: Listening on routing socket on fd #22 for interface updates
    Oct 18 04:16:56 mike systemd[1]: Started Network Time Service.
    Oct 18 04:16:56 mike systemd[1]: ntpd.service: main process exited, code=exited, status=255
    Oct 18 04:16:56 mike systemd[1]: Unit ntpd.service entered failed state.
    Trying to use it manually (eg. ntpd -qg) works, so I'm not sure what's wrong with it exactly. Where else should I look?
    Last edited by Mr_Mario (2012-12-06 11:29:57)

    slickvguy wrote:I've just started converting to systemd and ran into the same issue. I believe the problem is that you are missing the ntp group from your group file. If you updated your system and merely renamed your group.pacnew to group, it no longer contains the ntp group that was previously added. I just added the ntp group again ( ntp:x:87: ), and ntp started properly and the status is correct. Hope this helps.
    That was it. Thank you!

  • (Solved) systemd-journald extremely high CPU usage

    I started noticing this problem a few days ago, but I thought it was because I was running too much with too little RAM. But when running nothing more than a KDE desktop, my CPU usage bounces between 50% and 100%, making things laggy. It looks like systemd-journald is to blame, as it is using 50% of the CPU. This is an AMD Phenom II dual core, so this definitely shouldn't be happening. I noticed journal logs were more than 2 GB, so I deleted everything within /var/log/journal/. Rebooted, no change, so I disabled journal storage, but that did not solve the problem.
    Nothing in the logs looks like a problem to me:
    $ sudo journalctl
    -- Logs begin at Tue 2013-03-12 17:31:37 PDT, end at Tue 2013-03-12 18:15:56 PDT. --
    Mar 12 17:31:37 silverstone systemd-journal[149]: Allowing runtime journal files to grow to 298.6M.
    Mar 12 17:31:37 silverstone kernel: Initializing cgroup subsys cpuset
    Mar 12 17:31:37 silverstone kernel: Initializing cgroup subsys cpu
    Mar 12 17:31:37 silverstone kernel: Linux version 3.7.10-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.2 (G
    Mar 12 17:31:37 silverstone kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=31669ea0-76db
    Mar 12 17:31:37 silverstone kernel: e820: BIOS-provided physical RAM map:
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000000e2000-0x00000000000fffff] reserved
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cff8ffff] usable
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cff90000-0x00000000cff9dfff] ACPI data
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cff9e000-0x00000000cffdffff] ACPI NVS
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cffe0000-0x00000000cfffffff] reserved
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
    Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000100000000-0x00000001afffffff] usable
    Mar 12 17:31:37 silverstone kernel: NX (Execute Disable) protection: active
    Mar 12 17:31:37 silverstone kernel: SMBIOS 2.5 present.
    Mar 12 17:31:37 silverstone kernel: DMI: MSI MS-7642/890GXM-G65 (MS-7642) , BIOS V1.2 03/31/2010
    Mar 12 17:31:37 silverstone kernel: e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
    Mar 12 17:31:37 silverstone kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Mar 12 17:31:37 silverstone kernel: No AGP bridge found
    Mar 12 17:31:37 silverstone kernel: e820: last_pfn = 0x1b0000 max_arch_pfn = 0x400000000
    Mar 12 17:31:37 silverstone kernel: MTRR default type: uncachable
    Mar 12 17:31:37 silverstone kernel: MTRR fixed ranges enabled:
    Mar 12 17:31:37 silverstone kernel: 00000-9FFFF write-back
    Mar 12 17:31:37 silverstone kernel: A0000-EFFFF uncachable
    Mar 12 17:31:37 silverstone kernel: F0000-FFFFF write-protect
    Mar 12 17:31:37 silverstone kernel: MTRR variable ranges enabled:
    Mar 12 17:31:37 silverstone kernel: 0 base 000000000000 mask FFFF80000000 write-back
    Mar 12 17:31:37 silverstone kernel: 1 base 000080000000 mask FFFFC0000000 write-back
    Mar 12 17:31:37 silverstone kernel: 2 base 0000C0000000 mask FFFFF0000000 write-back
    Mar 12 17:31:37 silverstone kernel: 3 disabled
    Mar 12 17:31:37 silverstone kernel: 4 disabled
    Mar 12 17:31:37 silverstone kernel: 5 disabled
    Mar 12 17:31:37 silverstone kernel: 6 disabled
    Mar 12 17:31:37 silverstone kernel: 7 disabled
    Mar 12 17:31:37 silverstone kernel: TOM2: 00000001b0000000 aka 6912M
    Mar 12 17:31:37 silverstone kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Mar 12 17:31:37 silverstone kernel: e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved
    Mar 12 17:31:37 silverstone kernel: e820: last_pfn = 0xcff90 max_arch_pfn = 0x400000000
    Mar 12 17:31:37 silverstone kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [ffff880
    Mar 12 17:31:37 silverstone kernel: initial memory mapped: [mem 0x00000000-0x1fffffff]
    Mar 12 17:31:37 silverstone kernel: Base memory trampoline at [ffff880000099000] 99000 size 24576
    $ systemctl status systemd-journald
    systemd-journald.service - Journal Service
    Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
    Active: active (running) since Tue 2013-03-12 18:10:41 PDT; 8min ago
    Docs: man:systemd-journald.service(8)
    man:journald.conf(5)
    Main PID: 142 (systemd-journal)
    Status: "Processing requests..."
    CGroup: name=systemd:/system/systemd-journald.service
    `-142 /usr/lib/systemd/systemd-journald
    However, it looks like the log files keep getting corrupted:
    $ sudo journalctl --verify
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-000000000007f543-0004d7c4445effa4.journal
    Invalid object contents at 124687944ââââââââââââââââââââââââââââââââââââââââââ 49%
    File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000a8cb7-0004d7c3d52e9748.journal:124687944 (of 134074368, 92%).
    FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000a8cb7-0004d7c3d52e9748.journal (Bad message)
    Invalid object contents at 75715936âââââââââââââââââââââââââââââââââââââââââââ 49%
    File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system.journal:75715936 (of 76156928, 99%).
    FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system.journal (Bad message)
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000290d6-0004d7c3a0033472.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-0000000000000001-0004d7c413227650.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/[email protected]~
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000fcfc0-0004d7c3fd8ee9c5.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/[email protected]~
    Invalid object contents at 124701856ââââââââââââââââââââââââââââââââââââââââââ 49%
    File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-0000000000000001-0004d7c3876dda65.journal:124701856 (of 134049792, 93%).
    FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-0000000000000001-0004d7c3876dda65.journal (Bad message)
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-00000000000a9da8-0004d7c45187e39e.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000d26b1-0004d7c3ea1b73f7.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-000000000002a43f-0004d7c425785944.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000539fb-0004d7c3b2d1f935.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-0000000000054d23-0004d7c4354da4ef.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/user-1000@2c1af599e637441985385fe37ded2a2c-0000000000001706-0004d7c38cd3de88.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/user-1000@5e6edd359123491f9998a310206ccbf9-00000000000019b4-0004d7c4153f8628.journal
    PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-000000000007e345-0004d7c3c3ed8197.journal
    I am using a two or three year old SSD, so maybe it has gotten some bad sectors? But that doesn't explain why journald still bricks things when it isn't logging anything. The install is 10 months old, and I switched from init to systemd around October. Is there anything I can do, short of reinstalling?
    Thanks,
    Nicholas
    Last edited by bicyclingrevolution (2013-03-14 05:57:13)

    Thanks for the tip ilkyest, but it didn't make any difference to the systemd-journald problem.
    However, I looked at journalctl again and found it cluttered with CUPS failures:
    -- Logs begin at Tue 2013-03-12 19:17:00 PDT, end at Wed 2013-03-13 22:31:31 PDT. --
    Mar 12 19:17:00 silverstone spideroak_inotify[796]: Program started
    Mar 12 19:21:30 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 7199 messages from /system
    Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
    Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 5471 messages from /system
    Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 5699 messages from /system
    Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
    Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
    Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
    Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
    Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
    Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
    Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:30 silverstone systemd-coredump[1592]: Process 1590 (cupsd) dumped core.
    Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_3840-Gray..
    Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_3840-RGB..
    Mar 12 19:21:28 silverstone colord[354]: Device added: cups-Deskjet_3840
    Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_F4100-Gray..
    Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_F4100-RGB..
    Mar 12 19:21:28 silverstone colord[354]: Device added: cups-Deskjet_F4100
    Mar 12 19:21:28 silverstone dbus[337]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Mar 12 19:21:28 silverstone dbus[337]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs
    Mar 12 19:21:28 silverstone colord[354]: Profile removed: Deskjet_3840-Gray..
    Mar 12 19:21:28 silverstone colord[354]: Profile removed: Deskjet_3840-RGB..
    Mar 12 19:21:28 silverstone colord[354]: device removed: cups-Deskjet_3840
    Mar 12 19:21:31 silverstone colord[354]: Profile removed: Deskjet_F4100-Gray..
    Mar 12 19:21:31 silverstone colord[354]: Profile removed: Deskjet_F4100-RGB..
    Mar 12 19:21:31 silverstone colord[354]: device removed: cups-Deskjet_F4100
    Mar 12 19:21:31 silverstone dbus-daemon[337]: dbus[337]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
    Mar 12 19:21:31 silverstone dbus-daemon[337]: dbus[337]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or director
    Mar 12 19:21:31 silverstone systemd-journal[143]: Missed 6365 kernel messages
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone cupsd[1590]: Unknown directive DefaultAuthType on line 9.
    Mar 12 19:21:31 silverstone cupsd[1590]: cupsd: client.c:757: avahi_client_get_host_name: Assertion `client' failed.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone cupsd[1594]: Unknown directive DefaultAuthType on line 9.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
    Disabling cups solved the CPU usage issue.
    It looks like the root of the problem is Avahi failing to start, but I have no idea why it isn't working.
    $ systemctl status dbus-org.freedesktop.Avahi.service
    dbus-org.freedesktop.Avahi.service
    Loaded: error (Reason: No such file or directory)
    Active: inactive (dead)

  • Systemd --user not autostarting jobs

    I am playing around with the idea of switching all my user jobs to be controlled by Systemd, I followed the wiki on the matter but none of the are auto starting but work fine when I start them manually.
    when my .xinitrc only contains the systemd --user line Xorg starts but nothing else starts, after changing it to
    #!/bin/sh
    systemd --user &
    exec /home/vendion/gocode/bin/wingo
    My window manager starts but nothing else does, my systemd unit files are as follows:
    default.target mystuff.target mystuff.target.wants wingo.service wm.target wm.target.wants [email protected]
    I ran "systemctl --user enable" on both wingo.service and [email protected], when I run the xcompmgr unit manually via "systemctl --user start xcompmgr@:0.service" it runs fine and starts up xcompmgr so I know it is not an issue with the unit file itself.
    This is what my units look like:
    arch-testing% cat wm.target
    [Unit]
    Description=Window manager target
    Wants=xorg.target
    Wants=mystuff.target
    Requires=dbus.socket
    AllowIsolate=true
    [Install]
    Alias=default.target
    arch-testing% cat mystuff.target
    [Unit]
    Description=Xinitrc Stuff
    Wants=wm.target
    [Install]
    Alias=default.target
    arch-testing% cat wingo.service
    [Unit]
    Description=Wingo window manager service
    Before=mystuff.target
    After=xorg.target
    Requires=xorg.target
    [Service]
    ExecStart=/home/vendion/gocode/bin/wingo
    Restart=always
    RestartSec=10
    [Install]
    WantedBy=wm.target
    arch-testing% cat [email protected]
    [Unit]
    Description=xcompmgr start script
    [Service]
    ExecStart=/usr/bin/xcompmgr
    Environment=DISPLAY=%i
    [Install]
    WantedBy=mystuff.target
    Any clues that would help debug this issue?

    I am playing around with the idea of switching all my user jobs to be controlled by Systemd, I followed the wiki on the matter but none of the are auto starting but work fine when I start them manually.
    when my .xinitrc only contains the systemd --user line Xorg starts but nothing else starts, after changing it to
    #!/bin/sh
    systemd --user &
    exec /home/vendion/gocode/bin/wingo
    My window manager starts but nothing else does, my systemd unit files are as follows:
    default.target mystuff.target mystuff.target.wants wingo.service wm.target wm.target.wants [email protected]
    I ran "systemctl --user enable" on both wingo.service and [email protected], when I run the xcompmgr unit manually via "systemctl --user start xcompmgr@:0.service" it runs fine and starts up xcompmgr so I know it is not an issue with the unit file itself.
    This is what my units look like:
    arch-testing% cat wm.target
    [Unit]
    Description=Window manager target
    Wants=xorg.target
    Wants=mystuff.target
    Requires=dbus.socket
    AllowIsolate=true
    [Install]
    Alias=default.target
    arch-testing% cat mystuff.target
    [Unit]
    Description=Xinitrc Stuff
    Wants=wm.target
    [Install]
    Alias=default.target
    arch-testing% cat wingo.service
    [Unit]
    Description=Wingo window manager service
    Before=mystuff.target
    After=xorg.target
    Requires=xorg.target
    [Service]
    ExecStart=/home/vendion/gocode/bin/wingo
    Restart=always
    RestartSec=10
    [Install]
    WantedBy=wm.target
    arch-testing% cat [email protected]
    [Unit]
    Description=xcompmgr start script
    [Service]
    ExecStart=/usr/bin/xcompmgr
    Environment=DISPLAY=%i
    [Install]
    WantedBy=mystuff.target
    Any clues that would help debug this issue?

  • [SOLVED]systemd-timesyncd is not syncing time

    Quick solution:
    1) Check that systemd-networkd is running (if not, start it)
    2) If it is running and timesyncd is not syncing, just restart systemd-networkd
    more on this in the last post.
    Hello,
    I tried to replace ntp with systemd-timesyncd. I disabled ntpd, enabled systemd-timesyncd, enabled and set systemd-networkd (I found that it might help) over netctl (which I could uninstall then). It somehow worked for few reboots, but then it stopped. Of course there must be a reason why, but I can't figure out what it could be. Everything looks fine to me, but time is just not syncing and I'm 30 minutes in the past (compared with realtime). It loads saved time (as fake-hwclock does), but then there is no sync.
    Here are my logs:
    ~ $ systemctl status systemd-networkd systemd-timedated systemd-timesyncd
    * systemd-networkd.service - Network Service
    Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled)
    Active: active (running) since Sun 2014-06-08 16:48:36 CEST; 15h ago
    Docs: man:systemd-networkd.service(8)
    Main PID: 149 (systemd-network)
    Status: "Processing requests..."
    CGroup: /system.slice/systemd-networkd.service
    `-149 /usr/lib/systemd/systemd-networkd
    Jun 08 16:48:36 smecpi systemd[1]: Starting Network Service...
    Jun 08 16:48:36 smecpi systemd-networkd[149]: eth0: link configured
    Jun 08 16:48:36 smecpi systemd[1]: Started Network Service.
    Jun 08 16:48:37 smecpi systemd-networkd[149]: eth0: gained carrier
    * systemd-timedated.service - Time & Date Service
    Loaded: loaded (/usr/lib/systemd/system/systemd-timedated.service; static)
    Active: active (running) since Mon 2014-06-09 08:14:05 CEST; 11min ago
    Docs: man:systemd-timedated.service(8)
    man:localtime(5)
    http://www.freedesktop.org/wiki/Software/systemd/timedated
    Main PID: 4520 (systemd-timedat)
    CGroup: /system.slice/systemd-timedated.service
    `-4520 /usr/lib/systemd/systemd-timedated
    Jun 09 08:14:05 smecpi systemd[1]: Started Time & Date Service.
    * systemd-timesyncd.service - Network Time Synchronization
    Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled)
    Active: active (running) since Sun 2014-06-08 16:48:35 CEST; 15h ago
    Docs: man:systemd-timesyncd.service(8)
    Main PID: 125 (systemd-timesyn)
    CGroup: /system.slice/systemd-timesyncd.service
    `-125 /usr/lib/systemd/systemd-timesyncd
    Jan 01 01:00:06 smecpi systemd-timesyncd[125]: System clock time unset or jumped backwards, restoring from recorded timestamp: Sun 2014-06-08 16:48:35 CEST
    Jun 08 16:48:35 smecpi systemd[1]: Started Network Time Synchronization.
    ~ $ timedatectl
    Local time: Mon 2014-06-09 08:29:51 CEST
    Universal time: Mon 2014-06-09 06:29:51 UTC
    RTC time: n/a
    Time zone: Europe/Prague (CEST, +0200)
    NTP enabled: yes
    NTP synchronized: no
    RTC in local TZ: no
    DST active: yes
    Last DST change: DST began at
    Sun 2014-03-30 01:59:59 CET
    Sun 2014-03-30 03:00:00 CEST
    Next DST change: DST ends (the clock jumps one hour backwards) at
    Sun 2014-10-26 02:59:59 CEST
    Sun 2014-10-26 02:00:00 CET
    Any ideas?
    Last edited by Kotrfa (2014-06-11 16:30:15)

    Ok, thank you for your help. I signed a bug here: https://bugs.freedesktop.org/show_bug.cgi?id=79836 .
    Edit:
    So here is a little help. timesyncd just waits for "network configuration change". I guess that (somehow) timesyncd is runned after networkd and then waits for change. All you have to do is
    systemctl restart systemd-networkd
    Here is example and steps to reproduce (after boot up, both networkd and timesyncd are enabled):
    ~ $ systemctl status systemd-timesyncd systemd-networkd
    * systemd-timesyncd.service - Network Time Synchronization
    Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled)
    Active: active (running) since Wed 2014-06-11 17:55:50 CEST; 24min ago
    Docs: man:systemd-timesyncd.service(8)
    Main PID: 126 (systemd-timesyn)
    CGroup: /system.slice/systemd-timesyncd.service
    `-126 /usr/lib/systemd/systemd-timesyncd
    Jun 01 01:00:06 locsmxp systemd-timesyncd[126]: System clock time unset or jumped backwards, restoring from recorded timestamp:...0 CEST
    Jun 11 17:55:50 locsmxp systemd[1]: Started Network Time Synchronization.
    * systemd-networkd.service - Network Service
    Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled)
    Active: active (running) since Wed 2014-06-11 17:55:51 CEST; 24min ago
    Docs: man:systemd-networkd.service(8)
    Main PID: 150 (systemd-network)
    Status: "Processing requests..."
    CGroup: /system.slice/systemd-networkd.service
    `-150 /usr/lib/systemd/systemd-networkd
    Jun 11 17:55:51 locsmxp systemd[1]: Started Network Service.
    Jun 11 17:55:51 locsmxp systemd-networkd[150]: eth0: link configured
    Jun 11 17:55:52 locsmxp systemd-networkd[150]: eth0: gained carrier
    Hint: Some lines were ellipsized, use -l to show in full.
    now restart networkd:
    ~ $ systemctl restart systemd-networkd
    and result:
    ~ $ systemctl status systemd-timesyncd systemd-networkd
    * systemd-timesyncd.service - Network Time Synchronization
    Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled)
    Active: active (running) since Wed 2014-06-11 17:55:50 CEST; 25min ago
    Docs: man:systemd-timesyncd.service(8)
    Main PID: 126 (systemd-timesyn)
    Status: "Using Time Server 216.239.32.15:123 (time2.google.com)."
    CGroup: /system.slice/systemd-timesyncd.service
    `-126 /usr/lib/systemd/systemd-timesyncd
    Jun 01 01:00:06 locsmxp systemd-timesyncd[126]: System clock time unset or jumped backwards, restoring from recorded timestamp:...0 CEST
    Jun 11 17:55:50 locsmxp systemd[1]: Started Network Time Synchronization.
    Jun 11 18:20:48 locsmxp systemd-timesyncd[126]: Network configuration changed, trying to establish connection.
    Jun 11 18:20:48 locsmxp systemd-timesyncd[126]: Network configuration changed, trying to establish connection.
    Jun 11 18:20:48 locsmxp systemd-timesyncd[126]: Using NTP server 216.239.32.15:123 (time2.google.com).
    Jun 11 18:20:49 locsmxp systemd-timesyncd[126]: interval/delta/delay/jitter/drift 64s/+0.000s/0.000s/0.000s/+0ppm
    * systemd-networkd.service - Network Service
    Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled)
    Active: active (running) since Wed 2014-06-11 18:20:48 CEST; 5s ago
    Docs: man:systemd-networkd.service(8)
    Main PID: 1129 (systemd-network)
    Status: "Processing requests..."
    CGroup: /system.slice/systemd-networkd.service
    `-1129 /usr/lib/systemd/systemd-networkd
    Jun 11 18:20:48 locsmxp systemd-networkd[1129]: eth0: gained carrier
    Jun 11 18:20:48 locsmxp systemd[1]: Started Network Service.
    Jun 11 18:20:48 locsmxp systemd-networkd[1129]: eth0: link configured
    Hint: Some lines were ellipsized, use -l to show in full.
    I solved this issue by adding new service (guide here: https://wiki.archlinux.org/index.php/Sy … rocess.3F) which runs this simple script
    #!/usr/bin/bash
    sleep 15
    systemctl restart systemd-networkd
    So workaround...
    Last edited by Kotrfa (2014-06-11 16:46:06)

Maybe you are looking for