Yes, after clear the spool files, i tried both:
kill -HUP <processid>
or
killall -HUP bearerbox
bearerbox's log shows that box already received the kill signal:
2014-11-14 09:16:01 [8086] [0] WARNING: SIGHUP received, catching and
re-opening logs
But bearerbox still keep retrying to find the route for queued messages. Ah
sorry that i'm talking about the MO message that bearerbox received from
upstream SMSC. I've not tested for MT sent out message yet.
::Lamnt
From: tapan.thapa2...@gmail.com
Date: Thu, 13 Nov 2014 20:03:10 -0800
Subject: RE: Delete message from queue
To: lam...@outlook.com; ismaberr...@yahoo.fr
CC: users@kannel.org
Have u given HUP singnal to bearerbox process Id after moving spool files?
Sent from my Windows PhoneFrom: Lam Nguyen Tuong
Sent: 14-11-2014 07:59
To: Tapan Kumar Thapa; ismail berrada
Cc: users@kannel.org
Subject: RE: Delete message from queue
Unfortunately, it is not work, Tapan.
Event spool files has been deleted, bearerbox still keep the queue in mem until
it be restarted.
Any idea?
Thanks.
::Lamnt.
Date: Thu, 13 Nov 2014 20:07:10 +0530
Subject: Re: Delete message from queue
From: tapan.thapa2...@gmail.com
To: ismaberr...@yahoo.fr
CC: users@kannel.org
You can delete the file however you also need to send a HUP signal to bearerbox.
ps -wef |grep bearerbox|grep -v grep // Check its process id
than
kill -HUP <processid>
On Thu, Nov 13, 2014 at 7:26 PM, ismail berrada <ismaberr...@yahoo.fr> wrote:
Hello
I have a MO that is not well formed and it is not sent to the ESME
I want to delete this MO without restarting kannel (production case)
The store type is spool and I found the file that contains the MO
The MO is blocked on SMPP Box side
Can I delete the file without any consequences and without restarting Kannel ?
Best regards
