QuincyGao created an issue (kamailio/kamailio#4171)
<!--
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
http server for microhttpd, kamailio received http request, but not return any message. it should return `<html><body>OK</body></html>`
here is my conf:
```
loadmodule "microhttpd.so"
modparam("microhttpd", "listen_addr", "172.16.4.111")
modparam("microhttpd", "listen_port", 8284)
event_route[microhttpd:request] {
xinfo("request: $mhttpd(method) - url: $mhttpd(url) - data: [$mhttpd(data)]\n");
mhttpd_reply("200", "OK", "text/html","<html><body>OK</body></html>");
}
```
microhttpd 1.0.1 installed:
```
ldd /usr/local/lib64/kamailio/modules/microhttpd.so
linux-vdso.so.1 => (0x00007ffff0fdf000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fb4d86b6000)
libm.so.6 => /lib64/libm.so.6 (0x00007fb4d83b4000)
librt.so.1 => /lib64/librt.so.1 (0x00007fb4d81ac000)
libmicrohttpd.so.12 => /usr/local/lib64/libmicrohttpd.so.12 (0x00007fb4d7f79000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fb4d7d5d000)
libc.so.6 => /lib64/libc.so.6 (0x00007fb4d798f000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb4d8ac4000)
```
```
ll /usr/local/lib64
kamailio
-rw-r--r--. 1 root root 532156 Mar 6 11:19 libhiredis.a
lrwxrwxrwx. 1 root root 19 Mar 6 11:19 libhiredis.so -> libhiredis.so.1.1.0
lrwxrwxrwx. 1 root root 19 Mar 6 11:19 libhiredis.so.1 -> libhiredis.so.1.1.0
-rwxr-xr-x. 1 root root 318832 Mar 6 11:19 libhiredis.so.1.1.0
-rw-r--r--. 1 root root 571974 Mar 6 11:19 liblua.a
-rw-r--r--. 1 root root 1902020 Mar 6 11:19 libmicrohttpd.a
-rwxr-xr-x. 1 root root 998 Mar 6 11:19 libmicrohttpd.la
lrwxrwxrwx. 1 root root 24 Mar 6 11:19 libmicrohttpd.so -> libmicrohttpd.so.12.62.1
lrwxrwxrwx. 1 root root 24 Mar 6 11:19 libmicrohttpd.so.12 -> libmicrohttpd.so.12.62.1
-rwxr-xr-x. 1 root root 992136 Mar 6 11:19 libmicrohttpd.so.12.62.1
```
<!--
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.
-->
#### 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).
-->
```
25(1659) DEBUG: microhttpd [microhttpd_mod.c:475]: ksr_microhttpd_request(): executing event_route[microhttpd:request] (3)
25(1659) DEBUG: <core> [core/parser/parse_fline.c:249]: parse_first_line(): first line type 1 (request) flags 1
25(1659) DEBUG: <core> [core/parser/msg_parser.c:722]: parse_msg(): SIP Request:
25(1659) DEBUG: <core> [core/parser/msg_parser.c:724]: parse_msg(): method: <OPTIONS>
25(1659) DEBUG: <core> [core/parser/msg_parser.c:726]: parse_msg(): uri: <sip:you@kamailio.org>
25(1659) DEBUG: <core> [core/parser/msg_parser.c:728]: parse_msg(): version: <SIP/2.0>
25(1659) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Via] type 1
25(1659) DEBUG: <core> [core/parser/parse_via.c:2663]: parse_via(): end of header reached, state=2
25(1659) DEBUG: <core> [core/parser/msg_parser.c:592]: parse_headers(): Via found, flags=2
25(1659) DEBUG: <core> [core/parser/msg_parser.c:594]: parse_headers(): this is the first via
25(1659) exec: *** cfgtrace:dbg_cfg_trace(): request_route=[microhttpd:request] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=1164 a=25 n=xinfo
25(1659) INFO: <script>: request: POST - url: / - data: [{
"jsonrpc":"2.0",
"method":"stats.get_statistics",
"params":["registered_users"],
"id":"123234",
"value":{
"test1":1111,
"test2":"2222"
}
}]
25(1659) exec: *** cfgtrace:dbg_cfg_trace(): request_route=[microhttpd:request] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=1165 a=28 n=mhttpd_reply
```
#### 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`
```
version: kamailio 5.8.5 (x86_64/linux)
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, 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_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_SEND_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:
compiled on 11:19:43 Mar 6 2025 with gcc 4.8.5
```
* **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`)
-->
```
centos7.9
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4171
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4171(a)github.com>
linuxmaniac created an issue (kamailio/kamailio#4156)
Forwarded from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096894
> The package fails to build in a test rebuild on at least amd64 with
> gcc-15/g++-15, but succeeds to build with gcc-14/g++-14. The
> severity of this report will be raised before the forky release.
> The full build log can be found at:
> http://qa-logs.debian.net/2025/02/16/amd64exp/kamailio_6.0.0-1_unstable_gcc…
> The last lines of the build log are at the end of this report.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4156
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4156(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
Suggest small bugfixes for CMakeLists.txt for modules and libs.
- `lib/ims` - remove libxml2 as not needed as in 5eac8fd5356cc424d87cac4b4102c99e97054414.
- `dialplan` - added pcre2 lib as a depend.
- `sctp` - switched searching for libsctp for linux only after 9b7719a61ab02c93939e3681cb90e9fa04f3ac5d. There's no libsctp in FreeBSD while kernel module exists, example.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4155
-- Commit Summary --
* lib/ims: libxml2 is not needed - removed from cmake
* dialplan: cmake - add pcre2
* sctp: cmake - search for libsctp on linux only
-- File Changes --
M src/lib/ims/CMakeLists.txt (2)
M src/modules/dialplan/CMakeLists.txt (6)
M src/modules/sctp/CMakeLists.txt (10)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4155.patchhttps://github.com/kamailio/kamailio/pull/4155.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4155
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4155(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:
* 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
Building the db_sqlite or db_unixodbc modules on Alpine 3.20 fails. This is the error for `db_unixodbc`. The error for `db_sqlite` is a similar nature
```
dbase.c:261:32: error: passing argument 2 of 'db_do_close' from incompatible pointer type [-Wincompatible-pointer-types]
261 | return db_do_close(_h, db_unixodbc_free_connection);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
| |
| void (*)(struct my_con *)
In file included from val.h:34,
from dbase.c:33:
../../lib/srdb1/db.h:495:40: note: expected 'void (*)(struct pool_con *)' but argument is of type 'void (*)(struct my_con *)'
495 | void db_do_close(db1_con_t *_h, void (*free_connection)(struct pool_con *));
|
```
I notice that it looks like a fix exists for this and I'm guessing it's not backported?
https://kamailio.org/mailman3/hyperkitty/list/sr-dev@lists.kamailio.org/mes…
### Troubleshooting
#### Reproduction
Follow normal build instructions on Alpine including either of these modules. This does not occur in Alpine 3.20
### Possible Solutions
I'm hoping the patch indicated in the link above would address the issue in 5.8.6. If there's any complier options, etc. that can be changed to address it as well that would be good to know.
* **Operating System**:
Alpine 3.21 ( docker image `alpine:3.21`)
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4121
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4121(a)github.com>