System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

unable to log on as root...

anthony m. gonzales
Frequent Advisor

unable to log on as root...

Hi all,

I do not know what happened, I suspect foul play, but, now that I try to log onto my TRU64 UNIX system as root I get login: no shell, no such file or directory. Is there a way to get the shell link re-etablished or is it a corrupt shell.

Thanks,
Anthony
4 REPLIES
Rick Retterer
Respected Contributor

Re: unable to log on as root...

Troubleshooting that can be done:

Try to login from console vs. network.

Test login from root rather than as a user.

Test login as a different user.

Test su access if a user can login.

Use fverify(8) against OSFBASE to see if permissions are OK.

Questions:

If NIS is being used, can this be isolated to NIS users ?

Is C2 (Enhanced security) being used?

Things to check:

Check logs after each test, is the error the same or different ?

Check /usr/adm/sialog if it exists.

Check audit logs( if applicable)

Check Accounting (also if applicable)

Check the login files specific to that shell, such as /etc/profile and .profile (if ksh/sh)



- Rick Retterer



Steven Schweda
Honored Contributor

Re: unable to log on as root...

> [...] I try to log onto [...]

How/where? Local workstation keyboard?
Serial port? Telnet? rsh? ssh?

> [...] as root [...]

> If NIS is being used, [...]

Normally, "root" is in the local passwd file,
and the local file is searched before the NIS
data. Problems with /etc/passwd or
/etc/nsswitch.conf (or whatever) could
violate this expectation, of course.

Does single-user mode work better?
Vladimir Fabecic
Honored Contributor

Re: unable to log on as root...

As others said, that could be many reasons.
Can you please post output of:
# grep root /etc/passwd
In vino veritas, in VMS cluster
anthony m. gonzales
Frequent Advisor

Re: unable to log on as root...

I have resolved the problem...I booted into single user mode then modified passwd with vipw and changed the shell path from /bin/ksh to /bin/sh...that did the trick.


Thanks to all.
Anthony