I updated my 13.1 ‘server’ 2015-11-07 to Leap 42.1. The update was ~ok and ez-ipupdate was working. Today 2015-11-10 I did a zypper up and received release 291.2 of ez.ipupdate.
xxxx:/etc # rpm -qi ez-ipupdate
Name : ez-ipupdate
Version : 3.0.11b8
Release : 291.2
Architecture: x86_64
.....
ez-ipupdate dident work after that.
A ‘systemctl status ez-update’ and journal gave me:
....
nov 10 11:52:58 xxxx systemd[4910]: Failed at step EXEC spawning /usr/sbin/ez-ipupdate: No such file or directory
-- Subject: Process /usr/sbin/ez-ipupdate could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /usr/sbin/ez-ipupdate could not be executed and failed.
--
-- The error number returned while executing this process is 2.
nov 10 11:52:58 xxxx systemd[1]: Failed to reset devices.list on /user.slice: Invalid argument
nov 10 11:52:58 xxxx systemd[1]: Failed to start Ez-ipupdate Check and update your IP to dynamic DNS Server.
-- Subject: Unit ez-ipupdate.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit ez-ipupdate.service has failed.
....
I tried to delete and re-install the release in Leap 42.1 (291.2) several times and even rebooted but no luck.
I went back to the release in 13.1:
[FONT=arial]xxxx:/etc # rpm -qi ez-ipupdate
Name : ez-ipupdate
Version : 3.0.11b8
Release : 284.1.2
Architecture: x86_64
....
And everything works fine. I have no idea if this is because a upgrade from 13.1 ->42.1. Maybe ez-ipupdate release 291.2
works fine in a new installation of 42.1.
I’m going to wildly speculate that the reason why your ez-ipupdate failed is due to the change in how the network interfaces are named.
You should be able to verify by inspecting your ez-ipupdate configuration settings to see if they are using the old interface names based on manufacturer names or the “new” LEAP method which is to use the old eth0, wlan0 type naming.
If that is the issue, then you’ll probably want to force re-install the application which should replace the old configuration file with a new, default configuration file you’ll need to re-configure.
Tanks for comment. The Bug is accepted and solved already.
Yes I was checking and the Nic name was/is eth0. I shows me something else that my servers is probably a upgrade from 12.3 (older then I remember(witch other thing shows as well)). Wasn’t it in systemd/openSuse 13.1 that ~enp""" was introduced? I think I have a weak memory when made a fresh install with 13.1 on my PC that I was asking about this in the forum (2013) :).
As a distro implementing state of art, openSUSE until 13.2 made the network interface naming changes as recommended upstream.
As a distro based on the more staid SLE*, LEAP is based on a core that still hadn’t implemented the change.