Ubuntu 20.04 focal: xt_RTPENGINE.ko not copied to /lib/modules

[hb9eue]

Hi

I installed rtpengine twice. Once on a ARM pine64 running Armbian to mess around ;-).
using dpkg-buildpackage --no-sign worked flawlessly, building debian packages which installed kernel module and everything worked on 2nd try (after figuring out --no-sign).

Now onto production machine under Ubuntu 20.04 foca.

I had to mess around with package names slightly different that on 'vanilla' debian. But I'm quite confident, all dependencies are met and the correct kernel header are installed.

I had to use dpkg-buildpackage -d --no-sign to not check packages as it would stumble over packages whose names don't match.

*.deb files are built and I see no obvious errors.

But ngcp-rtpengine-kernel-dkms_11.3.0.0+0~mr11.3.0.0_all.deb fails to install, most probably because of:

ngcp-rtpengine-iptables-setup[933809]: modprobe: FATAL: Module xt_RTPENGINE not found in directory /lib/modules/5.4.0-132-generic

uname -a

Linux rtpengine 5.4.0-132-generic

Yes that matches, it's the right kernel and correct path.

Did a depmod -a but that is useless, as the module is not being copied.

The module is built, and can be loaded successfully.

insmod git/rtpengine/kernel-module/xt_RTPENGINE.ko

Could anyone hint me to why the installing of the deb dkms file fails to copy the module to the /lib/modules directory?

-Benoît-

[rfuchs]

Have you applied the backports script for focal?

[hb9eue]

Thank you for the quick reply

No, but thank you for the hint, looking for those information (may I ask where to find it)?
Of would there be a PPA?

I guess I found it: pkg/deb/backports/focal

[hb9eue]

I guess those patches do not work anymore. I just checked out rtpengine again to have a clean install...

~/git/rtpengine/pkg/deb# backports/focal 
cp: cannot stat 'debian': No such file or directory
sed: can't read focal/control: No such file or directory
sed: can't read focal/control: No such file or directory
sed: can't read focal/rules: No such file or directory
sed: can't read focal/rules: No such file or directory
sed: can't read focal/rules: No such file or directory
backports/focal: line 24: focal/rules: No such file or directory
cp: cannot create regular file 'focal/': Not a directory
cp: cannot create regular file 'focal/': Not a directory
cp: cannot create regular file 'focal/': Not a directory
sed: can't read focal/source/lintian-overrides: No such file or directory
sed: can't read focal/control: No such file or directory
sed: can't read focal/control: No such file or directory
sed: can't read focal/control: No such file or directory
sed: can't read focal/rules: No such file or directory
sed: can't read focal/rules: No such file or directory
sed: can't read focal/rules: No such file or directory
sed: can't read focal/rules: No such file or directory
sed: can't read focal/rules: No such file or directory
sed: can't read focal/rules: No such file or directory
rm: cannot remove 'focal/rtpengine-iptables.dirs': No such file or directory
rm: cannot remove 'focal/rtpengine-iptables.install': No such file or directory
backports/focal: line 65: focal/rules: No such file or directory
WARN: wrap-and-sort (Debian package devscripts) not available.

[hb9eue]

I guess, those errors can be ignored...

[Fri Feb 24 14:51:04 2023] Registering xt_RTPENGINE module - version 11.3.0.0+0~mr11.3.0.0
[Fri Feb 24 14:51:04 2023] Unregistering xt_RTPENGINE module

But hunting down the next issue:

Starting NGCP RTP/media Proxy Daemon...
ngcp-rtpengine-daemon.service: Failed to apply ambient capabilities (before UID change): Operation not permitted
ngcp-rtpengine-daemon.service: Failed at step CAPABILITIES spawning /usr/bin/rtpengine: Operation not permitted
ngcp-rtpengine-daemon.service: Main process exited, code=exited, status=218/CAPABILITIES
ngcp-rtpengine-daemon.service: Failed with result 'exit-code'.
Failed to start NGCP RTP/media Proxy Daemon.

[hb9eue]

Solution from #1605 by commenting out that line seems to work for me. I would have prefered to be able to manage capabilities.

[rfuchs]

The MO for the backports script is: run generator.sh, then apply backports script, then replace the upper-level debian/ with the generated release-specific directory.

[rfuchs]

Solution from #1605 by commenting out that line seems to work for me. I would have prefered to be able to manage capabilities.

I'm still not sure where this is coming from because systemd should be able to set the capabilities just fine, unless running in some sort of non-standard environment maybe?