[Solved] systemd - network-online.target inactive dead

Still trying to get familiar with systemd after years with Ubuntu.
I have Crashplan installed and it's systemd service unit has the following line to wait until the network comes online.
After=network-online.target
However, this doesn't seem to be working. While trying to investigate this, I noticed that the target shows as 'inactive' and 'dead'. Not entirely sure what that means.
➜ ~ systemctl list-units --type=target --all | grep network-online
network-online.target loaded inactive dead Network is Online
Where can I go from here to make sure my Crashplan service only starts after the network is online?
Thanks.
Last edited by sajan (2015-04-21 22:18:14)

Head_on_a_Stick wrote:
Please post the output of:
systemctl status network-online.target
Do you actually have a working connection?
Well, I'm connected to the internet via Wifi by the time I get past my lightdm greeter. Not sure if systemd wants something else.
➜ ~ ping google.com
PING google.com (216.58.216.206) 56(84) bytes of data.
64 bytes from ord31s21-in-f14.1e100.net (216.58.216.206): icmp_seq=1 ttl=54 time=21.4 ms
64 bytes from ord31s21-in-f14.1e100.net (216.58.216.206): icmp_seq=2 ttl=54 time=74.9 ms
^C
--- google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 21.433/48.185/74.938/26.753 ms
➜ ~ systemctl status network-online.target
● network-online.target - Network is Online
Loaded: loaded (/usr/lib/systemd/system/network-online.target; static; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd.special(7)
http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget
➜ ~ ping google.com
PING google.com (216.58.216.206) 56(84) bytes of data.
64 bytes from ord31s21-in-f14.1e100.net (216.58.216.206): icmp_seq=1 ttl=54 time=19.3 ms
64 bytes from ord31s21-in-f14.1e100.net (216.58.216.206): icmp_seq=2 ttl=54 time=24.4 ms
64 bytes from ord31s21-in-f14.1e100.net (216.58.216.206): icmp_seq=3 ttl=54 time=19.2 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 19.243/20.992/24.429/2.435 ms
➜ ~
Last edited by sajan (2015-04-21 21:19:21)

Similar Messages

[SOLVED] network-online.target is reached too early

Hi,
I want to start a systemd service once my wireless card is correctly set up (especially the wifi channel).
I think that the network-online is what I need.
So, I added the following lines at the beginning of my service file :
[Unit]
Description=...
Wants=network-online.target
After=network-online.target
However, it seems that the network-online.target is reached really early in the boot process, far before the discovery of the wireless card.
I don't know if it's important, but my wireless network is configured with netctl-auto.
I'm not very familiar with systemd, so I don't even understand how network-online.target is supposed to be notified that the network is online.
So, any help would be apreciated.
Thanks.
PS : I hope my approximative English is understandable enough.
Last edited by PHF (2013-10-28 02:51:43)

Lone_Wolf wrote:PHF, if i understand correctly you need to be sure the wireless connection is up and configured before the hostapd daemon runs ?
Yes, exactly.
Lone_Wolf wrote:a solution to achieve this might be to write a special command to check if the connection is up and add a service for it like the NetworkManager-wait-online.service .
This special command could be simple, like grepping the output op of ip addr show <interfacename> in a loop until it has a valid ip address.
Well, that's what I started to guess, without certitude : I need to manually order a waiting service before network-online.target.
I think my problem is solved now .
Meanwhile, I have found the ExecUpPost option for my netctl profiles.
It gives me the ability to execute a command once the connection is active.
So, I should be able to use it for unlocking my waiting service.
Thanks a lot for your help.

Systemd --user and network-online.target

I am trying to set up a user timer unit to whose service should be triggered only after the network has become online. The problem is that the network.target and network-online.target are system targets and not available for the --user daemon. Is there anyway to achieve this?

I wonder if you are on the right track using --user? The man page says this option is "of little use except for debugging".

[Solved] Systemd in user mode not working properly

Hello.
I wrote this Systemd service that I would like to run as normal user.
[Unit]
Description=Google Drive mount
After=network-online.target
Wants=network-online.target
[Service]
ExecStart=/usr/bin/google-drive-ocamlfuse -m '/home/egidio/Google Drive'
ExecStop=/usr/bin/fusermount -u '/home/egidio/Google Drive'
[Install]
WantedBy=default.target
I start it and everything seems fine, but when I try to access the mounted point, I get this error.
[egidio@egidiolaptop user]$ ls -la ~/Google\ Drive
ls: cannot access /home/egidio/Google Drive: Transport endpoint is not connected
If I run the ExecStart command manually everything works perfectly.
Can you please help me?
Last edited by Aegidius (2015-05-13 18:17:12)

This is the output of journalctl --all
May 12 20:55:04 egidiolaptop /usr/lib/gdm/gdm-x-session[19552]: Activating service name='org.gnome.Terminal'
May 12 20:55:04 egidiolaptop /usr/lib/gdm/gdm-x-session[19552]: Successfully activated service 'org.gnome.Terminal'
May 12 20:55:26 egidiolaptop gnome-session[19563]: 1431456926458 addons.update-checker WARN Update manifest for {972ce4c6-7e08-4474-a285-3208198ce6fd} did not contain an updates property
May 12 20:56:03 egidiolaptop systemd[19544]: [/home/egidio/.config/systemd/user/googledrive.service:2] Unknown lvalue 'Type' in section 'Unit'
May 12 20:56:03 egidiolaptop systemd[19544]: Cannot add dependency job for unit network-online.target, ignoring: Unit network-online.target failed to load: No such file or directory.
May 12 20:56:03 egidiolaptop systemd[19544]: Created slice -.slice.
May 12 20:56:03 egidiolaptop systemd[19544]: Starting -.slice.
May 12 20:56:03 egidiolaptop systemd[19544]: Started Google Drive mount.
May 12 20:56:03 egidiolaptop systemd[19544]: Starting Google Drive mount...
May 12 20:56:03 egidiolaptop fusermount[20547]: /usr/bin/fusermount: failed to unmount /home/egidio/Google Drive: Device or resource busy
May 12 20:56:03 egidiolaptop systemd[19544]: googledrive.service: control process exited, code=exited status=1
May 12 20:56:03 egidiolaptop systemd[19544]: Unit googledrive.service entered failed state.
May 12 20:56:03 egidiolaptop systemd[19544]: googledrive.service failed.

[SOLVED] systemd service not starting

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

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

[SOLVED] [systemd] systed-module-load.service inactive (dead)

Hello archers,
I use VirtualBox and I'm tired of loading modules manually so I figured that a conf file can be created in /etc/modprobe.d/ that will load those modules at boot. Well, easier said than done because it doesn't seem to work.
Here's my virtualbox.conf:
# modules relevant to VirtualBox
vboxdrv
vboxnetadp
vboxnetflt
and here's my systemctl status systemd-modules-load.service:
systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
Active: inactive (dead)
start condition failed at Sun 2013-10-20 09:27:06 CEST; 6s ago
none of the trigger conditions were met
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Looking forward to hearing from you.
Last edited by robin92 (2013-10-20 11:10:55)

robin92 wrote:so I figured that a conf file can be created in /etc/modprobe.d/ that will load those modules at boot.
Why not read the Wiki and follow the instructions?
https://wiki.archlinux.org/index.php/VirtualBox
Last edited by loafer (2013-10-20 08:06:04)

[SOLVED] systemd + lost networking

After the last update I seem to have lost my network. Systemd complains it cannot find the network.service file.
The systemd package only contains network.target and not network.service
How can i manually start the network ( simple eth0 + dhcp).
And how can i fix my system?
Last edited by GogglesGuy (2012-07-16 14:52:17)

65kid wrote:network.service has been removed from systemd-arch-units, have a look at:
https://wiki.archlinux.org/index.php/Systemd#Network
Ah I see. Thanks.

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

[SOLVED] systemd+wpa_supplicant, but the name of interfaces changes

Hello,
I'm following instructions here for having the wireless connection ready at boot on my machine.
I needed to setup two different daemons since sometimes my wireless interfaces is wlp3s0 and sometimes is wlan0.
When the name of the interface is wlp3s0 everything works fine and I'm correctly given an IP address.
It doesn't happen the same when the name is wlan0.
Here's some output
$ systemctl status [email protected] -l
● [email protected] - Wireless network connectivity (wlan0)
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: inactive (dead)
Jun 22 16:10:19 banzi systemd[1]: Dependency failed for Wireless network connectivity (wlan0).
$ cat /etc/conf.d/network-wireless@wlan0
address=192.168.1.10
netmask=24
broadcast=192.168.1.255
gateway=192.168.1.1
$ cat /etc/conf.d/network-wireless@wlp3s0
address=192.168.1.8
netmask=24
broadcast=192.168.1.255
gateway=192.168.1.1
$ cat /etc/systemd/system/[email protected]
[Unit]
Description=Wireless network connectivity (%i)
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=/etc/conf.d/network-wireless@%i
ExecStart=/usr/bin/ip link set dev %i up
ExecStart=/usr/bin/wpa_supplicant -B -i %i -c /etc/wpa_supplicant/wpa_supplicant.conf
ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev %i
ExecStart=/usr/bin/ip route add default via ${gateway}
ExecStop=/usr/bin/ip addr flush dev %i
ExecStop=/usr/bin/ip link set dev %i down
[Install]
WantedBy=multi-user.target
What more info do you need?, what's wrong?
Thanks,
Giuseppe
Last edited by giuscri (2014-06-28 19:53:35)

Check your journal for messages relating to wlan0 and wlp3s0. I think you may find some kind of error message -- maybe having to do with firmware. I've seen thing like that break predicatible device names
If you've just one wlan interface, you could turn off predicable device names and just go with wlan0

[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 uses cronie.service in /usr/lib instead of /etc

I've been having a little problem getting systemd to use my custom service file for cronie. I've tried doing the same thing with ntpd and a few other services, and they all work fine.
[root@garrett garrett]# cp /{usr/lib,etc}/systemd/system/cronie.service
[root@garrett garrett]# systemctl reenable cronie.service
rm '/etc/systemd/system/multi-user.target.wants/cronie.service'
ln -s '/etc/systemd/system/cronie.service' '/etc/systemd/system/multi-user.target.wants/cronie.service'
[root@garrett garrett]# systemctl status cronie.service
cronie.service - Periodic Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/cronie.service; enabled)
Active: inactive (dead)
CGroup: name=systemd:/system/cronie.service
Sep 13 21:32:52 garrett /usr/sbin/crond[622]: (CRON) INFO (running with inotify support)
It appears to have something to do with the crond.service symlink to cronie.service, since when I remove it, systemd will use the service file in /etc.
[root@garrett garrett]# rm /usr/lib/systemd/system/crond.service
[root@garrett garrett]# cp /{usr/lib,etc}/systemd/system/cronie.service
[root@garrett garrett]# systemctl reenable cronie.service
rm '/etc/systemd/system/multi-user.target.wants/cronie.service'
ln -s '/etc/systemd/system/cronie.service' '/etc/systemd/system/multi-user.target.wants/cronie.service'
[root@garrett garrett]# systemctl status cronie.service
cronie.service - Periodic Command Scheduler
Loaded: loaded (/etc/systemd/system/cronie.service; enabled)
Active: inactive (dead)
CGroup: name=systemd:/system/cronie.service
Sep 13 21:32:52 garrett /usr/sbin/crond[622]: (CRON) INFO (running with inotify support)
However, these symlinks don't cause problems in other packages such as with cups.service, which has a symlink cupsd.service. I also tried the same commands above on another arch computer I have that is running systemd and encountered the same results. This just seems really strange, and I'm not exactly sure where to go from here. Any help would be greatly appreciated.
Last edited by Floft (2012-09-14 06:40:23)

I can not replicate on my system.
# find {/usr/lib,/etc}/systemd/system/ -name "*cron*" -ls
803795 4 -rw-r--r-- 1 root root 174 Aug 8 22:24 /usr/lib/systemd/system/cronie.service
803798 0 lrwxrwxrwx 1 root root 14 Aug 8 22:24 /usr/lib/systemd/system/crond.service -> cronie.service
793796 4 -rw-r--r-- 1 root root 174 Sep 14 03:01 /etc/systemd/system/cronie.service
932745 0 lrwxrwxrwx 1 root root 34 Sep 14 03:01 /etc/systemd/system/multi-user.target.wants/cronie.service -> /etc/systemd/system/cronie.service
# systemctl status cronie
cronie.service - Periodic Command Scheduler
Loaded: loaded (/etc/systemd/system/cronie.service; enabled)
Active: active (running) since Fri, 14 Sep 2012 03:06:05 -0300; 1s ago
Main PID: 13956 (crond)
CGroup: name=systemd:/system/cronie.service
└ 13956 /usr/sbin/crond -n

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

[SOLVED] systemd: laptop-mode-tools fails to start (No such file ...)

Hi,
I recently moved to systemd. I noticed that 'laptop-mode-tools' does not start:
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
Also laptop-mode itself does not run (but exits successfully), maybe this has something to do with it:
laptop-mode.service - Laptop Mode Tools
Loaded: loaded (/usr/lib/systemd/system/laptop-mode.service; enabled)
Active: active (exited) since Sat, 2012-11-10 10:44:13 CET; 2min 17s ago
Process: 1020 ExecStart=/usr/sbin/laptop_mode init auto (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/laptop-mode.service
I cannot find anything in journal that would help resolve this issue. Has someone else come across this problem? Where should I look to fix this issue?
Sidenote: When I boot up, there show up some errors about 'eth0' and 'wlan0' "No such file or directory", but I cannot find them in the journal so I don't know them exactly.
Last edited by javex (2012-11-10 12:41:07)

When I upgraded, pacman said the following
[2012-11-04 09:41] The systemd service name has changed from \laptop-mode-tools" to "laptop-mode"
[2012-11-04 09:41] The change requires the old symlink to be manually removed:
[2012-11-04 09:41] rm /etc/systemd/system/multi-user.target.wants/laptop-mode-tools.service
[2012-11-04 09:41] The laptop-mode.service can be enabled using:
[2012-11-04 09:41] systemctl enable laptop-mode
[2012-11-04 09:41] upgraded laptop-mode-tools (1.61-2 -> 1.62-2)

[SOLVED] systemd display-manager.service problem

Hi!
After the upgrade of systemd, i noticed today this error in dmesg:
systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
systemctl status display-manager.service
display-manager.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
The strange thing is why systemd tries to load a service that doesn't exist! And what is this unit for? I'm using slim to load my xfce desktop, and everything works well...
Any idea?
Thanks!
EDIT: Uhm, may be the alias in slim.service, set to display-manager.service, is the problem? Or may be this is not a problem, but it is its normal behaviour , and i misunderstood something! Is it?
Last edited by nierro (2012-07-15 17:13:42)

nierro wrote:
Hi!
After the upgrade of systemd, i noticed today this error in dmesg:
systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
systemctl status display-manager.service
display-manager.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
The strange thing is why systemd tries to load a service that doesn't exist! And what is this unit for? I'm using slim to load my xfce desktop, and everything works well...
Any idea?
Thanks!
EDIT: Uhm, may be the alias in slim.service, set to display-manager.service, is the problem? Or may be this is not a problem, but it is its normal behaviour , and i misunderstood something! Is it?
There has been a change regarding display managers. up until now they were WantedBy graphical.target, which was kind of stupid because this allowed you to enable multiple display managers.
Instead graphical.target now Wants display-manager.service and all display managers are supposed to install the appropriate Alias. Afaik all display manager service files have been updated ragarding this and a "systemctl reenable slim.service" should fix it.

[SOLVED] Systemd has problems with ntfs-3g

Hi!
I created a custom daemon.
It's very simple.
[Unit]
Description=Mounting partitions if Im at home
[Service]
Type=simple
ExecStart=/home/skitter/homemount.sh
[Install]
WantedBy=multi-user.target
And the content of a script:
#!/bin/bash
device0="/dev/disk/by-uuid/e2b0e86b-d377-4699-9407-48d56eb439d0"
if [ -b "$device0" ]
then
mount UUID=01CECC33AEE58980 /mnt/WINDOWS
mount UUID=ff2d44b5-bdd0-4524-89bf-6ac3bc005887 /mnt/Other
mount UUID=599D77CD384A8B00 /mnt/Files
fi
Unfortunately for some reason the ntfs partitions are being automatically unmounted.
The ext4 partition is not causing any problems.
$sudo systemctl status homemount
homemount.service - Mounting disk if Im at home
Loaded: loaded (/usr/lib/systemd/system/homemount.service; enabled)
Active: inactive (dead) since Sun 2013-10-27 21:56:23 CET; 1s ago
Process: 3202 ExecStart=/home/skitter/homemount.sh (code=exited, status=0/SUCCESS)
Main PID: 3202 (code=exited, status=0/SUCCESS)
Oct 27 21:56:22 archer ntfs-3g[3206]: Mounted /dev/sdb1 (Read-Write, label "", NTFS 3.1)
Oct 27 21:56:22 archer ntfs-3g[3206]: Cmdline options: rw
Oct 27 21:56:22 archer ntfs-3g[3206]: Mount options: rw,allow_other,nonempty,relatime,fsname=/dev/sdb1,blkdev,blksize=4096
Oct 27 21:56:22 archer ntfs-3g[3206]: Ownership and permissions disabled, configuration type 7
Oct 27 21:56:23 archer ntfs-3g[3213]: Version 2013.1.13 external FUSE 29
Oct 27 21:56:23 archer ntfs-3g[3213]: Mounted /dev/sda1 (Read-Write, label "Files", NTFS 3.1)
Oct 27 21:56:23 archer ntfs-3g[3213]: Cmdline options: rw
Oct 27 21:56:23 archer ntfs-3g[3213]: Mount options: rw,allow_other,nonempty,relatime,fsname=/dev/sda1,blkdev,blksize=4096
Oct 27 21:56:23 archer ntfs-3g[3213]: Ownership and permissions disabled, configuration type 7
Oct 27 21:56:23 archer ntfs-3g[3206]: Unmounting /dev/sdb1 ()
Last edited by Skitter (2013-10-27 21:43:32)

I think this is because the mount command exits, so the daemon is then considered dead (or completed). But I am not entirely sure about this.
A better solution would be to simply make an entry in your fstab with the noauto,x-systemd.automount,nofail options. This would essentially achieve what you are after I think. You could also make actualy systemd.mount and systemd.automount units as well, though these would automagically be generated by an entry in your fstab.
If you are unsure of what exactly to put in native systemd units, you can always see what systemd does in /run/systemd/generators. In fact, if you put a fstab entry for this ntfs-3g mount, let it generate (ie reboot, or run the generator) then check out that directory, you can simply pull those units out of there, give them an [Install] section, and enable them.

[Solved] systemd - network-online.target inactive dead

Similar Messages

Maybe you are looking for