Just been hit by the same problem twice in a row:

Start your Linode
Connect to lish
Hit enter to connect to the console
Run less /var/log/messages to view a large file
Scroll up and down a few times with pgup/pgdown
Your Linode should now have hung

I'm fairly useless with screen, but it looks like that's to blame here. The firewall I use (APF) may also be to blame as it sends details of the packets it blocks to the console over whatever program is running.

Can anyone else confirm this bug exists on their Linode?

I couldn't repeat your problem. I'm not using APF - maybe that's the cause?

_________________
/ Peter

Oh i had lots of console crashes/hangs from lish as well ... many of them when trying to run midnight commander. Sometimes it works but many times it hangs. It seems to happen whenever there is a big burst of data ...

Do you have anything that pipes output directly to the console? This is all that APF was doing in this case, but I haven't had a chance to test without it running.

I don't understand why this would actually be able to kill the Linode though. Is it set up so that if the screen session dies the Linode dies with it?

No, when your connection to Lish is killed, the Linode keeps running with the console in screen mode. When you're disconnected, just reconnect to Lish, and you can pick up where you left off.

In that case it's hard to explain why the whole Linode should crash when (I presume) it's just the screen session that dies.

I'm worried about using the console now

No

_________________
/ Peter