Ok, afraid I'm having to ask: how do access the mysql log file? Or,
how to enable logging... I gather this will cause a verbose mode from
the CLI?
Not sure what I should be doing here.
Thanks in advance.
As for the 3 elements listed below --wouldn't those be present in the
mysql db already if I can get in through the CLI, which I can?
On May 29, 2005, at 6:39 PM, sol beach wrote:
Gil,
THREE elements need to be match what is stored inside MYSQL DB.
1) username
2) password
3) hostname
You need to enable MYSQL logging, restart the DB, & try to login
from PHP.
Then, take a look at what MYSQL shows in its logfile & post the
results here!
YMMV
On 5/29/05, Peter <[EMAIL PROTECTED]> wrote:
Hi,
here is a workaround that might help you.
I guess you have a Network card. So instead of using 'localhost'
as host
use your ip e.g '192.168.0.1;. That will force MySQl use TCP/IP
instead
of socket.
Just have in mind that:
1. In /etc/my.cnf You should comment "skip-networking" if presenet
2. Make sure your user is allowed to make connections from YOUR_IP
3. Make sure you do not have Iptables rule that may block your
access.
Peter
[EMAIL PROTECTED] wrote:
Remember guys, I went through this on the phpmyadmin list before
turning here.
I was told to run the command 'mysqladmin variables' to find out
where
the the socket was; I did that successfully and it showed up at
/var/mysql/mysql.sock.
And viola, now with mysqld running, it does show up there, at /var/
mysql/mysql.sock.
When I shutdown mysqld it is gone, from /var/mysql.
(Btw, once in a recent post of mine, Philip referred to my
leaving out
the leading / at 'var', that was simply a typo and it was in the
script
post.)
So, running 'mysql variables' is giving me the socket path and I'm
still lost as to what's going why I cannot connect with a simple php
script.
Help?! I'll look for the mysql error log.
Gil
On May 29, 2005, at 3:59 PM, Philip George wrote:
mysql.sock is created by mysqld when it starts, and destroyed when
it stops.
haha. you're absolutely right. that doesn't make any sense. i
wasn't thinking about the nature of socket files when i wrote that.
now that i go back and read the post i was referring to, i
think the
poster was actually talking about the privileges of the enclosing
folder, not the socket itself. my bad.
but, regardless, i think it's a path problem anyway, as i mentioned
earlier.
pardon the misfire. running on zero sleep.
- philip
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?
[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?
[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
