CLI SSH login as root is successful; however, this results in logging in as a user that has no root privileges (I cannot even shutdown the system)
VNC into the machine and login as root; however, this results in the VNC session terminating immediately after login
Currently I am unable to test what funky behavior would result from me logging into the system locally as root because I administer this system remotely.
I believe all I have to do to fix the problem is have the system restarted manually (as I cannot execute the shutdown command with no root privileges); however, I cannot do this until tonight as this is a production system.
The problem only occurred once before (about a month ago) and a reboot seemed to do the trick; however, I would really like to know what causes this.
What is the exact command line you use when you ssh into the target machine? I think ssh normally tries to login as the user which is calling ssh, so when you are root and do “ssh machine”, it should translate to “ssh root@machine”. Also see if you have something in your ~/.ssh/config. – Yarny
On 03/08/2012 11:36 AM, Yarny wrote:
> danielcrawford;2446833 Wrote:
>> CLI SSH login as root is successful; however, this results in logging in
>> as a user that has no root privileges
> What is the exact command line you use when you ssh into the target
> machine? I think ssh normally tries to login as the user which is
> calling ssh, so when you are root and do “ssh machine”, it should
> translate to “ssh root@machine”. Also see if you have something in your
> ~/.ssh/config. – Yarny
As a rule, most systems disable root login from ssh as a security precaution. On
my remote systems, I log in as my normal user, then ‘su -’ to get a root login.
Would that work for you?
I guess I should have been clearer. Normally everything works perfectly fine on this system. The server in question is setup to allow root access to ssh and normally does so. Using putty from windows I can normally ssh into the server as root and run root commands such as the basic shutdown command. Furthermore, the ‘su’ command gives no further root access when the problem occurs.
This is the second time this has happened. A simple reboot has fixed the problem; however, I would still like to know the cause.