sts-sponsors team mailing list archive

[Mauricio Oliveira <mauricio.oliveira@xxxxxxxxxxxxx>]

Hi Chengen!
How are you?

I just found out this bug that needs SRU sponsorship for your ticket SF#341744.

Please excuse our lack of documentation; I'll be working on that,
but the reason our sponsor team (or at least me) was because
the 'SE SRU Sponsors' team was not _subscribed_ to the bug.

I see you added a `sts-sponsor` tag, but unfortunately it doesn't
generate any notification -- you can actually not use it anymore. :)

I went ahead and subscribed us (in the future, you can do this
by clicking "Subscribe someone else" and "SE SRU Sponsors"
(sts-sponsors).

And another important very step is to add the LP Bug URL in
Salesforce, in the 'Public Bug URL' field, e.g.,
https://bugs.launchpad.net/bugs/1999711

This allows our scripts to check for the SRUs in SF cases
and keep them moving forward until they are released!

Thanks for your upstream patch and bug report!
We'll take a look at it!

cheers,
Mauricio




---------- Forwarded message ---------
From: Launchpad Bug Tracker <1999711@xxxxxxxxxxxxxxxxxx>
Date: Thu, Jan 12, 2023 at 9:37 AM
Subject: [Sts-sponsors] [Bug 1999711] [NEW] Snmptrapd cannot reconnect
to MySQL server after hitting MySQL wait_timeout
To: <sts-sponsors@xxxxxxxxxxxxxxxxxxx>


You have been subscribed to a public bug by Mauricio Faria de Oliveira (mfo):

[Impact]
wait_timeout is the number of seconds the MySQL server waits for
activity before closing the connection.
MySQL v8.0.24 writes the reason for the connection before closing it,
and the client receives a more informative error message
(ER_CLIENT_INTERACTION_TIMEOUT).
Snmptrapd does not handle this error code, so the connection will not
reconnect to the MySQL server afterward.

[Test Plan]
1. Setup MySQL server and modify wait_timeout to 15 in
/etc/MySQL/mysql.conf.d/mysqld.cnf
2. Setup snmptrapd and execute snmptrap command
3. Sleep 15 seconds and re-execute snmptrap command, then the
connection will fail until the snmptrapd service restarted

[Where problems could occur]
Once the error happens, snmptrapd will keep the sql commands and
resend it after reconnecting to the MySQL server.
The regression can be considered as low.

[Other Info]

** Affects: net-snmp (Ubuntu)
     Importance: Undecided
     Assignee: ChengEn, Du (chengendu)
         Status: In Progress

** Affects: net-snmp (Ubuntu Bionic)
     Importance: Undecided
     Assignee: ChengEn, Du (chengendu)
         Status: In Progress

** Affects: net-snmp (Ubuntu Focal)
     Importance: Undecided
     Assignee: ChengEn, Du (chengendu)
         Status: In Progress

** Affects: net-snmp (Ubuntu Jammy)
     Importance: Undecided
     Assignee: ChengEn, Du (chengendu)
         Status: In Progress

** Affects: net-snmp (Ubuntu Kinetic)
     Importance: Undecided
     Assignee: ChengEn, Du (chengendu)
         Status: In Progress

** Affects: net-snmp (Ubuntu Lunar)
     Importance: Undecided
     Assignee: ChengEn, Du (chengendu)
         Status: In Progress


** Tags: bionic focal jammy kinetic lunar patch sts sts-sponsor
--
Snmptrapd cannot reconnect to MySQL server after hitting MySQL wait_timeout
https://bugs.launchpad.net/bugs/1999711
You received this bug notification because you are a member of SE SRU
("STS") Sponsors, which is subscribed to the bug report.

--
Mailing list: https://launchpad.net/~sts-sponsors
Post to     : sts-sponsors@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~sts-sponsors
More help   : https://help.launchpad.net/ListHelp


-- 
Mauricio Faria de Oliveira