/usr/bin/sudo must be owned by uid 0 and have the setuid bit set version .ubantu14.04 LTS

Question

when I set the EACCESS for npm and I was ran the chown command in my terminal for change owner permission but now i stuck in this sudo :" /usr/bin/sudo must be owned by uid 0 and have the setuid bit set" my version is : ubuntu14.04 LTS please help me guyz :)

Did you do what it says to do at this link: https://docs.npmjs.com/getting-started/fixing-npm-permissions That is the most brain-dead method of forcing an install to work I have ever seen. `chown -R myuser /usr/local`? Even for `/usr/local`, that is epically stupid. And you've apparently found out why. — Andrew Henle, May 03 '16 at 12:14
/usr/bin/sudo mv /usr/local/bin/sudo{,2} hash -r Refer this https://unix.stackexchange.com/questions/419122/sudo-must-be-owned-by-uid-0-and-have-the-setuid-bit-set?newreg=b2490740fb214ce79c316ad76f859e0a — Sachin Adkar, May 27 '19 at 19:45
finally, after finding too much i am really thanked https://askubuntu.com/users/10962/user10962 at this link : https://askubuntu.com/a/471503/528411 — Chirag thaker, May 03 '16 at 12:44

score 22 · Answer 1 · answered Sep 03 '19 at 08:00

22

First restart your pc, and press the ESC key while Ubuntu is booting.

This will bring you up the boot menu.

Select Advanced Options.

Select your OS version in (recovery mode), and press Enter Key.

It will bring you up another screen. Now select “Drop to root shell prompt” and press Enter.

It will load a command line at the bottom of the screen.

Now run each of the following commands.

mount -o remount,rw /
mount --all
chown root:root /usr/bin/sudo
chmod 4755 /usr/bin/sudo
shutdown -r now

answered Sep 03 '19 at 08:00

Abhi

305
5
23

How to do the same on EC2 AWS? – Himanshu Bansal Nov 19 '19 at 07:12
1

WOrked like a charm... THANK YOU1 – CodeConnoisseur Jan 09 '20 at 20:27
Worked perfectly on Mint 19.3 – Abk Feb 08 '20 at 10:22
1

This worked perfectly on ubuntu 20.04 i had ran `sudo chmod -R 777 on /bin` and the solution worked – Genes Apr 28 '20 at 09:47
Now i m facing mysql community service could not start error after login in user Ubuntu – May 03 '20 at 16:22
You are a savior!! This worked like charm!! Thanks! – Sukanya Pai Jun 10 '20 at 15:53
You really saved my day :P – Amit Mishra Aug 26 '20 at 15:00
Thanks!!!! worked on vbox guest fine – Rankinstudio Nov 01 '21 at 21:26
Worked for me, I used below command as I was not getting the Advanced Options, `$ init 1 $ mount -o remount / $ chown root:root /usr/bin/sudo $ chmod u+s /usr/bin/sudo` $ reboot as suggested by @James Risner & @justme in this thread and it worked for me. :) – Hemant Nov 30 '22 at 11:53

score 3 · Answer 2 · answered Aug 25 '22 at 04:31

If you have root user password then:

1.Login as root user

2.open terminal

3.Enter following cmd's:-

