[opensuse] "mysqld_safe" works, "systemctl start mysql.service" doesn't

Brian Sammon

13 Nov 2014 13 Nov '14

21:58

[mariadb 5.5.33-2.2 on OpenSuse x86_64 13.1, with some factory and some 13.2 packages] When I start mysql with "mysqld_safe", it runs, but when I try to start it via "systemctl start mysql.service", it does not. I suppose my questions are: 1) Am I right in expecting those two things to do the same thing? 2) Should I care that they don't, or just go ahead and use "mysqld_safe"? 3) If I do care, what do I do next? Can I increase the verbosity of the logging? When I use the systemctl method, I can't find any log files or information to tell me what went wrong. "systemctl status mysql.service" says: mysql.service - LSB: Start the MySQL database server Loaded: loaded (/etc/init.d/mysql) Active: active (exited) since Thu 2014-11-13 14:50:32 EST; 30min ago Process: 4320 ExecStop=/etc/init.d/mysql stop (code=exited, status=0/SUCCESS) Process: 4352 ExecStart=/etc/init.d/mysql start (code=exited, status=0/SUCCESS) Nov 13 14:50:32 mymachine mysql[4352]: Starting service MySQL ..done This is a dev machine for Ruby on Rails development, which had been installed with 13.1. Up until 2 days ago, this had been running without reboot for a few weeks, with mariadb running nonstop during that time. In the last few days, I thought it would be a good idea (Danger, Will Robinson! ) to upgrade some of my packages (mostly the ones that were factory versions) to the 13.2 versions. This ended up including a reboot, whereupon I found myself in my current dilemma, not knowing the right way to start mariaDB. P.S. Someone looking over my shoulder said "You're mixing packages from two different versions[13.1 and 13.2] -- that's your problem right there -- you should never do that" Agree/disagree? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Show replies by date

Florian Gleixner

13 Nov 13 Nov

22:24

On 11/13/2014 10:58 PM, Brian Sammon wrote:

...

[mariadb 5.5.33-2.2 on OpenSuse x86_64 13.1, with some factory and some 13.2 packages]

Mixing is not good. But you have mariadb from Opensuse 13.1. ...

...

"systemctl status mysql.service" says: mysql.service - LSB: Start the MySQL database server

