[sudo-users] What should I check?
leroy at datavoiceint.com
Mon Dec 21 15:27:29 MST 2015
I'll check that the next time it happens, all storage is local and the hardware is new but I do need to eliminate that possibility. They are VMs.
----- Original Message -----
From: "Shawn McMahon" <syberghost at gmail.com>
To: "Leroy Tennison" <leroy at datavoiceint.com>
Cc: sudo-users at sudo.ws
Sent: Monday, December 21, 2015 2:33:55 PM
Subject: Re: [sudo-users] What should I check?
On Mon, Dec 21, 2015 at 1:18 PM, Leroy Tennison < leroy at datavoiceint.com > wrote:
We have had this happen on CentOS7 and Ubunto 14.04 LTS recently. Login then do sudo -i, enter a correct password at the password prompt only to get:
sudo: unable to open /var/log/sudo-io/seq: Read-only file system
We haven't tampered with 'seq' (per direction in reponse to a previous question). A reboot solves the problem.
Sounds like you're skipping the obvious; /var is becoming read-only.
If those are VMs, make sure the backing store is on a reliable source. A common cause of this is having the stores on NFS over a flaky network.
Not a sudo problem, a system problem.
Confidentiality Notice | This email and any included attachments may be privileged, confidential and/or otherwise protected from disclosure. Access to this email by anyone other than the intended recipient is unauthorized. If you believe you have received this email in error, please contact the sender immediately and delete all copies. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
More information about the sudo-users