Re: 'could not open session'
- From: "Georg Klein" <gk@xxxxxxxxxx>
- Date: Sun, 9 Jul 2006 18:53:25 +0000 (UTC)
Hi,
On Fri, 07 Jul 2006 23:48:33 -0400, Tim Boyer wrote:
I've just done an upgrade from RHEL3 to 4, and have run into the strangest
thing.
I can't log in from the console. Every login attempt with the correct password
gives the message 'could not open session'.
I can ssh in, and enter a username and password. But from there, I can't su to
anybody - root, or another user. 'could not open session'.
Booting to single user mode gives me root, but as soon as I do a su - you
guessed it.
I can do a sudo.
I enabled telnet, just to see what happens:
login: tim
Password:
Permission denied
Connection closed by foreign host.
Permission problem, I think - but _where_??
Not sure whether it may help, but with RHEL4 you have SElinux enabled by
default (however only the targeted policy). But I have been
running into problems by restoring a RHEL4 system by no longer being able
to login, so I had to disable SElinux (and could login).
So try to disable SElinux at the boot prompt by adding a selinux=0 as a
kernel parameter.
hth, gk
.
- Follow-Ups:
- Re: 'could not open session'
- From: Tim Boyer
- Re: 'could not open session'
- References:
- 'could not open session'
- From: Tim Boyer
- 'could not open session'
- Prev by Date: Re: Double Python installation!
- Next by Date: Re: 'could not open session'
- Previous by thread: Re: 'could not open session'
- Next by thread: Re: 'could not open session'
- Index(es):
Relevant Pages
|
|