Unable to connect to VM...

[jmaggart]

First of all, I want to thank the people in charge of this site for the amazing tool to learn Linux/Unix. I am "teaching myself" Linux and have been looking for an effective tool for about 2 months and felt almost hopeless, until I found this site. I have learned more in the last week than in the last several months.

That being said, as I was trying to connect to a VM today I was unable to do so. As usual I entered my login information into the website, joined the queue, but when the normal "power controls" came up the option to switch on power stayed unlit. I tried logging out, and back in, restarting my browser, my computer, and everything else I can think of. At this point it shows I am logged on but has no information beside machine state, but the time is running down, and it still refreshes the site at normal intervals.

I tried telnetting in anyway and get no connection. I even downloaded putty to try and ssh, but not able to access that way either. I was so excited to get started on the next tutorial items and now I can't. Hopefully someone can help. I was going to try to insert a screenshot but I'm not sure how to do that. Thanks!

[jmaggart]

I should have also mentioned that none of the other boxes is able to be selected either.

[drgrussell]

One of the cloud nodes seems to have had a problem, but by the time I investigated the node has been removed from the cloud.
Really it should have been removed automatically as soon as you had the problem...

I will review the logs on monday and try to see what happened. In the meantime everything from a user's point of view seems to be back to normal.
Sorry for the problems.

Gordon.

[jmaggart]

Thanks Gordon, everything seems to be working awesome for me from my end as well.

[drgrussell]

I checked the logs and the problems seems to lie in a kernel bug, where brctl hung up for some reason at the end of a virtual machine session.
Unfortunately this left the linuxzoo control file locked, and stopped all other systems working.

Hopefully just a 1-off issue. I updated the kernel just in case, and will look at better timeout alarms to try to avoid this in the future.
Gordon.