Technical article 111044

su <username> fails with "bad supplemental group list" on an Openserver 5 System.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

When a user tries to become another user, using the su command, the command fails. It may look like this, where <username> is the user you to become:

# su <username>
Error: su: bad supplemental group list
or:
             # su - <username>
             Last   successful real login for <username>: Fri Sep 15 11:45:08
2000 on ttyp04
             Last unsuccessful real login for <username>: NEVER
             Error: eaccess failed for pathname /usr/<username>/.suppgroups: Not
a directory
             (error 20)
             su: Bad supplemental group list

This fails even though root can log in. The user cannot log in from the login prompt either. Trying to log in with this user will look like this:

login: <username> Password: Cannot change to home directory login:

The user cannot log in and you are returned to the login prompt.

Cause

The user's home directory can no longer be found and is now a file
rather than a directory.  This user's home directory must be
reinstated either from a backup or by re-creating the directory.

Solution

The user's directory must be put back into place. A tape recovery may be done, or you can create the directory again so the user can log in.

Log in as root and change directories to where your user's home directory is located, usually /home, /usr, or /u.

# cd /home

The user's directory may be under another name, and the user may still be the owner of the directory. This command:

# ls -l | grep <username>
may return something similar to this:
drwxr-xr-x    2  <username>  group      512  May 9 09:22 foobar

This means that someone moved the directory name to foobar. To fix this, type:

# mv foobar <username>

The user should now be able to log in.

If the 'ls -l | grep <username>' did not return anything, then the
user's home directory may need to be re-created.

To do this, you can either use a SCOadmin account to delete and re-create the account or just make the user's home directory here:

# mkdir <username>
Change ownership and group:
# chown <username>:<group> <username>
Change permissions:
# chmod 755 <username>

The user can now log in and the su <username> should no longer fail.

NOTE:     The user's home directory may have been moved to somewhere else on
          the system.

See also

ta104299, "'Warning: supplemental group list full, group auth not added.'"

From the Xinuos technical article database, record 111044. Reproduced with permission. The original is at www.sco.com/ta/111044, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.