RS6000 console display was locked by some user.

[mixmouse]

Hi,
When I tried to login from server's console, I saw there was a screen showed: "Display was locked by user '***'", another line asked for password. But when I typed password, the screen had no response to the keyboard. I tried this keyboard with other servers, my keyboard was OK. Later I found I had 4 servers behavior the same.

1. I still can telnet to these servers.
2. I still can ftp to these servers.
3. I can start X window on these servers using EXCEED.
4. Applications running on these servers were OK.

Is here anyone know this problem? Please give me a help.



Mixmouse

 

[Chapter11]

I am assuming finding the user who locked them out is probably not an option.

su to root and kill any "xlock" processes you find.

 

[mixmouse]

Chapter11:
I listed all processes, but I could not find any 'xlock' process.

More idea?


Thank you.

 

[lms123]

use root password.
it will unlock any i.d that lock the screen.

 

[Guest_imported]

I don't know if this will work but have you tried pdisable on the tty attached console? Like pdisable tty1 then penable tty1.


thanks
Jason

 

[aixqueen]

Well two cents that probably is of no use...but worth a thought

First I would kill any process that is running on that tty or lft. search the ps for
tty0 or lft0 or console and see what is running and kill it.

I would probably turn the monitor off and back on....or have someone do it...after all it is not working for you now...so no messages no nothing are coming through....There is probably a setup on it after a certain time put in screen lock...so maybe someone set it to be auto on lock after so many minutes...which means turning the monitor off and on may reset that and allow someone to go in and look to see what it is set at? and maybe change the password? Not sure monitor type...or tty type

So each site has an administrator who doesn't remember setting it? or they are no longer around? Or the person that set the machines up was a jerk and set it? Or did this come up all sudden.................used to work and now it doesn't?

You may end up with a reboot to get the console back if all the following fails...
but worth a thought... Turning the monitor off and on cant hurt if it isn't working now...

 

[Chapter11]

There should be no need to reboot if you can telnet in, get root, and kill all processes associated with X.

 

[aixqueen]

Chapter 11 is correct, of course ...you should not have to reboot......But
..I was just commenting if something really gets screwed up,
you may have to reboot........(Murphy's Law)
though the possibility is very very slim...I don't like people on production boxes being surprised, especially when they are killing running processes....................