The "LSB" means, that you start a systemV script from /etc/init.d/mysql This is different to mysqld_safe, because it adds some parameters: SAFE_MYSQLD=/usr/bin/mysqld_safe ... $SAFE_MYSQLD \ --mysqld=${MYSQLD#/usr/sbin/} \ $debug_flags \ --user="$mysql_daemon_user" \ --pid-file="$pid_file" \ --socket="$socket" \ --datadir="$datadir" &>/dev/null & You can see the output of /etc/init.d/mysql in /var/log/messages, and the error messages of mysql at /var/lib/mysql/*.err This should help to solve your problem. B.t.w. If you upgrade to Opensuse 13.2 you will have to upgrade your tables. Watch for instructions in the messages.

Brian Sammon

22:37

On Thu, 13 Nov 2014 23:24:46 +0100 Florian Gleixner wrote:

...

On 11/13/2014 10:58 PM, Brian Sammon wrote:

...
[mariadb 5.5.33-2.2 on OpenSuse x86_64 13.1, with some factory and som 13.2 packages]

Mixing is not good. But you have mariadb from Opensuse 13.1. ...

...
"systemctl status mysql.service" says: mysql.service - LSB: Start the MySQL database server

The "LSB" means, that you start a systemV script from /etc/init.d/mysql

Okay, this is useful information -- I am new to systemd, and I was not sure if /etc/init.d was the place to look. I can experiment with the file to troubleshoot this.

...

You can see the output of /etc/init.d/mysql in /var/log/messages, and the error messages of mysql at /var/lib/mysql/*.err

Nothing gets logged to /var/lib/mysql/*.err (the latest thing in the file is from my successful attempts via "mysqld_safe") /var/log/messages only gets one line: <timestamp> <hostname> mysql[6471]: Starting service MySQL ..done But mysqld is not running as a result. I am hoping there is a way to increase the verbosity. I'll look at /etc/init.d/mysql in greater detail.

...

B.t.w. If you upgrade to Opensuse 13.2 you will have to upgrade your tables. Watch for instructions in the messages.

Good to know. Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Brian Sammon

14 Nov 14 Nov

15:47

On Thu, 13 Nov 2014 17:37:43 -0500 Brian Sammon wrote:

...

On Thu, 13 Nov 2014 23:24:46 +0100 Florian Gleixner wrote:

...
On 11/13/2014 10:58 PM, Brian Sammon wrote:

...
[mariadb 5.5.33-2.2 on OpenSuse x86_64 13.1, with some factory and som 13.2 packages]

Mixing is not good. But you have mariadb from Opensuse 13.1. ...

...
"systemctl status mysql.service" says: mysql.service - LSB: Start the MySQL database server

The "LSB" means, that you start a systemV script from /etc/init.d/mysq

Okay, this is useful information -- I am new to systemd, and I was not sure if /etc/init.d was the place to look. I can experiment with the file to troubleshoot this.

So, the problem appears to be with the lines: "$MYSELF" status >/dev/null && echo -n "Starting service MySQL " && \ rc_status -v && rc_exit on line 285 and 286. If I comment out those lines, mysql starts when I do "systemctl start mysql.service" If I leave that line in, and add a "echo 'test'" on the next line, mysql does not start, and 'test' does not appear in /var/log/messages (as it does when I put "echo 'test'" before those lines) Either way, "Starting service MySQL ..done" appears in /var/log/messages. My current theory, is that when doing those two lines, the script gets to "rc_exit", but it shouldn't, due to "rc_status -v" generating unexpected results. Any ideas? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Brian Sammon

22:02

Well, it appears the problem was that mariadb 5.5.33-2.2 (from 13.1) and systemd 210-25.5.4 (from 13.2) are not compatible. After I downgraded systemd to 208 (and powercycled my machine, because the systemd downgrade broke "reboot") mariadb started as expected. Annoyingly, there's a bunch of packages in 13.2 that depend (directly or indirectly) on systemd 210 that I'd like to use. Not quite sure where I'll go next with this. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Cristian Rodríguez

15 Nov 15 Nov

04:01

El 14/11/14 a las 19:02, Brian Sammon escribió:

...

Well, it appears the problem was that mariadb 5.5.33-2.2 (from 13.1) and systemd 210-25.5.4 (from 13.2) are not compatible.

After I downgraded systemd to 208 (and powercycled my machine, because the systemd downgrade broke "reboot") mariadb started as expected.

Annoyingly, there's a bunch of packages in 13.2 that depend (directly or indirectly) on systemd 210 that I'd like to use.

Not quite sure where I'll go next with this.

You are not supposed to mix 13.2 packages with 13.1 at all. You upgrade completely and reboot the machine, anything else is unsupported and will very likely not work. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

05:04

On 2014-11-14 23:02, Brian Sammon wrote:

...

Well, it appears the problem was that mariadb 5.5.33-2.2 (from 13.1) and systemd 210-25.5.4 (from 13.2) are not compatible.

After I downgraded systemd to 208 (and powercycled my machine, because the systemd downgrade broke "reboot") mariadb started as expected.

Annoyingly, there's a bunch of packages in 13.2 that depend (directly or indirectly) on systemd 210 that I'd like to use.

Why don't you fully upgrade to 13.2, what's the problem? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

Brian Sammon

06:12

On Sat, 15 Nov 2014 06:04:54 +0100 "Carlos E. R." wrote:

...

Why don't you fully upgrade to 13.2, what's the problem?

Well, the main reason is that upgrading mariaDB from 5.5.33 to 10.0.13 is (or seems like) a big step. Another good question is "Why don't I just stay with 13.1?" The answer to that was that I wanted to run ruby 2.1, which isn't packaged for 13.1. What I'm learning is that there's no supported way to run ruby2.1 and mariaDB 5 on the same openSUSE install. Coming from the Debian world, where mixing version 7.5 with version 7.7 is no big deal, this takes some getting used to. Is there any chance Tumbleweed contains the answer to my problem? -- Brian Sammon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov

06:54

В Sat, 15 Nov 2014 01:12:31 -0500 Brian Sammon пишет:

...

On Sat, 15 Nov 2014 06:04:54 +0100 "Carlos E. R." wrote:

...
Why don't you fully upgrade to 13.2, what's the problem?

Well, the main reason is that upgrading mariaDB from 5.5.33 to 10.0.13 is (or seems like) a big step.

Another good question is "Why don't I just stay with 13.1?"

The answer to that was that I wanted to run ruby 2.1, which isn't packaged for 13.1.

ruby 2.1 for 13.1 is available in devel:languages:ruby repository on OBS. http://software.opensuse.org/download.html?project=devel%3Alanguages%3Aruby&package=ruby2.1

...

What I'm learning is that there's no supported way to run ruby2.1 and mariaDB 5 on the same openSUSE install.

Coming from the Debian world, where mixing version 7.5 with version 7.7 is no big deal, this takes some getting used to.

Is there any chance Tumbleweed contains the answer to my problem?

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

13:59

On 2014-11-15 07:12, Brian Sammon wrote:

...

On Sat, 15 Nov 2014 06:04:54 +0100 "Carlos E. R." <> wrote:

...

The answer to that was that I wanted to run ruby 2.1, which isn't packaged for 13.1.

I see 2.0, 2.1, 1.9... Where did you look? http://software.opensuse.org/package/ruby?search_term=%22ruby%22 Make sure that you tick "Show unstable packages", which really means "show unofficial packages". Notice that only the oss and non-oss repos are "official".

...

Coming from the Debian world, where mixing version 7.5 with version 7.7 is no big deal, this takes some getting used to.

Of course you can, as long as somebody packages it. If not, you can create the package yourself.

...

Is there any chance Tumbleweed contains the answer to my problem?

No. TW should always have the most recent version of everything, as it is a rolling (beta) release. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

3460

Age (days ago)

3462

Last active (days ago)

List overview

Download

9 comments

5 participants

participants (5)

Andrei Borzenkov
Brian Sammon
Carlos E. R.
Cristian Rodríguez
Florian Gleixner