Hello,
tls module does some initialization of libssl when it is loaded,
otherwise other modules that link against libssl can initialize the lib
before, making it unusable with shared memory.
Although is not a constraint, core parameters should be before module
parameters, otherwise the module mig
Hi,
thanks for the patience. We finally found it. Starting it with debug info
to stdout didn't show much more, but it again showed the "is disabled"
message was still there. So I moved the "enable_tls" line and the "listen:"
line up before loading the module. And that changed everything. Now
Kamai
Hello,
run with -E -ddd command line parameters, some of the messages are in
stderror.
The error is somewhere else, because the the one related to tls is
during shutdown process, therefore something else was detected before.
Cheers,
Daniel
On 16/11/15 09:53, Sebastian Damm wrote:
> Hi Daniel,
>
Hi Daniel,
as I wrote, I copied the last log line from shutdown and the first lines
from the start. That was just to show that those lines really are the first
lines that appear in the log. You can see the PID change and the 5sec gap
between the shutdown and start.
There are no error messages, o
Hello,
the following log message:
Nov 13 17:29:37 lasola /usr/sbin/kamailio[3536]: DEBUG:
[mem/shm_mem.c:235]: shm_mem_destroy(): destroying the shared memory lock
indicates that Kamailio is shutting down already. Can you check up in
the logs and see if there are other error messages?
Do you h
Hi Daniel,
I just moved the TLS config lines up top even before sl and tm module. Also
moved the modparam stuff up there. When starting, Kamailio says, it is
listening on a TLS socket, but netstat says, it isn't. It's basically the
same behavior as before. (This is the last log line from shutting
Hello,
it could be related to the fact that a lot of internal things are
initialized when the first modparam is found in config, but I thought
that change was done in 3.x.
Can you put the tls module config part being the first? The other
modules don't need to be initialized before, actually tls n
Hi Daniel,
yes, we see this message.
Nov 13 11:44:42 lasola /usr/sbin/kamailio[16113]: DEBUG:
[sr_module.c:959]: init_mod(): tls
Nov 13 11:44:42 lasola /usr/sbin/kamailio[16113]: WARNING: tls
[tls_mod.c:287]: mod_init(): tls support is disabled (set enable_tls=1 in
the config to enable it)
Nov 1
Hello,
if you start with debug=3, do you see the message:
DEBUG: [sr_module.c:959]: init_mod(): tls
Cheers,
Daniel
On 13/11/15 12:17, Sebastian Damm wrote:
> Hello,
>
> we just updated one kamailio server from 4.1.5 to 4.3.3, and although
> the config file is correct and kamailio starts up, it
Hello,
we just updated one kamailio server from 4.1.5 to 4.3.3, and although the
config file is correct and kamailio starts up, it doesn't initialize TLS
and says " tls support enabled, but no tls engine available (forgot to
load the tls module?)"
In the log I see:
Old shutdown (last lines):
No
10 matches
Mail list logo
