<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [ ] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [ ] PR should be backported to stable branches
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3213
-- Commit Summary --
* secfilter: machine-parsable data structure for RPC printing data
-- File Changes --
M src/modules/secfilter/secfilter_rpc.c (383)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3213.patchhttps://github.com/kamailio/kamailio/pull/3213.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3213
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3213(a)github.com>
```
CC (gcc) [kamailio] core/crypto/shautils.o
CC (gcc) [kamailio] core/cfg/cfg.o
CC (gcc) [kamailio] core/cfg/cfg_ctx.o
core/cfg/cfg_ctx.c: In function 'cfg_update_defaults':
core/cfg/cfg_ctx.c:287:28: warning: the comparison will always evaluate as 'true' for the pointer operand in '(unsigned char *)&ginst->vars + (sizetype)var->offset' must not be NULL [-Waddress]
287 | if(ginst->vars + var->offset) {
| ^~~~~
CC (gcc) [kamailio] core/cfg/cfg_script.o
CC (gcc) [kamailio] core/cfg/cfg_select.o
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3208
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3208(a)github.com>
### Description
Upgraded to 5.6 from 5.5, looked through docs - and no mention of removal of ring_insert_callid - so upgrade failed.
Found https://github.com/kamailio/kamailio/issues/2989
### Possible Solutions
Add documentation that the function is removed, and how to replace it with textops/htable and/or reply routes
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3212
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3212(a)github.com>
#### Pre-Submission Checklist
- [X] Commit message has the format required by CONTRIBUTING guide
- [X] Commits are split per component (core, individual modules, libs, utils, ...)
- [X] Each component has a single commit (if not, squash them into one commit)
- [X] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [X] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
- [X] PR should be backported to stable branches
- [X] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
There's a problem after upgrade to 5.6 on FreeBSD. Kamailio isn't starting successful.
```
14:19:20.540514 kamailio 40921 - - DEBUG: <core> [core/cfg.y:1964]: yyparse(): loading module tls.so
14:19:20.540893 kamailio 40921 - - DEBUG: <core> [core/sr_module.c:513]: ksr_locate_module(): found module to load </usr/local/lib/kamailio/modules/tls.so>
14:19:20.540912 kamailio 40921 - - DEBUG: <core> [core/sr_module.c:563]: load_module(): trying to load </usr/local/lib/kamailio/modules/tls.so>
14:19:20.543301 kamailio 40921 - - ERROR: <core> [core/sr_module.c:352]: ksr_version_control(): no version info in module </usr/local/lib/kamailio/modules/tls.so>: Undefined symbol "_nss_cache_cycle_prevention_function"
```
The problem is in `ksr_version_control()` probably. In FreeBSD environment it should to flush `dlerror` before call `dlsym()` - [dlopen(3)](https://www.freebsd.org/cgi/man.cgi?query=dlopen&sektion=3&a…at=html).
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3184
-- Commit Summary --
* core: fix ksr_version_control() for FreeBSD build
-- File Changes --
M src/core/sr_module.c (3)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3184.patchhttps://github.com/kamailio/kamailio/pull/3184.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3184
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3184(a)github.com>
Hi Guys,
I have recently modified a custom module, where I now shm_mallocxz 2MB, as part of module start up and this memory is not being used as yet.
Previously, the would be smaller chunks(100 bytes at most) shm_malloced during message processing.
I have observed significant runtime performance degradation from just this single change. I would appreciate any suggestions/thoughts you might have.
Below are some the relevant details.
OS:Alpine Linux
RAM: 16GB
Configured Shared memory: 4GB
shm_force_alloc=1
Typical shared memory usage: 1.5GB
System swapping is disabled, also observed during load testing that no mem is getting swapped.
Since updating to 5.6, Kamailio segfaults when calling `get_redirects("1")`.
```
#0 0x000055d12c93c527 in get_str_fparam (dst=dst@entry=0x7ffd246edfe0, msg=msg@entry=0x7f83973b6a80, param=0x0) at core/sr_module.c:1646
val = {n = 1, s = {s = 0x1 <error: Cannot access memory at address 0x1>, len = 749136082}, re = 0x1}
ret = <optimized out>
avp = <optimized out>
pv_val = {rs = {s = 0x1 <error: Cannot access memory at address 0x1>, len = 749136082}, ri = 1, flags = 0}
__func__ = "get_str_fparam"
#1 0x00007f838d2f0a17 in w_get_redirect2 (msg=0x7f83973b6a80, max_c=0x0, reason=<optimized out>) at uac_redirect.c:337
n = <optimized out>
max = <optimized out>
sreason = {s = 0x1a <error: Cannot access memory at address 0x1a>, len = -828131391}
__func__ = "w_get_redirect2"
#2 0x000055d12c975624 in do_action (h=h@entry=0x7ffd246ee820, a=a@entry=0x7f83cedd3670, msg=msg@entry=0x7f83973b6a80) at core/action.c:1085
ret = <optimized out>
v = <optimized out>
...
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3197
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3197(a)github.com>