[OpenSIPS-Users] Raspberry Pi / OpenSIPS

[Răzvan Crainea]

Hi, Duncan!

It seems like the Rasperry Pi cannot allocate more than 250 semaphores 
at once, but the usrloc module and dialog try to allocate more than 
that. In order to get fewer errors, you should configure OpenSIPS to 
allocate for each module less than 250 semaphores. For the dialog and 
usrloc module you can use the hash_size parameter to do that:

modparam("usrloc", "hash_size", 7)
modparam("dialog", "hash_size", 7)

Setting the hash size to 7, it will allocate 2^7 = 128 semaphores, which 
is less than 250 the upper limit, therefore no critical errors will be 
displayed.
The first error (CRITICAL:tm:lock_set_init: semget ...) cannot be 
avoided from the script, you will have to change some defines in 
OpenSIPS source code.

Regards,

Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 07/05/2012 08:10 PM, Duncan Bell wrote:
> Hi
>
> I installed OpenSIPS on my Raspberry Pi as a project in exactly the 
> same way as I would on any other machine following the webinar guide 
> from the OpenSIPS site.  It works and I can register extensions etc, 
> but there are a huge amount of errors in the logs I normally do not get.
>
> The error starts here...
>
> Jul  3 18:32:14 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: 
> CRITICAL:tm:lock_set_init: semget (..., 251, 0700) failed: Invalid 
> argument
> Jul  3 18:32:14 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: 
> INFO:tm:lock_initialize: semaphore arrays of size 250 allocated
> Jul  3 18:32:14 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: INFO:rr:mod_init: rr - 
> initializing
> Jul  3 18:32:14 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: INFO:maxfwd:mod_init: 
> initializing...
> Jul  3 18:32:14 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: 
> INFO:sipmsgops:mod_init: initializing...
> Jul  3 18:32:14 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: 
> CRITICAL:usrloc:lock_set_init: semget (..., 512, 0700) failed: Invalid 
> argument
>
> and I get it counts all the way down from 512 > 250 with a line for 
> each error... until
>
> Jul  3 18:32:14 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: 
> CRITICAL:usrloc:lock_set_init: semget (..., 251, 0700) failed: Invalid 
> argument
> Jul  3 18:32:14 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: 
> INFO:usrloc:ul_init_locks: locks array size 250
> Jul  3 18:32:14 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: 
> INFO:registrar:mod_init: initializing...
> Jul  3 18:32:14 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: INFO:acc:mod_init: 
> initializing...
> Jul  3 18:32:14 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: INFO:auth:mod_init: 
> initializing...
> Jul  3 18:32:14 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: INFO:auth_db:mod_init: 
> initializing...
> Jul  3 18:32:14 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: INFO:dialog:mod_init: 
> Dialog module - initializing
> Jul  3 18:32:14 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: 
> CRITICAL:dialog:lock_set_init: semget (..., 2048, 0700) failed: 
> Invalid argument
>
> counting all the way down with a error per line from 2048 > 251
>
> Jul  3 18:32:15 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: 
> CRITICAL:dialog:lock_set_init: semget (..., 251, 0700) failed: Invalid 
> argument
> Jul  3 18:32:15 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: 
> INFO:core:probe_max_sock_buff: using rcv buffer of 216 kb
> Jul  3 18:32:15 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: 
> INFO:core:probe_max_sock_buff: using snd buffer of 216 kb
> Jul  3 18:32:15 raspberryvoip 
> /usr/local/opensips_proxy/sbin/opensips[1139]: 
> INFO:core:init_sock_keepalive: -- TCP keepalive enabled on socket
> Jul  3 18:32:15 raspberryvoip opensips: INFO:core:daemonize: 
> pre-daemon process exiting with 0
>
> Any ideas of these several thousand CRITICAL errors... or is this just 
> down to the unit not being able to handle OpenSIPS?
>
> Thanks
> Duncan
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20120706/309560c2/attachment.htm>