[Users] openser with TLS

Joao Pereira joao.pereira at fccn.pt
Thu Mar 23 15:04:42 CET 2006 

Hello,the version I m using  is 1.0.1-tls and its crashing on startup.

Thats the end of the output with debug level =6

Listening on
Aliases:
             *: mex.fccn.pt:*
             *: XXX.XXX.XXX.XXX:*

WARNING: no fork mode and no udp listen address found
 0(3486) fm_malloc_init: F_OPTIMIZE=16384, /ROUNDTO=2048
 0(3486) fm_malloc_init: F_HASH_SIZE=2067, fm_block size=16548
 0(3486) fm_malloc_init(0xf4eb1000, 33554432), start=0xf4eb1000
 0(3486) shm_mem_init: success
 0(0) core dump limits set to 4294967295
 0(0) DEBUG: init_mod: postgres
postgres - initializing
 0(0) DEBUG: init_mod: sl_module
stateless - initializing
 0(0) DEBUG: register_fifo_cmd: new command (sl_stats) registered
 0(0) unixsock_register_cmd: New command (sl_stats) registered
 0(0) DEBUG: MD5 calculated: 1d0376a2244771bba12e9da5f03652d9
 0(0) DEBUG: init_mod: tm
 0(0) TM - (size of cell=2832, sip_msg=768) initializing...
 0(0) Call-ID initialization: '7abab1f5'
 0(0) DEBUG: register_fifo_cmd: new command (t_uac_dlg) registered
 0(0) DEBUG: register_fifo_cmd: new command (t_uac_cancel) registered
 0(0) DEBUG: register_fifo_cmd: new command (t_hash) registered
 0(0) DEBUG: register_fifo_cmd: new command (t_reply) registered
 0(0) unixsock_register_cmd: New command (t_uac_dlg) registered
 0(0) unixsock_register_cmd: New command (t_uac_cancel) registered
 0(0) unixsock_register_cmd: New command (t_hash) registered
 0(0) unixsock_register_cmd: New command (t_reply) registered
 0(0) DEBUG: lock_initialize: lock initialization started
 0(0) DEBUG: register_fifo_cmd: new command (t_stats) registered
 0(0) unixsock_register_cmd: New command (t_stats) registered
Segmentation fault (core dumped)


Previously I installed the version 1.0.0-tls. But I belieave the 1.0.1 
"make install" overwrites the previous openser, and the problem shouldnt 
be this.
Thanks
Joao Pereira



Bogdan-Andrei Iancu wrote:

