fist of all,
I see setted two identical smsbox configurations, one of them without smsbox-id
next the sqlbox with same smsbox-id of smsbox-01
in case you want to use the sqlbox handling ONLY MT traffic
you have to start the sqlbox instance after you have the smsbox running
so the order is bearererbox, smsbox, sqlbox
in case you want sqlbox to handle all the MO MT and DLR traffic, the order will
be
bearerbox, sqlbox, smsbox and
the sqlbox config will need some adjustments
-----Original Message-----
From: users @ kannel. org [EMAIL PROTECTED]
Sent: 14 ????? 2008 ?.
To: seik
Subject:Store's growing, smsbox doesnt seem to take MOs
> Here's the configs:
> group = core
> admin-port = 13000
> admin-password = fxxbar
> status-password = sTtx
> admin-deny-ip = "*.*.*.*"
> admin-allow-ip = "*.*.*.*"
> box-deny-ip = "*.*.*.*"
> box-allow-ip = "*.*.*.*"
> wdp-interface-name = "*"
> log-file = "/var/log/kannel/main.log"
> log-level = 1
> access-log = "/var/log/kannel/raw.log"
> smsbox-port = 13001
> dlr-storage = pgsql
> store-type = spool
> store-location = "/var/spool/kannel"
> #include = "/etc/kannel/bx-sql.conf"
> include = "/etc/kannel/bx-sms.conf"
> include = "/etc/kannel/smsc.conf"
> include = "/etc/kannel/routing-mo.conf"
> include = "/etc/kannel/routing-mt.conf"
> include = "/etc/kannel/db.conf"
> include = "/etc/kannel/routing-dlr.conf"
> group = smsbox
> bearerbox-host = "localhost"
> log-file = "/var/log/kannel/bx-sms.log"
> log-level = 0
> mo-recode = true
> http-request-retry = 10
> http-queue-delay = 60
> smsbox-id = smsbox-01
> sendsms-port = 13002
> #bearerbox-is-sqlbox = true
> group = smsbox
> bearerbox-host = "localhost"
> log-file = "/var/log/kannel/bx-sms2.log"
> log-level = 0
> mo-recode = true
> http-request-retry = 10
> http-queue-delay = 60
> #smsbox-id = smsbox-01
> sendsms-port = 13002
> #bearerbox-is-sqlbox = true
> group = sqlbox
> id = dlr-01-db
> smsbox-id = smsbox-01
> bearerbox-host = "127.0.0.1"
> bearerbox-port = 13001
> smsbox-port = 13005
> smsbox-port-ssl = false
> sql-log-table = k_messaginglog
> sql-insert-table = k_messagingqueues
> log-file = "/var/log/kannel/bx-sql.log"
> log-level = 2
> And here's the startup script:
> #!/bin/sh
> START_SMSBOX='YES'
> START_WAPBOX=''
> START_SQLBOX='YES'
> BOXPATH=/usr/local/sbin
> PIDFILES=/var/kannel
> CONF=/etc/kannel/bx-bearer.conf
> CONFSQL=/etc/kannel/bx-sql.conf
> PATH=$BOXPATH:$PATH
> case "$1" in
> start)
> echo -n "Starting Kannel:"
> echo -n " bearerbox"
> start-stop-daemon --start --quiet \
> --pidfile $PIDFILES/bearerbox.pid \
> --chuid kannel \
> --exec $BOXPATH/run_kannel_box \
> -- \
> --pidfile $PIDFILES/bearerbox.pid \
> --no-extra-args \
> $BOXPATH/bearerbox -v 4 -- $CONF
> sleep 1 # Wait for bearerbox
> test ! -z $START_SQLBOX && (
> echo -n " SQL"
> start-stop-daemon --start --quiet \
> --pidfile $PIDFILES/sqlbox.pid \
> --chuid kannel \
> --exec $BOXPATH/run_kannel_box \
> -- \
> --pidfile $PIDFILES/sqlbox.pid \
> --no-extra-args \
> /usr/local/bin/sqlbox -v 4 -- $CONFSQL
> )
> test ! -z $START_WAPBOX && (
> echo -n " WAP"
> start-stop-daemon --start --quiet \
> --pidfile $PIDFILES/wapbox.pid \
> --chuid kannel \
> --exec $BOXPATH/run_kannel_box \
> -- \
> --pidfile $PIDFILES/wapbox.pid \
> --no-extra-args \
> $BOXPATH/wapbox -v 4 -- $CONF
> )
> test ! -z $START_SMSBOX && (
> echo -n " SMS"
> start-stop-daemon --start --quiet \
> --pidfile $PIDFILES/smsbox.pid \
> --chuid kannel \
> --exec $BOXPATH/run_kannel_box \
> -- \
> --pidfile $PIDFILES/smsbox.pid \
> --no-extra-args \
> $BOXPATH/smsbox -v 4 -- $CONF
> )
> echo "."
> ;;
> stop)
> echo -n "Stopping Kannel:"
> test ! -z $START_SMSBOX && (
> echo -n " SMS"
> start-stop-daemon --stop --quiet \
> --pidfile $PIDFILES/smsbox.pid \
> --exec $BOXPATH/run_kannel_box
> )
> test ! -z $START_WAPBOX && (
> echo -n " WAP"
> start-stop-daemon --stop --quiet \
> --pidfile $PIDFILES/wapbox.pid \
> --exec $BOXPATH/run_kannel_box
> )
> test ! -z $START_SQLBOX && (
> echo -n " SQL"
> start-stop-daemon --stop --quiet \
> --pidfile $PIDFILES/sqlbox.pid \
> --exec $BOXPATH/run_kannel_box
> )
> echo -n " MAIN"
> start-stop-daemon --stop --quiet \
> --pidfile $PIDFILES/bearerbox.pid \
> --exec $BOXPATH/run_kannel_box
> echo "."
> ;;
> reload)
> # We don't have support for this yet.
> exit 1
> ;;
> restart|force-reload)
> $0 stop
> sleep 10
> $0 start
> ;;
> *)
> echo "Usage: $0 {start|stop|restart|force-reload}"
> exit 1
> esac
> exit 0
> On Mon, Apr 14, 2008 at 7:01 PM, seik <[EMAIL PROTECTED]> wrote:
> what is the start order of your kannel boxes ?
> bearerbox, then sqlbox, then smsbox ?
> OR bearerbox, smsbox, sqlbox ?
> what ARE the sqlbox and the smsbox config ?
> -----Original Message-----
> From: [email protected] [EMAIL PROTECTED]
> Sent: 14 ????? 2008 ?.
> To: seik
> Subject:Store's growing, smsbox doesnt seem to take MOs
>> I have a problem with MOs get no execution and stay on the bearer side
>> (queued).
>> Problem is detected on 1.4.1, upgraded to the latest cvs HEAD
>> (cvs-20080409) and still have the same problem.
>> I receive MOs, but nothing gets passed to smsbox, reading the logs,
>> for every received MO (in the access log) i get a line in the bearerbox-log
>> like this:
>> 2008-04-14 16:44:44 [19228] [9] WARNING: smsbox_list empty!
>> I thought smsbox is not connected to bearerbox, but it's not the case, i
>> have lines like this:
>> 2008-04-14 16:39:59 [19228] [5] INFO: Client connected from <127.0.0.1>
>> I get such problem in a non regular basis, kannel keeps going
>> without problems and with nothing new, it gets into queuing MOs and stops
>> forwarding to smsbox.
>> here's a typical status page of kannel at the queuing stage:
>> Kannel bearerbox version `cvs-20080409'. Build `Apr 14 2008
>> 16:34:09', compiler `4.1.2 20061115 (prerelease) (Debian 4.1.1-21)'.
>> System Linux, release 2.6.18-5-686, version #1 SMP Tue Dec 18
>> 21:24:20 UTC 2007, machine i686. Hostname tux2.tun-school.com, IP
>> 127.0.1.1. Libxml version 2.6.27. Using OpenSSL 0.9.8c 05 Sep 2006. Using
>> native malloc.
>> Status: running, uptime 0d 0h 7m 3s
>> WDP: received 0 (0 queued), sent 0 (0 queued)
>> SMS: received 89 (89 queued), sent 0 (0 queued), store size 89
>> SMS: inbound 0.21 msg/sec, outbound 0.00 msg/sec
>> DLR: 19 queued, using pgsql storage
>> Box connections:
>> smsbox:smsbox-01, IP 127.0.0.1 (0 queued), (on-line 0d 0h 7m 1s)
>> smsbox:smsbox-01, IP 127.0.0.1 (0 queued), (on-line 0d 0h 6m 2s)
>> SMSC connections:
>> SMPP-01-TT SMPP:172.17.23.6:2775/2775:smgs:VMA (online 423s,
>> rcvd 0, sent 0, failed 0, queued 0 msgs)
>> SMPP-02-TT SMPP:192.168.160.18:2775/2775:reclamationtt:VMA
>> (online 423s, rcvd 89, sent 0, failed 0, queued 0 msgs)
>> As you can see, and as i can understand ,smsbox is connected (i
>> dont know why it shows two smsboxes with the same id, i have only
>> one) and there's nothing queued at smsbox side ...
>> Am using sqlbox for MT sending, but as i think, it has nothing to
>> do with this randomly occured problem.
>> Hoping to get any help, thanks,
