Hello.
> I've also discovered that its generating log entries (I've got a
> 3 Gbyte log file) even though I havent asked for them.
You may want to disable the general log where errors are written. See:
http://dev.mysql.com/doc/mysql/en/query-log.html
http://dev.mysql.com/doc/mysq
Hello.
Have you run mysql_fix_privilege_tables script after the upgrade?
"T. Horsnell" <[EMAIL PROTECTED]> wrote:
> After replacing a 3.23.28 server with 4.1.14 server binaries on an Alpha
> running Tru64 5.1B, I get things like:
>
> ERROR 1045 (28000): Access denied for user 'tsh'@'10
>Hi,
>It is skip-name-resolve - I just wrote it by memory and was wrong. There is
>also a nice piece on "Access denied" errors at
>
>http://dev.mysql.com/doc/mysql/en/access-denied.html
Thanks - I'd already read that.
I've also discovered that its generating log entries (I've got a
3 Gbyte log fi
Hi,
Does the 10.4.0.101 reverse resolve to a specific hostname? If it does you are
probably running MySQL with the skip_hostname_resolve option and if it
doesn't there is no way the MySQL server could tell from which host the
request is comming.
My opinion is that it is always better to use the
After replacing a 3.23.28 server with 4.1.14 server binaries on an Alpha
running Tru64 5.1B, I get things like:
ERROR 1045 (28000): Access denied for user 'tsh'@'10.4.0.101' (using password:
YES)
when trying to connect from a remote host.
The problem goes away if I replace hostnames by IP addre