<!--
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.
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 have installed kamailio and also mariadb server with mysql.I also updated kamctlrc file values with my actual hostname and the user ,database,tables its password .But grtting errors while configuring kamailio.
### Troubleshooting
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
root@jigasi:/# sudo vi /etc/kamailio/kamailio.cfg
root@jigasi:/# sudo systemctl restart kamailio.service
Job for kamailio.service failed because the control process exited with error code.
See "systemctl status kamailio.service" and "journalctl -xeu kamailio.service" for details.
root@jigasi:/# sudo systemctl status kamailio.service
× kamailio.service - Kamailio - the Open Source SIP Server
Loaded: loaded (/lib/systemd/system/kamailio.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2023-05-04 08:45:03 UTC; 10s ago
Process: 29245 ExecStart=/usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY --atexit=no (code=exited, status=255/EXCEPTION)
CPU: 32ms
May 04 08:45:03 jigasi.pune.cdac.in systemd[1]: kamailio.service: Scheduled restart job, restart counter is at 5.
May 04 08:45:03 jigasi.pune.cdac.in systemd[1]: Stopped Kamailio - the Open Source SIP Server.
May 04 08:45:03 jigasi.pune.cdac.in systemd[1]: kamailio.service: Start request repeated too quickly.
May 04 08:45:03 jigasi.pune.cdac.in systemd[1]: kamailio.service: Failed with result 'exit-code'.
May 04 08:45:03 jigasi.pune.cdac.in systemd[1]: Failed to start Kamailio - the Open Source SIP Server.
root@jigasi:/# kamailio -c
0(29260) ERROR: <core> [core/modparam.c:175]: set_mod_param_regex(): parameter <host> of type <1:string> not found in module <db_mysql>
0(29260) CRITICAL: <core> [core/cfg.y:3686]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 259, column 51: Can't set module parameter
0(29260) ERROR: <core> [core/modparam.c:175]: set_mod_param_regex(): parameter <port> of type <2:int> not found in module <db_mysql>
0(29260) CRITICAL: <core> [core/cfg.y:3686]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 260, column 34: Can't set module parameter
0(29260) ERROR: <core> [core/modparam.c:175]: set_mod_param_regex(): parameter <dbname> of type <1:string> not found in module <db_mysql>
0(29260) CRITICAL: <core> [core/cfg.y:3686]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 261, column 42: Can't set module parameter
0(29260) ERROR: <core> [core/modparam.c:175]: set_mod_param_regex(): parameter <table> of type <1:string> not found in module <db_mysql>
0(29260) CRITICAL: <core> [core/cfg.y:3686]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 262, column 43: Can't set module parameter
0(29260) ERROR: <core> [core/modparam.c:175]: set_mod_param_regex(): parameter <username> of type <1:string> not found in module <db_mysql>
0(29260) CRITICAL: <core> [core/cfg.y:3686]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 263, column 44: Can't set module parameter
0(29260) ERROR: <core> [core/modparam.c:175]: set_mod_param_regex(): parameter <password> of type <1:string> not found in module <db_mysql>
0(29260) CRITICAL: <core> [core/cfg.y:3686]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 264, column 47: Can't set module parameter
0(29260) ERROR: <core> [core/modparam.c:175]: set_mod_param_regex(): parameter <db_url> of type <1:string> not found in module <db_mysql>
0(29260) CRITICAL: <core> [core/cfg.y:3686]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 265, column 91: Can't set module parameter
0(29260) ERROR: <core> [core/modparam.c:175]: set_mod_param_regex(): parameter <username_column> of type <1:string> not found in module <auth_db>
0(29260) CRITICAL: <core> [core/cfg.y:3686]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 299, column 50: Can't set module parameter
ERROR: bad config file (8 errors) (parsing code: 0)
0(29260) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
#### 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)
```root@jigasi:/# kamailio -v
version: kamailio 5.5.6 (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, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled with gcc 9.4.0
root@jigasi:/#
* **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/3433
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3433(a)github.com>
### Description
Restarting kamailio service on FreeBSD takes a one minute to complete. With default config in place.
### Troubleshooting
#### Reproduction
```
service kamailio restart
```
#### Debugging Data
#### Log Messages
### 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`
5.5.4
```
sudo service kamailio restart
Performing sanity check on kamailio configuration:
0(14393) WARNING: <core> [core/socket_info.c:1480]: fix_hostname(): could not rev. resolve 192.168.0.18
0(14393) WARNING: <core> [core/socket_info.c:1480]: fix_hostname(): could not rev. resolve 192.168.0.18
config file ok, exiting...
Stopping kamailio.
Waiting for PIDS: 14307.
Starting kamailio.
```
* **Operating System**:
FreeBSD
<!--
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/3431
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3431(a)github.com>
Hello,
during past on-site/online devel meetings as well as on mailing lists or
tracker, there were various discussions around the idea or requests to
make new features available quicker to stable branches.
Of course, one can do local git cherry-picking, but I thought to bring
this in discussion and see if makes sense to get something more
coordinated between developers and community. Therefore I am
cross-posting to sr-dev and sr-users to see if there is interest for it
from both communities.
Somehow inspired from Debian, my first idea would be to create a
"x.y-backports" branch, where "x.y" is the branch for the stable release
series. For example, with 5.6 release series built from branch "5.6",
there could be "5.6-backports" branch which is kept in sync in "5.6" but
also can get "selected" new features from devel (master branch) backported.
The "selected" new features should be mostly a matter of the people
willing to put effort in backporting, but I would consider a list
recommendations not to end up with devel and backports branches being
more or less the same. For example, in the "no-backporting" list:
- no backporting of completely new modules
- no backporting of significant changes to the config file language
and native scripting interpreter
In the "ok-to-backport":
- updates to enable use with newer versions of external libraries
- changes to make some functions/modules to cope better with the core
infrastructure or end points
Commits to the backports branch can be proposed via pull requests.
The backports branch should be done only for latest stable version,
picking from the development version. Right now it would be 5.6, but we
can wait till 5.7 is released and then have it for it.
No packaging and no official releases should be made from backports
branch, only a git branch to be maintained as a community effort. Of
course, if someone wants to put more resources into it, we can discuss
about.
Anyhow, the first questions would be if such branch sounds good to have
and if there are people that think they can also contribute to maintain it.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com
Good morning everyone ,
My name is Wael Heni : https://www.linkedin.com/in/heniwael/
I would like to contribute to the project , i will start by resolving bugs
, then may be i will try to add feature
but i need a few docs about installing the dev env and getting the
permission to pushing to github repository
Any help is appreciated
Regards
Wael
Hello,
in about 1 hour the kamailio.org server will be rebooted for some system
upgrades, it should be quickly back running, but if anyone accesses the
web/wiki or mailing lists archives exactly during that time, they might
not respond -- just wait for a minute and try again.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com