[BlueOnyx:01507] Re: SSH Closes Connection

[Richard Sidlin]

Thanks Michael. I will give this a go and sorry for posting on the wrong 
forum.

----- Original Message ----- 
From: "Michael Stauber" <mstauber at blueonyx.it>
To: "BlueOnyx General Mailing List" <blueonyx at blueonyx.it>
Sent: Thursday, June 25, 2009 12:55 AM
Subject: [BlueOnyx:01494] Re: SSH Closes Connection


> Hi Richard,
>
>> Bit more of a problem now. I cannot get access by SSH, SCP or even with a
>> monitor and keyboard attached to it. The admin GUI and all of the sites
>> continue to work but that probably won't last long and for some reason I
>> will need access. Sorry for posting in the top forum and this is a
>> BlueQuartz box but does anyone have the best course of action that I can
>> take here please?
>
> Well, if that box is a BlueQuartz, then this is not really the right list 
> for
> it.
>
> But in general what I said in my previous message on that topic applies:
>
> Apparently you shot your authentication layer when you applied the NuOnce
> procedure to switch your box from PAM to Shadow.
>
> If you followed the procedure to the letter, then you created backup files 
> of
> almost everything you replaced or modified. Best thing would be to copy 
> those
> backups back and to revert the box to its previous state.
>
> As you cannot login anymore (even with keyboard and monitor attached) you 
> must
> boot off the CD to bypass the authentication.
>
> So do this:
>
> 1.) Boot the server off the BlueQuartz CD.
>
> 2.)  At the BlueQuartz splash screen type in "rescue" to enter rescue 
> mode. Or
> "linux rescue" if that doesn't work.
>
> 3.) Set your language and keyboard and choose to configure the network.
>
> 4.) If asked if you want to access your disks, choose the leftmost from 
> the
> three options. Which should already be selected, so just hit return.
>
> 5.) Once you reach the command prompt, type "chroot /mnt/sysimage/" to 
> chroot
> the filesystem on the HDs.
>
> At that point you can access your data directly as if you'd be logged in 
> to
> the problematic server as /root.
>
> As first thing check if the directory /SYSTEM-BACKUP is still present. You
> created it when you ran the NuOnce procedure.
>
> If it is, you need to copy all files from that directory back to the 
> places
> where they came from.
>
> That should almost get you going again, but you also need to fix the two 
> files
> you edited, meaning:
>
> /usr/sausalito/perl/Base/User.pm
> /usr/sausalito/perl/Base/Group.pm
>
> Those changes need to be reverted as well. Look at the initial procedure 
> to
> see what needs to be changed to get those files back to their original 
> state.
>
> Additionally:
>
> Copy the file /etc/pam.d/system-auth.backup back to 
> /etc/pam.d/system-auth:
>
> cp /etc/pam.d/system-auth.backup back /etc/pam.d/system-auth
>
> If you managed to revert back all those changes you made, then you could 
> try a
> reboot and see if it works. To do so simply type "/sbin/reboot" and be 
> sure to
> eject the CD, too.
>
>
> -- 
> With best regards
>
> Michael Stauber
>
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at blueonyx.it
> http://www.blueonyx.it/mailman/listinfo/blueonyx
>
> -- 
> This message has been scanned for viruses and
> dangerous content by the Help Internet
> MailScanner, and is believed to be clean.
>