Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

3004-501 Cannot su to "root"

1,478 views
Skip to first unread message

Russ Cain

unread,
Oct 21, 1999, 3:00:00 AM10/21/99
to
I'm sure this is a simple one, but I can't afford to lose anymore hair.
We recently upgraded (migrated) from 4.1.5 to 4.3.3 .. The upgrade went
smooth, however we are having a problem "SU'ing" to root. I can login
fine as root from the console and telnet. I have checked to make sure
root is allowed to be SU'd to but to no avail. I've added a new userCan
anyone shed any light on this for me?

thanks..

Russ Cain
rc...@tchm.org


Norman Levin

unread,
Oct 21, 1999, 3:00:00 AM10/21/99
to
Russ Cain wrote:
>
> I'm sure this is a simple one, but I can't afford to lose anymore hair.
> We recently upgraded (migrated) from 4.1.5 to 4.3.3 .. The upgrade went
> smooth, however we are having a problem "SU'ing" to root. I can login
> fine as root from the console and telnet. I have checked to make sure
> root is allowed to be SU'd to but to no avail.
*** do a "smit chuser"
and respond "root"
See if the line "TTYs" says ALL or has specific addresses.
If specific addresses - then su root
is restricted to those addresses too.

--
Norman Levin
vm/dynAmIX inc.

Adams

unread,
Oct 21, 1999, 3:00:00 AM10/21/99
to
Russ;

I suppose you get this message in detail:

$ su - root
root's Password:
3004-307 You are not allowed to su to this account.

3004-501 Cannot su to "root" : Account is not accessible.

?????? Right ??

Logon at the console as root. run this command:

chuser su='true' root

Should fix the problem if it is only an account profile attribute.

Hope it helps.

Scott


Russ Cain wrote:
>
> I'm sure this is a simple one, but I can't afford to lose anymore hair.
> We recently upgraded (migrated) from 4.1.5 to 4.3.3 .. The upgrade went
> smooth, however we are having a problem "SU'ing" to root. I can login
> fine as root from the console and telnet. I have checked to make sure

David Reid

unread,
Oct 22, 1999, 3:00:00 AM10/22/99
to
The other thing worth checking is the file permissions on /usr/bin/su
They should be r-sr-xr-x

Regards,

D Reid


Sent via Deja.com http://www.deja.com/
Before you buy.

Russ Cain

unread,
Oct 25, 1999, 3:00:00 AM10/25/99
to
I looked in to the data you sent me on the APARS. Special attention was
spent on IX75071 - Cannot su to Root.
We had the following output through SMIT:

Fileset bos.64bit is not applied on the system
Fileset bos.adt.prof:4.3.1.0 is applied on the system
Fileset bos.rte.control:4.3.1.0 is applied on the system
Fileset bos.rte.libc:4.3.1.0 is applied on the system
Fileset bos.rte.shell:4.3.1.0 is applied on the system

I was a little concerned with bos.64bit not being applied on the system.
I would hate to go down a path that is leading me away from the original
problem, but is this something to be concerned with?

Also, I checked the file permissions on su and this is the result:

-rwxr-xr-x 1 root security 17974 Aug 05 17:03 /usr/bin/su

thanks for the help...

Russ Cain


Rob Kouwenberg

unread,
Oct 25, 1999, 3:00:00 AM10/25/99
to
Russ Cain <rc...@comnetcom.net> wrote:

> Also, I checked the file permissions on su and this is the result:
> -rwxr-xr-x 1 root security 17974 Aug 05 17:03 /usr/bin/su

Shouldn't there be an s bit on it ? Worse yet !? It has a time stamp
that I don't know from distribution.

Better replace that with an original one ... Dunno who visited you
august 5th, but IMHO I don't like it ..

0 new messages