[OpenSER-Users] null socket list

[Bogdan-Andrei Iancu]

Hi Michael,

This is rather strange - I will try to get you a small patch for more 
debug output.... Is it ok with you?

Regards,
bogdan

Michael Barinek wrote:
> I've tried both. The below configuration is using fork=no
>
> Mar 20 08:59:14 [18124] WARNING:core:main: no fork mode  and more than 
> one listen address found(will use only the first one)
>
> ///
>
> here's the log_stderror with fork=yes
>
>  0(15547) fm_malloc_init: F_OPTIMIZE=16384, /ROUNDTO=2048
>  0(15547) fm_malloc_init: F_HASH_SIZE=2067, fm_block size=16548
>  0(15547) fm_malloc_init(0x1000000, 33554432), start=0x1000000
>  0(15547) shm_mem_init: success
> clapton:openser-1.0.1 root#  0(0) core dump limits set to 4294967295
>  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: '17fbfb95'
>  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
>  0(0) BUG: uac_init: null socket list
>  0(0) ERROR: mod_init: uac_init failed
>  0(0) init_mod(): Error while initializing module tm
> ERROR: error while initializing modules
>  0(0) DEBUG: tm_shutdown : start
>  0(0) DEBUG: unlink_timer_lists : emptying DELETE list
>  0(0) DEBUG: tm_shutdown : emptying hash table
>  0(0) DEBUG: tm_shutdown : releasing timers
>  0(0) DEBUG: tm_shutdown : removing semaphores
>  0(0) DEBUG: tm_shutdown : destroying tmcb lists
>  0(0) DEBUG: tm_shutdown : done
>  0(15549) shm_mem_destroy
>  0(15549) destroying the shared memory lock
>
>
>
> Bogdan-Andrei Iancu wrote:
>> Hi Michael,
>>
>> are you starting your openser in non fork mode?
>>
>> Regards,
>> Bogdan
>>
>> Michael Barinek wrote:
>>> I have openser-1.3.1-notls installed although am unable to start 
>>> openser. Any suggestions/ideas regarding the below error? Any 
>>> existing docs/links would be great.
>>>
>>> Thanks
>>>
>>> ///
>>>
>>> Mar 20 08:59:14 [18124] WARNING:core:fix_socket_list: could not rev. 
>>> resolve 10.138.86.56
>>> Mar 20 08:59:14 [18124] WARNING:core:fix_socket_list: could not rev. 
>>> resolve 10.138.87.100
>>> Mar 20 08:59:14 [18124] WARNING:core:fix_socket_list: could not rev. 
>>> resolve 10.37.129.2
>>> Mar 20 08:59:14 [18124] WARNING:core:fix_socket_list: could not rev. 
>>> resolve 10.211.55.2
>>> Mar 20 08:59:14 [18124] WARNING:core:fix_socket_list: could not rev. 
>>> resolve 10.138.86.56
>>> Mar 20 08:59:14 [18124] WARNING:core:fix_socket_list: could not rev. 
>>> resolve 10.138.87.100
>>> Mar 20 08:59:14 [18124] WARNING:core:fix_socket_list: could not rev. 
>>> resolve 10.37.129.2
>>> Mar 20 08:59:14 [18124] WARNING:core:fix_socket_list: could not rev. 
>>> resolve 10.211.55.2
>>> Listening on
>>>               udp: 127.0.0.1 [127.0.0.1]:5060
>>>               udp: 10.138.86.56 [10.138.86.56]:5060
>>>               udp: 10.138.87.100 [10.138.87.100]:5060
>>>               udp: 10.37.129.2 [10.37.129.2]:5060
>>>               udp: 10.211.55.2 [10.211.55.2]:5060
>>>               tcp: 127.0.0.1 [127.0.0.1]:5060
>>>               tcp: 10.138.86.56 [10.138.86.56]:5060
>>>               tcp: 10.138.87.100 [10.138.87.100]:5060
>>>               tcp: 10.37.129.2 [10.37.129.2]:5060
>>>               tcp: 10.211.55.2 [10.211.55.2]:5060
>>> Aliases:
>>>               tcp: my.machine.name:5060
>>>               udp: my.machine.name:5060
>>>
>>> Mar 20 08:59:14 [18124] WARNING:core:main: no fork mode  and more 
>>> than one listen address found(will use only the first one)
>>> Mar 20 08:59:14 [18124] INFO:core:init_tcp: using kqueue as the TCP 
>>> io watch method (auto detected)
>>> Mar 20 08:59:14 [18124] NOTICE:core:main: version: openser 
>>> 1.3.1-notls (i386/darwin)
>>> Mar 20 08:59:14 [18124] INFO:core:main: using 32 Mb shared memory
>>> Mar 20 08:59:14 [18124] INFO:core:main: using 1 Mb private memory 
>>> per process
>>> Mar 20 08:59:14 [18124] INFO:sl:mod_init: Initializing StateLess engine
>>> Mar 20 08:59:14 [18124] INFO:tm:mod_init: TM - initializing...
>>> Mar 20 08:59:14 [18124] CRITICAL:tm:uac_init: null socket list
>>> Mar 20 08:59:14 [18124] ERROR:tm:mod_init: uac_init failed
>>> Mar 20 08:59:14 [18124] ERROR:core:init_mod: failed to initialize 
>>> module tm
>>> Mar 20 08:59:14 [18124] ERROR:core:main: error while initializing 
>>> modules
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.openser.org
>>> http://lists.openser.org/cgi-bin/mailman/listinfo/users
>>>
>>>   
>>
>>
>