Hello Niko,
Here is the log, as you see everything seems to work with manual launch:
xxx:~# /usr/sbin/bearerbox /etc/kannel/kannel.conf
[1] 17633
xxx:~# 2010-01-26 01:18:04 [17633] [0] INFO: Debug_lvl = -1, log_file =
<none>, log_lvl = 0
2010-01-26 01:18:04 [17633] [0] INFO: MYSQL: Connected to server at
localhost.
2010-01-26 01:18:04 [17633] [0] INFO: MYSQL: server version
5.0.51a-24+lenny2, client version 5.0.51a.
2010-01-26 01:18:04 [17633] [0] INFO: MYSQL: Connected to server at
localhost.
2010-01-26 01:18:04 [17633] [0] INFO: MYSQL: server version
5.0.51a-24+lenny2, client version 5.0.51a.
2010-01-26 01:18:04 [17633] [0] INFO: DLR using storage type: mysql
2010-01-26 01:18:04 [17633] [0] DEBUG: Kannel bearerbox version `1.4.1'.
Build `Oct 17 2006 05:35:40', compiler `4.1.2 20061007 (prerelease) (Debian
4.1.1-16)'.
System Linux, release 2.6.31.5-grsec-xxxx-grs-ipv4-64, version #3 SMP Tue
Nov 24 16:51:16 UTC 2009, machine x86_64.
Hostname iggmedia.com, IP xx.xx.xx.xx
Libxml version 2.6.26.
Using OpenSSL 0.9.8c 05 Sep 2006.
Compiled with MySQL 5.0.24a, using MySQL 5.0.51a.
Using native malloc.
2010-01-26 01:18:04 [17633] [0] INFO: Added logfile
`/var/log/kannel/bearerbox/gateway.log' with level `0'.
2010-01-26 01:18:04 [17633] [0] INFO: Started access logfile
`/var/log/kannel/billing/access.log'.
2010-01-26 01:18:04 [17633] [0] INFO: HTTP: Opening server at port 13000.
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 1
(gwlib/fdset.c:poller)
2010-01-26 01:18:04 [17633] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps
to pid 17633.
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 2
(gwlib/http.c:server_thread)
2010-01-26 01:18:04 [17633] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread)
maps to pid 17633.
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 3
(gw/bb_http.c:httpadmin_run)
2010-01-26 01:18:04 [17633] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run)
maps to pid 17633.
2010-01-26 01:18:04 [17633] [0] DEBUG: starting smsbox connection module
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 4
(gw/bb_boxc.c:sms_to_smsboxes)
2010-01-26 01:18:04 [17633] [4] DEBUG: Thread 4
(gw/bb_boxc.c:sms_to_smsboxes) maps to pid 17633.
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 5
(gw/bb_boxc.c:smsboxc_run)
2010-01-26 01:18:04 [17633] [5] DEBUG: Thread 5 (gw/bb_boxc.c:smsboxc_run)
maps to pid 17633.
2010-01-26 01:18:04 [17633] [0] INFO: Set SMS resend frequency to 60
seconds.
2010-01-26 01:18:04 [17633] [0] INFO: SMS resend retry set to unlimited.
2010-01-26 01:18:04 [17633] [0] INFO: DLR rerouting for smsc id <DHSL>
disabled.
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 6
(gw/smsc/smsc_smpp.c:io_thread)
2010-01-26 01:18:04 [17633] [6] DEBUG: Thread 6
(gw/smsc/smsc_smpp.c:io_thread) maps to pid 17633.
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 7
(gw/smsc/smsc_smpp.c:io_thread)
2010-01-26 01:18:04 [17633] [7] DEBUG: Thread 7
(gw/smsc/smsc_smpp.c:io_thread) maps to pid 17633.
2010-01-26 01:18:04 [17633] [0] INFO: DLR rerouting for smsc id <FHSL>
disabled.
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 8
(gw/smsc/smsc_smpp.c:io_thread)
2010-01-26 01:18:04 [17633] [8] DEBUG: Thread 8
(gw/smsc/smsc_smpp.c:io_thread) maps to pid 17633.
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 9
(gw/smsc/smsc_smpp.c:io_thread)
2010-01-26 01:18:04 [17633] [9] DEBUG: Thread 9
(gw/smsc/smsc_smpp.c:io_thread) maps to pid 17633.
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 10
(gw/bb_smscconn.c:sms_router)
2010-01-26 01:18:04 [17633] [10] DEBUG: Thread 10
(gw/bb_smscconn.c:sms_router) maps to pid 17633.
2010-01-26 01:18:04 [17633] [0] DEBUG: starting UDP sender/receiver module
2010-01-26 01:18:04 [17633] [10] DEBUG: sms_router: time to sleep 30.00
secs.
2010-01-26 01:18:04 [17633] [0] INFO: Adding interface *
2010-01-26 01:18:04 [17633] [0] DEBUG: udpc_create: Bound to UDP
<0.0.0.0:9200>
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 11
(gw/bb_udp.c:udp_receiver)
2010-01-26 01:18:04 [17633] [11] DEBUG: Thread 11 (gw/bb_udp.c:udp_receiver)
maps to pid 17633.
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 12
(gw/bb_udp.c:udp_sender)
2010-01-26 01:18:04 [17633] [12] DEBUG: Thread 12 (gw/bb_udp.c:udp_sender)
maps to pid 17633.
2010-01-26 01:18:04 [17633] [0] DEBUG: udpc_create: Bound to UDP
<0.0.0.0:9201>
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 13
(gw/bb_udp.c:udp_receiver)
2010-01-26 01:18:04 [17633] [13] DEBUG: Thread 13 (gw/bb_udp.c:udp_receiver)
maps to pid 17633.
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 14
(gw/bb_udp.c:udp_sender)
2010-01-26 01:18:04 [17633] [0] DEBUG: starting wapbox connection module
2010-01-26 01:18:04 [17633] [14] DEBUG: Thread 14 (gw/bb_udp.c:udp_sender)
maps to pid 17633.
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 15
(gw/bb_boxc.c:wdp_to_wapboxes)
2010-01-26 01:18:04 [17633] [15] DEBUG: Thread 15
(gw/bb_boxc.c:wdp_to_wapboxes) maps to pid 17633.
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 16
(gw/bb_boxc.c:wapboxc_run)
2010-01-26 01:18:04 [17633] [0] DEBUG: starting WDP router
2010-01-26 01:18:04 [17633] [16] DEBUG: Thread 16 (gw/bb_boxc.c:wapboxc_run)
maps to pid 17633.
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 17
(gw/bearerbox.c:wdp_router)
2010-01-26 01:18:04 [17633] [0]
INFO: ----------------------------------------
2010-01-26 01:18:04 [17633] [0] INFO: Kannel bearerbox II version 1.4.1
starting
2010-01-26 01:18:04 [17633] [17] DEBUG: Thread 17
(gw/bearerbox.c:wdp_router) maps to pid 17633.
2010-01-26 01:18:04 [17633] [0] INFO: Loading store file
`/var/cache/smsgateway/store'
2010-01-26 01:18:04 [17633] [0] INFO: Store-file size 0, starting to unpack
2010-01-26 01:18:04 [17633] [0] INFO: Retrieved 0 messages, non-acknowledged
messages: 0
2010-01-26 01:18:04 [17633] [0] DEBUG: Started thread 18
(gw/bb_store.c:store_dumper)
2010-01-26 01:18:04 [17633] [0] INFO: MAIN: Start-up done, entering mainloop
2010-01-26 01:18:04 [17633] [18] DEBUG: Thread 18
(gw/bb_store.c:store_dumper) maps to pid 17633.
..... etc ....
Do you find something wrong here?
Efraristo patriati,
Nikos
----- Original Message -----
From: "Nikos Balkanas" <[email protected]>
To: "CHRONIS, N." <[email protected]>; "Jovan Kostovski" <[email protected]>
Cc: <[email protected]>
Sent: Monday, January 25, 2010 11:15 PM
Subject: Re: Problem launching with /etc/init.d/kannel
Hi Niko,
From a console type:
gw/bearerbox <conffile>
And post output. If not output is created check /var/log/messages for any
segfaults. If that fails try:
ldd gw/bearerbox
to see if you are linking to a wrong (32bit) library.
BR,
Nikos
----- Original Message -----
From: "CHRONIS, N." <[email protected]>
To: "Jovan Kostovski" <[email protected]>
Cc: <[email protected]>
Sent: Monday, January 25, 2010 11:27 PM
Subject: Re: Problem launching with /etc/init.d/kannel
Hello Jovan,
The startup script is the same also.
Nothing has been changed. Strange error.
Kannel is started by start-stop-daemon. No error, processes launched, but
log file not recording with the old kannel.conf
I really don't know how to fix this. I tryed so much things...
If anyone can help me, it would be really nice.
Best regards,
Nikos
----- Original Message -----
From: "Jovan Kostovski" <[email protected]>
To: "CHRONIS, N." <[email protected]>
Sent: Monday, January 25, 2010 10:08 PM
Subject: Re: Problem launching with /etc/init.d/kannel
On Mon, Jan 25, 2010 at 5:14 PM, CHRONIS, N. <[email protected]> wrote:
Hello everybody,
I migrated my server to a 64 bits server.
Server is Debian stable.
Kannel is 1.4.1
After an apt-get install kannel, the services is launched properly, but
after I enter my "old" (working) config, nothing happend, and no log
files
appear, eithe no error.
check the startup script.
If the only thing that was changed was the system and the startup script
check to see how kannel is started
But if I launch it manually (without the start-stop-daemon) i can see
log
file in console.
check the user with which the script is run, and see if it has write
permissions
in the folder where the logs should be created.
BR, Jovan
__________ Information provenant d'ESET NOD32 Antivirus, version de la
base des signatures de virus 4026 (20090421) __________
Le message a οΏ½tοΏ½ vοΏ½rifiοΏ½ par ESET NOD32 Antivirus.
http://www.eset.com
__________ Information provenant d'ESET NOD32 Antivirus, version de la
base des signatures de virus 4026 (20090421) __________
Le message a ιtι vιrifiι par ESET NOD32 Antivirus.
http://www.eset.com
