sudo: unable to mkdir /var/log/sudo-io/00/2A: No space left on device
A script began throwing errors related to not being able to init an I/O plugin sudoers_io: (amazon linux).
I can't get into delete some logs since each time I use the sudo command, it fails to log that I used the command (I am guessing here). Any ideas on how to free up space or delete/rotate the logs?
Output below:
[ec2-user@ip-xx-xx-xx-xx log]$ sudo bash
sudo: unable to mkdir /var/log/sudo-io/00/2A: No space left on device
sudo: error initializing I/O plugin sudoers_io
[ec2-user@ip-xx-xx-xx-xx log]$ du -s * | sort -nr | head
du: cannot read directory ‘audit’: Permission denied
du: cannot read directory ‘sudo-io’: Permission denied
16092 secure
2188 secure-20180401
640 messages-20180325
640 messages-20180318
636 messages-20180401
636 messages-20180311
196 cloud-init.log
160 wtmp
132 messages
104 dracut.log
linux sudo amazon-ec2 amazon-linux
asked Apr 2 '18 at 13:13
jrjames83jrjames83
1085
add a comment |
A script began throwing errors related to not being able to init an I/O plugin sudoers_io: (amazon linux).
I can't get into delete some logs since each time I use the sudo command, it fails to log that I used the command (I am guessing here). Any ideas on how to free up space or delete/rotate the logs?
Output below:
[ec2-user@ip-xx-xx-xx-xx log]$ sudo bash
sudo: unable to mkdir /var/log/sudo-io/00/2A: No space left on device
sudo: error initializing I/O plugin sudoers_io
[ec2-user@ip-xx-xx-xx-xx log]$ du -s * | sort -nr | head
du: cannot read directory ‘audit’: Permission denied
du: cannot read directory ‘sudo-io’: Permission denied
16092 secure
2188 secure-20180401
640 messages-20180325
640 messages-20180318
636 messages-20180401
636 messages-20180311
196 cloud-init.log
160 wtmp
132 messages
104 dracut.log
linux sudo amazon-ec2 amazon-linux
asked Apr 2 '18 at 13:13
jrjames83jrjames83
1085
add a comment |
A script began throwing errors related to not being able to init an I/O plugin sudoers_io: (amazon linux).
I can't get into delete some logs since each time I use the sudo command, it fails to log that I used the command (I am guessing here). Any ideas on how to free up space or delete/rotate the logs?
Output below:
[ec2-user@ip-xx-xx-xx-xx log]$ sudo bash
sudo: unable to mkdir /var/log/sudo-io/00/2A: No space left on device
sudo: error initializing I/O plugin sudoers_io
[ec2-user@ip-xx-xx-xx-xx log]$ du -s * | sort -nr | head
du: cannot read directory ‘audit’: Permission denied
du: cannot read directory ‘sudo-io’: Permission denied
16092 secure
2188 secure-20180401
640 messages-20180325
640 messages-20180318
636 messages-20180401
636 messages-20180311
196 cloud-init.log
160 wtmp
132 messages
104 dracut.log
linux sudo amazon-ec2 amazon-linux
asked Apr 2 '18 at 13:13
jrjames83jrjames83
1085
A script began throwing errors related to not being able to init an I/O plugin sudoers_io: (amazon linux).
I can't get into delete some logs since each time I use the sudo command, it fails to log that I used the command (I am guessing here). Any ideas on how to free up space or delete/rotate the logs?
Output below:
[ec2-user@ip-xx-xx-xx-xx log]$ sudo bash
sudo: unable to mkdir /var/log/sudo-io/00/2A: No space left on device
sudo: error initializing I/O plugin sudoers_io
[ec2-user@ip-xx-xx-xx-xx log]$ du -s * | sort -nr | head
du: cannot read directory ‘audit’: Permission denied
du: cannot read directory ‘sudo-io’: Permission denied
16092 secure
2188 secure-20180401
640 messages-20180325
640 messages-20180318
636 messages-20180401
636 messages-20180311
196 cloud-init.log
160 wtmp
132 messages
104 dracut.log
linux sudo amazon-ec2 amazon-linux
linux sudo amazon-ec2 amazon-linux
asked Apr 2 '18 at 13:13
jrjames83jrjames83
1085
asked Apr 2 '18 at 13:13
jrjames83jrjames83
1085
asked Apr 2 '18 at 13:13
jrjames83jrjames83
1085
asked Apr 2 '18 at 13:13
jrjames83jrjames83
1085
asked Apr 2 '18 at 13:13
jrjames83jrjames83
1085
1085
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
You apparently have enabled full output logging in sudo(ers).
The easiest way to free space, probably deleting the sudo logs, is either logging as root, or using su, if your configurations allow it.
Depending on how much /var/log is full, those procedures might or might not be successful. On the worst case, booting in single mode or from a live system will allow you to clean up things.
Unless you have very specific needs to log so much of sudo operations, I would edit /etc/sudoers to change the logging setup. Having such a verbose setup will exhaust quickly again the available space.
answered Apr 2 '18 at 13:28
Rui F RibeiroRui F Ribeiro
40k1479135
1
Thanks. I had to find sacrifice lots of cached anaconda packages, but after deleting I was able to sudo bash my way back to clearing these sudo-io log files.
– jrjames83
Apr 2 '18 at 14:11
add a comment |
The most likely cause of this problem in case you have free space in the disk (did you check with df -h?) is a problem with inodes. Just run df -i to check inodes usage, for example check var partition here...
[root@test-kompjuteras ~]# df -hi
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/mapper/VolGroup-lv_root 313K 9.5K 304K 4% /
tmpfs 984K 1 984K 1% /dev/shm
/dev/sda1 126K 44 125K 1% /boot
/dev/mapper/VolGroup-lv_var 250K 250K 0 100% /var
If you have 100% somewhere - you will need to delete some files or to move them on other partition or other storage.
edited Jan 30 at 6:42
RalfFriedl
5,4103925
answered Jan 30 at 5:50
KompjuterasKompjuteras
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f435049%2fsudo-unable-to-mkdir-var-log-sudo-io-00-2a-no-space-left-on-device%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You apparently have enabled full output logging in sudo(ers).
The easiest way to free space, probably deleting the sudo logs, is either logging as root, or using su, if your configurations allow it.
Depending on how much /var/log is full, those procedures might or might not be successful. On the worst case, booting in single mode or from a live system will allow you to clean up things.
Unless you have very specific needs to log so much of sudo operations, I would edit /etc/sudoers to change the logging setup. Having such a verbose setup will exhaust quickly again the available space.
answered Apr 2 '18 at 13:28
Rui F RibeiroRui F Ribeiro
40k1479135
1
Thanks. I had to find sacrifice lots of cached anaconda packages, but after deleting I was able to sudo bash my way back to clearing these sudo-io log files.
– jrjames83
Apr 2 '18 at 14:11
add a comment |
You apparently have enabled full output logging in sudo(ers).
The easiest way to free space, probably deleting the sudo logs, is either logging as root, or using su, if your configurations allow it.
Depending on how much /var/log is full, those procedures might or might not be successful. On the worst case, booting in single mode or from a live system will allow you to clean up things.
Unless you have very specific needs to log so much of sudo operations, I would edit /etc/sudoers to change the logging setup. Having such a verbose setup will exhaust quickly again the available space.
answered Apr 2 '18 at 13:28
Rui F RibeiroRui F Ribeiro
40k1479135
1
Thanks. I had to find sacrifice lots of cached anaconda packages, but after deleting I was able to sudo bash my way back to clearing these sudo-io log files.
– jrjames83
Apr 2 '18 at 14:11
add a comment |
You apparently have enabled full output logging in sudo(ers).
The easiest way to free space, probably deleting the sudo logs, is either logging as root, or using su, if your configurations allow it.
Depending on how much /var/log is full, those procedures might or might not be successful. On the worst case, booting in single mode or from a live system will allow you to clean up things.
Unless you have very specific needs to log so much of sudo operations, I would edit /etc/sudoers to change the logging setup. Having such a verbose setup will exhaust quickly again the available space.
answered Apr 2 '18 at 13:28
Rui F RibeiroRui F Ribeiro
40k1479135
You apparently have enabled full output logging in sudo(ers).
The easiest way to free space, probably deleting the sudo logs, is either logging as root, or using su, if your configurations allow it.
Depending on how much /var/log is full, those procedures might or might not be successful. On the worst case, booting in single mode or from a live system will allow you to clean up things.
Unless you have very specific needs to log so much of sudo operations, I would edit /etc/sudoers to change the logging setup. Having such a verbose setup will exhaust quickly again the available space.
answered Apr 2 '18 at 13:28
Rui F RibeiroRui F Ribeiro
40k1479135
edited Jan 30 at 16:54
answered Apr 2 '18 at 13:28
Rui F RibeiroRui F Ribeiro
40k1479135
answered Apr 2 '18 at 13:28
Rui F RibeiroRui F Ribeiro
40k1479135
answered Apr 2 '18 at 13:28
Rui F RibeiroRui F Ribeiro
40k1479135
40k1479135
1
Thanks. I had to find sacrifice lots of cached anaconda packages, but after deleting I was able to sudo bash my way back to clearing these sudo-io log files.
– jrjames83
Apr 2 '18 at 14:11
add a comment |
1
Thanks. I had to find sacrifice lots of cached anaconda packages, but after deleting I was able to sudo bash my way back to clearing these sudo-io log files.
– jrjames83
Apr 2 '18 at 14:11
1
1
Thanks. I had to find sacrifice lots of cached anaconda packages, but after deleting I was able to sudo bash my way back to clearing these sudo-io log files.
– jrjames83
Apr 2 '18 at 14:11
Thanks. I had to find sacrifice lots of cached anaconda packages, but after deleting I was able to sudo bash my way back to clearing these sudo-io log files.
– jrjames83
Apr 2 '18 at 14:11
add a comment |
The most likely cause of this problem in case you have free space in the disk (did you check with df -h?) is a problem with inodes. Just run df -i to check inodes usage, for example check var partition here...
[root@test-kompjuteras ~]# df -hi
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/mapper/VolGroup-lv_root 313K 9.5K 304K 4% /
tmpfs 984K 1 984K 1% /dev/shm
/dev/sda1 126K 44 125K 1% /boot
/dev/mapper/VolGroup-lv_var 250K 250K 0 100% /var
If you have 100% somewhere - you will need to delete some files or to move them on other partition or other storage.
edited Jan 30 at 6:42
RalfFriedl
5,4103925
answered Jan 30 at 5:50
KompjuterasKompjuteras
1
add a comment |
The most likely cause of this problem in case you have free space in the disk (did you check with df -h?) is a problem with inodes. Just run df -i to check inodes usage, for example check var partition here...
[root@test-kompjuteras ~]# df -hi
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/mapper/VolGroup-lv_root 313K 9.5K 304K 4% /
tmpfs 984K 1 984K 1% /dev/shm
/dev/sda1 126K 44 125K 1% /boot
/dev/mapper/VolGroup-lv_var 250K 250K 0 100% /var
If you have 100% somewhere - you will need to delete some files or to move them on other partition or other storage.
edited Jan 30 at 6:42
RalfFriedl
5,4103925
answered Jan 30 at 5:50
KompjuterasKompjuteras
1
add a comment |
The most likely cause of this problem in case you have free space in the disk (did you check with df -h?) is a problem with inodes. Just run df -i to check inodes usage, for example check var partition here...
[root@test-kompjuteras ~]# df -hi
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/mapper/VolGroup-lv_root 313K 9.5K 304K 4% /
tmpfs 984K 1 984K 1% /dev/shm
/dev/sda1 126K 44 125K 1% /boot
/dev/mapper/VolGroup-lv_var 250K 250K 0 100% /var
If you have 100% somewhere - you will need to delete some files or to move them on other partition or other storage.
edited Jan 30 at 6:42
RalfFriedl
5,4103925
answered Jan 30 at 5:50
KompjuterasKompjuteras
1
The most likely cause of this problem in case you have free space in the disk (did you check with df -h?) is a problem with inodes. Just run df -i to check inodes usage, for example check var partition here...
[root@test-kompjuteras ~]# df -hi
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/mapper/VolGroup-lv_root 313K 9.5K 304K 4% /
tmpfs 984K 1 984K 1% /dev/shm
/dev/sda1 126K 44 125K 1% /boot
/dev/mapper/VolGroup-lv_var 250K 250K 0 100% /var
If you have 100% somewhere - you will need to delete some files or to move them on other partition or other storage.
edited Jan 30 at 6:42
RalfFriedl
5,4103925
answered Jan 30 at 5:50
KompjuterasKompjuteras
1
edited Jan 30 at 6:42
RalfFriedl
5,4103925
edited Jan 30 at 6:42
RalfFriedl
5,4103925
edited Jan 30 at 6:42
RalfFriedl
5,4103925
5,4103925
answered Jan 30 at 5:50
KompjuterasKompjuteras
1
answered Jan 30 at 5:50
KompjuterasKompjuteras
1
answered Jan 30 at 5:50
KompjuterasKompjuteras
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f435049%2fsudo-unable-to-mkdir-var-log-sudo-io-00-2a-no-space-left-on-device%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
