Technical article 125593

Telnet or integrity on my OpenServer 5 system is failing with "System Defaults database could not be allocated due to: cannot be read"

OpenServer 5.0.5OpenServer 5.0.6OpenServer 5.0.7

Written · Last revised

Problem

Telnet or Integrity are failing with the following error message:

System Defaults database could not be allocated due to: cannot be read

Existing logins can use the system fine, but attempting a
new connection fails.  Root can login to the system from
the console and can bring the system to single user mode.
Although trying to run integrity displays the same error
message, but continues to run and the system will have the
same problem with telnet.

Cause

The /etc/auth/system/default file is corrupt or missing.

Solution

Restore this file from a valid backup.  If there is
not a backup of this file, it could be recreated by hand.
It is highly recommended to restore this file from backup
though.  The permissions on this file should be:
-rw-rw-r--   1 auth     auth         433 DATE TIME default
The contents of this file could be as follows, this is an example
from an OpenServer system set to traditional security with no
additional modifications.  Quite a few scoadmin managers alter this
file, only use this example if no other option exists:
-- Cut here --
default:\
     :d_name=default:\
     :u_pwd=*:\
     :u_priority#0:u_cmdpriv=audittrail,su,queryspace,printqueue,mem,terminal:\
     :u_syspriv=execsuid,nopromain,chmodsugid,chown:\
     :u_minchg#0:u_maxlen#8:u_exp#0:u_life#0:\
     :u_pickpw:u_genpwd:u_restrict@:u_nullpw:\
     :u_suclog#0:u_unsuclog#0:u_maxtries#99:u_lock:\
     :u_singleuserpswd:u_secclass=c2:u_integrity@:u_tcbpw@:\
     :u_pwseg#1:\
     :t_logdelay#1:t_maxtries#99:t_login_timeout#60:\
     :chkent:
-- Cut here --
See Also: default(F) prpw(F) ttys(F)

From the Xinuos technical article database, record 125593. Reproduced with permission. The original is at www.sco.com/ta/125593, which is reachable but blocked from search engines.

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.