I have upgraded MysqlMemberships.py member adaptor once again, this time
solving (I think) the problem of disconnection/reconnection when the link
to the SQL server has died.
In my tests it works fine (reconnects) when I kill the link with
"mysqladmin kill NNN"
However I don't know what strategy
Hello,
I have upgraded the MysqlMemberships.py member adaptor, so that it uses only
one connection for all lists, and not one connection per list (as it did
before).
Everything works fine (only one day of operation though), except when the
mysql link is broken (I stopped mysqld to check that). Th
Hello,
I have updated the MysqlMembership extension
http://trac.rezo.net/trac/rezo/browser/Mailman/MySQLMemberAdaptor/MysqlMemberships.py
I would appreciate it if someone could verify that this patch indeed
potentially fixes the "TypeError" bug we used to get on some SetBounceInfo:
http://trac.r
> What sort of setting does the MySQL server you are running have for timing
> out idle connections? Could it be that you aren't "hitting" it often
> enough? In which case, going away a lot is normal.
Right. It's optimized for apache (short connexions), so I guess it's normal :)
-- Fil
___
On 11/23/05 3:38 AM, "Fil" <[EMAIL PROTECTED]> wrote:
>> Unfortunately this still doesn't succeed reconnecting to the server: I get
>> this traceback:
>>
>> File "/var/local/mailman/Mailman/MysqlMemberships.py", line 141, in
>> _prodServerConnection
>> if self.connection.ping() == 0: Operat
> Unfortunately this still doesn't succeed reconnecting to the server: I get
> this traceback:
>
> File "/var/local/mailman/Mailman/MysqlMemberships.py", line 141, in
> _prodServerConnection
> if self.connection.ping() == 0: OperationalError: (2006, 'MySQL server
> has gone away')
A littl
Fil wrote:
>
>Unfortunately this still doesn't succeed reconnecting to the server: I get
>this traceback:
>
> File "/var/local/mailman/Mailman/MysqlMemberships.py", line 141, in
> _prodServerConnection
>if self.connection.ping() == 0: OperationalError: (2006, 'MySQL server has
> gone away')
@ Fil <[EMAIL PROTECTED]> :
> > I'm running the patch as is, and there's trouble. Here is the error log:
>
> OK, good. A quick fix is to add on line 153
> self.cursor = self.connection.cursor()
>
> The correct fix would be to isolate the connection/reconnection procedure in
> a unique fun
> I'm running the patch as is, and there's trouble. Here is the error log:
OK, good. A quick fix is to add on line 153
self.cursor = self.connection.cursor()
The correct fix would be to isolate the connection/reconnection procedure in
a unique function, but that'll be for later.
-- Fil
> If looked at this a bit more closely, and it turns out not to be quite
> that simple. The major issue is the way things currently exist in your
> MysqlMemberships.py, rev 19, 'connection' is a local variable in the
> MysqlMemberships class __init__ method. It is not visible to
> _prodServerConnec
Mark Sapiro wrote:
>in _prodServerConnection(), you can't do
>
>if ping(self.connection) == 0:
>
>you need to do
>
>if self.connection.ping() == 0:
If looked at this a bit more closely, and it turns out not to be quite
that simple. The major issue is the way things currently exist in you
Fil wrote:
>
>Well, it currently has a "works *not* for me" flavor and I'd appreciate som
>help on the two outstanding bugs I still have (in my version, but I guess
>Kev's version has them too).
Yes, Kev's has them too, at least the 1.61 version.
>1) if the DB connection dies or fades away, pin
12 matches
Mail list logo
