Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #206074

Re: systemd error

Show all headers | View raw

	Hi.

On Fri, Mar 08, 2019 at 04:00:05PM -0500, Default User wrote:
> Hi.  Got a (minor) systemd problem.
...
>            └─3684 /usr/sbin/minissdpd -i enp7s0 -i wlp6s0
...
> So, although the minissdpd.service unit is enables, it does not start
> automatically at boot, but will start manually using systemctl start/stop.

What is most likely happening at boot is that systemd tries to start
minissdpd before configuring interfaces enp7s0 and wlp6s0.
So it fails at boot, but works for manual restart because by then you
have both enp7s0 and wlp6s0 up and running.
Adding a dependency in the form of:

[Unit]
After=sys-subsystem-net-devices-enp7s0.device sys-subsystem-net-devices-wlp6s0.device
Requires=sys-subsystem-net-devices-enp7s0.device sys-subsystem-net-devices-wlp6s0.device

Should help with the issue.

Reco

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

systemd error Default User <hunguponcontent@gmail.com> - 2019-03-08 22:20 +0100
  Re: systemd error Reco <recoverym4n@enotuniq.net> - 2019-03-09 08:50 +0100
    Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-10 03:50 +0100
      Re: systemd error Reco <recoverym4n@enotuniq.net> - 2019-03-10 08:40 +0100
        Re: systemd error Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2019-03-10 12:10 +0100
          Re: systemd error Curt <curty@free.fr> - 2019-03-10 14:30 +0100
            Re: systemd error Reco <recoverym4n@enotuniq.net> - 2019-03-10 16:30 +0100
              Re: systemd error Curt <curty@free.fr> - 2019-03-10 17:50 +0100
              Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-10 17:50 +0100
                Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-10 20:50 +0100
                Re: systemd error Reco <recoverym4n@enotuniq.net> - 2019-03-10 21:10 +0100
                Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-11 05:00 +0100
                Re: systemd error Sven Hartge <sven@svenhartge.de> - 2019-03-11 08:50 +0100
                Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-11 13:50 +0100
                Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-13 06:00 +0100
                Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-13 06:10 +0100
                Re: systemd error <tomas@tuxteam.de> - 2019-03-13 09:50 +0100
                Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-13 14:30 +0100
                Re: systemd error Dan Ritter <dsr@randomstring.org> - 2019-03-13 16:10 +0100
                Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-13 19:20 +0100
                Re: systemd error deloptes <deloptes@gmail.com> - 2019-03-13 21:30 +0100
                Re: systemd error <tomas@tuxteam.de> - 2019-03-13 22:00 +0100
  Re: systemd error Curt <curty@free.fr> - 2019-03-09 10:30 +0100
    Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-10 03:40 +0100
      Re: systemd error Curt <curty@free.fr> - 2019-03-10 10:40 +0100
        Re: systemd error Cindy-Sue Causey <butterflybytes@gmail.com> - 2019-03-10 15:10 +0100

csiph-web