Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.2.25
-
None
-
Red Hat Enterprise Linux Server release 7.6 (Maipo)
Linux bdsandbox-dev02.si.sti.usherbrooke.ca 3.10.0-957.21.3.el7.x86_64 #1 SMP Fri Jun 14 02:54:29 EDT 2019 x86_64 x86_64 x86_64 GNU/Linux
Description
I have the same errors as MDEV-19481 when starting with systemctl.
[mysql@bdsandbox-dev02 mysql.d]$ sudo systemctl status udes-mariadb@mysqld1
|
● udes-mariadb@mysqld1.service - MariaDB database server instance mysqld1
|
Loaded: loaded (/usr/lib/systemd/system/udes-mariadb@.service; enabled; vendor preset: disabled)
|
Active: failed (Result: exit-code) since Thu 2019-08-08 09:32:12 EDT; 12s ago
|
Docs: man:mysqld(8)
|
https://mariadb.com/kb/en/library/systemd/
|
Process: 9478 ExecStart=/usr/local/mysql/bin/mysqld --defaults-file=/opt/mysql.d/%I.cnf (code=exited, status=1/FAILURE)
|
Main PID: 9478 (code=exited, status=1/FAILURE)
|
|
|
Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca systemd[1]: Starting MariaDB database server instance mysqld1...
|
Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca mysqld[9478]: /usr/local/mysql/bin/mysqld: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /usr/local/mysql/bin/mysqld)
|
Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca mysqld[9478]: /usr/local/mysql/bin/mysqld: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /usr/local/mysql/bin/mysqld)
|
Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca systemd[1]: udes-mariadb@mysqld1.service: main process exited, code=exited, status=1/FAILURE
|
Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca systemd[1]: Failed to start MariaDB database server instance mysqld1.
|
Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca systemd[1]: Unit udes-mariadb@mysqld1.service entered failed state.
|
Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca systemd[1]: udes-mariadb@mysqld1.service failed
|
I am using package mariadb-10.2.25-linux-systemd-x86_64.tar.gz.
When I switch back to 10,2.23, instance goes up normally with systemctl.
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | Mariadb on Red Hat 7 with systemd does start after upgrade to 10.2.25 | Mariadb on Red Hat 7 with systemd does not start after upgrade to 10.2.25 |
| Description |
I have the same errors as [mysql@bdsandbox-dev02 mysql.d]$ sudo systemctl status udes-mariadb@mysqld1 ● udes-mariadb@mysqld1.service - MariaDB database server instance mysqld1 Loaded: loaded (/usr/lib/systemd/system/udes-mariadb@.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2019-08-08 09:32:12 EDT; 12s ago Docs: man:mysqld(8) https://mariadb.com/kb/en/library/systemd/ Process: 9478 ExecStart=/usr/local/mysql/bin/mysqld --defaults-file=/opt/mysql.d/%I.cnf (code=exited, status=1/FAILURE) Main PID: 9478 (code=exited, status=1/FAILURE) Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca systemd[1]: Starting MariaDB database server instance mysqld1... Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca mysqld[9478]: /usr/local/mysql/bin/mysqld: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /usr/local/mysql/bin/mysqld) Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca mysqld[9478]: /usr/local/mysql/bin/mysqld: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /usr/local/mysql/bin/mysqld) Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca systemd[1]: udes-mariadb@mysqld1.service: main process exited, code=exited, status=1/FAILURE Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca systemd[1]: Failed to start MariaDB database server instance mysqld1. Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca systemd[1]: Unit udes-mariadb@mysqld1.service entered failed state. Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca systemd[1]: udes-mariadb@mysqld1.service failed I am using package mariadb-10.2.25-linux-systemd-x86_64.tar.gz. When I switch back to 10,2.23, instance goes up normally with systemctl. |
I have the same errors as {noformat} [mysql@bdsandbox-dev02 mysql.d]$ sudo systemctl status udes-mariadb@mysqld1 ● udes-mariadb@mysqld1.service - MariaDB database server instance mysqld1 Loaded: loaded (/usr/lib/systemd/system/udes-mariadb@.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2019-08-08 09:32:12 EDT; 12s ago Docs: man:mysqld(8) https://mariadb.com/kb/en/library/systemd/ Process: 9478 ExecStart=/usr/local/mysql/bin/mysqld --defaults-file=/opt/mysql.d/%I.cnf (code=exited, status=1/FAILURE) Main PID: 9478 (code=exited, status=1/FAILURE) Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca systemd[1]: Starting MariaDB database server instance mysqld1... Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca mysqld[9478]: /usr/local/mysql/bin/mysqld: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /usr/local/mysql/bin/mysqld) Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca mysqld[9478]: /usr/local/mysql/bin/mysqld: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /usr/local/mysql/bin/mysqld) Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca systemd[1]: udes-mariadb@mysqld1.service: main process exited, code=exited, status=1/FAILURE Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca systemd[1]: Failed to start MariaDB database server instance mysqld1. Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca systemd[1]: Unit udes-mariadb@mysqld1.service entered failed state. Aug 08 09:32:12 bdsandbox-dev02.si.sti.usherbrooke.ca systemd[1]: udes-mariadb@mysqld1.service failed {noformat} I am using package mariadb-10.2.25-linux-systemd-x86_64.tar.gz. When I switch back to 10,2.23, instance goes up normally with systemctl. |
| Component/s | Packaging [ 10700 ] | |
| Fix Version/s | N/A [ 14700 ] | |
| Resolution | Duplicate [ 3 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Link |
This issue is duplicated by |
| Workflow | MariaDB v3 [ 98810 ] | MariaDB v4 [ 156594 ] |
As the fix version in
MDEV-19481states, it was fixed in 10.2.26.