About an hour ago, our alert systems started spamming us. It seems like a
problem with Amazon AWS, US East. I'm able to access at least two of the
systems in US East via https - but one of them is not responding to ssh - So I
figured I would reboot it via AWS control panel -
And when I login to
What exactly is the error you get with SSH? (try ssh -vvv)
I think AWS only uses public key auth (good), but if you NEED to login via
password and keys are thwarting you, try
ssh -o PreferredAuthentications=password m...@example.com
As for the "crap your pants" moment when nothing is right in
> From: greg.rundl...@gmail.com [mailto:greg.rundl...@gmail.com] On Behalf
> Of Greg Rundlett (freephile)
>
> As for the "crap your pants" moment when nothing is right in your control
> panel, I've noticed that if you have more than one AWS login, that it can be
> difficult to login to the right a
Yup, something weird on their firewalls. Right now, I have two machines in our
colo, with different externally facing IP's that are both in the same network
segment, both continuously pinging a machine in Amazon. As I sit here,
intermittently for no apparent reason, the amazon machine stops repl
Or not so much?
Turns out that all of the setting stuff won't stick until after logging
into Steam. So that's an improvement. And then I tried the basic Debian
systemd evisceration process.
Yeah... no. Boot process breaks badly. Going forward, it looks like
SteamOS will have hard enough depe
