### Description
See `lock_hash` in `h_table.c`:
```C
void lock_hash(int i)
{
int mypid;
mypid = my_pid();
if (likely(atomic_get(&_tm_table->entries[i].locker_pid) != mypid)) {
lock(&_tm_table->entries[i].mutex);
atomic_set(&_tm_table->entries[i].locker_pid, mypid);
} else {
/* locked within the same process that called us*/
_tm_table->entries[i].rec_lock_level++;
}
}
```
Flowing lines of code do not guarantee atomicity and I think it is not safe:
* atomic_get(&_tm_table->entries[i].locker_pid) != mypid
* lock(&_tm_table->entries[i].mutex)
* atomic_set(&_tm_table->entries[i].locker_pid, mypid)
Would you mind solving my confusion?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3083
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3083(a)github.com>
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
I set up Kamailio IMS , in the end everything turned out great, calls are made, and I decided to check how Kamailio copes with the load. I am creating load using sipp application. There is no problem with a low call generation rate, but if you raise the call generation to more than 20 calls per second, some of the calls fail.
### Troubleshooting
Challenges are always dropped sequentially
![image](https://user-images.githubusercontent.com/92918808/161745286-264d6e9b-47bb-4fcb-923a-1f5ded4cd999.png)
I compared the calls and saw that the ICSCF does not send a 180 Ringing message towards the SCSCF.
![image](https://user-images.githubusercontent.com/92918808/161745354-2f97f8d1-2eb4-4a53-a9b0-2cb9d9d536d6.png)
Below is an example of a successful call.
![image](https://user-images.githubusercontent.com/92918808/161745412-20f0ecc6-3952-4e01-9c74-4f6fa6cfd3c8.png)
CPU, MEM indicators are normal. I increased the shr_mem and pkg_mem parameters.
S-CSCF and I-CSCF communicate over UDP, but reside on the same server. It doesn't look like the packets are dropping or suffering from collisions.
10.21.4.226 external IP P-CSCF
10.10.0.1 IP P-CSCF
10.10.0.2 IP S/I-CSCF
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
Using the sipp application, generate 100 calls at a generation rate greater than 20 calls per second.
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
```
none
```
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
attached below
```
[logs.zip](https://github.com/kamailio/kamailio/files/8417659/logs.zip)
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
attached below
```
[call_rejected.zip](https://github.com/kamailio/kamailio/files/8417640/call_…
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.3.2 (x86_64/linux) 42be5d
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: 42be5d
compiled on 10:39:53 Dec 27 2021 with gcc 9.3.0
```
* **Operating System**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `lsb_release -a` and `uname -a`)
-->
```
Ubuntu 20.04.3 LTS Linux ims-core 5.4.0-104-generic #118-Ubuntu SMP Wed Mar 2 19:02:41 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3071
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3071(a)github.com>
Module: kamailio
Branch: master
Commit: c43432e6fda8db527ffca3442d7cea8e601a211e
URL: https://github.com/kamailio/kamailio/commit/c43432e6fda8db527ffca3442d7cea8…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2022-04-13T11:16:09+02:00
modules: readme files regenerated - geoip2 ... [skip ci]
---
Modified: src/modules/geoip2/README
---
Diff: https://github.com/kamailio/kamailio/commit/c43432e6fda8db527ffca3442d7cea8…
Patch: https://github.com/kamailio/kamailio/commit/c43432e6fda8db527ffca3442d7cea8…
---
diff --git a/src/modules/geoip2/README b/src/modules/geoip2/README
index 0362750258..98d8d97f5c 100644
--- a/src/modules/geoip2/README
+++ b/src/modules/geoip2/README
@@ -91,7 +91,10 @@ Chapter 1. Admin Guide
to enable access to the results of a query to the database.
Many queries can be done and store results in different containers to
- be able to use in parallel. Database is loaded at startup in cache.
+ be able to use in parallel. Database is loaded at startup in cache. The
+ cache can be reloaded with an RPC command. In this case make sure that
+ you do not overwrite the file in place, but replace it, e.g. with a
+ “move” command.
2. Dependencies
Module: kamailio
Branch: master
Commit: 166edc37177c2a92f57a31591ca781b15202a57f
URL: https://github.com/kamailio/kamailio/commit/166edc37177c2a92f57a31591ca781b…
Author: Henning Westerholt <hw(a)gilawa.com>
Committer: Henning Westerholt <hw(a)gilawa.com>
Date: 2022-04-13T09:04:31Z
geoip2: add a note about db replacement recommendations
---
Modified: src/modules/geoip2/doc/geoip2_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/166edc37177c2a92f57a31591ca781b…
Patch: https://github.com/kamailio/kamailio/commit/166edc37177c2a92f57a31591ca781b…
---
diff --git a/src/modules/geoip2/doc/geoip2_admin.xml b/src/modules/geoip2/doc/geoip2_admin.xml
index d3d0228946..cbcc2d8c79 100644
--- a/src/modules/geoip2/doc/geoip2_admin.xml
+++ b/src/modules/geoip2/doc/geoip2_admin.xml
@@ -44,6 +44,9 @@
<para>
Many queries can be done and store results in different containers to
be able to use in parallel. Database is loaded at startup in cache.
+ The cache can be reloaded with an RPC command. In this case make sure
+ that you do not overwrite the file in place, but replace it, e.g. with
+ a <quote>move</quote> command.
</para>
</section>
<section>
### Description
Currently, the `geoip2` module loads the IP database at startup and keeps it in cache and there is no way to tell Kamailio to reload the database without a full restart.
### Possible Solutions
To keep this module inline with other modules that use external datasources, I would suggest to implement a new RPC command and a new geoip2 function to reload the database defined in the `path` geoip2 modparam without the need of a restart.
I'm not aware of the effort required for implementing either of them, but only having an RPC command would effectively solve this issue as you can call RPC commands from within Kamailio conf, thus, the reload function would not be something strictly required but more of a nice-to-have.
### Examples:
Function:
```
geoip2_reload()
```
RPC command:
```
kamctl rpc gip2.reload / kamctl rpc geoip2.reload
```
Kamcmd command:
```
kamcmd geoip2.reload
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2029