Mageia Bugzilla – Attachment 8938 Details for
Bug 20143
mysqld is not Active after start
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Requests
|
Help
|
Log In
[x]
|
New Account
|
Forgot Password
Konsole I/O from patching
patch.txt (text/plain), 3.79 KB, created by
Arne Spiegelhauer
on 2017-02-06 16:12:54 CET
(
hide
)
Description:
Konsole I/O from patching
Filename:
MIME Type:
Creator:
Arne Spiegelhauer
Created:
2017-02-06 16:12:54 CET
Size:
3.79 KB
patch
obsolete
>[aspiegel@localhost ~]$ su - >Password: >[root@localhost ~]# systemctl status mysqld.service >â mysqld.service - MySQL database server > Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: enabled) > Active: deactivating (stop-sigterm) (Result: exit-code) > Process: 1769 ExecStartPost=/usr/sbin/mysqld-wait-ready $MAINPID (code=exited, status=1/FAILURE) > Process: 1513 ExecStart=/usr/bin/mysqld_safe --nowatch (code=exited, status=0/SUCCESS) > Process: 1472 ExecStartPre=/usr/sbin/mysqld-prepare-db-dir (code=exited, status=0/SUCCESS) > CGroup: /system.slice/mysqld.service > ââ1767 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysq > >Feb 06 15:48:43 localhost systemd[1]: Starting MySQL database server... >Feb 06 15:48:43 localhost mysqld_safe[1513]: 170206 15:48:43 mysqld_safe Logging to '/var/log/mysqld/my >Feb 06 15:48:43 localhost mysqld_safe[1513]: 170206 15:48:43 mysqld_safe Starting mysqld daemon with da >Feb 06 15:48:44 localhost systemd[1]: mysqld.service: Control process exited, code=exited status=1 >[root@localhost ~]# patch -p0 < /home/aspiegel/debug/mysqld_safe.patch >Ignoring potentially dangerous file name /usr/bin/mysqld_safe >can't find file to patch at input line 3 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- /usr/bin/mysqld_safe.orig 2017-01-29 20:16:41.000000000 +0100 >|+++ /usr/bin/mysqld_safe 2017-02-06 12:25:43.851172322 +0100 >-------------------------- >File to patch: /usr/bin/mysqld_safe >patching file /usr/bin/mysqld_safe >[root@localhost ~]# patch -p0 < /home/aspiegel/debug/mysqld.service.patch >Ignoring potentially dangerous file name /usr/lib/systemd/system/mysqld.service >can't find file to patch at input line 3 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|--- /usr/lib/systemd/system/mysqld.service.orig 2017-01-29 20:19:13.000000000 +0100 >|+++ /usr/lib/systemd/system/mysqld.service 2017-02-06 11:07:01.810710428 +0100 >-------------------------- >File to patch: /usr/lib/systemd/system/mysqld.service >patching file /usr/lib/systemd/system/mysqld.service >[root@localhost ~]# systemctl daemon-reload >[root@localhost ~]# systemctl stop mysqld.service >[root@localhost ~]# systemctl start mysqld.service >[root@localhost ~]# systemctl status mysqld.service >â mysqld.service - MySQL database server > Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: enabled) > Active: active (running) since Mon 2017-02-06 15:54:21 CET; 4s ago > Process: 26829 ExecStartPre=/usr/sbin/mysqld-prepare-db-dir (code=exited, status=0/SUCCESS) > Main PID: 26845 (mysqld) > Status: "Taking your SQL requests now..." > CGroup: /system.slice/mysqld.service > ââ26845 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mys > >Feb 06 15:54:20 localhost systemd[1]: Starting MySQL database server... >Feb 06 15:54:20 localhost mysqld_safe[26845]: 170206 15:54:20 mysqld_safe Logging to '/var/log/mysqld/m >Feb 06 15:54:20 localhost mysqld_safe[26845]: 170206 15:54:20 mysqld_safe Starting mysqld daemon with d >Feb 06 15:54:21 localhost systemd[1]: Started MySQL database server. >lines 1-13/13 (END)
[aspiegel@localhost ~]$ su - Password: [root@localhost ~]# systemctl status mysqld.service â mysqld.service - MySQL database server Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: enabled) Active: deactivating (stop-sigterm) (Result: exit-code) Process: 1769 ExecStartPost=/usr/sbin/mysqld-wait-ready $MAINPID (code=exited, status=1/FAILURE) Process: 1513 ExecStart=/usr/bin/mysqld_safe --nowatch (code=exited, status=0/SUCCESS) Process: 1472 ExecStartPre=/usr/sbin/mysqld-prepare-db-dir (code=exited, status=0/SUCCESS) CGroup: /system.slice/mysqld.service ââ1767 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysq Feb 06 15:48:43 localhost systemd[1]: Starting MySQL database server... Feb 06 15:48:43 localhost mysqld_safe[1513]: 170206 15:48:43 mysqld_safe Logging to '/var/log/mysqld/my Feb 06 15:48:43 localhost mysqld_safe[1513]: 170206 15:48:43 mysqld_safe Starting mysqld daemon with da Feb 06 15:48:44 localhost systemd[1]: mysqld.service: Control process exited, code=exited status=1 [root@localhost ~]# patch -p0 < /home/aspiegel/debug/mysqld_safe.patch Ignoring potentially dangerous file name /usr/bin/mysqld_safe can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- /usr/bin/mysqld_safe.orig 2017-01-29 20:16:41.000000000 +0100 |+++ /usr/bin/mysqld_safe 2017-02-06 12:25:43.851172322 +0100 -------------------------- File to patch: /usr/bin/mysqld_safe patching file /usr/bin/mysqld_safe [root@localhost ~]# patch -p0 < /home/aspiegel/debug/mysqld.service.patch Ignoring potentially dangerous file name /usr/lib/systemd/system/mysqld.service can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- /usr/lib/systemd/system/mysqld.service.orig 2017-01-29 20:19:13.000000000 +0100 |+++ /usr/lib/systemd/system/mysqld.service 2017-02-06 11:07:01.810710428 +0100 -------------------------- File to patch: /usr/lib/systemd/system/mysqld.service patching file /usr/lib/systemd/system/mysqld.service [root@localhost ~]# systemctl daemon-reload [root@localhost ~]# systemctl stop mysqld.service [root@localhost ~]# systemctl start mysqld.service [root@localhost ~]# systemctl status mysqld.service â mysqld.service - MySQL database server Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2017-02-06 15:54:21 CET; 4s ago Process: 26829 ExecStartPre=/usr/sbin/mysqld-prepare-db-dir (code=exited, status=0/SUCCESS) Main PID: 26845 (mysqld) Status: "Taking your SQL requests now..." CGroup: /system.slice/mysqld.service ââ26845 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mys Feb 06 15:54:20 localhost systemd[1]: Starting MySQL database server... Feb 06 15:54:20 localhost mysqld_safe[26845]: 170206 15:54:20 mysqld_safe Logging to '/var/log/mysqld/m Feb 06 15:54:20 localhost mysqld_safe[26845]: 170206 15:54:20 mysqld_safe Starting mysqld daemon with d Feb 06 15:54:21 localhost systemd[1]: Started MySQL database server. lines 1-13/13 (END)
View Attachment As Raw
Actions:
View
Attachments on
bug 20143
:
8915
|
8925
|
8936
|
8937
| 8938 |
8944
|
8952
|
8953
|
8954
|
8955