- This topic has 2 replies, 1 voice, and was last updated 21 years, 3 months ago by
.
-
Posts
-
Hi,
This morning I logged in as admin with ssh to one of our production servers, upon trying to su it appeared that I was no longer able, it asked for the password again. The server (MacOSX 10.3.8 server on 2×1.33GHZ xserve) is used as an Open Directory Master and AFP and SMB file server. All the functionality needed is still working, but not I’m only able to go in as root through the private root key (id_dsa) I made for the root user on the server and keep somewhere safe for situations like this. So I have still root functionality, but not through su or sudo.
I noticed that Security Server was not operating so I started this as root with /System/Library/StartupItems/SecurityServer/SecurityServer start and now it is running, but still no su or sudo.
I tried to reset the password through Server Admin, wich succeeded but still not able to su or sudo.
I logged in through Apple Remote Desktop to use netinfo to reset the root password, wich succeeded but still no su or sudo.
I logged the admin user out of the Window Server console and now I’m no longer able to login throug the Window server on the server, still all server functionality is still operational.
lookupd and netinfod are apparantly working
Rebooting could be an option, but since it is a production server I’m worried that the server will not startup like it should, Is there anyone who had this issue before or knows what the source of the problem could be ?
As I said, i’m still able to control the server through Server Admin, Workgroup Manager, Server Monitor and commandline root (by the ssh key I keep for the root account), but I would like to resolve this issue because I’m unsure where this problem originates from.
If anyone has merely a hint on what the source of this problem could be, I would be very grateful.
Dimi.
I’ve just set up a test system (more or less the same as our production server, also 10.3.8 server) and tried the following :
– killed the Security Server
– tried to log in with ssh : same behaviour : could not login
– tried to su or sudo : same behaviour : could not login
– logged out the window server : could not get the login window backso I rebooted the test server to see if everything would be ok again and it was. I’ll be rebooting our production server two days from now (wich is a non production day) and hope that it’ll have the same outcome.
It make sense if you look at the /etc/pam.d information :
goll:~ admin$ cat /etc/pam.d/su
# su: auth account session
auth sufficient pam_rootok.so
auth required pam_wheel.so use_uid group=admin group=wheel
auth sufficient pam_securityserver.so
auth sufficient pam_unix.so
auth required pam_deny.so
account required pam_permit.so
password required pam_netinfo.so
session required pam_permit.sohope this info is of any help.
Dimi.
- You must be logged in to reply to this topic.