sr-users February 2021

sr-users@lists.kamailio.org

56 participants
81 discussions

Runnning kamailio (docker) with remote connection with MYSQL (docker) fails on start/restart due to socket or database connection
by Nuñez, Mario 16 Feb '21

16 Feb '21

Hi, I am running docker with this: https://hub.docker.com/layers/kamailio/kamailio/5.4.3-trusty/images/sha256-… and https://hub.docker.com/layers/mysql/library/mysql/8.0.23/images/sha256-8708… I made some configurations in Kamailio container: /etc/default/kamailio RUN_KAMAILIO=yes USER=kamailio GROUP=kamailio CFGFILE=/etc/kamailio/kamailio.cfg DUMP_CORE=yes /etc/kamailio/kamailio.cfg #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB /etc/kamailio/kamctlrc SIP_DOMAIN=kamailio.org DBENGINE=MYSQL DBHOST=172.19.0.3 DBPORT=3306 DBNAME=kamailio DBRWUSER="kamailio" DBRWPW="kamailiorw" DBROUSER="kamailioro" DBROPW="kamailioro" DBACCESSHOST=172.19.0.5 DBROOTUSER="root" DBROOTPW="whatever" CHARSET="latin1" USERCOL="user" Then I run creation of database: /usr/sbin/kamdbctl create All was ok so I can see in MYSQL database: +------------------+------------+-----------------------+ | user | host | plugin | +------------------+------------+-----------------------+ | root | % | mysql_native_password | | kamailio | 172.19.0.3 | mysql_native_password | | kamailioro | 172.19.0.3 | mysql_native_password | | kamailio | 172.19.0.5 | mysql_native_password | | kamailioro | 172.19.0.5 | mysql_native_password | | kamailio | localhost | mysql_native_password | | kamailioro | localhost | mysql_native_password | | mysql.infoschema | localhost | caching_sha2_password | | mysql.session | localhost | caching_sha2_password | | mysql.sys | localhost | caching_sha2_password | | root | localhost | mysql_native_password | +------------------+------------+-----------------------+ At this point, if I try to restart kamailio i get an error and container will never go up again, so I had to delete it and restart the whole installation and configuration process. Log details are: ==========================================ON RESTART KAMAILIO FROM CONTAINER CONSOLE: Listening on udp: 127.0.0.1:5060 udp: 172.17.0.4:5060 tcp: 127.0.0.1:5060 tcp: 172.17.0.4:5060 Aliases: tcp: mykamailio:5060 tcp: localhost:5060 udp: mykamailio:5060 udp: localhost:5060 0(1) INFO: <core> [core/tcp_main.c:4984]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(1) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 0(1) INFO: <core> [main.c:2834]: main(): processes (at least): 33 - shm size: 67108864 - pkg size: 8388608 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 21(28) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/28 23(30) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 0(1) ALERT: <core> [main.c:774]: handle_sigs(): child process 205 exited normally, status=255 0(1) INFO: <core> [main.c:802]: handle_sigs(): terminating due to SIGCHLD 2(9) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 1(8) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 3(10) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 4(11) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 6(13) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 5(12) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 7(14) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 10(17) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 12(19) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 14(21) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 29(36) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 24(31) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 28(35) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 15(22) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 19(26) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 13(20) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 17(24) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 8(15) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 23(30) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 22(29) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 21(28) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 26(33) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 20(27) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 31(38) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 32(39) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 9(16) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 30(37) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 11(18) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 16(23) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 27(34) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 18(25) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 25(32) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 0(1) ERROR: ctl [ctl.c:390]: mod_destroy(): ERROR: ctl: could not delete unix socket /var/run/kamailio//kamailio_ctl: No such file or directory (2) 0(1) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ==========================================SO CONTAINER WAS DOWN, AND THEN IF I TRY TO START CONTAINER AGAIN: Listening on udp: 127.0.0.1:5060 udp: 172.17.0.4:5060 udp: 172.19.0.5:5060 tcp: 127.0.0.1:5060 tcp: 172.17.0.4:5060 tcp: 172.19.0.5:5060 Aliases: tcp: mykamailio:5060 tcp: localhost:5060 udp: mykamailio:5060 udp: localhost:5060 0(1) INFO: <core> [core/tcp_main.c:4984]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(1) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 0(1) INFO: auth [auth_mod.c:346]: mod_init(): qop set, but nonce-count (nonce_count) support disabled 0(1) INFO: <core> [main.c:2834]: main(): processes (at least): 41 - shm size: 67108864 - pkg size: 8388608 0(1) ERROR: db_mysql [km_my_con.c:163]: db_mysql_new_connection(): driver error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) 0(1) ERROR: <core> [db.c:319]: db_do_init2(): could not add connection to the pool 0(1) ERROR: usrloc [dlist.c:852]: register_udomain(): failed to open database connection 0(1) ERROR: registrar [registrar.c:711]: domain_fixup(): failed to register domain 0(1) ERROR: <core> [core/route.c:1167]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:698 0(1) ERROR: <core> [core/rvalue.c:3869]: fix_rval_expr(): failure in cfg at line: 698 col: 22 0(1) ERROR: <core> [core/rvalue.c:3869]: fix_rval_expr(): failure in cfg at line: 698 col: 22 0(1) ERROR: <core> [core/route.c:1167]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:701 error -1 while trying to fix configuration 0(1) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ======================================================SO NO WAY TO GET IT UP. Any idea on what could be the problem? I tried giving permissions to some folders in Kamailio docker container: chown kamailio:kamailio /usr/sbin/kam* chmod 755 /usr/sbin/kam* chown -R kamailio:kamailio /etc/kamailio chmod -R 755 /etc/kamailio chown -R root:kamailio /var/run chmod -R 755 /var/run chown -R kamailio:kamailio /run/kamailio chown -R 755 /run/kamailio But had no effect... Thank you in advance. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional. Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes. Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.

