MySQL broken after upgrade to 18.04
MySQL won't start after I upgraded to 18.04 from 16.04 (or maybe 14. I can't quite remember).
I think I know why - systemctl does this:
Process: 3570 ExecStart=/etc/init.d/mysql start (code=exited, status=0/SUCCESS)
which looks successful. However, what actually happened is this, the third line executed in /etc/init.d/mysql is this:
test -x /usr/bin/mysqld_safe || exit 0
which exits because mysqld_safe does not exist.
MySQL say this:
"For some Linux platforms, MySQL installation from RPM or Debian packages includes systemd support for managing MySQL server startup and shutdown. On these platforms, mysqld_safe is not installed because it is unnecessary. "
I think the previous Ubuntu version was 16.04, and the original install was a 12.04.
What should be happening here? Presumably the upgrade left the original /etc/init.d/mysql in place?
My initial guess appears to be incorrect. I've done a mysql-server install on a clean live usb and mysqld_safe is there!
dpkg says this on the upgraded system, which can't be good:
rc mysql-server-5.5 5.5.57-0ubuntu0.14.04.1 i386 MySQL database server binaries and system database setup
rc mysql-server-5.7 5.7.24-0ubuntu0.18.04.1 i386 MySQL database server binaries and system database setup
18.04 mysql
asked Dec 11 at 23:12
Digger
62
add a comment |
MySQL won't start after I upgraded to 18.04 from 16.04 (or maybe 14. I can't quite remember).
I think I know why - systemctl does this:
Process: 3570 ExecStart=/etc/init.d/mysql start (code=exited, status=0/SUCCESS)
which looks successful. However, what actually happened is this, the third line executed in /etc/init.d/mysql is this:
test -x /usr/bin/mysqld_safe || exit 0
which exits because mysqld_safe does not exist.
MySQL say this:
"For some Linux platforms, MySQL installation from RPM or Debian packages includes systemd support for managing MySQL server startup and shutdown. On these platforms, mysqld_safe is not installed because it is unnecessary. "
I think the previous Ubuntu version was 16.04, and the original install was a 12.04.
What should be happening here? Presumably the upgrade left the original /etc/init.d/mysql in place?
My initial guess appears to be incorrect. I've done a mysql-server install on a clean live usb and mysqld_safe is there!
dpkg says this on the upgraded system, which can't be good:
rc mysql-server-5.5 5.5.57-0ubuntu0.14.04.1 i386 MySQL database server binaries and system database setup
rc mysql-server-5.7 5.7.24-0ubuntu0.18.04.1 i386 MySQL database server binaries and system database setup
18.04 mysql
asked Dec 11 at 23:12
Digger
62
The above must be included in question with as much as details you can provide. Thanks :-)
– Kulfy
Dec 12 at 12:01
add a comment |
MySQL won't start after I upgraded to 18.04 from 16.04 (or maybe 14. I can't quite remember).
I think I know why - systemctl does this:
Process: 3570 ExecStart=/etc/init.d/mysql start (code=exited, status=0/SUCCESS)
which looks successful. However, what actually happened is this, the third line executed in /etc/init.d/mysql is this:
test -x /usr/bin/mysqld_safe || exit 0
which exits because mysqld_safe does not exist.
MySQL say this:
"For some Linux platforms, MySQL installation from RPM or Debian packages includes systemd support for managing MySQL server startup and shutdown. On these platforms, mysqld_safe is not installed because it is unnecessary. "
I think the previous Ubuntu version was 16.04, and the original install was a 12.04.
What should be happening here? Presumably the upgrade left the original /etc/init.d/mysql in place?
My initial guess appears to be incorrect. I've done a mysql-server install on a clean live usb and mysqld_safe is there!
dpkg says this on the upgraded system, which can't be good:
rc mysql-server-5.5 5.5.57-0ubuntu0.14.04.1 i386 MySQL database server binaries and system database setup
rc mysql-server-5.7 5.7.24-0ubuntu0.18.04.1 i386 MySQL database server binaries and system database setup
18.04 mysql
asked Dec 11 at 23:12
Digger
62
MySQL won't start after I upgraded to 18.04 from 16.04 (or maybe 14. I can't quite remember).
I think I know why - systemctl does this:
Process: 3570 ExecStart=/etc/init.d/mysql start (code=exited, status=0/SUCCESS)
which looks successful. However, what actually happened is this, the third line executed in /etc/init.d/mysql is this:
test -x /usr/bin/mysqld_safe || exit 0
which exits because mysqld_safe does not exist.
MySQL say this:
"For some Linux platforms, MySQL installation from RPM or Debian packages includes systemd support for managing MySQL server startup and shutdown. On these platforms, mysqld_safe is not installed because it is unnecessary. "
I think the previous Ubuntu version was 16.04, and the original install was a 12.04.
What should be happening here? Presumably the upgrade left the original /etc/init.d/mysql in place?
My initial guess appears to be incorrect. I've done a mysql-server install on a clean live usb and mysqld_safe is there!
dpkg says this on the upgraded system, which can't be good:
rc mysql-server-5.5 5.5.57-0ubuntu0.14.04.1 i386 MySQL database server binaries and system database setup
rc mysql-server-5.7 5.7.24-0ubuntu0.18.04.1 i386 MySQL database server binaries and system database setup
18.04 mysql
18.04 mysql
asked Dec 11 at 23:12
Digger
62
asked Dec 11 at 23:12
Digger
62
edited Dec 12 at 15:23
asked Dec 11 at 23:12
Digger
62
asked Dec 11 at 23:12
Digger
62
asked Dec 11 at 23:12
Digger
62
62
The above must be included in question with as much as details you can provide. Thanks :-)
– Kulfy
Dec 12 at 12:01
add a comment |
The above must be included in question with as much as details you can provide. Thanks :-)
– Kulfy
Dec 12 at 12:01
The above must be included in question with as much as details you can provide. Thanks :-)
– Kulfy
Dec 12 at 12:01
The above must be included in question with as much as details you can provide. Thanks :-)
– Kulfy
Dec 12 at 12:01
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1100168%2fmysql-broken-after-upgrade-to-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1100168%2fmysql-broken-after-upgrade-to-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The above must be included in question with as much as details you can provide. Thanks :-)
– Kulfy
Dec 12 at 12:01