[Spce-user] lb and proxy not starting

[Andrew Pogrebennyk]

Hi,
for the record: there was a typo in load-balancer config when TLS is
enabled. I have pushed the fix to 2.7 repo today. So this thread can be
considered solved now.

On 01/23/2013 10:43 AM, Andreas Granig wrote:
> Hi,
> 
> Try to play with the pkg_mem and shm_mem settings in config.yml (there
> are two of each, one for lb, one for proxy), you might need to increase
> them. The given values are in MB.
> 
> Andreas
> 
> On 01/23/2013 12:08 AM, Jirka Jirout wrote:
>> Hello,
>>
>> I have a weird problem. Today, I got our verisign certificates and
>> decided to switch to them fully. I have changed the paths in
>> config.yml, ngcpcfg apply and the TLS was using my certificate. Then I
>> wanted to use it for www admin interface as well. Again, changed the
>> paths and.... Kamailio instances will not start. When I try to start
>> them manually using /etc/init.d/kamailio-proxy (or -lb) the proxy
>> reports an error in configuration file:
>>
>>> Not executing command for kamailio-proxy: invalid configuration file!
>>> -e
>>>   0(29874) : <core> [cfg.lex:1456]: ERROR:lex:addstr: memory
>>> allocation error
>>>   0(29874) : <core> [cfg.lex:1458]: ERROR:lex:addstr: try to increase
>>> pkg size with -M parameter
>>
>> While the load balancer goes thru the check and then fails:
>>
>>> Starting kamailio-lb using /etc/kamailio/lb/kamailio.cfg:
>>> loading modules under
>>> /usr/lib/kamailio/modules_k:/usr/lib/kamailio/modules
>>> Listening on
>>>               udp: 172.30.39.11 [172.30.39.11]:5888
>>>               udp: 127.0.0.1:5888
>>>               tcp: 172.30.39.11 [172.30.39.11]:5888
>>>               tcp: 127.0.0.1:5888
>>>               tls: 172.30.39.11 [172.30.39.11]:5889
>>> Aliases:
>>>               *: public_ip:5889
>>>               *: public_ip:5888
>>>
>>> kamailio error, failed to start.
>>
>> The log contains something like this:
>>
>>> Jan 22 23:39:19 crypto2 kamailio: INFO: tls [tls_init.c:377]: tls:
>>> init_tls: disabling compression...
>>> Jan 22 23:39:19 crypto2 kamailio: INFO: <core> [tcp_main.c:4829]:
>>> init_tcp: using epoll_lt as the io watch method (auto detected)
>>> Jan 22 23:39:19 crypto2 /usr/sbin/kamailio[29991]: WARNING: sl
>>> [../../modules/tm/tm_load.h:151]: Cannot import load_tm function from
>>> tm module
>>> Jan 22 23:39:19 crypto2 /usr/sbin/kamailio[29991]: INFO: sl
>>> [sl.c:163]: could not bind tm module - only stateless mode available
>>> Jan 22 23:39:19 crypto2 /usr/sbin/kamailio[29991]: INFO: usrloc
>>> [hslot.c:53]: locks array size 512
>>> Jan 22 23:39:19 crypto2 /usr/sbin/kamailio[29991]: INFO: db_text
>>> [dbt_base.c:99]: using database at: /etc/kamailio/lb/db
>>> Jan 22 23:39:19 crypto2 /usr/sbin/kamailio[29991]: INFO: db_text
>>> [dbt_base.c:99]: using database at: /etc/kamailio/lb/db
>>> Jan 22 23:39:19 crypto2 /usr/sbin/kamailio[29991]: INFO: tls
>>> [tls_init.c:541]: tls: _init_tls_h:  compiled  with  openssl  version
>>> "OpenSSL 0.9.8o 01 Jun 2010" (0x009080ff), kerberos support: off,
>>> compression: on
>>> Jan 22 23:39:19 crypto2 /usr/sbin/kamailio[29991]: INFO: tls
>>> [tls_init.c:549]: tls: init_tls_h: installed openssl library version
>>> "OpenSSL 0.9.8o 01 Jun 2010" (0x009080ff), kerberos support: off, 
>>> zlib compression: on#012 compiler: gcc -fPIC -DOPENSSL_PIC -DZLIB
>>> -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64
>>> -DL_ENDIAN -DTERMIO -O3 -Wa,--noexecstack -g -Wall -DMD32_REG_T=int
>>> -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM
>>> -DAES_ASM
>>> Jan 22 23:39:19 crypto2 /usr/sbin/kamailio[29991]: WARNING: tls
>>> [tls_init.c:603]: tls: openssl bug #1491 (crash/mem leaks on low
>>> memory) workaround enabled (on low memory tls operations will fail
>>> preemptively) with free memory thresholds 16777216 and 8388608 bytes
>>> Jan 22 23:39:19 crypto2 /usr/sbin/kamailio[29991]: INFO: <core>
>>> [cfg/cfg_ctx.c:613]: INFO: cfg_set_now(): tls.low_mem_threshold1 has
>>> been changed to 16777216
>>> Jan 22 23:39:19 crypto2 /usr/sbin/kamailio[29991]: INFO: <core>
>>> [cfg/cfg_ctx.c:613]: INFO: cfg_set_now(): tls.low_mem_threshold2 has
>>> been changed to 8388608
>>> Jan 22 23:39:19 crypto2 /usr/sbin/kamailio[29991]: ERROR: maxfwd
>>> [maxfwd.c:119]: invalid MAXFWD number <0> [1,256]
>>> Jan 22 23:39:19 crypto2 /usr/sbin/kamailio[29991]: ERROR: <core>
>>> [route.c:1216]: fixing failed (code=-1) at
>>> cfg:/etc/kamailio/lb/kamailio.cfg:160
>>> Jan 22 23:39:19 crypto2 /usr/sbin/kamailio[29991]: ERROR: <core>
>>> [route.c:1216]: fixing failed (code=-1) at
>>> cfg:/etc/kamailio/lb/kamailio.cfg:168
>>
>> What is particularly frustrating is the fact, that this error persists
>> even after I return to the previous version of the config.yml which
>> used to work fine just a few hours ago (that uses default self-signed
>> certificates) or even to the factory default config file.
>>
>> More info:
>> - spce version 2.6
>> - there is about 800 MB free memory
>> - the certificate and the key are fine
>>
>> Any tips? I really do not want to reinstall the whole thing or even
>> restore weekly backup if it is not absolutely necessary...
>>
>> regards, jj
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/listinfo/spce-user
>>
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user