The mailing list for listmasters using Sympa

["Silvers, Tim" <address@concealed>]

I have added a comment to the bug report on this issue [1]. However, the issue has been closed. Could it be reopened?

 

[1] https://github.com/sympa-community/sympa/issues/1359

 

 

Thanks,

 

Tim

 

From: address@concealed <address@concealed> on behalf of Phil Stracchino <address@concealed>
Date: Friday, July 15, 2022 at 12:12 PM
To: address@concealed <address@concealed>
Subject: [External] Re: [sympa-users] Unsubscribe and Signoff Requests Cause Sympa Service Crash in 6.2.68 #1359

This message was sent from a non-IU address. Please exercise caution when clicking links or opening attachments from external sources.
-------

On 7/15/22 10:46, True, James Scott wrote:
> Hello,
>
> Indiana University applied the “patch” for this issue early Sunday July
> 10^th . We have had no errors due to Signoff Request until this morning.
> I removed the message from the queue and restarted Sympa. It has been
> running normally since. The Sympa logs are below. There only thing in
> the MySQL logs is “Got timeout reading communication packets”. This
> error occurs when idle threads are killed by wait_timeout. Does Sympa
> call mysql_close() in scripts when the connection is no longer needed?

If Sympa is going to open connections and use them persistently, then it
should probably issue a SET SESSION WAIT_TIMEOUT = 28800 (or some other
suitable value) upon opening its connection.  On the other hand if it is
intended that Sympa's database connections be transient, then as James
notes, when it is done with a connection it has opened it should
properly close it, not just abandon it.


--
   Phil Stracchino
   Babylon Communications
   address@concealed
   address@concealed
   Landline: +1.603.293.8485
   Mobile:   +1.603.998.6958