I've tested this furthermore and has to say it's NOT solved :(

Even if I use shutdown via kannel's web-interface bearerbox still brokes up
with PANIC if there was a queue processing when restart command was issued.

So I guess the bug is somewhere inside the kannel.

2012/4/16 spameden <[email protected]>

> http://pastebin.com/w9mHmeHd -- init script for Debian (works fine on
> Debian Squeeze)
>
> also you need to add these lines to /etc/default/kannel:
>
> START_WAPBOX=0
> START_SMSBOX=1
> START_SMPPBOX=0
> START_SQLBOX=1
>
> if you need to enable particular service, just set it to 1.
>
>
>
> 2012/4/16 spameden <[email protected]>
>
>> needs further testing, but pretty sure it should be OK
>>
>> 2012/4/16 spameden <[email protected]>
>>
>>> I think I resolved this via workaround:
>>>
>>> altered /etc/init.d/kannel script with:
>>>
>>>   stop)
>>>     echo -n "Stopping WAP gateway:"
>>>     CORE_CONF=$(grep -r 'group[[:space:]]*=[[:space:]]*core' $CONFDIR |
>>> cut -d: -f1)
>>>     ADMIN_PORT=$(grep '^admin-port' $CORE_CONF | sed
>>> "s/.*=[[:space:]]*//")
>>>     ADMIN_PASS=$(grep '^admin-password' $CORE_CONF | sed
>>> "s/.*=[[:space:]]*//")
>>>     STOP_URL="http://127.0.0.1:
>>> ${ADMIN_PORT}/shutdown?password=${ADMIN_PASS}"
>>>     lynx -source $STOP_URL >/dev/null
>>>
>>> i.e. I'm shutting down bearerbox via it's web-interface before bringing
>>> down run-kannel-box daemons
>>>
>>> hopefully it will help someone else.
>>>
>>>
>>> 2012/4/12 spameden <[email protected]>
>>>
>>>> Hello, any update on this? Still having this issue with spool-queue
>>>> (happens also on filestore I think)
>>>>
>>>>
>>>> 2012/4/5 spameden <[email protected]>
>>>>
>>>>> Hello, list.
>>>>>
>>>>> This bug was already discussed here:
>>>>>
>>>>> http://www.kannel.org/pipermail/users/2010-August/012229.html
>>>>>
>>>>> But still no solution!
>>>>>
>>>>> I have smsbox->sqlbox->bearerbox scheme and _VERY_OFTEN_ if i restart
>>>>> kannel when it has active queue bearerbox fails to restart.
>>>>>
>>>>> Please suggest.
>>>>>
>>>>
>>>>
>>>
>>
>

Reply via email to