Package: systemd
Version: 215-5
Severity: normal

If networking.service wasn't activated (due to, for instance, no symlink in
/etc/init.d/networking not having start symlinks in any /etc/rc*.d/), then
there is no /run/network directory created.

However, systemd still instantiate and starts ifup@*.service units, which are
failing due to the lack of /run/network directory. Consequence is that the
system is seen as being in degraded mode.

We can make ifup@ template have a Conditional Path on /run/network.


Example of $ sudo systemctl status [email protected][email protected] - ifup for wlan0
   Loaded: loaded (/lib/systemd/system/[email protected]; static)
Active: failed (Result: exit-code) since ven. 2014-11-14 08:53:56 CET; 2h 53min ago
 Main PID: 652 (code=exited, status=1/FAILURE)

nov. 14 08:53:56 tidus ifup[652]: /sbin/ifup: failed to open lockfile /run/network/.ifstate.lock: No such file or directory nov. 14 08:53:56 tidus ifup[653]: /sbin/ifup: failed to open lockfile /run/network/.ifstate.lock: No such file or directory nov. 14 08:53:56 tidus systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE nov. 14 08:53:56 tidus systemd[1]: [email protected]: control process exited, code=exited status=1 nov. 14 08:53:56 tidus ifdown[664]: /sbin/ifdown: failed to open lockfile /run/network/.ifstate.lock: No such file or directory nov. 14 08:53:56 tidus systemd[1]: [email protected]: control process exited, code=exited status=1
nov. 14 08:53:56 tidus systemd[1]: Failed to start ifup for wlan0.
nov. 14 08:53:56 tidus systemd[1]: Unit [email protected] entered failed state.


-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- no debconf information


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to