> ok :)
>
> what version are you using? does is crash on start-up or on first 
> request? can you provide the backtrace?
>
> regards,
> bogdan
>
> Joao Pereira wrote:
>
>> Yes, with "fork=no" I found the problem:
>>
>> Segmentation fault (core dumped)
>>
>> :P
>>
>>
>> Bogdan-Andrei Iancu wrote:
>>
>>> Hi Joao,
>>>
>>> try yo start openser in foreground - set fork=no and 
>>> log_stderror=yes in your config. Maybe you will get a hint.
>>>
>>> regards,
>>> bogdan
>>>
>>> Joao Pereira wrote:
>>>
>>>> Yes, I did "ps fax" and there was no OpenSER.
>>>> How can I find the error? Even with a higher debug level, there are 
>>>> no errors in the stdout:
>>>> (debug level = 8)
>>>>
>>>> Listening on
>>>> Aliases:
>>>>             *: mex.fccn.pt:*
>>>>             *: XXX.XXX.XXX.XXX:*
>>>>
>>>> 0(22568) fm_malloc_init: F_OPTIMIZE=16384, /ROUNDTO=2048
>>>> 0(22568) fm_malloc_init: F_HASH_SIZE=2067, fm_block size=16548
>>>> 0(22568) fm_malloc_init(0xf4eb1000, 33554432), start=0xf4eb1000
>>>> 0(22568) shm_mem_init: success
>>>> 0(0) core dump limits set to 4294967295
>>>> 0(0) DEBUG: init_mod: postgres
>>>> postgres - initializing
>>>> 0(0) DEBUG: init_mod: sl_module
>>>> stateless - initializing
>>>> 0(0) DEBUG: register_fifo_cmd: new command (sl_stats) registered
>>>> 0(0) unixsock_register_cmd: New command (sl_stats) registered
>>>> 0(0) DEBUG: MD5 calculated: 1d0376a2244771bba12e9da5f03652d9
>>>> 0(0) DEBUG: init_mod: tm
>>>> 0(0) TM - (size of cell=2832, sip_msg=768) initializing...
>>>> 0(0) Call-ID initialization: '2ffddfe3'
>>>> 0(0) DEBUG: register_fifo_cmd: new command (t_uac_dlg) registered
>>>> 0(0) DEBUG: register_fifo_cmd: new command (t_uac_cancel) registered
>>>> 0(0) DEBUG: register_fifo_cmd: new command (t_hash) registered
>>>> 0(0) DEBUG: register_fifo_cmd: new command (t_reply) registered
>>>> 0(0) unixsock_register_cmd: New command (t_uac_dlg) registered
>>>> 0(0) unixsock_register_cmd: New command (t_uac_cancel) registered
>>>> 0(0) unixsock_register_cmd: New command (t_hash) registered
>>>> 0(0) unixsock_register_cmd: New command (t_reply) registered
>>>> [root at mex openser-1.0.1-tls]#  0(0) DEBUG: lock_initialize: lock 
>>>> initialization started
>>>> 0(0) DEBUG: register_fifo_cmd: new command (t_stats) registered
>>>> 0(0) unixsock_register_cmd: New command (t_stats) registered
>>>>
>>>>
>>>> Could be a problem in the certificates?
>>>> Joao Pereira
>>>>
>>>> Daniel-Constantin Mierla wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> did you check with "ps auxw | grep openser"? Wasn't there any 
>>>>> openser process running. From the logs looks like openser started 
>>>>> ok (tm module initialized succesfully - is it tm you last module 
>>>>> in the loadmodule list?).
>>>>>
>>>>> Cheers,
>>>>> Daniel
>>>>>
>>>>>
>>>>> On 03/22/06 14:21, Joao Pereira wrote:
>>>>>
>>>>>> Hello to all
>>>>>> Im trying to put OpenSER to work with TLS.
>>>>>> I created the certificates, and configured openser.cfg. ("openser 
>>>>>> -c" shows no errors)
>>>>>> But when I start OpenSER, there are no errors, but the server 
>>>>>> doesn't start:
>>>>>> It says this (with debug level 4) :
>>>>>>
>>>>>> Listening on
>>>>>> Aliases:
>>>>>>             *: mex.fccn.pt:*
>>>>>>             *: XXX.XXX.XXX.XXX:*
>>>>>>
>>>>>> 0(22549) fm_malloc_init: F_OPTIMIZE=16384, /ROUNDTO=2048
>>>>>> 0(22549) fm_malloc_init: F_HASH_SIZE=2067, fm_block size=16548
>>>>>> 0(22549) fm_malloc_init(0xf4eb1000, 33554432), start=0xf4eb1000
>>>>>> 0(22549) shm_mem_init: success
>>>>>> 0(0) core dump limits set to 4294967295
>>>>>> 0(0) DEBUG: init_mod: postgres
>>>>>> postgres - initializing
>>>>>> 0(0) DEBUG: init_mod: sl_module
>>>>>> stateless - initializing
>>>>>> 0(0) DEBUG: register_fifo_cmd: new command (sl_stats) registered
>>>>>> 0(0) unixsock_register_cmd: New command (sl_stats) registered
>>>>>> 0(0) DEBUG: MD5 calculated: 1d0376a2244771bba12e9da5f03652d9
>>>>>> 0(0) DEBUG: init_mod: tm
>>>>>> 0(0) TM - (size of cell=2832, sip_msg=768) initializing...
>>>>>> 0(0) Call-ID initialization: '6efffbed'
>>>>>> 0(0) DEBUG: register_fifo_cmd: new command (t_uac_dlg) registered
>>>>>> 0(0) DEBUG: register_fifo_cmd: new command (t_uac_cancel) registered
>>>>>> 0(0) DEBUG: register_fifo_cmd: new command (t_hash) registered
>>>>>> 0(0) DEBUG: register_fifo_cmd: new command (t_reply) registered
>>>>>> 0(0) unixsock_register_cmd: New command (t_uac_dlg) registered
>>>>>> 0(0) unixsock_register_cmd: New command (t_uac_cancel) registered
>>>>>> 0(0) unixsock_register_cmd: New command (t_hash) registered
>>>>>> 0(0) unixsock_register_cmd: New command (t_reply) registered
>>>>>> [root at mex openser-1.0.1-tls]#  0(0) DEBUG: lock_initialize: lock 
>>>>>> initialization started
>>>>>> 0(0) DEBUG: register_fifo_cmd: new command (t_stats) registered
>>>>>> 0(0) unixsock_register_cmd: New command (t_stats) registered
>>>>>>
>>>>>>
>>>>>> and nothing happens... OpenSER isnt runnig :(
>>>>>> -------------------------------------------------------------------------------------------------------------- 
>>>>>>
>>>>>>
>>>>>> this is a part of my openser.cfg:
>>>>>>
>>>>>> listen = tls:XXX.XXX.XXX.XXX
>>>>>>
>>>>>> tls_port_no = 5062
>>>>>> tls_method=SSLv23
>>>>>>
>>>>>> tls_certificate="/services/openser/openser-1.0.1-tls/tls/tools/rootCA/cacert.pem" 
>>>>>>
>>>>>> tls_private_key="/services/openser/openser-1.0.1-tls/tls/tools/rootCA/private/cakey.pem" 
>>>>>>
>>>>>> tls_ca_list="/services/openser/openser-1.0.1-tls/tls/tools/rootCA/certs/01.pem" 
>>>>>>
>>>>>>
>>>>>> tls_ciphers_list="NULL-SHA:NULL-MD5:AES256-SHA:AES128-SHA"
>>>>>>
>>>>>> tls_verify = 1
>>>>>> tls_require_certificate = 1
>>>>>> tls_handshake_timeout=119    # number of seconds
>>>>>> tls_send_timeout=121         # number of seconds
>>>>>>
>>>>>>
>>>>>> If you know whats the problem, please tell me :)
>>>>>> Thanks
>>>>>> Joao Pereira
>>>>>>
>>>>>> _______________________________________________
>>>>>> Users mailing list
>>>>>> Users at openser.org
>>>>>> http://openser.org/cgi-bin/mailman/listinfo/users
>>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at openser.org
>>>> http://openser.org/cgi-bin/mailman/listinfo/users
>>>>
>>>
>>
>

More information about the sr-users mailing list