12 messages in com.mysql.lists.perlRe: Accessing MySQL on another machin...
FromSent OnAttachments
Hal Vaughan25 Mar 2003 21:35 
Todd Finney25 Mar 2003 21:42 
Hal Vaughan25 Mar 2003 23:54 
Jochen Wiedmann26 Mar 2003 00:42 
Hal Vaughan26 Mar 2003 01:45 
Christopher Hicks26 Mar 2003 08:30 
Hal Vaughan26 Mar 2003 09:15 
Ulrich Borchers26 Mar 2003 10:03 
Hal Vaughan26 Mar 2003 12:07 
Ulrich Borchers26 Mar 2003 13:37 
Hal Vaughan26 Mar 2003 13:55 
Hal Vaughan26 Mar 2003 23:22 
Subject:Re: Accessing MySQL on another machine w/ DBI.pm
From:Hal Vaughan (ha@thresholddigital.com)
Date:03/26/2003 01:55:42 PM
List:com.mysql.lists.perl

On Wednesday 26 March 2003 04:38 pm, Ulrich Borchers wrote:

When I installed the latest (4.0.x -- whatever was just announced as stable), I had NO /etc/my.cnf. Now it reads:

[mysqld] socket=/var/lib/mysql/mysql.sock

[client] socket=/var/lib/mysql/mysql.sock

Could my setting the sockets to this particular file be effecting this?

I am not familiar with the absence of my.cnf which usually contains much more. Maybe adding "port=3306" will help. Use netstat and telnet to find a listening tcp socket.

You could also examine/change parameters to safe_mysqld, the accessibility of mysql-tables (file privileges) and the dsn string which should be: "DBI:mysql:host=192.168.1.11;port=3306;database=lopas"

DBI->connect(database=lopas;host=mysqlhost;port=3306) failed: Access denied for user: 'hal@192.168.1.11' to database 'MaliningList' at ./test.pl line 13

Have you noticed that the error message refers to a different database and there might be a typo in 'MaliningList' in case it should read 'MailingList' ?!

I'll be looking into the earlier points as soon as I can. I just wanted to reply on this one point -- I changed the name of the database so someone I'm working with could remember which list was which. To avoid confusion, I had been replacing the new name (lopas) with the old one when I posted the error messages.

Hal

Uli