Snmptrapd cannot reconnect to MySQL server after hitting MySQL wait_timeout

Bug #1999711 reported by Chengen Du
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
net-snmp (Ubuntu)
Fix Released
Undecided
Chengen Du
Focal
Fix Released
Undecided
Chengen Du
Jammy
Fix Released
Undecided
Chengen Du
Kinetic
Fix Released
Undecided
Chengen Du
Lunar
Fix Released
Undecided
Chengen Du

Bug Description

[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. Launch 2 VMs (1 for MySQL Server, 1 for snmptrapd client in focal)
2. Prepare the MySQL server
    2-1. Installed mysql-server
        # sudo apt install mysql-server
    2-2. Configured it to require a root password
        # systemctl stop mysql
        # sudo systemctl set-environment MYSQLD_OPTS="--skip-networking --skip-grant-tables"
        # sudo systemctl start mysql.service
        # sudo mysql -u root
        # mysql> flush privileges;
            Query OK, 0 rows affected (0.00 sec)
        # mysql> USE mysql
            Database changed
        # mysql> ALTER USER 'root'@'localhost' IDENTIFIED BY 'the-new-password';
            Query OK, 0 rows affected (0.01 sec)
        # mysql> quit;
        # sudo systemctl unset-environment MYSQLD_OPTS
        # sudo systemctl revert mysql
        # sudo killall -u mysql
        # sudo systemctl restart mysql.service
3. Connected to mysql and created the necessary user / database / tables for snmptrapd to work
    # mysql -u root -p
    # mysql> create database net_snmp;
        Query OK, 1 row affected (0.02 sec)
    # mysql> create user 'remotesnmp'@'%' identified by 'password';
        Query OK, 0 rows affected (0.02 sec)
    # mysql> grant all privileges on net_snmp.* to 'remotesnmp'@'%';
        Query OK, 0 rows affected (0.15 sec)
    # mysql> USE net_snmp;
        Database changed
    # mysql> DROP TABLE IF EXISTS notifications;
        Query OK, 0 rows affected, 1 warning (0.01 sec)
    # mysql> CREATE TABLE IF NOT EXISTS `notifications` (
    # -> `trap_id` int(11) unsigned NOT NULL AUTO_INCREMENT,
    # -> `date_time` datetime NOT NULL,
    # -> `host` varchar(255) NOT NULL,
    # -> `auth` varchar(255) NOT NULL,
    # -> `type`
    # -> ENUM('get','getnext','response','set','trap','getbulk','inform','trap2','report') NOT NULL,
    # -> `version` ENUM('v1','v2c', 'unsupported(v2u)','v3') NOT NULL,
    # -> `request_id` int(11) unsigned NOT NULL,
    # -> `snmpTrapOID` varchar(1024) NOT NULL,
    # -> `transport` varchar(255) NOT NULL,
    # -> `security_model` ENUM('snmpV1','snmpV2c','USM') NOT NULL,
    # -> `v3msgid` int(11) unsigned,
    # -> `v3security_level` ENUM('noAuthNoPriv','authNoPriv','authPriv'),
    # -> `v3context_name` varchar(32),
    # -> `v3context_engine` varchar(64),
    # -> `v3security_name` varchar(32),
    # -> `v3security_engine` varchar(64),
    # -> PRIMARY KEY (`trap_id`)
    # -> ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
        Query OK, 0 rows affected, 3 warnings (0.04 sec)
    # mysql> DROP TABLE IF EXISTS varbinds;
        Query OK, 0 rows affected, 1 warning (0.00 sec)
    # mysql> CREATE TABLE IF NOT EXISTS `varbinds` (
    # -> `trap_id` int(11) unsigned NOT NULL default '0',
    # -> `oid` varchar(1024) NOT NULL,
    # -> `type` ENUM('boolean','integer','bit','octet','null','oid','ipaddress','counter','unsigned','timeticks','opaque','unused1','counter64','unused2') NOT NULL,
    # -> `value` blob NOT NULL,
    # -> KEY `trap_id` (`trap_id`)
    # -> ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
        Query OK, 0 rows affected, 1 warning (0.05 sec)
    # mysql> exit
        Bye
4. Edit the mysqld configuration file to let it bind to all network interfaces and also set wait_timeout:
    # vi /etc/mysql/mysql.conf.d/mysqld.cnf
    ...
    [mysqld]
    #
    # * Basic Settings
    #
    user = mysql
    # pid-file = /var/run/mysqld/mysqld.pid
    # socket = /var/run/mysqld/mysqld.sock
    # port = 3306
    # datadir = /var/lib/mysql
    wait_timeout = 660
    ...
    # systemctl restart mysql.service
5. Connect to the database and set the wait_timeout and interactive_timeout:
    # mysql -u root -p
    # mysql> SET interactive_timeout=660;
        Query OK, 0 rows affected (0.00 sec)
    # mysql> SET wait_timeout=660;
        Query OK, 0 rows affected (0.00 sec)
    # mysql> SHOW VARIABLES LIKE "%wait%";
    +---------------------------------------------------+----------+
    | Variable_name | Value |
    +---------------------------------------------------+----------+
    | innodb_lock_wait_timeout | 50 |
    | innodb_log_wait_for_flush_spin_hwm | 400 |
    | innodb_spin_wait_delay | 6 |
    | innodb_spin_wait_pause_multiplier | 50 |
    | lock_wait_timeout | 31536000 |
    | mysqlx_wait_timeout | 28800 |
    | performance_schema_events_waits_history_long_size | 10000 |
    | performance_schema_events_waits_history_size | 10 |
    | wait_timeout | 660 |
    +---------------------------------------------------+----------+
    9 rows in set (0.01 sec)
    # mysql> quit
        Bye
6. Prepare the snmptrapd clients:
    6-1. Install the snmptrapd, mysql client:
        # sudo apt-get install snmp snmpd snmptrapd snmp-mibs-downloader mysql-client-core-8.0
    6-2.. Edit the client configuration file
        # cat /etc/mysql/conf.d/mysql.cnf
        [mysql]
        user=remotesnmp
        password=password
        host=XXX.XX.XX.XXX
    6-3. Test that you can connect to the database:
        # mysql> use net_snmp;
        Reading table information for completion of table and column names
        You can turn off this feature to get a quicker startup with -A

        Database changed
        # mysql> show tables;
        +--------------------+
        | Tables_in_net_snmp |
        +--------------------+
        | notifications |
        | varbinds |
        +--------------------+
        2 rows in set (0.01 sec)
    6-4. Setup the snmptrapd mysql credentials and add the wait_timeout:
        # cat /etc/mysql/conf.d/snmptrapd.cnf
        [snmptrapd]
        user=remotesnmp
        password=password
        host=XXX.XX.XX.XXX
        wait_timeout=660
7. Configure snmptrapd
    # cat /etc/snmp/snmptrapd.conf
    disableAuthorization yes
    authCommunity log mytrapcommunity
    traphandle default /usr/bin/logger
    sqlMaxQueue 1
    sqlSaveInterval 9
    # sudo systemctl restart snmptrapd.service
8. Send a trap / sleep 660 / try to send a couple more traps:

We'll observe that trap 1 works, trap 2 and 3 fails with SQL Error 4031 (HY000): The client was disconnected by the server because of inactivity.
The problem will persist until we restart snmptrapd.

[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]

Chengen Du (chengendu)
Changed in net-snmp (Ubuntu Bionic):
assignee: nobody → ChengEn, Du (chengendu)
Changed in net-snmp (Ubuntu Focal):
assignee: nobody → ChengEn, Du (chengendu)
Changed in net-snmp (Ubuntu Jammy):
assignee: nobody → ChengEn, Du (chengendu)
Changed in net-snmp (Ubuntu Kinetic):
assignee: nobody → ChengEn, Du (chengendu)
Changed in net-snmp (Ubuntu Lunar):
assignee: nobody → ChengEn, Du (chengendu)
tags: added: sts
Revision history for this message
Chengen Du (chengendu) wrote :

Attached is a patch that resolves the issue on Bionic.

Revision history for this message
Chengen Du (chengendu) wrote :

Attached is a patch that resolves the issue on Focal.

Revision history for this message
Chengen Du (chengendu) wrote :

Attached is a patch that resolves the issue on Jammy.

Revision history for this message
Chengen Du (chengendu) wrote :

Attached is a patch that resolves the issue on Kinetic.

Revision history for this message
Chengen Du (chengendu) wrote :

Attached is a patch that resolves the issue on Lunar.

Changed in net-snmp (Ubuntu Bionic):
status: New → In Progress
Changed in net-snmp (Ubuntu Focal):
status: New → In Progress
Changed in net-snmp (Ubuntu Jammy):
status: New → In Progress
Changed in net-snmp (Ubuntu Kinetic):
status: New → In Progress
Changed in net-snmp (Ubuntu Lunar):
status: New → In Progress
Chengen Du (chengendu)
tags: added: bionic focal jammy kinetic lunar
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "bionic_snmptrapd_mysql_reconnection.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

tags: added: patch
Chengen Du (chengendu)
tags: added: sts-sponsor
tags: removed: sts-sponsor
tags: added: se-sponsor-dgadomski
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

I'll see if I can sponsor this

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

I noticed a follow-up commit in the upstream git repo a week or so after the original fix:

original fix:
commit 62b2907a46c9e495c1c71114cc8f18ed137b7f34
Author: Chengen Du <email address hidden>
Date: Wed Nov 23 14:11:36 2022 +0800

    apps/snmptrap: Fix mysql reconnection after hitting wait_timeout

    MySQL v8.0 supports ER_CLIENT_INTERACTION_TIMEOUT, which is not handled
    in snmptrapd

    Signed-off-by: Chengen Du <email address hidden>

A few days later, this changes "bool" to "int":
commit a1c80f7778da0aaadfb3fc44b213586f632d8d5d
Author: Bart Van Assche <email address hidden>
Date: Mon Dec 5 19:19:40 2022 -0800

    apps/snmptrapd_sql: Fix a recently introduced build error

    Fixes: 62b2907a46c9 ("apps/snmptrap: Fix mysql reconnection after hitting wait_timeout")

I vaguely remember a mysql build issue when mysql 8 came along, where mysql stopped exporting my_bool iirc. I see we use "bool" all the way to focal, and then in bionic use "int". And the patch correctly flags that bionic change as being a backport.

Can you detail the test case a bit more, for those not familiar setting up snmp traps? I'll sponsor lunar, but a more detailed step by step test case for the SRU would be great.

Revision history for this message
Chengen Du (chengendu) wrote :

Attached is a patch that resolves the issue on Bionic.

Revision history for this message
Chengen Du (chengendu) wrote :

Attached is a patch that resolves the issue on Focal.

Revision history for this message
Chengen Du (chengendu) wrote :

Attached is a patch that resolves the issue on Jammy.

Revision history for this message
Chengen Du (chengendu) wrote :

Attached is a patch that resolves the issue on Kinetic.

Revision history for this message
Chengen Du (chengendu) wrote :

Attached is a patch that resolves the issue on Lunar.

Revision history for this message
Chengen Du (chengendu) wrote :

@dgadomski @ahasenack
Sorry for not noticing the follow-up commit.
The build error doesn't happen in ubuntu but maybe on other platforms.
For integrity, I uploaded new patches and please use those for testing.
Again, sorry for any inconvenience.

@ahasenack
Here are the steps to reproduce the issue.
https://pastebin.canonical.com/p/MkZ9PR7kmh/
Xenial will not have any problems because it uses an older mysql version.
Another thing is Lunar seems to apply the patch already (able to get the patch by 'pull-lp-source net-snmp lunar').
So I uploaded another patch to cover the build error patch upstream.

Please don't hesitate to let me know if you encounter any problems during the test.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package net-snmp - 5.9.3+dfsg-2ubuntu2

---------------
net-snmp (5.9.3+dfsg-2ubuntu2) lunar; urgency=medium

  * Fix snmptrapd reconnection issue after hitting MySQL wait_timeout
    (LP: #1999711)
    - d/p/snmptrapd-mysql-reconnection-after-hitting-wait_timeout.patch

 -- Chengen Du <email address hidden> Thu, 16 Feb 2023 20:16:57 -0300

Changed in net-snmp (Ubuntu Lunar):
status: In Progress → Fix Released
Revision history for this message
Andreas Hasenack (ahasenack) wrote (last edit ):

Thanks for the updated patches and detailed test case.

For the future, when you are adding the "Origin" tag to the DEP3 header in the patch, if the fix was merged upstream, please use a commit to the master/main branch or some other stable reference, instead of a PR.

For this particular case, since the fix was merged, I would have used this reference instead, for the reconnect patch:

Origin: upstream, https://github.com/net-snmp/net-snmp/commit/62b2907a46c9e495c1c71114cc8f18ed137b7f34

Tip: with such a reference, github can get you a nice patch file, with author, subject, etc., by just attaching the string ".patch" to the url, like so:

https://github.com/net-snmp/net-snmp/commit/62b2907a46c9e495c1c71114cc8f18ed137b7f34.patch

So it's quite easy to extract a patch from a commit reference if needed.

All of the above is just an observation, no need to update the patches.

For the test plan, please:
a) sanitize it, it has references to outside entities in the example trap. If you can, use a random/standard trap instead of the one you have there which needs sanitizing. Note that OID numbers can refer to company names too.
b) you probably don't need that many VMs to show a working and non-working case, but if you prefer it like that, that's fine. Just be sure that all ubuntu releases are covered in the "working" case.
c) don't use a PPA for the test plan. To show the bug, use the packages currently in Ubuntu, and to show the fix, use the ${release}-proposed pocket.

