After mariaDB 10.0 to 10.1 upgrade, mysql can no longer write tmpdir
I ordered a new server that came with mariaDB 10.0 installed. I edited /etc/my.cnf to change the tmpdir to /home/mysql_tmp_dir (owned by mysql:mysql). All worked fine.
Did upgrade to mariaDB 10.1.37 and the tmpdir can no longer be written to:
[ERROR] mysqld: Can't create/write to file '/home/mysql_tmp_dir/ibV9SvJP' (Errcode: 13 "Permission denied")
This of course caused all kinds of problems, mainly that innodb engine was unable to load.
Commenting tmpdir out to revert to the default and restarting temporarily resolved the issue. But, I am at a loss as to why this happened and how to resolve it.
I need a larger tmpdir, otherwise it fills up when optimizing large databases, which of course causes mysql to lock up until space is freed.
mariadb
asked Jan 28 at 2:53
vicosvicos
161
add a comment |
I ordered a new server that came with mariaDB 10.0 installed. I edited /etc/my.cnf to change the tmpdir to /home/mysql_tmp_dir (owned by mysql:mysql). All worked fine.
Did upgrade to mariaDB 10.1.37 and the tmpdir can no longer be written to:
[ERROR] mysqld: Can't create/write to file '/home/mysql_tmp_dir/ibV9SvJP' (Errcode: 13 "Permission denied")
This of course caused all kinds of problems, mainly that innodb engine was unable to load.
Commenting tmpdir out to revert to the default and restarting temporarily resolved the issue. But, I am at a loss as to why this happened and how to resolve it.
I need a larger tmpdir, otherwise it fills up when optimizing large databases, which of course causes mysql to lock up until space is freed.
mariadb
asked Jan 28 at 2:53
vicosvicos
161
1
Get your admin to place more temporary space in a proper place in the filesystem. /home is not a proper place for temp files, and many other things will not be able to write here either.
– Michael Hampton♦
Jan 28 at 4:03
Don't useOPTIMIZE TABLE; it is almost of no use.
– Rick James
Jan 30 at 2:04
This probably belongs in dba.stackexchange.com .
– Rick James
Jan 30 at 2:08
add a comment |
I ordered a new server that came with mariaDB 10.0 installed. I edited /etc/my.cnf to change the tmpdir to /home/mysql_tmp_dir (owned by mysql:mysql). All worked fine.
Did upgrade to mariaDB 10.1.37 and the tmpdir can no longer be written to:
[ERROR] mysqld: Can't create/write to file '/home/mysql_tmp_dir/ibV9SvJP' (Errcode: 13 "Permission denied")
This of course caused all kinds of problems, mainly that innodb engine was unable to load.
Commenting tmpdir out to revert to the default and restarting temporarily resolved the issue. But, I am at a loss as to why this happened and how to resolve it.
I need a larger tmpdir, otherwise it fills up when optimizing large databases, which of course causes mysql to lock up until space is freed.
mariadb
asked Jan 28 at 2:53
vicosvicos
161
I ordered a new server that came with mariaDB 10.0 installed. I edited /etc/my.cnf to change the tmpdir to /home/mysql_tmp_dir (owned by mysql:mysql). All worked fine.
Did upgrade to mariaDB 10.1.37 and the tmpdir can no longer be written to:
[ERROR] mysqld: Can't create/write to file '/home/mysql_tmp_dir/ibV9SvJP' (Errcode: 13 "Permission denied")
This of course caused all kinds of problems, mainly that innodb engine was unable to load.
Commenting tmpdir out to revert to the default and restarting temporarily resolved the issue. But, I am at a loss as to why this happened and how to resolve it.
I need a larger tmpdir, otherwise it fills up when optimizing large databases, which of course causes mysql to lock up until space is freed.
mariadb
mariadb
asked Jan 28 at 2:53
vicosvicos
161
asked Jan 28 at 2:53
vicosvicos
161
asked Jan 28 at 2:53
vicosvicos
161
asked Jan 28 at 2:53
vicosvicos
161
asked Jan 28 at 2:53
vicosvicos
161
161
1
Get your admin to place more temporary space in a proper place in the filesystem. /home is not a proper place for temp files, and many other things will not be able to write here either.
– Michael Hampton♦
Jan 28 at 4:03
Don't useOPTIMIZE TABLE; it is almost of no use.
– Rick James
Jan 30 at 2:04
This probably belongs in dba.stackexchange.com .
– Rick James
Jan 30 at 2:08
add a comment |
1
Get your admin to place more temporary space in a proper place in the filesystem. /home is not a proper place for temp files, and many other things will not be able to write here either.
– Michael Hampton♦
Jan 28 at 4:03
Don't useOPTIMIZE TABLE; it is almost of no use.
– Rick James
Jan 30 at 2:04
This probably belongs in dba.stackexchange.com .
– Rick James
Jan 30 at 2:08
1
1
Get your admin to place more temporary space in a proper place in the filesystem. /home is not a proper place for temp files, and many other things will not be able to write here either.
– Michael Hampton♦
Jan 28 at 4:03
Get your admin to place more temporary space in a proper place in the filesystem. /home is not a proper place for temp files, and many other things will not be able to write here either.
– Michael Hampton♦
Jan 28 at 4:03
Don't use
OPTIMIZE TABLE; it is almost of no use.– Rick James
Jan 30 at 2:04
Don't use
OPTIMIZE TABLE; it is almost of no use.– Rick James
Jan 30 at 2:04
This probably belongs in dba.stackexchange.com .
– Rick James
Jan 30 at 2:08
This probably belongs in dba.stackexchange.com .
– Rick James
Jan 30 at 2:08
add a comment |
1 Answer
1
active
oldest
votes
In earlier 10.1 release MariaDB added some systemd hardening, one of those was the setting to protect the homedir,
Try this
awk '/Protect/' /usr/lib/systemd/system/mariadb.service
If you see ProtectHome=true, you can either move the tmpdir somewhere else, or add
// File: /etc/systemd/system/mariadb.service.d/protecthome.conf
[Service]
ProtectHome=false
Related links
- https://jira.mariadb.org/browse/MDEV-10298
- https://jira.mariadb.org/browse/MDEV-10399
answered Jan 28 at 3:02
Ryan GibbonsRyan Gibbons
958920
Thanks for the info. I will investigate further and try this solution.
– vicos
Jan 29 at 4:17
I tried the ProtectHome=false and still was not able to write to home.
– vicos
Jan 30 at 4:20
Never mind. All is well! I didn't do 'systemctl daemon-reload' before restarting mysql.
– vicos
Jan 30 at 15:04
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
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%2fserverfault.com%2fquestions%2f951053%2fafter-mariadb-10-0-to-10-1-upgrade-mysql-can-no-longer-write-tmpdir%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In earlier 10.1 release MariaDB added some systemd hardening, one of those was the setting to protect the homedir,
Try this
awk '/Protect/' /usr/lib/systemd/system/mariadb.service
If you see ProtectHome=true, you can either move the tmpdir somewhere else, or add
// File: /etc/systemd/system/mariadb.service.d/protecthome.conf
[Service]
ProtectHome=false
Related links
- https://jira.mariadb.org/browse/MDEV-10298
- https://jira.mariadb.org/browse/MDEV-10399
answered Jan 28 at 3:02
Ryan GibbonsRyan Gibbons
958920
Thanks for the info. I will investigate further and try this solution.
– vicos
Jan 29 at 4:17
I tried the ProtectHome=false and still was not able to write to home.
– vicos
Jan 30 at 4:20
Never mind. All is well! I didn't do 'systemctl daemon-reload' before restarting mysql.
– vicos
Jan 30 at 15:04
add a comment |
In earlier 10.1 release MariaDB added some systemd hardening, one of those was the setting to protect the homedir,
Try this
awk '/Protect/' /usr/lib/systemd/system/mariadb.service
If you see ProtectHome=true, you can either move the tmpdir somewhere else, or add
// File: /etc/systemd/system/mariadb.service.d/protecthome.conf
[Service]
ProtectHome=false
Related links
- https://jira.mariadb.org/browse/MDEV-10298
- https://jira.mariadb.org/browse/MDEV-10399
answered Jan 28 at 3:02
Ryan GibbonsRyan Gibbons
958920
Thanks for the info. I will investigate further and try this solution.
– vicos
Jan 29 at 4:17
I tried the ProtectHome=false and still was not able to write to home.
– vicos
Jan 30 at 4:20
Never mind. All is well! I didn't do 'systemctl daemon-reload' before restarting mysql.
– vicos
Jan 30 at 15:04
add a comment |
In earlier 10.1 release MariaDB added some systemd hardening, one of those was the setting to protect the homedir,
Try this
awk '/Protect/' /usr/lib/systemd/system/mariadb.service
If you see ProtectHome=true, you can either move the tmpdir somewhere else, or add
// File: /etc/systemd/system/mariadb.service.d/protecthome.conf
[Service]
ProtectHome=false
Related links
- https://jira.mariadb.org/browse/MDEV-10298
- https://jira.mariadb.org/browse/MDEV-10399
answered Jan 28 at 3:02
Ryan GibbonsRyan Gibbons
958920
In earlier 10.1 release MariaDB added some systemd hardening, one of those was the setting to protect the homedir,
Try this
awk '/Protect/' /usr/lib/systemd/system/mariadb.service
If you see ProtectHome=true, you can either move the tmpdir somewhere else, or add
// File: /etc/systemd/system/mariadb.service.d/protecthome.conf
[Service]
ProtectHome=false
Related links
- https://jira.mariadb.org/browse/MDEV-10298
- https://jira.mariadb.org/browse/MDEV-10399
answered Jan 28 at 3:02
Ryan GibbonsRyan Gibbons
958920
answered Jan 28 at 3:02
Ryan GibbonsRyan Gibbons
958920
answered Jan 28 at 3:02
Ryan GibbonsRyan Gibbons
958920
answered Jan 28 at 3:02
Ryan GibbonsRyan Gibbons
958920
958920
Thanks for the info. I will investigate further and try this solution.
– vicos
Jan 29 at 4:17
I tried the ProtectHome=false and still was not able to write to home.
– vicos
Jan 30 at 4:20
Never mind. All is well! I didn't do 'systemctl daemon-reload' before restarting mysql.
– vicos
Jan 30 at 15:04
add a comment |
Thanks for the info. I will investigate further and try this solution.
– vicos
Jan 29 at 4:17
I tried the ProtectHome=false and still was not able to write to home.
– vicos
Jan 30 at 4:20
Never mind. All is well! I didn't do 'systemctl daemon-reload' before restarting mysql.
– vicos
Jan 30 at 15:04
Thanks for the info. I will investigate further and try this solution.
– vicos
Jan 29 at 4:17
Thanks for the info. I will investigate further and try this solution.
– vicos
Jan 29 at 4:17
I tried the ProtectHome=false and still was not able to write to home.
– vicos
Jan 30 at 4:20
I tried the ProtectHome=false and still was not able to write to home.
– vicos
Jan 30 at 4:20
Never mind. All is well! I didn't do 'systemctl daemon-reload' before restarting mysql.
– vicos
Jan 30 at 15:04
Never mind. All is well! I didn't do 'systemctl daemon-reload' before restarting mysql.
– vicos
Jan 30 at 15:04
add a comment |
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f951053%2fafter-mariadb-10-0-to-10-1-upgrade-mysql-can-no-longer-write-tmpdir%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
1
Get your admin to place more temporary space in a proper place in the filesystem. /home is not a proper place for temp files, and many other things will not be able to write here either.
– Michael Hampton♦
Jan 28 at 4:03
Don't use
OPTIMIZE TABLE; it is almost of no use.– Rick James
Jan 30 at 2:04
This probably belongs in dba.stackexchange.com .
– Rick James
Jan 30 at 2:08