Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: BigEye on February 09, 2007, 05:35:31 AM
-
Ok, I'm a green horn and I've done a ton of looking around and I cant make this thing work on the lan interface :roll: Ive tried the following commands:
config setprop mysqld LocalNetworkingOnly no
# /sbin/e-smith/expand-template /etc/my.cnf
# /etc/rc.d/init.d/supervise/mysqld stop
Stopping mysqld: [ OK ]
# /etc/rc.d/init.d/supervise/mysqld start
Starting mysqld: [ OK ]
when I netstat -ln | grep mysql
I get this :
unix 2 [ ACC ] STREAM LISTENING 12819 /var/lib/mysql/mysql.sock
isnt the 12819 the port ? - when I try to connect on it I get 100061 error on the connector
After doing this I still get the following error on the MySQL ODBC 3.51 connector when I test :shock: :shock:
Access denied for user 'username'@'pc-00130.domain.com' (using password: YES)
one question I have is the @'pc-00130.domain.com' is not the database name I entered into the connector setup?
I'LL GLADLY ACCEPT ANY PITTY FROM SOME ONE OF KNOLEDGE :lol:
-
3306 is the default MySQL port.
-
I realised that I'm just unsure of how to get it to that or if that was what it was telling me?
-
I realised that I'm just unsure of how to get it to that or if that was what it was telling me?
-
well enough reading and finnally......
you have to use mysql odbc 3.5.12 (nothing older works)
also you have to specify user name with % for localhost permision, otherwise you get 10060 permision denied
and you also have to do the above lines entered with root permisions
:lol: :idea: :lol: :idea: :lol: :idea:
next on to the DNS server :shock:
any one with experience installing POWERDNS from powerdns.com :?:
-
BigEye
Go and read the mysql ODBC connector manual online, especially re how to set up users and passwords so that you can access your mysql dbs using the connector.
eg you want to enter something like this in mysql
grant all on dbname.* to username@localhost identified by 'password';
grant all on dbname.* to username@'%' identified by 'password';
flush privileges;
Of course you can be more specific with your privileges and user name etc, but you need to enter both the localhost and % versions (in that order).
Then put the db & user & pw into the ODBC connector setup.