Once that is done, put the revised test plan in the bug description, in the [Test Plan] section. If it's still too large for launchpad to show it nicely, feel free to attach it as a text file and then just refer to the attachment in the description.

Now a question about the patches. I noticed a difference in the bionic patch, it doesn't have this "#if HAVE_MYSQL_OPTIONS" bit that is present in the other patches:

+#if HAVE_MYSQL_OPTIONS
+ mysql_options(_sql.conn, MYSQL_READ_DEFAULT_GROUP, "snmptrapd");
+#endif

I checked and mysql from bionic (version 5.7) does have this option, so why is this bit not in the patch? Is this why you marked that patch as a backport in the origin tag?

https://dev.mysql.com/doc/c-api/5.7/en/mysql-options.html

Revision history for this message
Chengen Du (chengendu) wrote :

First, sorry for the vague test plan.
I should tidy it up instead of just paste the whole steps.

I'd like to clarify that the definition of HAVE_MYSQL_OPTIONS is introduced in a separate commit (011342d8e453 snmptrapd: Let configure check for mysql_options()) that is unrelated to the issue I'm fixing.
It may be better to avoid including too many other modifications and focus solely on fixing this issue, imho.
Therefore, I've marked the patch as a backport in bionic.

Chengen Du (chengendu)
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello ChengEn, or anyone else affected,

