3 messages in com.mysql.lists.perlRe: connection error (111)| From | Sent On | Attachments |
|---|---|---|
| Burghelea Vasile | 21 Feb 2001 00:40 | |
| Jochen Wiedmann | 21 Feb 2001 01:03 | |
| Burghelea Vasile | 21 Feb 2001 08:42 |
| Subject: | Re: connection error (111) |
|---|---|
| From: | Burghelea Vasile (el...@dntis.ro) |
| Date: | 02/21/2001 08:42:04 AM |
| List: | com.mysql.lists.perl |
Howdy, people First of all, a big thank-you to Jochen :) Unfortunately, I couldn't manage to make it work (atleast not this afternoon), so I followed my instincts: grabbed a newercopy of mysql (3.23.32-1.7.6x, with version 3.23.22 of mysqlclient) and upgraded the current (that is ex-) installation, and everything works smooth now. I don't know why, and I really don't care (:D), but if anyone has the same problem as I did, I recommend it :)) Again, thanks, and all the best to y'all :)
Elis.
-- Vasile Burghelea Web Design & Development Department Dynamic Network Technologies - Iasi, Romania Phone: +40-32-252936 252938 Mobile: +40-93-690622 e-mail: V.Bu...@dntis.ro http://www.dntis.ro
On Wed, 21 Feb 2001, Jochen Wiedmann wrote:
Both have their own compiled values for this location. In other words, if your client library and and your server are from different sources, or if you have some different setting in my.cnf, then it may well happen, that the client is using the wrong socket file.
From DBD::mysql's point of view the location of the file is configurable via some DSN option. The same applies to the server, but I do not remember exactly how. Besides, you can always try to connect via IP, by specifying 127.0.0.1 as host.
Bye,
Jochen