sudo: unable to mkdir /var/log/sudo-io/00/2A: No space left on device

up vote
1
down vote

favorite

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

asked Apr 2 at 13:13

jrjames83

1084

add a commentÂ |Â

up vote
1
down vote

favorite

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

asked Apr 2 at 13:13

jrjames83

1084

add a commentÂ |Â

up vote
1
down vote

favorite

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

asked Apr 2 at 13:13

jrjames83

1084

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

asked Apr 2 at 13:13

jrjames83

1084

asked Apr 2 at 13:13

jrjames83

1084

asked Apr 2 at 13:13

jrjames83

1084

asked Apr 2 at 13:13

jrjames83

1084

add a commentÂ |Â

1 Answer
1

active

oldest

votes

up vote
2
down vote

accepted

You apparently enable 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.

edited Apr 2 at 13:42

answered Apr 2 at 13:28

Rui F Ribeiro

34.7k1269113

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 at 14:11

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',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

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

Name

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
2
down vote

accepted

You apparently enable 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.

edited Apr 2 at 13:42

answered Apr 2 at 13:28

Rui F Ribeiro

34.7k1269113

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 at 14:11

add a commentÂ |Â

up vote
2
down vote

accepted

You apparently enable 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.

edited Apr 2 at 13:42

answered Apr 2 at 13:28

Rui F Ribeiro

34.7k1269113

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 at 14:11

add a commentÂ |Â

up vote
2
down vote

accepted

You apparently enable 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.

edited Apr 2 at 13:42

answered Apr 2 at 13:28

Rui F Ribeiro

34.7k1269113

You apparently enable 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.

edited Apr 2 at 13:42

answered Apr 2 at 13:28

Rui F Ribeiro

34.7k1269113

edited Apr 2 at 13:42

answered Apr 2 at 13:28

Rui F Ribeiro

34.7k1269113

answered Apr 2 at 13:28

Rui F Ribeiro

34.7k1269113

answered Apr 2 at 13:28

Rui F Ribeiro

34.7k1269113

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 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 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 at 14:11

add a commentÂ |Â

draft saved

draft discarded

draft saved

draft discarded

Post as a guest

Name

搜尋此網誌

mjhjmtu