Home • Explore • Blog • CI
☰



man-pages
13th chunk of `sudo.man`
f1ca63d04e20e82729790f8c95acd55f6f20c8e739c2f4610000000100000c2e
 set‐user‐ID bit set.  Also, it
             must not be located on a file system mounted with the ‘nosuid’ op‐
             tion or on an NFS file system that maps uid 0 to  an  unprivileged
             uid.

       effective  uid  is  not  0,  is  sudo on a file system with the ’nosuid’
             option set or an NFS file system without root privileges?
             sudo was not run with root privileges.  The sudo  binary  has  the
             proper  owner  and  permissions but it still did not run with root
             privileges.  The most common reason for this is that the file sys‐
             tem the sudo binary is located on is mounted with the ‘nosuid’ op‐
             tion or it is an NFS file system that maps uid 0  to  an  unprivi‐
             leged uid.

       fatal error, unable to load plugins
             An error occurred while loading or initializing the plugins speci‐
             fied in sudo.conf(5).

       invalid environment variable name
             One or more environment variable names specified via the -E option
             contained  an  equal  sign  (‘=’).  The arguments to the -E option
             should be environment variable names without an associated value.

       no password was provided
             When sudo tried to read the password, it did not receive any char‐
             acters.  This may happen if no terminal is available  (or  the  -S
             option  is  specified)  and the standard input has been redirected
             from /dev/null.

       a terminal is required to read the password
             sudo needs to read the password but there is no  mechanism  avail‐
             able for it to do so.  A terminal is not present to read the pass‐
             word  from, sudo has not been configured to read from the standard
             input, the -S option was not used, and no askpass helper has  been
             specified either via the sudo.conf(5) file or the SUDO_ASKPASS en‐
             vironment variable.

       no writable temporary directory found
             sudoedit  was unable to find a usable temporary directory in which
             to store its intermediate files.

       The “no new privileges” flag is set, which prevents sudo from running as
             root.
             sudo was run by a process that has the Linux “no  new  privileges”
             flag  is  set.  This causes the set‐user‐ID bit to be ignored when
             running an executable, which will prevent sudo  from  functioning.
             The  most likely cause for this is running sudo within a container
             that sets this flag.  Check the documentation to see if it is pos‐
             sible to configure the container such that the flag is not set.

       sudo must be owned by uid 0 and have the setuid bit set
             sudo was not run with root privileges.  The sudo binary  does  not
             have  the  correct  owner or permissions.  It must be owned by the
             root user and have the set‐user‐ID bit set.

       sudoedit is
Title: Sudo Diagnostics (Continued)
Summary
This section continues listing diagnostic error messages that can occur when using sudo. Messages include 'invalid environment variable name', 'no password was provided', 'a terminal is required to read the password', 'no writable temporary directory found', errors related to the 'no new privileges' flag, and errors related to sudo not being owned by uid 0 and having the setuid bit set.