Recently, I received a ticket from a user that couldn't ssh into the box he rents from my unnamed benefactors. I fire up the console accessible via web to check if ssh is running, it's not. So, I do:
$service ssh start [FAILED] Can't locate lib.foo.so.10 No big deal, lets do a bit of looking around and see why it can't find some library it relies on.
$locate foo.whatever.so /foo_dir/lib.foo.so.1 foo_/dir/lib.foo.so.10 $ls -l /foo_dir/ lib.foo.so.1 -> lib.foo.so.10 lib.foo.so.10 -> lib.foo.so.1 As I scratch my head a minute wondering how his foo got so barred, characters begin to creep into the prompt. Characters I wasn't typing...
$please help me... [-bash please: command not found] $ $don't hit enter! #me $vi #me Hello, your foo is barred... | #me Please help me fix. | #user I uninstalled foo. | #user Sysop will attempt to fix your foo. | #me ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ :q! $try: other methods \for much longer time \ than I'm allowed to help \ this tier of user [No dice] You need foo for me to fix it. | #me Perhaps your foo is too barred. Backups?| #me No. | #user Unmanaged system. I can do no more. | #me /* I had really done more Try to submit a ticket plea... | #me /* than I should've already. Ok thank you for trying. | #user Godspeed. | #me ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ :q! Has anyone else ever had someone on the other end of a console session and experienced this awkwardness? I imagine there's some veterans who have stories out there. Wish I was allowed to do more for the guy though, but he was definitely on his own as far as what we were allowed to do.
As an aside. Reflexively I may have typed exit on my way out of the session. oops...
I think the answer in retrospect was spin up another VM and netcat stuff to him. But I'm still new.
[link][8 comments]