[MDEV-4728] MariaDB can't start while bootup - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Minor
Resolution: Fixed
Affects Version/s: 5.5.29-galera
Fix Version/s: 5.5.39-galera, 10.0.13-galera
Component/s: None
Labels:
- galera
Environment:
centos 6.4 amd64

Description

Start it from command:

/usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/var/run/mysqld/mysqld.pid --basedir=/usr --user=mysql --log-error=/var/log/mysqld.log

And it will NOT never create sub process with mysqld , the status is shown as below:

root     13648  0.0  0.1 122240  4784 ?        S    13:18   0:00 /usr/bin/python /usr/bin/pidproxy /var/run/mysqld/mysqld.pid /usr/bin/mysqld_safe --datadir=/var/lib/my

root     13649  0.0  0.0 108328  1544 ?        S    13:18   0:00 /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/va

root     13921  0.0  0.0 103248   848 ?        S    13:18   0:00 grep WSREP: Recovered position:

HOW TO FIX IT:
in /usr/bin/mysqld_safe (MariaDB-Galera-server-5.5.29-1.x86_64.rpm)
line 220:

  [ "$EUID" = "0" ] && chown $user $wr_logfile

to fix it:

  [ "$EUID" == "0" ] && chown $user $wr_logfile

Attachments

Activity

Ascending order - Click to sort in descending order

Yuanjun.Li created issue - 2013-06-28 09:08

Yuanjun.Li made changes - 2013-06-28 09:22

Field	Original Value	New Value
Description	Start it from command: /usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/var/run/mysqld/mysqld.pid --basedir=/usr --user=mysql --log-error=/var/log/mysqld.log And it will NOT create sub process with mysqld , the status is shown as blow: root 13648 0.0 0.1 122240 4784 ? S 13:18 0:00 /usr/bin/python /usr/bin/pidproxy /var/run/mysqld/mysqld.pid /usr/bin/mysqld_safe --datadir=/var/lib/my root 13649 0.0 0.0 108328 1544 ? S 13:18 0:00 /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/va root 13921 0.0 0.0 103248 848 ? S 13:18 0:00 grep WSREP: Recovered position: HOW TO FIX IT: in /usr/bin/mysqld_safe (MariaDB-Galera-server-5.5.29-1.x86_64.rpm) line 220: [ "$EUID" = "0" ] && chown $user $wr_logfile to fix it: [ "$EUID" == "0" ] && chown $user $wr_logfile	Start it from command: {code} /usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/var/run/mysqld/mysqld.pid --basedir=/usr --user=mysql --log-error=/var/log/mysqld.log {code} And it will NOT create sub process with mysqld , the status is shown as blow: {code} root 13648 0.0 0.1 122240 4784 ? S 13:18 0:00 /usr/bin/python /usr/bin/pidproxy /var/run/mysqld/mysqld.pid /usr/bin/mysqld_safe --datadir=/var/lib/my root 13649 0.0 0.0 108328 1544 ? S 13:18 0:00 /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/va root 13921 0.0 0.0 103248 848 ? S 13:18 0:00 grep WSREP: Recovered position: {code} HOW TO FIX IT: in /usr/bin/mysqld_safe (MariaDB-Galera-server-5.5.29-1.x86_64.rpm) line 220: [ "$EUID" = "0" ] && chown $user $wr_logfile to fix it: [ "$EUID" == "0" ] && chown $user $wr_logfile

Yuanjun.Li made changes - 2013-06-28 09:23

Description

*Start it from command:*
{code}
/usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/var/run/mysqld/mysqld.pid --basedir=/usr --user=mysql --log-error=/var/log/mysqld.log
{code}

*And it will NOT create sub process with mysqld , the status is shown as blow:*
{code}
root 13648 0.0 0.1 122240 4784 ? S 13:18 0:00 /usr/bin/python /usr/bin/pidproxy /var/run/mysqld/mysqld.pid /usr/bin/mysqld_safe --datadir=/var/lib/my
root 13649 0.0 0.0 108328 1544 ? S 13:18 0:00 /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/va
root 13921 0.0 0.0 103248 848 ? S 13:18 0:00 grep WSREP: Recovered position:
{code}

*HOW TO FIX IT:*
in /usr/bin/mysqld_safe (MariaDB-Galera-server-5.5.29-1.x86_64.rpm)
line 220:
[ "$EUID" = "0" ] && chown $user $wr_logfile

