MYSQL connection problem (correction re-post)

[mario.lobo at ipad.com.br]

Hi Arun;

> hrmm.
> Can you try switching the port to another port number? Perhaps a lower port 
> number?
> See if you can get it to connect in that way?

Makes no difference

> In your log file, does it print messages about having successfully started 
> up?

Yes, it does. Like I said, if I use mysql.sock I connect fine. The problem is in TCP connections.

> Do you have ipfw or any other packet filter on your machine?

None whatsoever, of any kind.

-- 
   //|  //||
  // | // ||
-//--//---|| ARIO LOBO
//  //    ||
---------------------------------
mario.lobo at ipad.com.br
http://www.ipad.com.br


> 
> ----- Original Message ----- 
> From: <mario.lobo at ipad.com.br>
> To: "Arun Pereira" <arun at velcom.com>
> Cc: <freebsd-hackers at freebsd.org>
> Sent: Tuesday, November 30, 2004 12:24 PM
> Subject: Re: MYSQL connection problem (correction re-post)
> 
> 
> Sorry for this :( . Correction marked with  " <=====**** "
> 
> I typed a my.cnf from another machine. only the port differs.
> 
> ==============
> Yeah, it is the only one on that port. The worst part is that the connection 
> attempt doesn´t even
> generates a log entry !! I looked into the log also !!
> 
> netstat -an  | grep LIST
> tcp4       0      0  *.5007                 *.*                    LISTEN
> tcp4       0      0  *.199                  *.*                    LISTEN
> tcp4       0      0  *.443                  *.*                    LISTEN
> tcp4       0      0  *.80                   *.*                    LISTEN
> tcp4       0      0  127.0.0.1.25           *.*                    LISTEN
> tcp4       0      0  *.22                   *.*                    LISTEN
> 
> here is my.cnf
> 
> [mysqld]
> datadir=/bd/mysql/data
> socket=/home/xxxxxxx/mysql/mysql.sock
> 
> port=5007         <=====****
> 
> set-variable = max_connections=2000
> 
> [mysql.server]
> user=xxxxxxx
> basedir=/bd/
> 
> [safe_mysqld]
> err-log=/home/xxxxxxx/mysql/mysqld.log
> pid-file=/home/xxxxxxx/mysql/mysqld.pid
> 
> >
> > I know this might sound rather obvious but have you checked whether mysql 
> > is
> > actually listening on that port? Perhaps that port is  being used by 
> > another
> > daemon or process and mysql cannot bind to it while starting.
> > use netstat to check this. Also try and look at the error log file for the
> > mysql daemon. Usually this is located in the /var/db/mysql directory.
> >
> 
> -- 
>    //|  //||
>   // | // ||
> -//--//---|| ARIO LOBO
> //  //    ||
> ---------------------------------
> mario.lobo at ipad.com.br
> http://www.ipad.com.br
> 
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"
> 
> 
> 
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"