Peter Rabbitson | 3 Jan 2010 16:39
Picon

Re: Problems working with a non-local (tcp-reachable) mysql database

Paul J Stevens wrote:
> Jorge, Peter,
> 
> I don't believe there's a problem with the query.
> 
> Peter, try connection to the remove database using the mysql client
> (mysql -h somehost...) and run the query mentioned below. That way you
> will evade any dbmail issues.
> 
> My guess is this is a libmysqlclient versioning issue.
> 

Nope, all queries are running fine standalone. In fact as you can see in the
full dbmail-util log in the bugreport, the same query runs *several times*
before actually failing.

Any other ideas on how to pin this down?
Paul J Stevens | 3 Jan 2010 17:23
Picon
Favicon
Gravatar

Re: Problems working with a non-local (tcp-reachable) mysql database

I don't have a clue. I use non-local tcp connections from dbmail-2.2 to
mysql servers (32bit) all the time without any problems like this.

Only thing I havent tested is connecting from a 32bit mysql client to a
64 bit mysql server....

Peter Rabbitson wrote:
> Paul J Stevens wrote:
>> Jorge, Peter,
>>
>> I don't believe there's a problem with the query.
>>
>> Peter, try connection to the remove database using the mysql client
>> (mysql -h somehost...) and run the query mentioned below. That way you
>> will evade any dbmail issues.
>>
>> My guess is this is a libmysqlclient versioning issue.
>>
> 
> Nope, all queries are running fine standalone. In fact as you can see in the
> full dbmail-util log in the bugreport, the same query runs *several times*
> before actually failing.
> 
> Any other ideas on how to pin this down?
> _______________________________________________
> DBmail mailing list
> DBmail <at> dbmail.org
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
> 

(Continue reading)

Peter Rabbitson | 4 Jan 2010 14:42
Picon

Re: Problems working with a non-local (tcp-reachable) mysql database

Paul J Stevens wrote:
> I don't have a clue. I use non-local tcp connections from dbmail-2.2 to
> mysql servers (32bit) all the time without any problems like this.
> 
> Only thing I havent tested is connecting from a 32bit mysql client to a
> 64 bit mysql server....
> 
> 

Upgrading to 5.1 seems to make the issue disappear entirely. Now all I need
to know if mysql 5.1 is still a disaster a year after it was released. If it
performs acceptably - I'll just close the bug and move on.

Gmane