to fix it:
[ "$EUID" == "0" ] && chown $user $wr_logfile

*Start it from command:*
{code}
/usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/var/run/mysqld/mysqld.pid --basedir=/usr --user=mysql --log-error=/var/log/mysqld.log
{code}

*And it will NOT never create sub process with mysqld , the status is shown as blow:*
{code}
root 13648 0.0 0.1 122240 4784 ? S 13:18 0:00 /usr/bin/python /usr/bin/pidproxy /var/run/mysqld/mysqld.pid /usr/bin/mysqld_safe --datadir=/var/lib/my
root 13649 0.0 0.0 108328 1544 ? S 13:18 0:00 /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/va
root 13921 0.0 0.0 103248 848 ? S 13:18 0:00 grep WSREP: Recovered position:
{code}

*HOW TO FIX IT:*
in /usr/bin/mysqld_safe (MariaDB-Galera-server-5.5.29-1.x86_64.rpm)
line 220:
{code} [ "$EUID" = "0" ] && chown $user $wr_logfile {code}

to fix it:
{code} [ "$EUID" == "0" ] && chown $user $wr_logfile {code}

Yuanjun.Li made changes - 2013-06-28 09:25

Description

*Start it from command:*
{code}
/usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/var/run/mysqld/mysqld.pid --basedir=/usr --user=mysql --log-error=/var/log/mysqld.log
{code}

*And it will NOT never create sub process with mysqld , the status is shown as blow:*
{code}
root 13648 0.0 0.1 122240 4784 ? S 13:18 0:00 /usr/bin/python /usr/bin/pidproxy /var/run/mysqld/mysqld.pid /usr/bin/mysqld_safe --datadir=/var/lib/my
root 13649 0.0 0.0 108328 1544 ? S 13:18 0:00 /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/va
root 13921 0.0 0.0 103248 848 ? S 13:18 0:00 grep WSREP: Recovered position:
{code}

*HOW TO FIX IT:*
in /usr/bin/mysqld_safe (MariaDB-Galera-server-5.5.29-1.x86_64.rpm)
line 220:
{code} [ "$EUID" = "0" ] && chown $user $wr_logfile {code}

to fix it:
{code} [ "$EUID" == "0" ] && chown $user $wr_logfile {code}

*Start it from command:*
{code}
/usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/var/run/mysqld/mysqld.pid --basedir=/usr --user=mysql --log-error=/var/log/mysqld.log
{code}

*And it will NOT never create sub process with mysqld , the status is shown as below:*
{code}
root 13648 0.0 0.1 122240 4784 ? S 13:18 0:00 /usr/bin/python /usr/bin/pidproxy /var/run/mysqld/mysqld.pid /usr/bin/mysqld_safe --datadir=/var/lib/my
root 13649 0.0 0.0 108328 1544 ? S 13:18 0:00 /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/va
root 13921 0.0 0.0 103248 848 ? S 13:18 0:00 grep WSREP: Recovered position:
{code}

*HOW TO FIX IT:*
in /usr/bin/mysqld_safe (MariaDB-Galera-server-5.5.29-1.x86_64.rpm)
line 220:
{code} [ "$EUID" = "0" ] && chown $user $wr_logfile {code}

to fix it:
{code} [ "$EUID" == "0" ] && chown $user $wr_logfile {code}

Elena Stepanova made changes - 2013-06-28 15:10

Assignee

Elena Stepanova [ elenst ]

Elena Stepanova added a comment - 2013-06-28 15:28

Hi,

I agree there is a potential problem, but I'm not sure about your solution.

You put CentOS 6.4 in the environment field. What does your /bin/sh point at?

In my (more or less default) installation of CentOS 6.4 it points at bash, of version 4.1.2, which seems to be equally happy about either "=" or "==".

At the same time, on Ubuntu 12.04 /bin/sh points at dash; and it accepts "=", although it doesn't work correctly (hence the problem), but with "==" it complains about a syntax error.

So,

please clarify which shell you are using as /bin/sh, and of which version;
please create the script:

./1.sh
#!/bin/sh

[ "$EUID" = "0" ] && echo "My EUID with =: $EUID"
[ "$EUID" == "0" ] && echo "My EUID with ==: $EUID"

make it executable and execute twice, first time as a normal non-root user, and then under sudo, and paste the output.

Thanks.

Elena Stepanova added a comment - 2013-06-28 15:28 Hi, I agree there is a potential problem, but I'm not sure about your solution. You put CentOS 6.4 in the environment field. What does your /bin/sh point at? In my (more or less default) installation of CentOS 6.4 it points at bash, of version 4.1.2, which seems to be equally happy about either "=" or "==". At the same time, on Ubuntu 12.04 /bin/sh points at dash; and it accepts "=", although it doesn't work correctly (hence the problem), but with "==" it complains about a syntax error. So, please clarify which shell you are using as /bin/sh, and of which version; please create the script: ./1.sh #!/bin/sh [ "$EUID" = "0" ] && echo "My EUID with =: $EUID" [ "$EUID" == "0" ] && echo "My EUID with ==: $EUID" make it executable and execute twice, first time as a normal non-root user, and then under sudo, and paste the output. Thanks.

Elena Stepanova added a comment - 2013-06-28 19:20

It turns out that the '=' comparison in dash also works correctly, the problem is that EUID is not defined in dash, hence the comparison with 0 is always false. This problem has been fixed in the current tree by defining a local euid as
euid=$(id -u)
and using it further in the comparison. It works both in dash and bash.

But the comparison is still '=', so the question above about your shell version (which understands '==' but not '=') becomes even more important.

Elena Stepanova added a comment - 2013-06-28 19:20 It turns out that the '=' comparison in dash also works correctly, the problem is that EUID is not defined in dash, hence the comparison with 0 is always false. This problem has been fixed in the current tree by defining a local euid as euid=$(id -u) and using it further in the comparison. It works both in dash and bash. But the comparison is still '=', so the question above about your shell version (which understands '==' but not '=') becomes even more important.

Elena Stepanova made changes - 2013-06-28 19:20

Due Date

2013-07-28

Yuanjun.Li added a comment - 2013-07-01 07:03 - edited

Here are some test outputs:

[root@linux_dev_193 ~]# ls -lh /bin/sh

lrwxrwxrwx. 1 root root 4 6月  20 11:46 /bin/sh -> bash

[root@linux_dev_193 ~]# rpm -qa | grep bash

bash-4.1.2-14.el6.x86_64

[root@linux_dev_193 ~]# cat > 1.sh << EOF

> #!/bin/sh

> [ "$EUID" = "0" ] && echo "My EUID with =: $EUID"

> [ "$EUID" == "0" ] && echo "My EUID with ==: $EUID"

> EOF

[root@linux_dev_193 ~]# chmod +x 1.sh

[root@linux_dev_193 ~]# ./1.sh

My EUID with =: 0

My EUID with ==: 0

And this is my fault, I think it's a supervisor bug, or weird behavior of 'mktemp', see following code:

  wr_logfile=$(mktemp)

  [ "$EUID" = "0" ] && chown $user $wr_logfile

  chmod 600 $wr_logfile

  log_notice "WSREP: Running position recovery with --log_error=$wr_logfile"

  $mysqld_cmd --log_error=$wr_logfile --wsrep-recover

  rp=$(grep "WSREP: Recovered position:" $wr_logfile)

if wr_logfile is empty, and the 'grep' command will hang everything, but in normal shell, mktemp can NOT failed, so it's weird
so, for safety:

  wr_logfile=`mktemp`

  [ -f $wr_logfile ] || return 0

  [ "$EUID" == "0" ] && chown $user $wr_logfile

  chmod 600 $wr_logfile

  log_notice "WSREP: Running position recovery with --log_error=$wr_logfile"

  $mysqld_cmd --log_error=$wr_logfile --wsrep-recover

  rp=$(grep "WSREP: Recovered position:" $wr_logfile)

Yuanjun.Li added a comment - 2013-07-01 07:03 - edited Here are some test outputs: [root@linux_dev_193 ~]# ls -lh /bin/sh lrwxrwxrwx. 1 root root 4 6月 20 11:46 /bin/sh -> bash [root@linux_dev_193 ~]# rpm -qa | grep bash bash-4.1.2-14.el6.x86_64 [root@linux_dev_193 ~]# cat > 1.sh << EOF > #!/bin/sh > > [ "$EUID" = "0" ] && echo "My EUID with =: $EUID" > [ "$EUID" == "0" ] && echo "My EUID with ==: $EUID" > EOF [root@linux_dev_193 ~]# chmod +x 1.sh [root@linux_dev_193 ~]# ./1.sh My EUID with =: 0 My EUID with ==: 0 And this is my fault, I think it's a supervisor bug, or weird behavior of 'mktemp', see following code: wr_logfile=$(mktemp) [ "$EUID" = "0" ] && chown $user $wr_logfile chmod 600 $wr_logfile log_notice "WSREP: Running position recovery with --log_error=$wr_logfile" $mysqld_cmd --log_error=$wr_logfile --wsrep-recover rp=$(grep "WSREP: Recovered position:" $wr_logfile) if wr_logfile is empty, and the 'grep' command will hang everything, but in normal shell, mktemp can NOT failed, so it's weird so, for safety: wr_logfile=`mktemp` [ -f $wr_logfile ] || return 0 [ "$EUID" == "0" ] && chown $user $wr_logfile chmod 600 $wr_logfile log_notice "WSREP: Running position recovery with --log_error=$wr_logfile" $mysqld_cmd --log_error=$wr_logfile --wsrep-recover rp=$(grep "WSREP: Recovered position:" $wr_logfile)

