+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: System Setup & Installation (/forum-32.html)
+--- Thread: ERROR: Unable to connect SQL server ! (/thread-7977.html)
Pages: 1 2
RE: ERROR: Unable to connect SQL server ! - joximu - 12-01-2009 07:57 AM
please more infos - stop proftpd and run it like this:
proftpd -nd 5
output post here...
/J
RE: ERROR: Unable to connect SQL server ! - motokochan - 12-01-2009 01:17 PM
Is MySQL listening on port 3306?
Some distributions include the "--skip-networking" option on MySQL startup, which leaves MySQL only listening on a local socket. ispCP needs MySQL to listen on a network port.
RE: ERROR: Unable to connect SQL server ! - joximu - 12-01-2009 05:45 PM
hm, either -skip-networking or bind-address=127.0.0.1 do IMHO the same...
mysql must listen on localhost - the external IP is not a must.
/J
RE: ERROR: Unable to connect SQL server ! - motokochan - 12-01-2009 05:58 PM
(12-01-2009 05:45 PM)joximu Wrote: hm, either -skip-networking or bind-address=127.0.0.1 do IMHO the same...
They actually are different. Giving --skip-networking (just skip-networking in my.cnf) has MySQL not use any IP address. It only opens a local socket. Using bind-address does cause MySQL to listen on a port on a specific IP.
(12-01-2009 05:45 PM)joximu Wrote: mysql must listen on localhost - the external IP is not a must.
Indeed, having it only bind to localhost is fine and will work fine. However, skip-networking will not work. The first step in debugging this issue is making sure MySQL is listening on a port.