[SR-Users] rtpengine upgrade fails

[Juha Heinanen]

On 07/16/14 14:57:59, Richard Fuchs wrote:

> Hard to tell without further information. Perhaps dist-upgrade tried to
> upgrade the daemon after the kernel module was removed but before the
> new module was installed? Did you install the kernel module through
> dkms? Do you have the metapackage installed? You can check the dpkg.log
> and dkms log files for more info.

Richard,

Somehow I missed your above reply in July.  I have the metapackage
installed.

Now I made another dist-upgrade upgrading rtpengine from
3.3.0.0+0~mr3.4.1.0 to 3.3.0.0+0~mr3.5.0. Indeed dist-upgrade tries to
setup daemon after the kernel module was removed but before new kernel
module was installed.

Should dependency on ngcp-rtpengine-kernel-dkms be added to
ngcp-rtpengine-daemon in control file?

-- Juha

-------------------------------------------------------

# apt-get dist-upgrade
...

Preparing to replace ngcp-rtpengine-daemon 3.3.0.0+0~mr3.4.1.0 (using .../ngcp-rtpengine-daemon_3.3.0.0+0~mr3.5.0.0_amd64.deb) ...
Unpacking replacement ngcp-rtpengine-daemon ...
Preparing to replace ngcp-rtpengine-iptables 3.3.0.0+0~mr3.4.1.0 (using .../ngcp-rtpengine-iptables_3.3.0.0+0~mr3.5.0.0_amd64.deb) ...
Unpacking replacement ngcp-rtpengine-iptables ...
Preparing to replace ngcp-rtpengine-kernel-dkms 3.3.0.0+0~mr3.4.1.0 (using .../ngcp-rtpengine-kernel-dkms_3.3.0.0+0~mr3.5.0.0_all.deb) ...
Stopping RTP/media proxy: rtpengine-daemon.

-------- Uninstall Beginning --------
Module:  rtpengine
Version: 3.3.0.0+0~mr3.4.1.0
Kernel:  3.2.0-4-amd64 (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

xt_MEDIAPROXY.ko:
 - Uninstallation
   - Deleting from: /lib/modules/3.2.0-4-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod.........

DKMS: uninstall completed.

------------------------------
Deleting module version: 3.3.0.0+0~mr3.4.1.0
completely from the DKMS tree.
------------------------------
Done.
Unpacking replacement ngcp-rtpengine-kernel-dkms ...
Preparing to replace ngcp-rtpengine 3.3.0.0+0~mr3.4.1.0 (using .../ngcp-rtpengine_3.3.0.0+0~mr3.5.0.0_all.deb) ...
Unpacking replacement ngcp-rtpengine ...
Preparing to replace ngcp-rtpengine-dev 3.3.0.0+0~mr3.3.1.0 (using .../ngcp-rtpengine-dev_3.3.0.0+0~mr3.5.0.0_all.deb) ...
Unpacking replacement ngcp-rtpengine-dev ...
Preparing to replace ngcp-rtpengine-kernel-source 3.3.0.0+0~mr3.4.1.0 (using .../ngcp-rtpengine-kernel-source_3.3.0.0+0~mr3.5.0.0_all.deb) ...
Unpacking replacement ngcp-rtpengine-kernel-source ...
Setting up ngcp-rtpengine-daemon (3.3.0.0+0~mr3.5.0.0) ...
Restarting RTP/media proxy: ngcp-rtpengine-daemonFATAL: Module xt_MEDIAPROXY not found.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
FAILED TO CREATE KERNEL TABLE 0, KERNEL FORWARDING DISABLED
invoke-rc.d: initscript ngcp-rtpengine-daemon, action "restart" failed.
dpkg: error processing ngcp-rtpengine-daemon (--configure):
 subprocess installed post-installation script returned error exit status 255
Setting up ngcp-rtpengine-iptables (3.3.0.0+0~mr3.5.0.0) ...
Setting up ngcp-rtpengine-kernel-dkms (3.3.0.0+0~mr3.5.0.0) ...
Creating symlink /var/lib/dkms/rtpengine/3.3.0.0+0~mr3.5.0.0/source ->
                 /usr/src/rtpengine-3.3.0.0+0~mr3.5.0.0

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
make KERNELRELEASE=3.2.0-4-amd64 -C /lib/modules/3.2.0-4-amd64/build M=/var/lib/dkms/rtpengine/3.3.0.0+0~mr3.5.0.0/build MEDIAPROXY_VERSION=3.3.0.0+0~mr3.5.0.0.......
cleaning build area....

DKMS: build completed.

xt_MEDIAPROXY:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.2.0-4-amd64/updates/dkms/

depmod....

DKMS: install completed.
...