Hello,
I noticed that , with kamailio ver. 5.2.1 starting with empty rtpengine table causes strange messages in kamailio and it doesn't start
modparam("rtpengine", "db_url", "text:///tmp/kamailio/dbtext") cat /tmp/kamailio/dbtext/rtpengine id(int,auto) setid(int) url(string) weight(int) disabled(int) stamp(int)
0(2856) WARNING: tm [tm.c:760]: mod_init(): reparse_on_dns_failover is enabled on a multihomed host -- check the readme of tm module! 0(2856) WARNING: rtpengine [rtpengine_db.c:100]: rtpp_load_db(): No rtpproxy instances in database 0(2856) ERROR: rtpengine [rtpengine.c:2768]: select_rtpp_set(): no rtpp_set_list->rset_first 0(2856) NOTICE: rtpengine [rtpengine.c:1664]: mod_init(): Default rtpp set 0 NOT found 1(2857) NOTICE: usrloc [udomain.c:434]: preload_udomain(): filtered by server_id[0] 2(2858) ERROR: rtpengine [rtpengine.c:1722]: build_rtpp_socks(): no more pkg memory for rtpp_socks 2(2858) ERROR: <core> [core/sr_module.c:847]: init_mod_child(): error while initializing module rtpengine (/usr/lib/x86_64-linux-gnu/kamailio/modules/rtpengine.so) (idx: 2 rank: 2 desc: [udp receiver child=1 sock=172.28.0.120:5060]) 2(2858) ERROR: <core> [core/pt.c:342]: fork_process(): init_child failed for process 2, pid 2858, "udp receiver child=1 sock=172.28.0.120:5060" 2(2858) CRITICAL: <core> [main.c:1633]: main_loop(): Cannot fork 4(2860) ERROR: rtpengine [rtpengine.c:1722]: build_rtpp_socks(): no more pkg memory for rtpp_socks 4(2860) ERROR: <core> [core/sr_module.c:847]: init_mod_child(): error while initializing module rtpengine (/usr/lib/x86_64-linux-gnu/kamailio/modules/rtpengine.so) (idx: 4 rank: 4 desc: [udp receiver child=3 sock=172.28.0.120:5060]) 4(2860) ERROR: <core> [core/pt.c:342]: fork_process(): init_child failed for process 4, pid 2860, "udp receiver child=3 sock=172.28.0.120:5060" 4(2860) CRITICAL: <core> [main.c:1633]: main_loop(): Cannot fork
any hint on what could be wrong ? (5.2.0 works perfectly) many thanks!
Paolo
Hello, going back to 5.2.0 is actually not possible anymore if you didn't save locally the distro packages because right now on the repos only Kamailio 5.2.1 is available
Il giorno gio 31 gen 2019 alle ore 13:13 * Paolo Visintin - evosip.cloud paolo.visintin@evosip.cloud ha scritto:
Hello,
I noticed that , with kamailio ver. 5.2.1 starting with empty rtpengine table causes strange messages in kamailio and it doesn't start
modparam("rtpengine", "db_url", "text:///tmp/kamailio/dbtext") cat /tmp/kamailio/dbtext/rtpengine id(int,auto) setid(int) url(string) weight(int) disabled(int) stamp(int)
0(2856) WARNING: tm [tm.c:760]: mod_init(): reparse_on_dns_failover is enabled on a multihomed host -- check the readme of tm module! 0(2856) WARNING: rtpengine [rtpengine_db.c:100]: rtpp_load_db(): No rtpproxy instances in database 0(2856) ERROR: rtpengine [rtpengine.c:2768]: select_rtpp_set(): no rtpp_set_list->rset_first 0(2856) NOTICE: rtpengine [rtpengine.c:1664]: mod_init(): Default rtpp set 0 NOT found 1(2857) NOTICE: usrloc [udomain.c:434]: preload_udomain(): filtered by server_id[0] 2(2858) ERROR: rtpengine [rtpengine.c:1722]: build_rtpp_socks(): no more pkg memory for rtpp_socks 2(2858) ERROR: <core> [core/sr_module.c:847]: init_mod_child(): error while initializing module rtpengine (/usr/lib/x86_64-linux-gnu/kamailio/modules/rtpengine.so) (idx: 2 rank: 2 desc: [udp receiver child=1 sock=172.28.0.120:5060]) 2(2858) ERROR: <core> [core/pt.c:342]: fork_process(): init_child failed for process 2, pid 2858, "udp receiver child=1 sock=172.28.0.120:5060" 2(2858) CRITICAL: <core> [main.c:1633]: main_loop(): Cannot fork 4(2860) ERROR: rtpengine [rtpengine.c:1722]: build_rtpp_socks(): no more pkg memory for rtpp_socks 4(2860) ERROR: <core> [core/sr_module.c:847]: init_mod_child(): error while initializing module rtpengine (/usr/lib/x86_64-linux-gnu/kamailio/modules/rtpengine.so) (idx: 4 rank: 4 desc: [udp receiver child=3 sock=172.28.0.120:5060]) 4(2860) ERROR: <core> [core/pt.c:342]: fork_process(): init_child failed for process 4, pid 2860, "udp receiver child=3 sock=172.28.0.120:5060" 4(2860) CRITICAL: <core> [main.c:1633]: main_loop(): Cannot fork
any hint on what could be wrong ? (5.2.0 works perfectly) many thanks!
Paolo _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
On Fri, Feb 01, 2019 at 05:44:45PM +0100, Enrico Bandiera wrote:
Hello, going back to 5.2.0 is actually not possible anymore if you didn't save locally the distro packages because right now on the repos only Kamailio 5.2.1 is available
I made the same conclusion with an upgrade to 5.1.6 from 5.1.4. A rollback wasn't possible. Looking into aptly or debmirror to create a local repository with history.
But maybe the maintainer can keep older versions?
Hi there,
Is in my TODO list to integrate aptly into our deb build environment. https://github.com/sipwise/kamailio-deb-jenkins/issues/9
On Mon, 4 Feb 2019 at 11:09, Daniel Tryba d.tryba@pocos.nl wrote:
But maybe the maintainer can keep older versions?
If you really need them, jenkins keeps the artifacts, so you just need to get the ones you want, for instance: https://kamailio.sipwise.com/job/kamailio52-binaries/architecture=amd64,dist...
On Mon, Feb 04, 2019 at 01:33:32PM +0100, Victor Seva wrote:
Hi there,
Is in my TODO list to integrate aptly into our deb build environment. https://github.com/sipwise/kamailio-deb-jenkins/issues/9
Okay, good to know that others see this as a "problem". I'll wait patiently for this enhancement.
good to know for the future implementation and super for the artifacts!
Anyone else experienced the bug regarding a empty rtpengine table causing non kamailio starting ?
Many thanks
Il giorno lun 4 feb 2019 alle ore 17:22 Daniel Tryba d.tryba@pocos.nl ha scritto:
On Mon, Feb 04, 2019 at 01:33:32PM +0100, Victor Seva wrote:
Hi there,
Is in my TODO list to integrate aptly into our deb build environment. https://github.com/sipwise/kamailio-deb-jenkins/issues/9
Okay, good to know that others see this as a "problem". I'll wait patiently for this enhancement.
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
I noticed it as well when switching from 5.2.0 to 5.2.1 using the docker images, but got around it by adding a row with localhost as the destination. Kamailio did start but wasnt able to connect, which was fine.
On Mon, 4 Feb 2019 at 18:22, * Paolo Visintin - evosip.cloud paolo.visintin@evosip.cloud wrote:
good to know for the future implementation and super for the artifacts!
Anyone else experienced the bug regarding a empty rtpengine table causing non kamailio starting ?
Many thanks
Hello Grant,
Can you elaborate more on your solution?
Thanks! Regards,
David Villasmil email: david.villasmil.work@gmail.com phone: +34669448337
On Tue, Feb 5, 2019 at 7:05 AM Grant Bagdasarian grantbagdasarian@gmail.com wrote:
I noticed it as well when switching from 5.2.0 to 5.2.1 using the docker images, but got around it by adding a row with localhost as the destination. Kamailio did start but wasnt able to connect, which was fine.
On Mon, 4 Feb 2019 at 18:22, * Paolo Visintin - evosip.cloud paolo.visintin@evosip.cloud wrote:
good to know for the future implementation and super for the artifacts!
Anyone else experienced the bug regarding a empty rtpengine table causing non kamailio starting ?
Many thanks
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-
* Paolo Visintin - evosip.cloud -
Daniel Tryba -
David Villasmil -
Enrico Bandiera -
Grant Bagdasarian -
Victor Seva