[Spce-user] mr5.5.3 RTPengine not installed after upgrade

Alex Lutay alutay at sipwise.com
Mon Apr 9 05:33:37 EDT 2018


There is known race condition might happens when both rtpengine kernel
module and linux kernel are upgraded simultaneously. To confirm it I
need to see the complete upgrade.log, you can send it to me privately.

JFYI, the situation here has been improved already in mr6.2+
> https://github.com/sipwise/rtpengine/commit/a76b474127e4b744bd7256b373e2687d1c9c6d64and will be considered for backporting to mr5.5 LTS if no issues found.

So far you can execute 'sudo dkms autoinstall' which should trigger DKMS
to install rtpending kernel module for the current kernel.

Also "sudo dkms status" should tells you:
> ngcp-rtpengine, some_version, 4.9.0-6-amd64, x86_64: installed
for all the kernels are currently installed.

Thank you for reporting it here!

On 04/09/2018 10:13 AM, Henk wrote:
> After upgrading from to 5.5.3 from 5.5.x I noticed the following message
> in the iptables file:
> # WARNING: Kernel module "xt_RTPENGINE" not loaded!
> Doing some research, it seems there are 2 kernel versions in the
> /lib/modules directory:
> 4.9.0-5-amd64 with xt_RTPENGINE.ko in the updates directory
> 4.9.0-6-amd64 with no update directory
> This is the build log:
> Building module:
> cleaning build area...
> make -j2 KERNELRELEASE=4.9.0-5-amd64 -C /lib/modules/4.9.0-5-amd64/build
> M=/var/lib/dkms/ngcp-rtpengine/
> cleaning build area...
> DKMS: build completed.
> Running module version sanity check.
>  - Original module
>    - No original module exists within this kernel
>  - Installation
>    - Installing to /lib/modules/4.9.0-5-amd64/updates/dkms/
> So the newly build module is in the old kernel directory.
> What is the best way to solve this?

Alex Lutay

More information about the Spce-user mailing list