I don't start the kanne; in a different way when using the dlr-storage=mysql. And when using internal I don't have the problem. So how can it be related to the order in which I start the services?
Anyways, when starting only berearbox I get the following exception: [EMAIL PROTECTED] sbin]# ./bearerbox -v 0 /usr/local/kannel/etc/kannel.conf 2007-11-11 09:58:29 [26371] [0] INFO: Debug_lvl = 0, log_file = <none>, log_lvl = 0 2007-11-11 09:58:29 [26371] [0] PANIC: DLR: storage type 'mySql' is not supported! 2007-11-11 09:58:29 [26371] [0] PANIC: ./bearerbox(gw_panic+0xa3) [0x80dd347] 2007-11-11 09:58:29 [26371] [0] PANIC: ./bearerbox(dlr_init+0x1c0) [0x8083e88] 2007-11-11 09:58:29 [26371] [0] PANIC: ./bearerbox(main+0xec) [0x807a450] 2007-11-11 09:58:29 [26371] [0] PANIC: /lib/tls/libc.so.6(__libc_start_main+0xe3) [0x30be33] 2007-11-11 09:58:29 [26371] [0] PANIC: ./bearerbox [0x8079ed9] Meaning it says mysql is not supported, and this is after I compiled it with mysql specifically. So what can it be? Knaan Ratosh Acting VP R&D AxisMobile Ltd. Consumer Mobile Email Tel: Int +972-3-7685529 Mobile: Int +972-54-3138460 [EMAIL PROTECTED] -----Original Message----- From: Rodrigo Cremaschi [mailto:[EMAIL PROTECTED] Sent: Friday, November 09, 2007 2:44 PM To: Enver ALTIN Cc: users@kannel.org Subject: Re: Problem starting kannel with dlr-storage mysql Hi Knaan, > 2007-11-09 07:21:48 [2652] [0] ERROR: error connecting to server `localhost' at port `13002' > 2007-11-09 07:21:48 [2652] [0] PANIC: Couldn't connect to the bearerbox. Be sure that bearerbox is up and running before starting any other box. On Nov 9, 2007 7:30 AM, Enver ALTIN <[EMAIL PROTECTED]> wrote: > On Fri, 2007-11-09 at 10:05 +0200, Knaan Ratosh wrote: > > I was trying to start the kannel using dlr-storage=mysql, but the it > > fails. The logs in the wapbox.log say: > > wapbox.log doesn't help, in order to understand the problem we need the > output from bearerbox. > -- > Enver > ************************************************************************ ************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses. ************************************************************************ ************
