Hi all,
I'm using Kamailio timers to execute a series of calls with a certain
delay. I have found out that from time to time, the timers are triggered
too soon, sometimes they are triggered 2/3 seconds before they should.
There is nothing significant in the logs, some of the log lines previous to
the premature call are:
10(16136) DEBUG: tm [timer.c:606]: wait_handler(): WAIT timer hit
@1111936903 for 0x7f32cc4eede8 (timer_lm 0x7f32cc4eee70)
10(16136) DEBUG: tm [timer.c:643]: wait_handler(): …
[View More]finished transaction:
0x7f32cc4eede8 (p:0x7f32cc34ee90/n:0x7f32cc34ee90)
10(16136) DEBUG: tm [h_table.c:132]: free_cell_helper(): freeing
transaction 0x7f32cc4eede8 from timer.c:652
And some other ones after the call are
10(16136) DEBUG: tm [timer.c:494]: retr_buf_handler(): timer
retr_buf_handler @1111937043 (0x7f32cc4efa18 -> 0x7f32cc4ef9f8 ->
0x7f32cc4ef6d8)
10(16136) DEBUG: tm [timer.c:545]: retr_buf_handler(): new interval 2000 ms
/ 16 ticks (max 4000 ms)
10(16136) DEBUG: tm [timer.c:329]: retransmission_handler(): request
resending (t=0x7f32cc4ef6d8, SUBSCRIBE ... )
10(16136) DEBUG: tm [timer.c:573]: retr_buf_handler(): timer
retr_buf_handler @1111937043 (0x7f32cc4efa18
->0x7f32cc4ef9f8->0x7f32cc4ef6d8) exiting min (16, 24)
I have read in the documentation that it is normal to have a bit of delay
in some of the timers, but it doesn't mention anything about this behavior.
Is this normal?
Thank you.
[View Less]
Module: kamailio
Branch: master
Commit: a4a55c42aa719f8674ae54d30527acca85763358
URL: https://github.com/kamailio/kamailio/commit/a4a55c42aa719f8674ae54d30527acc…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2022-02-09T08:55:41+01:00
htable: docs for rpc commands to set value and expire
---
Modified: src/modules/htable/doc/htable_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]a4a55c42aa719f8674ae54d30527acc…
Patch: https://github.com/kamailio/kamailio/commit/a4a55c42aa719f8674ae54d30527acc…
---
diff --git a/src/modules/htable/doc/htable_admin.xml b/src/modules/htable/doc/htable_admin.xml
index 9ea5c183f7..45f41f4561 100644
--- a/src/modules/htable/doc/htable_admin.xml
+++ b/src/modules/htable/doc/htable_admin.xml
@@ -1550,6 +1550,68 @@ kamcmd htable.seti test x[0] 123
# set expire for $sht(test=>x) to 120 secs
kamctl rpc htable.seti test x 120
...
+</programlisting>
+ </section>
+ <section id="htable.rpc.setxs">
+ <title>
+ <function moreinfo="none">htable.setxs htable key value expire</function>
+ </title>
+ <para>
+ Set the string value and expire for an item in hash table.
+ </para>
+ <para>
+ Name: <emphasis>htable.setxs</emphasis>
+ </para>
+ <para>Parameters:</para>
+ <itemizedlist>
+ <listitem><para>htable : name of the hash table</para>
+ </listitem>
+ <listitem><para>key : key name in the hash table</para>
+ </listitem>
+ <listitem><para>value : string value for the item</para>
+ </listitem>
+ <listitem><para>expire : integer value for the expire (seconds)</para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Example:
+ </para>
+<programlisting format="linespecific">
+...
+# set value to 'abc' and expire for $sht(test=>x) to 120 secs
+kamctl rpc htable.setxs test x abc 120
+...
+</programlisting>
+ </section>
+ <section id="htable.rpc.setxi">
+ <title>
+ <function moreinfo="none">htable.setxi htable key value expire</function>
+ </title>
+ <para>
+ Set the integer value and expire for an item in hash table.
+ </para>
+ <para>
+ Name: <emphasis>htable.setxi</emphasis>
+ </para>
+ <para>Parameters:</para>
+ <itemizedlist>
+ <listitem><para>htable : name of the hash table</para>
+ </listitem>
+ <listitem><para>key : key name in the hash table</para>
+ </listitem>
+ <listitem><para>value : integer value for the item</para>
+ </listitem>
+ <listitem><para>expire : integer value for the expire (seconds)</para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Example:
+ </para>
+<programlisting format="linespecific">
+...
+# set value to 10 and expire for $sht(test=>x) to 120 secs
+kamctl rpc htable.setxi test x 10 120
+...
</programlisting>
</section>
<section id="htable.rpc.dump">
[View Less]
Module: kamailio
Branch: master
Commit: c1335157c53ca014bbeec6de312f42d955221d58
URL: https://github.com/kamailio/kamailio/commit/c1335157c53ca014bbeec6de312f42d…
Author: Adrian Bunk <bunk(a)debian.org>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2022-02-09T08:10:15+01:00
src/Makefile: Also stop compiling kamcmd from here
---
Modified: src/Makefile
---
Diff: https://github.com/kamailio/kamailio/commit/c1335157c53ca014bbeec6de312f42d…
Patch: https://github.…
[View More]com/kamailio/kamailio/commit/c1335157c53ca014bbeec6de312f42d…
---
diff --git a/src/Makefile b/src/Makefile
index 11be15fb2b..a6380c2283 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -202,7 +202,7 @@ cmodules=$(foreach mods,$(modules_dirs), $($(mods)))
# list of utils directories that should be compiled by make utils
-C_COMPILE_UTILS= ../utils/kamcmd
+C_COMPILE_UTILS= # kamcmd is now installed by ctl
# list of binaries that should be installed alongside
# (they should be created after make utils, see C_COMPILE_UTILS)
C_INSTALL_BIN= # kamcmd is now installed by ctl
[View Less]
### Description
We have a couple of Kamailio containers running on AWS ECS Fargate. Using a Cloudwatch Agent sidecar container I should be able to collect metrics from the Kamailio containers and push them to Cloudwatch for monitoring.
```
xHTTP_PROM exposes the metrics like this:
# Kamailio whole internal statistics
kamailio_app_python3_traced_replies 0 1640265350616
kamailio_app_python3_traced_requests 0 1640265350616
kamailio_core_bad_URIs_rcvd 0 1640265350616
kamailio_core_bad_msg_hdr 0 …
[View More]1640265350616
```
While other prometheus metrics I have seen are throwing metrics like this:
```
# HELP kamailio_core_shmmem_free Free shared memory.
# TYPE kamailio_core_shmmem_free gauge
```
### Troubleshooting
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
#### 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.
-->
```
(paste your debugging data here)
```
#### 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).
-->
```
(paste your log messages here)
```
#### 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).
-->
```
(paste your sip traffic here)
```
### 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`
```
(paste your output here)
```
* **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`)
-->
```
(paste your output here)
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3001
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3001(a)github.com>
[View Less]
#### 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
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [X] New feature …
[View More](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
- [X] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
EPEL now includes a openssl11 package for CentOS 7. This feature is for users who want to build kamailio-tls with OpenSSL 1.1.1 instead of OpenSSL 1.0.2.
It is implemented as a `--with=openssl11` conditional (the default os off), so should not affect/change the regular CentOS 7 builds as distributed by kamailio.org.
This is for adventurous users on CentOS 7 willing to maintain their own OpenSSL 1.1.1-enabled TLS package. EPEL dependencies( openssl11-libs, openssl11-devel) are required at runtime and for build.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2779
-- Commit Summary --
* pkg: enable CentOS 7 to build with OpenSSL 1.1.1
-- File Changes --
M pkg/kamailio/obs/kamailio.spec (32)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2779.patchhttps://github.com/kamailio/kamailio/pull/2779.diff
--
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/pull/2779
[View Less]