Accepted net-snmp into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/net-snmp/5.9.3+dfsg-1ubuntu1.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in net-snmp (Ubuntu Kinetic):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-kinetic
Revision history for this message
Steve Langasek (vorlon) wrote :

the SRU rationale mentions mysql 8.0.24 which is only present in focal and later. bionic does not have mysql-8.0 at all, it shipped mysql-5.7. Why is a change needed for bionic?

Changed in net-snmp (Ubuntu Bionic):
status: In Progress → Incomplete
Changed in net-snmp (Ubuntu Jammy):
status: In Progress → Fix Committed
tags: added: verification-needed-jammy
Revision history for this message
Steve Langasek (vorlon) wrote :

Hello ChengEn, or anyone else affected,

Accepted net-snmp into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/net-snmp/5.9.1+dfsg-1ubuntu2.6 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in net-snmp (Ubuntu Focal):
status: In Progress → Fix Committed
tags: added: verification-needed-focal
Revision history for this message
Steve Langasek (vorlon) wrote :

Hello ChengEn, or anyone else affected,

Accepted net-snmp into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/net-snmp/5.8+dfsg-2ubuntu2.7 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Chengen Du (chengendu) wrote :

The patch actually resolved two issues. The first issue was related to the reconnection problem with snmptrapd. The second issue was that whenever the snmptrapd hit the MySQL wait timeout, all events in the queue were being cleared instead of resent. As the error was expected, it wasn't ideal to have the events dropped. Therefore, I discovered that the same issue also existed in bionic. As a result, I believe that it would be better to make a change in bionic to address this issue as well.

Revision history for this message
Chengen Du (chengendu) wrote :

I have tested the following versions: 5.9.3+dfsg-1ubuntu1.4 for kinetic, 5.9.1+dfsg-1ubuntu2.6 for jammy, and 5.8+dfsg-2ubuntu2.7 for focal. The issue no longer exists in these versions based on the same test plan.

tags: added: verification-done-focal verification-done-jammy verification-done-kinetic
removed: verification-needed-focal verification-needed-jammy verification-needed-kinetic
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (net-snmp/5.9.3+dfsg-1ubuntu1.4)

All autopkgtests for the newly accepted net-snmp (5.9.3+dfsg-1ubuntu1.4) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

asterisk/1:18.14.0~dfsg+~cs6.12.40431414-1 (arm64)
php8.1/unknown (s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/kinetic/update_excuses.html#net-snmp

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Dariusz Gadomski (dgadomski) wrote :

I've looked into the regressions and both of them seem unrelated:
* asterisk:
<VirtSubproc>: failure: Timed out on waiting for ssh connection
autopkgtest [18:39:03]: ERROR: testbed failure: cannot send to testbed: [Errno 32] Broken pipe

* php8.1:
VirtSubproc.Timeout
autopkgtest [20:46:20]: ERROR: testbed failure: cannot send to testbed: [Errno 32] Broken pipe

Both appear infra-related. I have restarted the two just to be sure.

Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (net-snmp/5.9.1+dfsg-1ubuntu2.6)

All autopkgtests for the newly accepted net-snmp (5.9.1+dfsg-1ubuntu2.6) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

cluster-glue/1.0.12-20ubuntu3 (amd64)
php8.1/unknown (s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#net-snmp

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Dariusz Gadomski (dgadomski) wrote :

After restart:

* same s390x testbed setup error for php,
* asterisk is fine this time
* new regression reported for cluster-glue (which was fine before):
=== ha_logger ===
logd is not runningautopkgtest [07:00:28]: test logd: -----------------------]
autopkgtest [07:00:29]: test logd: - - - - - - - - - - results - - - - - - - - - -
logd FAIL non-zero exit status 1
autopkgtest [07:00:29]: test logd: - - - - - - - - - - stderr - - - - - - - - - -
logd is not running

This may also be a timing issue.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package net-snmp - 5.9.3+dfsg-1ubuntu1.4

---------------
net-snmp (5.9.3+dfsg-1ubuntu1.4) kinetic; urgency=medium

  * Fix snmptrapd reconnection issue after hitting MySQL wait_timeout
    (LP: #1999711)
    - d/p/snmptrapd-mysql-reconnection-after-hitting-wait_timeout.patch
    - d/p/snmptrapd-mysql-fix-build-error.patch

 -- Chengen Du <email address hidden> Fri, 17 Feb 2023 03:41:21 +0000

Changed in net-snmp (Ubuntu Kinetic):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for net-snmp has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package net-snmp - 5.9.1+dfsg-1ubuntu2.6

---------------
net-snmp (5.9.1+dfsg-1ubuntu2.6) jammy; urgency=medium

  * Fix snmptrapd reconnection issue after hitting MySQL wait_timeout
    (LP: #1999711)
    - d/p/snmptrapd-mysql-reconnection-after-hitting-wait_timeout.patch
    - d/p/snmptrapd-mysql-fix-build-error.patch

 -- Chengen Du <email address hidden> Fri, 17 Feb 2023 03:25:16 +0000

Changed in net-snmp (Ubuntu Jammy):
status: Fix Committed → Fix Released
tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package net-snmp - 5.8+dfsg-2ubuntu2.7

---------------
net-snmp (5.8+dfsg-2ubuntu2.7) focal; urgency=medium

  * Fix snmptrapd reconnection issue after hitting MySQL wait_timeout
    (LP: #1999711)
    - d/p/snmptrapd-mysql-reconnection-after-hitting-wait_timeout.patch
    - d/p/snmptrapd-mysql-fix-build-error.patch

 -- Chengen Du <email address hidden> Fri, 17 Feb 2023 03:05:10 +0000

Changed in net-snmp (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Dariusz Gadomski (dgadomski) wrote :

After discussing comments #20 and #23 with ChengEn we agreed that bionic may not need that fix.

Hence, I'm removing it from the affected series.

no longer affects: net-snmp (Ubuntu Bionic)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.