Consider this as a placeholder for requesting RHEL 8 / CentOS 8(TBS) builds in OBS.
RHEL 8 now ships with Python 3.6 so `app_python3` can be included the the RPMs.
Thank you.
--
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/1949
<!--
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
on busy servers, there's a sporadic crash in slow timer.
we don't have any debugging data anymore nor a way to reliably reproduce it.
just posting here in case someone sees the same and can find a way to reliably reproduce it and maybe test the patch below.
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
### Troubleshooting
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
with the patch below we don't see any crashes
either `tl` or `tl->f` is null when it crashes. this is probably some race condition
```
diff --git a/src/core/timer.c b/src/core/timer.c
index 0e0dc8812..3c59db3da 100644
--- a/src/core/timer.c
+++ b/src/core/timer.c
@@ -1128,7 +1128,7 @@ void slow_timer_main()
#endif
SET_RUNNING_SLOW(tl);
UNLOCK_SLOW_TIMER_LIST();
- ret=tl->f(*ticks, tl, tl->data);
+ ret= (tl->f ? tl->f(*ticks, tl, tl->data) : 0);
/* reset the configuration group handles */
cfg_reset_all();
if (ret==0){
```
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
5.1 / 5.2
```
* **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 `uname -a`)
-->
```
CentOS7
```
--
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/2120
- fix leak socket when error handling errors in creation or destruction ipsec tunnel
<!-- 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 -->
- [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:
<!-- 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
<!-- Describe your changes in detail -->
Fixed socket leak on error during ipsec tunnel creation or destruction.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2114
-- Commit Summary --
* ims_ipsec_pcscf: closing mnl_socket in some exceptional situations
-- File Changes --
M src/modules/ims_ipsec_pcscf/cmd.c (5)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2114.patchhttps://github.com/kamailio/kamailio/pull/2114.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/2114
<!-- 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/1446
-- Commit Summary --
* kamailio db_redisusrloc
-- File Changes --
A src/modules/db_redisusrloc/Makefile (36)
A src/modules/db_redisusrloc/README (88)
A src/modules/db_redisusrloc/db_redisusrloc.c (100)
A src/modules/db_redisusrloc/doc/Makefile (4)
A src/modules/db_redisusrloc/doc/db_redisusrloc.xml (45)
A src/modules/db_redisusrloc/doc/db_redisusrloc_admin.xml (86)
A src/modules/db_redisusrloc/redisdb_base.c (1189)
A src/modules/db_redisusrloc/redisdb_connection.c (100)
A src/modules/db_redisusrloc/redisdb_connection.h (43)
A src/modules/db_redisusrloc/redisdb_dbase.h (96)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1446.patchhttps://github.com/kamailio/kamailio/pull/1446.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/1446
<!-- 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 -->
- [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 (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
<!-- Describe your changes in detail -->
this allow notify body aggregation with priorities
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2118
-- Commit Summary --
* presence_xml: adds option to aggregate xml body with priorities
-- File Changes --
M src/modules/presence_xml/notify_body.c (112)
M src/modules/presence_xml/presence_xml.c (7)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2118.patchhttps://github.com/kamailio/kamailio/pull/2118.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/2118
<!-- 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 -->
- [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 (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
<!-- Describe your changes in detail -->
Module to produce and send messages to a Kafka server busing librdkafka library.
I copy part of README file here:
Chapter 1. Admin Guide
Table of Contents
1. Overview
2. Dependencies
2.1. Kamailio Modules
2.2. External Libraries or Applications
2.3. Parameters
2.3.1. brokers (string)
2.3.2. configuration (string)
2.3.3. topic (string)
2.4. Functions
2.4.1. kafka_send(topic, msg)
2.5. RPC Commands
2.5.1. kafka.stats
2.5.2. kafka.stats_topic
1. Overview
This module produces and sends messages to a Kafka server.
2. Dependencies
2.1. Kamailio Modules
2.2. External Libraries or Applications
2.3. Parameters
2.3.1. brokers (string)
2.3.2. configuration (string)
2.3.3. topic (string)
2.4. Functions
2.4.1. kafka_send(topic, msg)
2.5. RPC Commands
2.5.1. kafka.stats
2.5.2. kafka.stats_topic
2.1. Kamailio Modules
The following modules must be loaded before this module:
* none.
2.2. External Libraries or Applications
The following libraries or applications must be installed before
running Kamailio with this module loaded:
* librdkafka: the Apache Kafka C/C++ client library.
https://github.com/edenhill/librdkafka
2.3. Parameters
2.3.1. brokers (string)
Specifies a list of brokers separated by commas.
From librdkafka documentation:
brokerlist is a ,-separated list of brokers in the format:
<broker1>,<broker2>,
Where each broker is in either the host or URL based format:
* <host>[:<port>]
* <proto>://<host>[:port]
<proto> is either PLAINTEXT, SSL, SASL, SASL_PLAINTEXT
The two formats can be mixed but ultimately the value of the
security.protocol config property decides what brokers are allowed.
This parameter is mandatory. There is no default value.
Example 1.1. Set brokers parameter
...
modparam("kafka", "brokers", "localhost:9092")
modparam("kafka", "brokers", "broker1:10000,broker2")
modparam("kafka", "brokers", "SSL://broker3:9000,ssl://broker2")
...
2.3.2. configuration (string)
Specifies a set of general properties.
Each configuration property follows: name = value pattern. And
configuration properties are separated by ;
This parameter is optional, but if it exists it can be configured only
once.
Example 1.2. Set configuration parameter
...
modparam("kafka", "configuration", "topic.metadata.refresh.interval.ms=20000;que
ue.buffering.max.messages=1000000;metadata.request.timeout.ms=90000")
modparam("kafka", "configuration", "topic.metadata.refresh.interval.ms=20000;que
ue.buffering.max.messages=500000;debug=all;metadata.request.timeout.ms=900000")
...
2.3.3. topic (string)
Specifies a topic name and a set of topic properties.
The topic defined in topic parameter has to already exist in Kafka
servers.
Each topic property is a list of attribute = value separated by
semicolon.
name atribute indicates the topic name. It is mandatory. Other
attributes mean names of properties and are optional.
This parameter is optional. Each topic needs a topic parameter so
several topic parameters are allowed.
Example 1.3. Set topic parameter
...
modparam("kafka", "topic", "name=my_topic;request.required.acks=0;request.timeou
t.ms=10000")
modparam("kafka", "topic", "name=second_topic;request.required.acks=0;request.ti
meout.ms=10000")
modparam("kafka", "topic", "name=third_topic")
...
2.4. Functions
2.4.1. kafka_send(topic, msg)
Send a message to a specific topic via Kafka server.
Parameters:
* topic: (string) name of the topic. It is mandatory.
* msg: (string) message to send. It is mandatory.
Available via KEMI framework as kafka.send.
Example 1.4. kafka_send usage
...
# Send "test message" to topic "my_topic"
kafka_send("my_topic", "test message");
...
2.5. RPC Commands
2.5.1. kafka.stats
Show statistics about total sent messages and failed to deliver ones.
Example 1.5. kafka.stats usage
...
kamcmd kafka.stats
Total messages: 26 Errors: 0
...
2.5.2. kafka.stats_topic
Show statistics about sent messages and failed to deliver ones for a
specific topic.
Parameter: topic (string) name of the topic. Required.
Example 1.6. kafka.stats usage
...
# Show statistics for my_topic.
kamcmd kafka.stats_topic "my_topic"
Topic: my_topic Total messages: 17 Errors: 0
...
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2112
-- Commit Summary --
* kafka: module to produce and send messages to a Kafka server
-- File Changes --
A src/modules/kafka/Makefile (23)
A src/modules/kafka/doc/Makefile (4)
A src/modules/kafka/doc/kafka.xml (41)
A src/modules/kafka/doc/kafka_admin.xml (221)
A src/modules/kafka/kafka_mod.c (335)
A src/modules/kafka/kfk.c (1175)
A src/modules/kafka/kfk.h (96)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2112.patchhttps://github.com/kamailio/kamailio/pull/2112.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/2112
### Description
When using Kamailio with `tcp_accept_haproxy=yes`, the `$si` and `$sp` variables have the
real IP & Port information from the original connection to the LB leaving no way to access the connection IP & Port from where the packet is received from Kamailio perspective.
### Possible Solutions
Create two new pseudovariables that contain the connection IP & Port where the packet was received for use cases where `tcp_accept_haproxy=yes`.
Suggested names (but could be any): $CI and $CP meaning -> Connection IP and Connection Port.
### Example
With `tcp_accept_haproxy=yes`:
UAC (1.1.1.1:45621) -> (2.2.2.2:5060) LB **with** Proxy Protocol (3.3.3.3:57482) -> (4.4.4.4:5060) Kamailio.
```
$si = 1.1.1.1
$sp = 45621
$CI = 3.3.3.3
$CP = 57482
```
With `tcp_accept_haproxy=no`:
UAC (1.1.1.1:45621) -> (2.2.2.2:5060) LB **without** Proxy Protocol (3.3.3.3:57482) -> (4.4.4.4:5060) Kamailio.
```
$si = 3.3.3.3
$sp = 57482
$CI = 3.3.3.3
$CP = 57482
```
I don't think there is any way to get the `3.3.3.3:57482` IP and Port from the example above when using `tcp_accept_haproxy=yes` but I could be wrong.
Thanks!
Joel.
--
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/2103
Hello Joel,
thank you – this is another error; on the disk it looks ok.. I need to investigate here as well.
To prevent further issues, I’ve switched the user group to read-only for now. I will activate the editing again when the problem is fixed.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
From: Joel Serrano <joel(a)textplus.com>
Sent: Wednesday, October 30, 2019 9:28 PM
To: Henning Westerholt <hw(a)skalatan.de>
Cc: miconda(a)gmail.com; Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Subject: Re: [SR-Users] Routing Blocks - Missing in latest core wiki
Hi guys,
This one also needs fixing:
https://www.kamailio.org/wiki/cookbooks/devel/pseudovariables
I assume caused from the newly created $tcp(c_si), $tcp(c_sp) and $tcp(connid) pseudovars. Please see right after $msrp(srcsock)
I also reported this in the ticket: https://github.com/kamailio/kamailio/issues/2103 but being closed I'm not sure if you get the notifications.
Thanks,
Joel.
On Wed, Oct 30, 2019 at 10:23 AM Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>> wrote:
Hello,
the error is still there, just tested it. I will have a look to it, there are some errors in the apache log related to PHP. I just created a local copy to be able to test it easier.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
From: sr-users <sr-users-bounces(a)lists.kamailio.org<mailto:sr-users-bounces@lists.kamailio.org>> On Behalf Of Daniel-Constantin Mierla
Sent: Wednesday, October 30, 2019 9:56 AM
To: Joel Serrano <joel(a)textplus.com<mailto:joel@textplus.com>>
Cc: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>>
Subject: Re: [SR-Users] Routing Blocks - Missing in latest core wiki
Hello,
ok, thanks for trying!
I added the content directly on the files on the server. We have to dig and see why the content is truncated, maybe some settings need to be adjusted.
Cheers,
Daniel
On 30.10.19 00:40, Joel Serrano wrote:
Hi Daniel,
I believe you are right, and I don't see the easy fix, I tried to edit myself to fix but no matter what I do, when I save the changes it gets truncated.
I also tried to add it in parts (section by section) and save with smaller changes, but when I got to the event_routes section I started getting the same problem and can't continue.
I'm attaching to this email the missing parts, because I clicked on "save" for core 5.2.x, that one got truncated too, so currently 5.2.x, 5.3.x and devel need to be fixed.
My suggestion is to replace from "Custom Global Parameters" onwards with the contents of the attached file, maybe you can edit the files directly on the wiki server? Or, if you manage to do it via the GUI I'd love to know how you got it working!
Sorry, I tried.. :-(
Cheers,
Joel.
On Tue, Oct 29, 2019 at 1:44 PM Daniel-Constantin Mierla <miconda(a)gmail.com<mailto:miconda@gmail.com>> wrote:
Hello,
that part has to be added back.
It was either an accidental change or a hit a limitation/bug of dokuwiki (because it removed last part).
Looking back at the history, it happened when I changed the version number in the title:
- http://www.kamailio.org/wiki/cookbooks/devel/core?do=diff&rev2%5B0%5D=15663…
If you want, you can go ahead and add it yourself, copying from the previous edition, otherwise I will do it tomorrow.
Cheers,
Daniel
On 29.10.19 21:03, Joel Serrano wrote:
Hi,
I was looking at the documentation and noticed that "Routing Blocks" section is missing in latest releases...
http://www.kamailio.org/wiki/cookbooks/5.2.x/core#routing_blocks is OK
But:
http://www.kamailio.org/wiki/cookbooks/5.3.x/core#routing_blockshttp://www.kamailio.org/wiki/cookbooks/devel/core#routing_blocks
Don't exist, have they been moved elsewhere?
Thanks!
Joel.
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com<http://www.asipto.com>
www.twitter.com/miconda<http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>
Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- https://asipto.com/u/kat
--
Daniel-Constantin Mierla -- www.asipto.com<http://www.asipto.com>
www.twitter.com/miconda<http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com<http://www.kamailioworld.com>