11 Nov
2015
11 Nov
'15
12:41 p.m.
Hi Steven,
On Wed, Nov 11, 2015 at 12:23:46PM +0000, Steven Walker wrote:
xen-shell> console
Running console for simpee - exit with Ctrl+]
[34294.348131] nfs: server 85.119.80.243 not responding, still trying
[34301.149539] nfs: server 85.119.80.243 OK
The NFS server that the rescue VM is running from didn't respond for
a couple of seconds. I don't know why, but it's unrelated.
BitFolk Rescue Environment -
https://tools.bitfolk.com/wiki/Rescue
This virtual machine is running read-only over NFS with a unionfs ramdisk to
allow changes. This means:
- anything you write to its filesystem will not survive a reboot
- you only have about half your RAM size as writable space
If you need to write more, or you need it to persist past a reboot, you'll need
to use your VPS's storage. Please see:
https://tools.bitfolk.com/wiki/Rescue#Persistence
for more information.
Your user account is called 'user' and its password has been randomly-generated
(see above). Be careful what you do with it as networking is now active and
sshd is running. The 'user' account has full sudo access.
rescue login:
All of the above is the login prompt and the motd file that appears
on every login. So all that happened was you pressing return a few
times failed the login and printed a new login prompt.
At boot of the rescue VM, the very last thing to be printed before
that motd and prompt above is the random password:
****************************************
Resetting user password to random value:
New user password: imeiXuoy
****************************************
BitFolk Rescue Environment - https://tools.bitfolk.com/wiki/Rescue
…etc
So perhaps I should just put the bit with the password into the motd
as well, so it reappears every time you fail your login.
In any case, I think we've established that you do not need to use
the rescue VM at this stage? So it is safe to use "shutdown" or
"destroy" from the Xen Shell.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
Please consider the environment before reading this e-mail.
— John Levine