acroitor created an issue (kamailio/kamailio#4340)
<!--
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:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio…
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-dev.lists.kamailio.o…
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
Note that an issue report may be closed automatically after about 2 months
if there is no interest from developers or community users on pursuing it, being
considered expired. In such case, it can be reopened by writing a comment that includes
the token `/notexpired`. About two weeks before considered expired, the issue is
marked with the label `stale`, trying to notify the submitter and everyone else
that might be interested in it. To remove the label `stale`, write a comment that
includes the token `/notstale`. Also, any comment postpone the `expire` timeline,
being considered that there is interest in pursuing 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
With kamailio built from latest sources from master, it fails to start if sipdump module is added to kamailio.cfg
<!--
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.
-->
Start Kamailio with <loadmodule "sipdump.so"> in kamailio.cfg
#### 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
kamailio[301309]: ERROR: <core> [core/sr_module.c:613]: ksr_load_module(): could not open module </usr/lib/x86_64-linux-gnu/kamailio/modules/sipdump.so>: /usr/lib/x86_64-linux-gnu/kamailio/modules/sipdump.so: undefined symbol: ksr_sigsem_xfree
kamailio[301309]: CRITICAL: <core> [core/cfg.y:4086]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 161, column 12-23: failed to load module
<!--
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/4340
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4340(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
- [ ] 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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
Added TLS encryption keys export into the database.
Later keys can be searched and saved to a file. Key search can be done by timestamp, connection IP addresses, and port numbers. For key search, used kamcmd utility.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4339
-- Commit Summary --
* tls_tracker: added module for tls encriptions key export
-- File Changes --
A src/modules/tls_tracker/Makefile (75)
A src/modules/tls_tracker/README (1)
A src/modules/tls_tracker/api.c (33)
A src/modules/tls_tracker/api.h (40)
A src/modules/tls_tracker/doc/Makefile (4)
A src/modules/tls_tracker/doc/tls_tracker.xml (117)
A src/modules/tls_tracker/tls_tracker_mod.c (1126)
A src/modules/tls_tracker/tls_tracker_mod.h (25)
A src/modules/tls_tracker/tls_tracker_rpc.c (478)
A src/modules/tls_tracker/tls_tracker_rpc.h (8)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4339.patchhttps://github.com/kamailio/kamailio/pull/4339.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4339
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4339(a)github.com>
sergey-safarov created an issue (kamailio/kamailio#4282)
I have refactored `alpine` image generation. This GitHub action works in a personal repository, but cannot clean up untagged images from the "kamailio" account.
Example
https://github.com/kamailio/kamailio/actions/runs/15605254192/job/439654377…
@linuxmaniac do you have any idea why this can happen?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4282
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4282(a)github.com>