Glad you solved it. Actually I'd suggest using socket instead of local interface if you're using MySQL on the same server where kannel installed. It gives more performance, to do this just remove port = 3306 directive from your sqlbox.conf.
2012/6/24 Moazzam Ali <moz...@gmail.com> > Thanks, i got it working. It was MySQL, you were right. I increased the > wait_timeout to 24 hours and the error has gone > > //moazzam > > On 06/23/2012 9:09 PM, spameden wrote: > > What about sqlbox ? Is it from latest SVN as well? You need to compile it > after you've installed kannel from trunk. > > Also try dropping kannel's database tables, sqlbox should re-create them > upon startup. > > 'MySQL server has gone away' generally means something wrong with your > MySQL setup, not with kannel. > > 2012/6/23 Julien Buratto <julien.bura...@linkas.it> > >> Why don't you try to measure how long that happens from start of >> connection ? >> Ie: start kannel and see what happens after x seconds until it goes to >> error.. Maybe is a timeout.. 120 secs is short if kannel is not keepaliving >> the connection.. >> >> Also check your my.cnf file as the compiled mysql libs us such conf file >> And check that libs are same version of server.. >> Test another mysql server instance and see if it happens again >> >> Julien Buratto >> Linkas SRL >> Tel.02 30321419 >> ------------------------------ >> *From: * Moazzam Ali <moz...@gmail.com> >> *Date: *Sat, 23 Jun 2012 18:41:13 +0500 >> *To: *spameden<spame...@gmail.com> >> *Cc: *<julien.bura...@linkas.it>; <users-boun...@kannel.org>; < >> users@kannel.org> >> *Subject: *Re: R: Kannel MySQL problem >> >> already upgraded to latest snapshot but error still persists >> >> 2012-06-23 13:29:59 [14633] [6] ERROR: MYSQL: database check failed! >> 2012-06-23 13:29:59 [14633] [6] ERROR: MYSQL: MySQL server has gone away >> >> >> >> >> On 06/23/2012 4:43 PM, spameden wrote: >> >> Why don't you use latest from the trunk? There were lots of fixes since >> 1.4.3. >> >> 2012/6/23 Moazzam Ali <moz...@gmail.com> >> >>> complied kannel 1.4.3 stable with mysql support from source on CentOS >>> 6 64-bit >>> >>> //moazzam >>> >>> On 06/23/2012 4:40 PM, spameden wrote: >>> >>> How did you install kannel? Is it from debian's packages? >>> >>> Try to install latest from SVN. >>> >>> 2012/6/23 Moazzam Ali <moz...@gmail.com> >>> >>>> wait_timeout is set to 120, is it the case? there is no firewall >>>> between mysql and kannel as they are both on localhost >>>> >>>> //moazzam >>>> >>>> >>>> On 06/23/2012 2:38 AM, Julien Buratto wrote: >>>> >>>>> Ali, >>>>> >>>>> Check also timeouts values in mysql.. Are you using a custom >>>>> configured mysql ? >>>>> Do you have any firewall/proxy/etc in between ? >>>>> Julien Buratto >>>>> Linkas SRL >>>>> Tel.02 30321419 >>>>> >>>>> -----Original Message----- >>>>> From: Moazzam Ali <moz...@gmail.com> >>>>> Sender: users-bounces@kannel.orgDate: Fri, 22 Jun 2012 23:33:00 >>>>> To: <users@kannel.org> >>>>> Subject: Kannel MySQL problem >>>>> >>>>> >>>>> I am facing one issue with the kannel 1.4.3 and MySQL, due to some >>>>> unknown reason sometime kannel throw following error in the log >>>>> >>>>> 2012-06-22 17:14:50 [18671] [6] ERROR: MYSQL: database check failed! >>>>> 2012-06-22 17:14:50 [18671] [6] ERROR: MYSQL: MySQL server has gone >>>>> away >>>>> 2012-06-22 17:14:50 [18671] [6] DEBUG: DBPool has too few connections, >>>>> reconnecting up to maximum... >>>>> 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: Connected to server at >>>>> localhost. >>>>> 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: server version 5.1.61-log, >>>>> client version 5.1.61. >>>>> 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: Connected to server at >>>>> localhost. >>>>> 2012-06-22 17:14:50 [18671] [6] INFO: MYSQL: server version 5.1.61-log, >>>>> client version 5.1.61. >>>>> >>>>> i have already tried increasing the max_connection both in kannel db >>>>> connection setting and in my.cnf but still same >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> > > >