1 0

Info: Kamailio presentations later today at ClueCon TGI
by Daniel-Constantin Mierla 16 Feb '21

16 Feb '21

Hello, short note to inform that later today will be 3 sessions related to Kamailio at ClueCon TGI (online event): * a workshop about basics of SIP routing with Kamailio * a presentation about DID routing with Kamailio * a presentation about outsourcing services from FreeSwitch to Kamailio The first two are done by me, the last one by Fred Posner. The event is free to attend, by participating to a video conference or watch the youtube stream -- more details at: * https://www.cluecon.com/ Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Funding: https://www.paypal.me/dcmierla

2 2

Re: [SR-Users] Advice on handling SIP trunk to a Perimeta SBC
by Björn Bylander 16 Feb '21

16 Feb '21

Hi again, I'm using Kamailio 5.3.2 by the way. Björn Bylander writes: > Hi, > > So I’m tasked with setting up a SIP trunk to a Perimeta SBC (https://www.metaswitch.com/products/perimeta-sbc). > > Apparently, > > Perimeta hides the topology of networks by rewriting or removing topology-sensitive information from SIP messages. By default, your Session Controller will make the following changes to SIP messages. > > > > The Session Controller generates new dialog identifiers (call-IDs, From tags and To tags) for each side of the call, so that it does not expose information about your core network to your access networks. > > The Session Controller strips Record-Route and Route information from the message. > > The Session Controller rewrites Contact and Via headers so that the source IP address is replaced with the local address of the outbound adjacency. > > The Session Controller replaces the IP addresses in c= lines in SDP with the addresses it has allocated for media forwarding. For more information on this, see Media addresses and gates. > > My problem is this: When the Perimeta SBC sends its first INVITE (I can't say anything about any succeeding INVITEs yet) it's added a Record-Route header with the "lr" parameter included which, as far as I can see makes Kamailio think it should use loose routing which is all well I think. But when the SBC sends an ACK for the "200 OK" from the Kamailio side it doesn't include any Route headers and I think that makes it hard for Kamailio (at least with the standard script which is basically what I'm using) to know where to relay the ACK, at least it makes the t_check_trans() call in WITHINDLG after 'is_method("ACK")' return false which makes the script ignore the ACK. > > Any thoughts or suggestions on how to handle this? > > Thanks in advance, > Björn Bylander

1 0

Kamailio v5.4.4 Released
by Daniel-Constantin Mierla 15 Feb '21

15 Feb '21

Hello, Kamailio SIP Server v5.4.4 stable release is out. This is a maintenance release of the latest stable branch, 5.4, that includes fixes since the release of v5.4.3. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.4.x. Deployments running previous v5.4.x versions are strongly recommended to be upgraded to v5.4.4. For more details about version 5.4.4 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2021/02/kamailio-v5-4-4-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

Releasing Kamailio v5.4.4
by Daniel-Constantin Mierla 15 Feb '21

15 Feb '21

Hello, I am considering to release Kamailio v5.4.4 sometime next week, likely on Monday, February 15, 2020. This is the usual heads up notification to see if anyone is aware of issues not yet reported to bug tracker and if yes, do it as soon as possible to give them a chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Funding: https://www.paypal.me/dcmierla

3 4

IMS-PSTN
by eyas barhouk 13 Feb '21

13 Feb '21

Hello dears I'm trying to build an IMS testbed based on kamailio and integrate it with the PSTN network, in order to do that I'm looking for AGCF,MGCF open source solution. Am I able to do the functionality of those nodes based on Kamailio,Asterisk or any other open source? thanks and regards Eyas

1 0

IMS-PSTN
by eyas37＠hotmail.com 12 Feb '21

12 Feb '21

1 0

basic help, In over my head in getting a webrtc up.
by Daniel Siemens 12 Feb '21

12 Feb '21

I am trying to get a webrtc setup going. Here is what I have I have asterisk server at 10.123.244.18. The webrtc works internally from the freepbx UCP application As well as the Raspberry phone allocation. This server doesn't have any nat on it all devices are on local / reouted networks. I have a Proxy server at 10.123.245.30 address. This server is located in AWS and has an elastic IP. On this server I have ngiinx that will load the raspberry phone up. What configuration do I need in kamailio and rtpengine to get this working. If I forward port 8089 in nginx to the /ws side on my asterisk server I can get a call to bridge but with no audio and the call end at 30 seconds when remote. It works internally fine. Likely beccuae the web browser can get to https://10.123.244.18:8089/ws ports fine. Thanks. ------------------------------------------------------------------ This email is intended solely for the use of the addressee and may contain information that is confidential, proprietary, or both. If you receive this email in error please immediately notify the sender and delete the email. ------------------------------------------------------------------

2 1

loose_route() does not find socket by name
by Juha Heinanen 12 Feb '21

12 Feb '21

I did more tests and found that loose_route() does not find socket by name given in ;sn param: Feb 12 10:40:59 lab /usr/bin/sip-proxy[16975]: WARNING: rr [loose.c:799]: rr_do_force_send_socket(): no socket found to match second RR (sip:tenantX.teams.tutpro.com:8007;transport=tls;r2=on;sn=ext_tls;lr;n1;savp=avp;pm=0) In config I have defined: listen=tls:192.x.x.x:8007 name "ext_tls" -- Juha

2 8

Kamailio Memory Leak
by Uttam Giri 11 Feb '21

11 Feb '21

Hi, We have observed increased memory utilization in Kamailio, It increases every day, even though traffic is not increased. We are using Kamailio+RTPEngine in our setup. Phone---->Kamailio+RTPEngine------>Asterisk /etc/kamailio# kamcmd mod.stats all shm Module: core { sip_msg_shm_clone(496): 542688 msg_lump_cloner(986): 178776 build_req_buf_from_sip_req(2218): 111968 xavp_new_value(116): 22240 counters_prefork_init(212): 39680 cfg_clone_str(130): 40 cfg_shmize(217): 712 main_loop(1313): 8 init_pt(107): 8 init_pt(106): 8 init_pt(105): 4592 register_timer(995): 192 init_tcp(4962): 8192 init_tcp(4956): 32768 init_tcp(4947): 8 init_tcp(4940): 8 init_tcp(4933): 8 init_tcp(4927): 8 init_tcp(4915): 8 init_avps(90): 8 init_avps(89): 8 timer_alloc(498): 48 init_dst_blacklist(438): 16384 init_dst_blacklist(430): 8 init_timer(267): 8 init_timer(266): 16384 init_timer(265): 8 init_timer(264): 8 init_timer(253): 8 init_timer(221): 8 init_timer(210): 278544 init_timer(209): 8 init_timer(197): 8 cfg_child_cb_new(829): 64 sr_cfg_init(361): 8 sr_cfg_init(354): 8 sr_cfg_init(347): 8 sr_cfg_init(335): 8 sr_cfg_init(323): 8 qm_shm_lock_init(1202): 8 Total: 1253464 } Module: sl { init_sl_stats_child(125): 5952 sl_startup(90): 8 init_sl_stats(110): 8 Total: 5968 } Module: siptrace { mod_init(319): 8 Total: 8 } Module: permissions { Total: 0 } Module: xlog { Total: 0 } Module: rtpengine { rtpp_function_call(2627): 1076024 shm_str_dup(779): 553016 rtpengine_hash_table_init(111): 14336 rtpengine_hash_table_init(96): 2048 rtpengine_hash_table_init(85): 1024 rtpengine_hash_table_init(76): 2048 rtpengine_hash_table_init(67): 2048 rtpengine_hash_table_init(58): 32 add_rtpengine_socks(975): 24 add_rtpengine_socks(956): 64 get_rtpp_set(870): 8 get_rtpp_set(861): 56 mod_init(1596): 8 mod_init(1589): 24 mod_init(1576): 8 mod_init(1569): 8 mod_init(1555): 16 Total: 1650792 } Module: pv { add_shvar(177): 8 add_shvar(170): 64 lock_set_alloc(66): 80 Total: 152 } Module: phonenum { Total: 0 } Module: textops { Total: 0 } Module: rtimer { Total: 0 } Module: tm { _reply_light(496): 1640 build_cell(334): 973848 relay_reply(2058): 69376 init_tm_stats_child(56): 7936 init_tmcb_lists(72): 16 init_tmcb_lists(70): 16 init_hash_table(482): 2097152 Total: 3149984 } Module: kex { pkg_proc_stats_init(79): 1488 Total: 1488 } Module: tmx { tmx_init_pretran_table(90): 256 Total: 256 } Module: utils { conf_init(552): 24 init_shmlock(134): 8 Total: 32 } Module: xhttp_prom { prom_metric_init(134): 8 Total: 8 } Module: dispatcher { ds_ht_init(89): 12288 reindex_dests(723): 768 mod_init(484): 80 ds_avl_insert(3621): 1712 pack_dest(411): 72 ds_ht_init(79): 32 ds_init_data(262): 16 ds_init_data(254): 16 mod_init(339): 8 mod_init(337): 8 ds_ping_active_init(138): 8 Total: 15008 } /etc/kamailio# kamcmd mod.stats all pkg Module: core { init_io_wait(469): 6192 init_modules(885): 16 rpc_hash_add(151): 1024 cnt_hash_add(394): 2048 add_callback(59): 168 register_select_table(458): 48 sr_wtimer_init(351): 136 cfg_new_group(79): 624 fix_sock_str(517): 1024 fix_sock_str(500): 240 add_alias(103): 96 add_alias(99): 96 init_dst_set(89): 32296 grp_hash_add(241): 512 fix_hostname(1457): 56 fix_socket_list(1666): 24 route_new_list(199): 184 fix_param(1114): 88 fix_param(1053): 312 fix_expr(554): 192 init_io_wait(516): 3224 subst_str(514): 720 mk_rval_expr2(2681): 17360 mk_elem(90): 232 mk_new_net(52): 48 tr_new(1730): 240 mk_rval_expr_v(2553): 216 yyparse(2852): 736 mk_rval_expr1(2621): 19096 mk_rval_expr_v(2540): 109152 pv_cache_add(349): 5616 pv_parse_format(1173): 4984 fix_param(1019): 2568 mk_action(118): 44416 cfg_declare(50): 3136 set_mod_param_regex(145): 88 set_mod_param_regex(134): 104 tr_table_add(1959): 360 register_module(233): 28784 register_module(216): 2808 load_module(417): 1552 sr_push_yy_state(1627): 1008 new_sock_info(348): 16 new_sock_info(339): 32 new_sock_info(327): 32 new_sock_info(304): 48 new_sock_info(299): 1200 add_alias(103): 56 add_alias(99): 64 yyparse(677): 40 yyparse(2387): 128 yyparse(658): 144 yyparse(1878): 168 get_hdr_field(116): 232 parse_headers(325): 64 subst_parser(301): 120 subst_parser(291): 1440 subst_parser(274): 640 pp_subst_add(58): 240 sr_push_yy_state(1697): 24 addstr(1445): 69072 rpc_hash_add(105): 16280 str_hash_alloc(59): 512 pv_table_add(236): 17248 pv_init_buffer(2139): 327680 pv_init_buffer(2129): 320 init_nonsip_hooks(43): 24 init_rlist(146): 40 rval_get_str(1259): 3696 route_add(124): 968 str_hash_alloc(59): 768 sr_push_yy_state(1687): 464 pp_define(1819): 568 init_counters(125): 128 cnt_hash_add(341): 27096 str_hash_alloc(59): 1280 Total: 762656 } Module: sl { sl_register_callback(514): 64 Total: 64 } Module: siptrace { mod_init(340): 384 Total: 384 } Module: permissions { get_pathname(243): 64 Total: 64 } Module: xlog { mod_init(212): 4104 xdbg_fixup_helper(498): 616 xlog_fixup_helper(533): 3720 Total: 8440 } Module: rtpengine { child_init(1964): 240 build_rtpp_socks(1791): 8 Total: 248 } Module: pv { pv_parse_xavp_name(541): 112 pv_parse_xavp_name(515): 112 tr_parse_string(2639): 120 tr_parse_string(2628): 120 tr_parse_string(2519): 104 tr_parse_string(2509): 64 tr_parse_string(2484): 64 tr_parse_string(2473): 64 add_var(65): 176 add_var(58): 344 Total: 1280 } Module: phonenum { pv_parse_phonenum_name(131): 32 sr_phonenum_add_item(99): 8 sr_phonenum_add_item(93): 304 Total: 344 } Module: textops { fixup_method(3598): 128 hname_fixup(3528): 504 Total: 632 } Module: rtimer { stm_e_param(384): 112 stm_t_param(299): 48 Total: 160 } Module: tm { Total: 0 } Module: kex { Total: 0 } Module: tmx { Total: 0 } Module: utils { Total: 0 } Module: xhttp_prom { Total: 0 } Module: dispatcher { Total: 0 } /etc/kamailio# kamailio -v version: kamailio 5.4.3 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 6.3.0 Any idea which could cause a memory leak. Does any of the module cause an issue? Thanks in Advance. Uttam

3 2

← Newer
1
2
3
4
5
6
7
8
9
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users February 2021