Bug ID 1190201
Summary ip statement doesn't work correctly during system boot
Classification openSUSE
Product openSUSE Distribution
Version Leap 15.3
Hardware x86-64
OS openSUSE Leap 15.3
Status NEW
Severity Normal
Priority P5 - None
Component Network
Assignee screening-team-bugs@suse.de
Reporter lopa@mailbox.org
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

The mediatomb UPnP server from the Packman Repository has a mediatomb.service
file and should be started by systemd at system boot time.

Content of mediatomb.service:
  [Unit]
  Description=mediatomb UPnP AV MediaServer
  After=network-online.target
  After=remote-fs.target
  After=time-sync.target

  [Service]
  EnvironmentFile=-/etc/mediatomb.conf
  ExecStart=/usr/lib/mediatomb
  ExecReload=/usr/bin/kill -HUP 

  [Install]
  WantedBy=multi-user.target

The exec file /usr/lib/mediatomb contains the following lines:
  IFACE_IP="`ip -oneline -family inet addr show dev ${MT_INTERFACE} | sed -n
's@\(^[0-9]\+:[[:blank:]]\+[^[:blank:]]\+[[:blank:]]\+inet[[:blank:]]\+\)\([^/]\+\)\(.*\)@\2@p'`"
  if test -z "${IFACE_IP}"
  then
      echo "No IPv4 found on MT_INTERFACE ${MT_INTERFACE}"
      exit 1
  fi

The startup fails and the message "No IPv4 found ..." is written to the
syslog,. but a later manual start with "systemctl start mediatomb" is
successful. Additional echo statements in the file /usr/lib/mediatomb did show,
that MT_INTERFACE is set correctly to eth0, but the statement "ip -oneline
-family inet addr show dev ${MT_INTERFACE}" returns nothing. Later, when the
system is up and running, it returns:

2: eth0    inet 192.168.1.17/24 brd 192.168.1.255 scope global eth0\      
valid_lft forever preferred_lft forever

It seems, that ip doesn't work correctly after the network-online.target. It
used to work in Leap until one of the last updates.


You are receiving this mail because: