Bug 937767 - mysql-community-server-client: The mysql server keeps restarting every minute
Summary: mysql-community-server-client: The mysql server keeps restarting every minute
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 13.1
Classification: openSUSE
Component: Maintenance (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Major (vote)
Target Milestone: ---
Deadline: 2015-07-03
Assignee: Mr Maintenance
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-12 20:05 UTC by Andreas Stieger
Modified: 2023-12-29 12:30 UTC (History)
6 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Stieger 2015-07-12 20:05:56 UTC
+++ This bug was initially created as a clone of Bug #934789 +++

(In reply to Olivier Nicolas from bug 934789 comment #24)
> After updating to "mysql-community-server-client-5.6.25-7.4.1.i586" on
> "openSUSE 13.1 (Bottle) (i586)"
> 
> The mysql server keeps restarting every minute 
> 
> Jul  9 19:00:11 blackened systemd[1]: Reloaded System Logging Service.
> Jul  9 19:00:57 blackened mysql-systemd-helper[337]: MySQL is still dead
> Jul  9 19:00:57 blackened systemd[1]: mysql.service: control process exited,
> code=exited status=1
> Jul  9 19:00:57 blackened systemd[1]: Failed to start MySQL server.
> Jul  9 19:00:57 blackened systemd[1]: Unit mysql.service entered failed
> state.
> Jul  9 19:00:57 blackened mysql-systemd-helper[335]: 2015-07-09 19:00:57 351
> [Note] /usr/sbin/mysqld: Normal shutdown
> Jul  9 19:00:57 blackened mysql-systemd-helper[335]: 2015-07-09 19:00:57 351
> [Note] Giving 2 client threads a chance to die gracefully
> Jul  9 19:00:57 blackened mysql-systemd-helper[335]: 2015-07-09 19:00:57 351
> [Note] Event Scheduler: Purging the queue. 0 events
> Jul  9 19:00:57 blackened mysql-systemd-helper[335]: 2015-07-09 19:00:57 351
> [Note] Shutting down slave threads
> Jul  9 19:00:57 blackened systemd[1]: mysql.service holdoff time over,
> scheduling restart.
> Jul  9 19:00:57 blackened systemd[1]: Stopping MySQL server...
> Jul  9 19:00:57 blackened systemd[1]: Starting MySQL server...
> Jul  9 19:00:57 blackened mysql-systemd-helper[1042]:
> /usr/bin/my_print_defaults: unknown option '--mysqld'
> Jul  9 19:00:57 blackened mysql-systemd-helper[1051]:
> /usr/bin/my_print_defaults: unknown option '--mysqld'
> Jul  9 19:00:57 blackened mysql-systemd-helper[1059]:
> /usr/bin/my_print_defaults: unknown option '--mysqld'
> Jul  9 19:00:57 blackened mysql-systemd-helper[1060]:
> /usr/bin/my_print_defaults: unknown option '--mysqld'
> Jul  9 19:00:57 blackened mysql-systemd-helper[1060]: Waiting for MySQL to
> start
> 
> 
> I had to modify the /usr/lib/mysql/mysql-systemd-helper to successfully
> start the mysql server 
> 
> 
> --- /usr/lib/mysql/mysql-systemd-helper.orig	2015-07-12 11:46:47.071715464
> +0200
> +++ /usr/lib/mysql/mysql-systemd-helper	2015-07-12 11:47:22.631715464 +0200
> @@ -20,10 +20,10 @@
>  
>  	# Read options - important for multi setup
>  	if [[ -n "$INSTANCE" && "x$INSTANCE" != "xdefault" ]]; then
> -		opts="$(/usr/bin/my_print_defaults --mysqld mysqld_multi "$INSTANCE")"
> +		opts="$(/usr/bin/my_print_defaults mysqld mysqld_multi "$INSTANCE")"
>  		tmp_opts="$opts"
>  	else
> -		opts="$(/usr/bin/my_print_defaults --mysqld)"
> +		opts="$(/usr/bin/my_print_defaults mysqld)"
>  		tmp_opts="$opts"
>  	fi
Comment 1 Andreas Stieger 2015-07-12 20:07:07 UTC
Thomas and Kristyna, anything you can make sense of here?
Comment 2 Martin Pluskal 2015-07-12 20:21:45 UTC
Hmm,
# /usr/bin/my_print_defaults --mysqld mysqld_multi
--innodb_file_format=Barracuda
--innodb_file_per_table=ON
--server-id=1
--sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES
--mysqld=/usr/bin/mysqld_safe
--mysqladmin=/usr/bin/mysqladmin
--log=/var/log/mysqld_multi.log

Seems that syntax is correct
Comment 3 Martin Pluskal 2015-07-12 20:26:31 UTC
(In reply to Martin Pluskal from comment #2)
> Hmm,
> # /usr/bin/my_print_defaults --mysqld mysqld_multi
> --innodb_file_format=Barracuda
> --innodb_file_per_table=ON
> --server-id=1
> --sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES
> --mysqld=/usr/bin/mysqld_safe
> --mysqladmin=/usr/bin/mysqladmin
> --log=/var/log/mysqld_multi.log
> 
> Seems that syntax is correct

It is correct with mariadb, but wirh mysql-community server I get:
# /usr/bin/my_print_defaults --mysqld mysqld_multi
/usr/bin/my_print_defaults: unknown option '--mysqld'
Comment 4 Martin Pluskal 2015-07-12 20:29:24 UTC
Anywat "/usr/bin/my_print_defaults mysqld mysqld_multi" seems to work with both mariadb and mysql
Comment 5 Martin Pluskal 2015-07-12 20:47:34 UTC
https://github.com/openSUSE/mysql-packaging/pull/11
Comment 6 Bernhard Wiedemann 2015-07-13 13:00:09 UTC
This is an autogenerated message for OBS integration:
This bug (937767) was mentioned in
https://build.opensuse.org/request/show/316414 Factory / mysql-community-server
Comment 7 Bernhard Wiedemann 2015-07-13 14:00:22 UTC
This is an autogenerated message for OBS integration:
This bug (937767) was mentioned in
https://build.opensuse.org/request/show/316420 Factory / mysql-community-server
https://build.opensuse.org/request/show/316442 13.2+13.1 / mysql-community-server
Comment 8 Andreas Stieger 2015-07-13 14:17:02 UTC
The submission SR#316442 contains the following diff:

+# mysql-devel needs to be provided as some pkgs still depend on it
+Provides:       mysql-devel = %{version}
+Obsoletes:      mysql-devel < %{version}

As this relates to bug 937630, a changelog entry would be missing.

The more important question would be if this conflicts with the same change done to MariaDB in any way? ("have choice for" situation)

Further, it contains the following diff:

-ln -sf lib%{libname}%{soname}.so.%{soname}.0.0 lib%{libname}_r.so
-ln -sf lib%{libname}%{soname}.so.%{soname}.0.0 lib%{libname}_r.so.%{soname}
-ln -sf lib%{libname}%{soname}.so.%{soname}.0.0 lib%{libname}_r.so.%{soname}.0.0
+ln -sf lib%{libname}.so.%{soname}.0.0 lib%{libname}_r.so
+ln -sf lib%{libname}.so.%{soname}.0.0 lib%{libname}_r.so.%{soname}
+ln -sf lib%{libname}.so.%{soname}.0.0 lib%{libname}_r.so.%{soname}.0.0

As this relates to bug 937754, a changelog entry would be missing.
Comment 9 Martin Pluskal 2015-07-13 14:21:56 UTC
(In reply to Andreas Stieger from comment #8)
> The submission SR#316442 contains the following diff:
> 
> +# mysql-devel needs to be provided as some pkgs still depend on it
> +Provides:       mysql-devel = %{version}
> +Obsoletes:      mysql-devel < %{version}
> 
> As this relates to bug 937630, a changelog entry would be missing.
> 
> The more important question would be if this conflicts with the same change
> done to MariaDB in any way? ("have choice for" situation)
> 
> Further, it contains the following diff:
> 
> -ln -sf lib%{libname}%{soname}.so.%{soname}.0.0 lib%{libname}_r.so
> -ln -sf lib%{libname}%{soname}.so.%{soname}.0.0 lib%{libname}_r.so.%{soname}
> -ln -sf lib%{libname}%{soname}.so.%{soname}.0.0
> lib%{libname}_r.so.%{soname}.0.0
> +ln -sf lib%{libname}.so.%{soname}.0.0 lib%{libname}_r.so
> +ln -sf lib%{libname}.so.%{soname}.0.0 lib%{libname}_r.so.%{soname}
> +ln -sf lib%{libname}.so.%{soname}.0.0 lib%{libname}_r.so.%{soname}.0.0
> 
> As this relates to bug 937754, a changelog entry would be missing.
hmm I was under impression that this update was now in queue for release, with proper changelog entry and that those two incidents can be merged

@scarabeus you created mr for boo#937754 ?
Comment 10 Tomáš Chvátal 2015-07-13 14:22:25 UTC
(In reply to Martin Pluskal from comment #9)
> (In reply to Andreas Stieger from comment #8)
> > The submission SR#316442 contains the following diff:
> > 
> > +# mysql-devel needs to be provided as some pkgs still depend on it
> > +Provides:       mysql-devel = %{version}
> > +Obsoletes:      mysql-devel < %{version}
> > 
> > As this relates to bug 937630, a changelog entry would be missing.
> > 
> > The more important question would be if this conflicts with the same change
> > done to MariaDB in any way? ("have choice for" situation)
> > 
> > Further, it contains the following diff:
> > 
> > -ln -sf lib%{libname}%{soname}.so.%{soname}.0.0 lib%{libname}_r.so
> > -ln -sf lib%{libname}%{soname}.so.%{soname}.0.0 lib%{libname}_r.so.%{soname}
> > -ln -sf lib%{libname}%{soname}.so.%{soname}.0.0
> > lib%{libname}_r.so.%{soname}.0.0
> > +ln -sf lib%{libname}.so.%{soname}.0.0 lib%{libname}_r.so
> > +ln -sf lib%{libname}.so.%{soname}.0.0 lib%{libname}_r.so.%{soname}
> > +ln -sf lib%{libname}.so.%{soname}.0.0 lib%{libname}_r.so.%{soname}.0.0
> > 
> > As this relates to bug 937754, a changelog entry would be missing.
> hmm I was under impression that this update was now in queue for release,
> with proper changelog entry and that those two incidents can be merged
> 
> @scarabeus you created mr for boo#937754 ?

Well to be completely honest it is just your problem you didn't merge any previous SR to this day...
So it is your problem that martin lost some changelog entry.
Also the mysql-devel is noop on the mysql-community-server because that conditional where this is provided is never sattisfied.
Comment 11 Andreas Stieger 2015-07-13 14:31:04 UTC
(In reply to Tomáš Chvátal from comment #10)
> Well to be completely honest it is just your problem you didn't merge any
> previous SR to this day...
> So it is your problem that martin lost some changelog entry.

Which unmerged submission for mysql-community-server are you referring to?

> Also the mysql-devel is noop on the mysql-community-server because that
> conditional where this is provided is never sattisfied.

Agreed on the mysql-devel part.

If library linking change for bug 937754 is also being fixed in mysql-community-server, would need to be mentioned in the changelog, please.
Comment 12 Tomáš Chvátal 2015-07-13 14:37:47 UTC
(In reply to Andreas Stieger from comment #11)
> (In reply to Tomáš Chvátal from comment #10)
> > Well to be completely honest it is just your problem you didn't merge any
> > previous SR to this day...
> > So it is your problem that martin lost some changelog entry.
> 
> Which unmerged submission for mysql-community-server are you referring to?
> 
Ah my overlook on that, indeed it was never sent to mysql, just mariadb.
Martin could you just causaly mention the bnc#937754 in the changelogs too?
Comment 13 Martin Pluskal 2015-07-13 14:39:48 UTC
(In reply to Tomáš Chvátal from comment #12)
> (In reply to Andreas Stieger from comment #11)
> > (In reply to Tomáš Chvátal from comment #10)
> > > Well to be completely honest it is just your problem you didn't merge any
> > > previous SR to this day...
> > > So it is your problem that martin lost some changelog entry.
> > 
> > Which unmerged submission for mysql-community-server are you referring to?
> > 
> Ah my overlook on that, indeed it was never sent to mysql, just mariadb.
> Martin could you just causaly mention the bnc#937754 in the changelogs too?

ok
Comment 14 Andreas Stieger 2015-07-13 14:49:53 UTC
Looks good. It is my understanding that this affects openSUSE only.
Comment 15 Bernhard Wiedemann 2015-07-13 15:00:18 UTC
This is an autogenerated message for OBS integration:
This bug (937767) was mentioned in
https://build.opensuse.org/request/show/316467 13.2+13.1 / mysql-community-server
Comment 16 Andreas Stieger 2015-07-26 08:46:15 UTC
releasing update
Comment 17 Swamp Workflow Management 2015-07-26 09:08:17 UTC
openSUSE-RU-2015:1286-1: An update that has two recommended fixes can now be installed.

Category: recommended (moderate)
Bug References: 937754,937767
CVE References: 
Sources used:
openSUSE 13.2 (src):    mysql-community-server-5.6.25-2.6.2
openSUSE 13.1 (src):    mysql-community-server-5.6.25-7.7.2
Comment 20 Swamp Workflow Management 2015-09-26 16:10:10 UTC
openSUSE-RU-2015:1644-1: An update that has four recommended fixes can now be installed.

Category: recommended (moderate)
Bug References: 902396,937767,942908,943096
CVE References: 
Sources used:
openSUSE 13.2 (src):    mariadb-10.0.21-2.15.1
openSUSE 13.1 (src):    mariadb-5.5.45-10.1
Comment 21 Maintenance Automation 2023-10-04 08:33:53 UTC
SUSE-RU-2023:3956-1: An update that solves 221 vulnerabilities and contains three features can now be installed.

Category: recommended (moderate)
Bug References: 1001367, 1005555, 1005558, 1005562, 1005564, 1005566, 1005569, 1005581, 1005582, 1006539, 1008253, 1012075, 1013882, 1019948, 1020873, 1020875, 1020877, 1020878, 1020882, 1020884, 1020885, 1020890, 1020891, 1020894, 1020896, 1020976, 1022428, 1038740, 1039034, 1041525, 1041891, 1042632, 1043328, 1047218, 1055165, 1055268, 1058374, 1058729, 1060110, 1062583, 1067443, 1068906, 1069401, 1080891, 1083087, 1088681, 1092544, 1098683, 1101676, 1101677, 1101678, 1103342, 1111858, 1111859, 1112368, 1112377, 1112384, 1112386, 1112391, 1112397, 1112404, 1112415, 1112417, 1112421, 1112432, 1112767, 1116686, 1118754, 1120041, 1122198, 1122475, 1127027, 1132666, 1136035, 1142909, 1143215, 1144314, 1156669, 1160285, 1160868, 1160878, 1160883, 1160895, 1160912, 1166781, 1168380, 1170204, 1173028, 1173516, 1174559, 1175596, 1177472, 1178428, 1180014, 1182218, 1182255, 1182739, 1183770, 1185870, 1185872, 1186031, 1189320, 1192497, 1195325, 1195334, 1195339, 1196016, 1197459, 1198603, 1198604, 1198605, 1198606, 1198607, 1198609, 1198610, 1198611, 1198612, 1198613, 1198628, 1198629, 1198630, 1198631, 1198632, 1198633, 1198634, 1198635, 1198636, 1198637, 1198638, 1198639, 1198640, 1199928, 1200105, 1201161, 1201163, 1201164, 1201165, 1201166, 1201167, 1201168, 1201169, 1201170, 1202863, 332530, 353120, 357634, 359522, 366820, 371000, 387746, 420313, 425079, 427384, 429618, 435519, 437293, 463586, 520876, 525065, 525325, 539243, 539249, 557669, 635645, 747811, 763150, 779476, 789263, 792444, 796164, 829430, 841709, 859345, 889126, 894479, 902396, 914370, 921955, 934789, 937754, 937767, 937787, 942908, 943096, 957174, 963810, 971456, 979524, 983938, 984858, 986251, 989913, 989919, 989922, 989926, 990890, 998309
CVE References: CVE-2006-0903, CVE-2006-4226, CVE-2006-4227, CVE-2007-5969, CVE-2007-5970, CVE-2007-6303, CVE-2007-6304, CVE-2008-2079, CVE-2008-7247, CVE-2009-4019, CVE-2009-4028, CVE-2009-4030, CVE-2012-4414, CVE-2012-5611, CVE-2012-5612, CVE-2012-5615, CVE-2012-5627, CVE-2013-1976, CVE-2015-4792, CVE-2015-4802, CVE-2015-4807, CVE-2015-4815, CVE-2015-4816, CVE-2015-4819, CVE-2015-4826, CVE-2015-4830, CVE-2015-4836, CVE-2015-4858, CVE-2015-4861, CVE-2015-4864, CVE-2015-4866, CVE-2015-4870, CVE-2015-4879, CVE-2015-4895, CVE-2015-4913, CVE-2015-5969, CVE-2015-7744, CVE-2016-0505, CVE-2016-0546, CVE-2016-0596, CVE-2016-0597, CVE-2016-0598, CVE-2016-0600, CVE-2016-0606, CVE-2016-0608, CVE-2016-0609, CVE-2016-0610, CVE-2016-0616, CVE-2016-0640, CVE-2016-0641, CVE-2016-0642, CVE-2016-0644, CVE-2016-0646, CVE-2016-0649, CVE-2016-0650, CVE-2016-0651, CVE-2016-0668, CVE-2016-2047, CVE-2016-3477, CVE-2016-3492, CVE-2016-3521, CVE-2016-3615, CVE-2016-5440, CVE-2016-5584, CVE-2016-5616, CVE-2016-5624, CVE-2016-5626, CVE-2016-5629, CVE-2016-6662, CVE-2016-6663, CVE-2016-6664, CVE-2016-7440, CVE-2016-8283, CVE-2016-9843, CVE-2017-10268, CVE-2017-10286, CVE-2017-10320, CVE-2017-10365, CVE-2017-10378, CVE-2017-10379, CVE-2017-10384, CVE-2017-15365, CVE-2017-3238, CVE-2017-3243, CVE-2017-3244, CVE-2017-3257, CVE-2017-3258, CVE-2017-3265, CVE-2017-3291, CVE-2017-3302, CVE-2017-3308, CVE-2017-3309, CVE-2017-3312, CVE-2017-3313, CVE-2017-3317, CVE-2017-3318, CVE-2017-3453, CVE-2017-3456, CVE-2017-3464, CVE-2017-3636, CVE-2017-3641, CVE-2017-3653, CVE-2018-25032, CVE-2018-2562, CVE-2018-2612, CVE-2018-2622, CVE-2018-2640, CVE-2018-2665, CVE-2018-2668, CVE-2018-2755, CVE-2018-2759, CVE-2018-2761, CVE-2018-2766, CVE-2018-2767, CVE-2018-2771, CVE-2018-2777, CVE-2018-2781, CVE-2018-2782, CVE-2018-2784, CVE-2018-2786, CVE-2018-2787, CVE-2018-2810, CVE-2018-2813, CVE-2018-2817, CVE-2018-2819, CVE-2018-3058, CVE-2018-3060, CVE-2018-3063, CVE-2018-3064, CVE-2018-3066, CVE-2018-3143, CVE-2018-3156, CVE-2018-3162, CVE-2018-3173, CVE-2018-3174, CVE-2018-3185, CVE-2018-3200, CVE-2018-3251, CVE-2018-3277, CVE-2018-3282, CVE-2018-3284, CVE-2019-18901, CVE-2019-2510, CVE-2019-2537, CVE-2019-2614, CVE-2019-2627, CVE-2019-2628, CVE-2019-2737, CVE-2019-2739, CVE-2019-2740, CVE-2019-2758, CVE-2019-2805, CVE-2019-2938, CVE-2019-2974, CVE-2020-13249, CVE-2020-14765, CVE-2020-14776, CVE-2020-14789, CVE-2020-14812, CVE-2020-15180, CVE-2020-2574, CVE-2020-2752, CVE-2020-2760, CVE-2020-2812, CVE-2020-2814, CVE-2020-7221, CVE-2021-2154, CVE-2021-2166, CVE-2021-2372, CVE-2021-2389, CVE-2021-27928, CVE-2021-35604, CVE-2021-46657, CVE-2021-46658, CVE-2021-46659, CVE-2021-46661, CVE-2021-46663, CVE-2021-46664, CVE-2021-46665, CVE-2021-46668, CVE-2021-46669, CVE-2022-21427, CVE-2022-21595, CVE-2022-24048, CVE-2022-24050, CVE-2022-24051, CVE-2022-24052, CVE-2022-27376, CVE-2022-27377, CVE-2022-27378, CVE-2022-27379, CVE-2022-27380, CVE-2022-27381, CVE-2022-27382, CVE-2022-27383, CVE-2022-27384, CVE-2022-27386, CVE-2022-27387, CVE-2022-27444, CVE-2022-27445, CVE-2022-27446, CVE-2022-27447, CVE-2022-27448, CVE-2022-27449, CVE-2022-27451, CVE-2022-27452, CVE-2022-27455, CVE-2022-27456, CVE-2022-27457, CVE-2022-27458, CVE-2022-32081, CVE-2022-32083, CVE-2022-32084, CVE-2022-32085, CVE-2022-32086, CVE-2022-32087, CVE-2022-32088, CVE-2022-32089, CVE-2022-32091, CVE-2022-38791, CVE-2022-47015
Jira References: PED-2455, SLE-12253, SLE-8269
Sources used:
SUSE Linux Enterprise High Performance Computing 15 SP1 LTSS 15-SP1 (src): mariadb104-10.4.30-150100.3.5.10, python-mysqlclient-1.4.6-150100.3.3.7
SUSE Linux Enterprise Server 15 SP1 LTSS 15-SP1 (src): mariadb104-10.4.30-150100.3.5.10, python-mysqlclient-1.4.6-150100.3.3.7
SUSE Linux Enterprise Server for SAP Applications 15 SP1 (src): mariadb104-10.4.30-150100.3.5.10, python-mysqlclient-1.4.6-150100.3.3.7
SUSE CaaS Platform 4.0 (src): mariadb104-10.4.30-150100.3.5.10, python-mysqlclient-1.4.6-150100.3.3.7

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
Comment 22 Maintenance Automation 2023-12-29 12:30:34 UTC
SUSE-RU-2023:4991-1: An update that solves 221 vulnerabilities and contains three features can now be installed.

Category: recommended (moderate)
Bug References: 1001367, 1005555, 1005558, 1005562, 1005564, 1005566, 1005569, 1005581, 1005582, 1006539, 1008253, 1012075, 1013882, 1019948, 1020873, 1020875, 1020877, 1020878, 1020882, 1020884, 1020885, 1020890, 1020891, 1020894, 1020896, 1020976, 1022428, 1038740, 1039034, 1041525, 1041891, 1042632, 1043328, 1047218, 1055165, 1055268, 1058374, 1058729, 1060110, 1062583, 1067443, 1068906, 1069401, 1080891, 1083087, 1088681, 1092544, 1098683, 1101676, 1101677, 1101678, 1103342, 1111858, 1111859, 1112368, 1112377, 1112384, 1112386, 1112391, 1112397, 1112404, 1112415, 1112417, 1112421, 1112432, 1112767, 1116686, 1118754, 1120041, 1122198, 1122475, 1127027, 1132666, 1136035, 1142909, 1143215, 1144314, 1156669, 1160285, 1160868, 1160878, 1160883, 1160895, 1160912, 1166781, 1168380, 1170204, 1173028, 1173516, 1174559, 1175596, 1177472, 1178428, 1180014, 1182218, 1182255, 1182739, 1183770, 1185870, 1185872, 1186031, 1189320, 1192497, 1195325, 1195334, 1195339, 1196016, 1197459, 1198603, 1198604, 1198605, 1198606, 1198607, 1198609, 1198610, 1198611, 1198612, 1198613, 1198628, 1198629, 1198630, 1198631, 1198632, 1198633, 1198634, 1198635, 1198636, 1198637, 1198638, 1198639, 1198640, 1199928, 1200105, 1201161, 1201163, 1201164, 1201165, 1201166, 1201167, 1201168, 1201169, 1201170, 1202863, 332530, 353120, 357634, 359522, 366820, 371000, 387746, 420313, 425079, 427384, 429618, 435519, 437293, 463586, 520876, 525065, 525325, 539243, 539249, 557669, 635645, 747811, 763150, 779476, 789263, 792444, 796164, 829430, 841709, 859345, 889126, 894479, 902396, 914370, 921955, 934789, 937754, 937767, 937787, 942908, 943096, 957174, 963810, 971456, 979524, 983938, 984858, 986251, 989913, 989919, 989922, 989926, 990890, 998309
CVE References: CVE-2006-0903, CVE-2006-4226, CVE-2006-4227, CVE-2007-5969, CVE-2007-5970, CVE-2007-6303, CVE-2007-6304, CVE-2008-2079, CVE-2008-7247, CVE-2009-4019, CVE-2009-4028, CVE-2009-4030, CVE-2012-4414, CVE-2012-5611, CVE-2012-5612, CVE-2012-5615, CVE-2012-5627, CVE-2013-1976, CVE-2015-4792, CVE-2015-4802, CVE-2015-4807, CVE-2015-4815, CVE-2015-4816, CVE-2015-4819, CVE-2015-4826, CVE-2015-4830, CVE-2015-4836, CVE-2015-4858, CVE-2015-4861, CVE-2015-4864, CVE-2015-4866, CVE-2015-4870, CVE-2015-4879, CVE-2015-4895, CVE-2015-4913, CVE-2015-5969, CVE-2015-7744, CVE-2016-0505, CVE-2016-0546, CVE-2016-0596, CVE-2016-0597, CVE-2016-0598, CVE-2016-0600, CVE-2016-0606, CVE-2016-0608, CVE-2016-0609, CVE-2016-0610, CVE-2016-0616, CVE-2016-0640, CVE-2016-0641, CVE-2016-0642, CVE-2016-0644, CVE-2016-0646, CVE-2016-0649, CVE-2016-0650, CVE-2016-0651, CVE-2016-0668, CVE-2016-2047, CVE-2016-3477, CVE-2016-3492, CVE-2016-3521, CVE-2016-3615, CVE-2016-5440, CVE-2016-5584, CVE-2016-5616, CVE-2016-5624, CVE-2016-5626, CVE-2016-5629, CVE-2016-6662, CVE-2016-6663, CVE-2016-6664, CVE-2016-7440, CVE-2016-8283, CVE-2016-9843, CVE-2017-10268, CVE-2017-10286, CVE-2017-10320, CVE-2017-10365, CVE-2017-10378, CVE-2017-10379, CVE-2017-10384, CVE-2017-15365, CVE-2017-3238, CVE-2017-3243, CVE-2017-3244, CVE-2017-3257, CVE-2017-3258, CVE-2017-3265, CVE-2017-3291, CVE-2017-3302, CVE-2017-3308, CVE-2017-3309, CVE-2017-3312, CVE-2017-3313, CVE-2017-3317, CVE-2017-3318, CVE-2017-3453, CVE-2017-3456, CVE-2017-3464, CVE-2017-3636, CVE-2017-3641, CVE-2017-3653, CVE-2018-25032, CVE-2018-2562, CVE-2018-2612, CVE-2018-2622, CVE-2018-2640, CVE-2018-2665, CVE-2018-2668, CVE-2018-2755, CVE-2018-2759, CVE-2018-2761, CVE-2018-2766, CVE-2018-2767, CVE-2018-2771, CVE-2018-2777, CVE-2018-2781, CVE-2018-2782, CVE-2018-2784, CVE-2018-2786, CVE-2018-2787, CVE-2018-2810, CVE-2018-2813, CVE-2018-2817, CVE-2018-2819, CVE-2018-3058, CVE-2018-3060, CVE-2018-3063, CVE-2018-3064, CVE-2018-3066, CVE-2018-3143, CVE-2018-3156, CVE-2018-3162, CVE-2018-3173, CVE-2018-3174, CVE-2018-3185, CVE-2018-3200, CVE-2018-3251, CVE-2018-3277, CVE-2018-3282, CVE-2018-3284, CVE-2019-18901, CVE-2019-2510, CVE-2019-2537, CVE-2019-2614, CVE-2019-2627, CVE-2019-2628, CVE-2019-2737, CVE-2019-2739, CVE-2019-2740, CVE-2019-2758, CVE-2019-2805, CVE-2019-2938, CVE-2019-2974, CVE-2020-13249, CVE-2020-14765, CVE-2020-14776, CVE-2020-14789, CVE-2020-14812, CVE-2020-15180, CVE-2020-2574, CVE-2020-2752, CVE-2020-2760, CVE-2020-2812, CVE-2020-2814, CVE-2020-7221, CVE-2021-2154, CVE-2021-2166, CVE-2021-2372, CVE-2021-2389, CVE-2021-27928, CVE-2021-35604, CVE-2021-46657, CVE-2021-46658, CVE-2021-46659, CVE-2021-46661, CVE-2021-46663, CVE-2021-46664, CVE-2021-46665, CVE-2021-46668, CVE-2021-46669, CVE-2022-21427, CVE-2022-21595, CVE-2022-24048, CVE-2022-24050, CVE-2022-24051, CVE-2022-24052, CVE-2022-27376, CVE-2022-27377, CVE-2022-27378, CVE-2022-27379, CVE-2022-27380, CVE-2022-27381, CVE-2022-27382, CVE-2022-27383, CVE-2022-27384, CVE-2022-27386, CVE-2022-27387, CVE-2022-27444, CVE-2022-27445, CVE-2022-27446, CVE-2022-27447, CVE-2022-27448, CVE-2022-27449, CVE-2022-27451, CVE-2022-27452, CVE-2022-27455, CVE-2022-27456, CVE-2022-27457, CVE-2022-27458, CVE-2022-32081, CVE-2022-32083, CVE-2022-32084, CVE-2022-32085, CVE-2022-32086, CVE-2022-32087, CVE-2022-32088, CVE-2022-32089, CVE-2022-32091, CVE-2022-38791, CVE-2022-47015
Jira References: PED-2455, SLE-12253, SLE-8269
Sources used:
SUSE Linux Enterprise Software Development Kit 12 SP5 (src): mariadb-connector-c-3.1.22-2.35.1, lz4-1.8.0-3.5.2, python-mysqlclient-1.3.14-8.9.2, mariadb104-10.4.30-8.5.46
SUSE Linux Enterprise High Performance Computing 12 SP5 (src): mariadb-connector-c-3.1.22-2.35.1, lz4-1.8.0-3.5.2, python-mysqlclient-1.3.14-8.9.2, mariadb104-10.4.30-8.5.46
SUSE Linux Enterprise Server 12 SP5 (src): mariadb-connector-c-3.1.22-2.35.1, lz4-1.8.0-3.5.2, python-mysqlclient-1.3.14-8.9.2, mariadb104-10.4.30-8.5.46
SUSE Linux Enterprise Server for SAP Applications 12 SP5 (src): mariadb-connector-c-3.1.22-2.35.1, lz4-1.8.0-3.5.2, python-mysqlclient-1.3.14-8.9.2, mariadb104-10.4.30-8.5.46

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.