Elena Stepanova added a comment - 2013-07-03 01:42

Hi Seppo,

See the suggestion above about making wsrep-related logic in mysqld_safe.sh slightly safer.

Elena Stepanova added a comment - 2013-07-03 01:42 Hi Seppo, See the suggestion above about making wsrep-related logic in mysqld_safe.sh slightly safer.

Elena Stepanova made changes - 2013-07-03 01:42

Fix Version/s		5.5.32-galera [ 13203 ]
Assignee	Elena Stepanova [ elenst ]	Seppo Jaakola [ seppo ]
Due Date	2013-07-28
Labels		galera
Priority	Major [ 3 ]	Minor [ 4 ]

Rasmus Johansson (Inactive) made changes - 2013-08-28 22:09

Fix Version/s		5.5.33-galera [ 13600 ]
Fix Version/s	5.5.32-galera [ 13203 ]

Sergei Golubchik made changes - 2013-10-01 11:30

Fix Version/s		5.5.34-galera [ 13900 ]
Fix Version/s	5.5.33a-galera [ 13600 ]

Rasmus Johansson (Inactive) made changes - 2013-11-29 14:14

Fix Version/s		5.5.35-galera [ 14300 ]
Fix Version/s	5.5.34-galera [ 13900 ]

Sergei Golubchik made changes - 2014-02-14 19:16

Fix Version/s		5.5.36-galera [ 14801 ]
Fix Version/s	5.5.35-galera [ 14300 ]

Jan Lindström (Inactive) made changes - 2014-02-27 16:31

Fix Version/s

5.5.36-galera [ 14801 ]

Sergei Golubchik made changes - 2014-06-13 15:06

Workflow

defaullt [ 27772 ]

MariaDB v2 [ 42744 ]

Nirbhay Choubey (Inactive) made changes - 2014-07-15 08:02

Assignee

Seppo Jaakola [ seppo ]

Nirbhay Choubey [ nirbhay_c ]

Nirbhay Choubey (Inactive) made changes - 2014-07-15 08:03

Status

Open [ 1 ]

In Progress [ 3 ]

Nirbhay Choubey (Inactive) added a comment - 2014-07-15 08:04

http://bazaar.launchpad.net/~maria-captains/maria/maria-5.5-galera/revision/3511

Nirbhay Choubey (Inactive) added a comment - 2014-07-15 08:04 http://bazaar.launchpad.net/~maria-captains/maria/maria-5.5-galera/revision/3511

Nirbhay Choubey (Inactive) made changes - 2014-07-15 08:04

Fix Version/s		5.5.39-galera [ 16302 ]
Fix Version/s		10.0.13-galera [ 16800 ]
Resolution		Fixed [ 1 ]
Status	In Progress [ 3 ]	Closed [ 6 ]

Yuanjun.Li added a comment - 2014-07-15 18:34

Nice!

Yuanjun.Li added a comment - 2014-07-15 18:34 Nice!

Rasmus Johansson (Inactive) made changes - 2015-05-18 17:51

Workflow

MariaDB v2 [ 42744 ]

MariaDB v3 [ 64529 ]

Sergei Golubchik made changes - 2021-12-06 21:38

Workflow

MariaDB v3 [ 64529 ]

MariaDB v4 [ 146821 ]

People

Assignee:: Nirbhay Choubey (Inactive)

Reporter:: Yuanjun.Li

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2013-06-28 09:08

Updated:: 2014-07-15 18:34

Resolved:: 2014-07-15 08:04

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server

Details

Description

Attachments

Activity

People

Dates

Git Integration