mount -o remount /
chown root:root /usr/bin/sudo && chmod 4755 /usr/bin/sudo
chown root:root /usr/lib/sudo/sudoers.so && chmod 4755/usr/lib/sudo/sudoers.so
chown root:root /var/* && chmod 4755 /var/*

If you do not have root user password then:

1.Reboot your system in recovery mode(boot and press and hold esc button to enter in recovery mode)

here it looks like

2.Nevigate to (advance option for linux) by using down arrow button and press two times Enter

here it looks like

3.Nevigate to root by using down arrow button and press Enter

here it looks like

4.Now enter following cmd's:-

mount -o remount /
chown root:root /usr/bin/sudo && chmod 4755 /usr/bin/sudo
chown root:root /usr/lib/sudo/sudoers.so && chmod 4755/usr/lib/sudo/sudoers.so
chown root:root /var/* && chmod 4755 /var/*

5.press ctrl+d and then select resume option to boot normal

Kudos you have made it

score 1 · Answer 3 · answered May 27 '19 at 19:47

1

/usr/bin/sudo mv /usr/local/bin/sudo{,2} hash -r

Refer this https://unix.stackexchange.com/questions/419122/sudo-must-be-owned-by-uid-0-and-have-the-setuid-bit-set?newreg=b2490740fb214ce79c316ad76f859e0a

answered May 27 '19 at 19:47

Sachin Adkar

79
4

score 1 · Answer 4 · answered Apr 02 '21 at 10:34

1

Simple fix

1-

2-select recovery

3-select root

4-mount -o remount,rw /

5-chmod u=rwxs,g=rx,o=rx /usr/bin/sudo /usr/bin/pkexec

6-reboot or exit

answered Apr 02 '21 at 10:34

Netwons

1,170
11
14

score 1 · Answer 5 · edited Nov 09 '22 at 02:02

1

For me, I solved this by running these commands:

 $ init 1 
 $ mount -o remount /
 $ chown root:root /usr/bin/sudo
 $ chmod u+s /usr/bin/sudo
 $ reboot

edited Nov 09 '22 at 02:02

James Risner

5,451
11
25
47

answered Nov 06 '22 at 08:38

justme

13
4

1

This has worked for me. I didn't have any access of root user, but after following these commands, I got it working. Thanks @James Risner and justme – Hemant Nov 30 '22 at 11:43

score 0 · Answer 6 · answered Sep 19 '18 at 06:51

0

Its beacuase of Permission issue

 $ su
 Password: <type your root password>

Switch to root user and run the command

# pkexec chmod a=rx,u+ws /usr/bin/sudo

Then check it by typing from the user

$sudo -l

it Works fine for me

Cheers....

answered Sep 19 '18 at 06:51

Keval Mangukiya

2,243
2
11
13

score 0 · Answer 7 · answered Apr 24 '19 at 15:12

0

Try this:

pkexec chown root:root /etc/sudoers /etc/sudoers.d -R

I've succeeded it

answered Apr 24 '19 at 15:12

Akane153

1
1

score 0 · Answer 8 · answered Nov 24 '21 at 17:41

To solve this issue, you need to boot into recovery mode which provides a scroll-down menu with an option to drop down to a root shell.

And type these commands one after another:

# remount disks in read-write mode
mount -o remount,rw /
mount --all

# return ownership
chown root:root /usr/bin/sudo

# fix permissions
chmod 4755 /usr/bin/sudo

After that, you can reboot and log in again.

You may try this, to know if It worked:

sudo -l

score 0 · Answer 9 · answered Dec 24 '21 at 16:15

1- Alt + Ctrl + mode + F1

if login root ok if not do is

2- Alt + mode + F1

than do to path /usr/bin

3- cd /usr/bin than do is

chmod u+s sudo su mount umount sg pkexec ping passwd newuidmap newgrp newgidmap ksu gpasswd fusermount expiry chsh chfn chage unix_chkpwd

than do is

chmod g+s wall write locate unix_chkpwd

than change passwd root passwd

4- Alt + Ctrl + mode + F7

Or

5- Alt + mode + F7

than try su to login root

su

if not work do it again and change passwd user and root example my user is mizel

6- su - mizel

root only

7- su

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). — Community, Dec 24 '21 at 19:28

score 0 · Answer 10 · answered Jul 05 '22 at 11:58

This worked for me

“sudo: /usr/bin/sudo must be owned by uid” Or sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set. Reason :This error occurs when incorrect permission or ownership is set on /usr/bin/sudo file.

Solution

Step 1 : Start the server in Single user mode using command at start.

init 1

Step 2 : Once single user mode starts use below commands

mount -o remount,rw /
- chown root:root /usr/bin/sudo
- chmod 4755 /usr/bin/sudo

Step 3: Now Reboot the Server and check.

reboot //(linux command line)

enter link description here

score 0 · Answer 11 · answered Jun 13 '23 at 22:38

This applies to those environments where they have docker / Kubernetes environment running and has host root file system mounted into the container / pod.

In this case host's root "/" is mounted as "/host" inside the pod.

kubectl exec -it mypod -- chown root:root /host/usr/bin/sudo && chmod 4755 /host/usr/bin/sudo

I have not tried creating a fresh Kubernetes pod but I guess that should work too.

/usr/bin/sudo must be owned by uid 0 and have the setuid bit set version .ubantu14.04 LTS

11 Answers11

Linked