sodcalculator

10 Tech How-To

Fixing sudo error in Ubuntu? Step-by-Step

Guide 10-20667 · Updated · Step by step

If you see a sudo error in Ubuntu, the fix usually involves repairing file permissions, checking the sudoers file, or reinstalling sudo itself. This guide walks you through the most common causes and solutions, from a simple typo to a broken system configuration.

What the sudo Command Does

sudo (short for “superuser do”) lets a permitted user run commands with the security privileges of another user, typically root. It is the standard way to administer an Ubuntu system without logging in as root. When you type sudo apt update, the system checks whether your username is in the sudoers file (/etc/sudoers) or in a group like sudo that is listed there. If everything is correct, you are asked for your password and the command runs with elevated privileges.

Because sudo controls access to the whole system, even a small error can lock you out of administrative tasks. The good news is that most sudo errors have straightforward fixes.

Common sudo Error Messages and What They Mean

Ubuntu users usually encounter one of these errors:

  • “user is not in the sudoers file” – Your account is not in the sudo group, or the sudoers file does not list you.
  • “sudo: unable to resolve host” – A hostname resolution problem, often after changing your computer name.
  • “sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set” – File permissions on the sudo binary are wrong.
  • “sudo: no valid sudoers sources found” – The sudoers file is corrupted or unreadable.
  • “command not found” – The command you typed does not exist, or the PATH environment variable is missing entries.

Each error points to a different underlying problem, so the fix is different.

How to Fix the Most Common sudo Errors

1. User Not in the sudoers File

If you just installed Ubuntu and created a user account, that account may not be in the sudo group. To fix this, you need to boot into recovery mode or use another user with sudo privileges. From a terminal, run:

  1. Log in as a user who has sudo rights (or use the root shell from recovery mode).
  2. Add your user to the sudo group: sudo usermod -aG sudo yourusername
  3. Log out and back in, then test with sudo whoami.

If you have no other sudo user, reboot, hold Shift to enter the GRUB menu, choose “Advanced options” and then “Recovery mode”. Select “root” to get a root shell, then run the usermod command. The root shell in recovery mode does not require a password.

2. Unable to Resolve Host

This error appears as sudo: unable to resolve host yourhostname. It happens when the hostname in /etc/hostname does not match an entry in /etc/hosts. To fix it:

  1. Check your hostname: hostname
  2. Edit /etc/hosts with sudo: sudo nano /etc/hosts
  3. Add a line like 127.0.1.1 yourhostname (replace with your actual hostname).
  4. Save and exit, then run sudo apt update to test.

3. Sudo Binary Has Wrong Permissions

The error sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set means the file permissions got changed, often accidentally with chmod. To fix, boot into recovery mode, get a root shell, and run:

chown root:root /usr/bin/sudo
chmod 4755 /usr/bin/sudo

The 4755 sets the setuid bit, which allows sudo to run with root privileges. After that, reboot and test.

4. Corrupted sudoers File

If you see sudo: no valid sudoers sources found, the /etc/sudoers file is broken. This can happen after a bad edit. To fix it, you need to edit the file as root. In recovery mode, run:

visudo -f /etc/sudoers

If the file is completely empty, you can recreate a minimal version:

Defaults env_reset
root ALL=(ALL:ALL) ALL
%sudo ALL=(ALL:ALL) ALL

Save and exit. Then reboot and try sudo again.

How to Edit the sudoers File Safely

The sudoers file controls who can use sudo and what they can do. Editing it incorrectly can lock you out of admin access. Always use visudo to edit it, because it checks the syntax before saving. If you make a syntax error, visudo will refuse to save and warn you. To edit, run:

sudo visudo

This opens the file in the default editor (usually nano). Add a line like:

yourusername ALL=(ALL:ALL) ALL

This gives your user full sudo rights. To allow passwordless sudo for a specific command, use NOPASSWD: before the command list, but be careful – that can be a security risk.

When sudo Is Completely Broken

If sudo is not working at all, you can still get root access by booting into recovery mode. Here is how:

  1. Reboot your computer.
  2. Press and hold the Shift key (or Esc on some systems) to open the GRUB menu.
  3. Select “Advanced options for Ubuntu”.
  4. Choose a kernel with “(recovery mode)”.
  5. In the recovery menu, select “root” to get a root shell.
  6. From there, run the necessary commands to fix your issue.

In recovery mode, the filesystem is mounted read-only. To make changes, remount it with write access:

mount -o remount,rw /

Then you can run the fixes described above.

Preventing Future sudo Errors

Most sudo errors are caused by accidental changes to system files. To avoid them:

  • Never use chmod or chown on system binaries unless you know exactly what you are doing.
  • Always use visudo to edit the sudoers file.
  • Keep your system updated with sudo apt update && sudo apt upgrade.
  • If you change your hostname, update /etc/hosts at the same time.
  • Back up important configuration files before editing them.

Frequently Asked Questions

Why does sudo say “command not found” even though I typed it correctly?

This usually means the command is not installed, or the PATH variable does not include its directory. For example, ifconfig is not installed by default on newer Ubuntu; use ip addr instead. If a command is in /sbin or /usr/sbin, your user PATH may not include it. Use the full path like /sbin/command or install the package that provides it.

Can I fix sudo errors without rebooting into recovery mode?

Yes, if you have another user with sudo access. Log in as that user and run the fixes from a terminal. If you are the only user and sudo is broken, recovery mode is the standard way to regain root access.

What does “setuid bit” mean and why does sudo need it?

The setuid bit (represented by the ‘s’ in the permissions, e.g., -rwsr-xr-x) allows a program to run with the permissions of the file owner, not the user who runs it. Sudo needs this because it must run as root to perform privileged operations. If the bit is missing, sudo will not work.

Is it safe to use sudo su instead of fixing the error?

sudo su gives you a root shell, but it does not fix the underlying problem. If sudo is broken, sudo su will fail too. Once you fix the error, you can use sudo su if you need a root shell, but it is generally safer to use sudo for individual commands.

What if I accidentally deleted the sudoers file?

If /etc/sudoers is missing, sudo will not work. Boot into recovery mode, remount the filesystem as read-write, and recreate the file with the minimal content shown earlier. Then run chmod 440 /etc/sudoers and chown root:root /etc/sudoers to set correct permissions.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →