Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RTP Engine not start on clear install version 3.4 #2450

Open
1 of 6 tasks
gmoreno90 opened this issue Dec 11, 2023 · 7 comments
Open
1 of 6 tasks

RTP Engine not start on clear install version 3.4 #2450

gmoreno90 opened this issue Dec 11, 2023 · 7 comments
Labels
+bug Bug *tempest* IvozProvider 4.x Tempest Release

Comments

@gmoreno90
Copy link

gmoreno90 commented Dec 11, 2023

Description

When I install the version 3.4 on a new server, the RTP engine not start.
to reproduce only need to install a new server with version 3.4 and check the instalation logs you can see that the RTP Engine was not install becouse not found

then when restart and check the status of rtpengine.service:

root@ivozprovider34-01:~# systemctl status rtpengine.service
● rtpengine.service - RTPEngine Mediaproxy
     Loaded: loaded (/lib/systemd/system/rtpengine.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Mon 2023-12-11 14:58:53 CET; 1min 8s ago
    Process: 723 ExecStartPre=/usr/sbin/iptables -D INPUT -p udp -j RTPENGINE --id 0 (code=exited, status=2)
    Process: 725 ExecStart=/usr/sbin/rtpengine --config-file /etc/rtpengine/rtpengine.conf (code=exited, status=255/EXCEPTION)
    Process: 726 ExecStopPost=/usr/sbin/iptables -D INPUT -p udp -j RTPENGINE --id 0 (code=exited, status=2)
    Process: 728 ExecStopPost=/bin/bash -c /bin/echo del 0 > /proc/rtpengine/control (code=exited, status=1/FAILURE)
        CPU: 56ms

Dec 11 14:58:53 ivozprovider34-01 systemd[1]: rtpengine.service: Scheduled restart job, restart counter is at 5.
Dec 11 14:58:53 ivozprovider34-01 systemd[1]: Stopped RTPEngine Mediaproxy.
Dec 11 14:58:53 ivozprovider34-01 systemd[1]: rtpengine.service: Start request repeated too quickly.
Dec 11 14:58:53 ivozprovider34-01 systemd[1]: rtpengine.service: Failed with result 'exit-code'.
Dec 11 14:58:53 ivozprovider34-01 systemd[1]: Failed to start RTPEngine Mediaproxy.

  • IvozProvider version: 3.4 holliday

  • Related sections:

    • SIP & Telephony
    • vPBX Functionalities
    • Billing & Invoicing
    • Web Interface
    • API
    • Other

Troubleshooting

Manual install of headers and the reboot, after that the rtpengine service starts fine

apt-get install linux-image-amd64 linux-headers-amd64

Additional Information

Tested on different providers (vultr, digitalocean and clouding.io) whith the same results

@Kaian
Copy link
Member

Kaian commented Dec 12, 2023

Hi!

Thanks for reporting and following provided templates!

The machine requires a reboot after initial installation in order to load the kernel module xt_RTPENGINE.
Check last green box in the docs: https://irontec.github.io/ivozprovider/en/artemis/basic_concepts/installation/debian_install.html

Does this problem persist after rebooting without installing any additional packages?

Best Regards

@gmoreno90
Copy link
Author

Hi Kaian,
I can confirm that I follow that steps for holliday version https://irontec.github.io/ivozprovider/en/halliday/basic_concepts/installation/debian_install.html

I reboot after instalation as the documentation mentionen and have the same issue. The only way to solve is installing manual the packages.

Best Regards

@Kaian
Copy link
Member

Kaian commented Dec 12, 2023

Ok, Thanks for the input.

One last question, is this an ISO install or using apt with Irontec Debian repositories?

Best regards,

@gmoreno90
Copy link
Author

Hi, i'm using apt with Irontec Debian repositories. tell me if need more information.

Many thanks in advance
Gon

@gmoreno90
Copy link
Author

Hi, the problem persist, please could you tell us an stimation when will be solve or prioritize?
Many thanks in advance
Gon

@Kaian
Copy link
Member

Kaian commented Feb 29, 2024

Hi!

There is no current ETA for the resolution of this issue.

I think the best approach will be to add linux-image-amd64 linux-headers-amd64 as ivozprovider-rtpengine package dependencies and build the kernel module for all installed kernels (running, latest, ...).

Well try to add this for the next minor release, but as there are an existing manual workaround to fix the problem, we'll address other bugs first.

Regards

@gmoreno90
Copy link
Author

Hi Kaian!
yes many thanks! for my site no worry, I'm thinking only in new installations that not always check the open reported issues.

Best regards
Gon

@Kaian Kaian added +bug Bug *tempest* IvozProvider 4.x Tempest Release labels Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
+bug Bug *tempest* IvozProvider 4.x Tempest Release
Development

No branches or pull requests

2 participants