Hi,

A minor feature request: Can you please add the ability to see a linode's console log on the web, perhaps under the Utilities menu? When my linode is acting up, it would be helpful to see the console log. I do not always have access to ssh (due to work firewall, etc), but always have access to the web.

Thanks,

--Eric

Do this from inside your linode:

neo101:/var/www/public# ssh harmone@host91.atlanta.linode.com > data.txt

Then you (anyone) can browse to your textfile to read what is happening.
Ask again if you wish me to elaborate.

The main reason I am asking this to be implemented by Linode is that it will always have the latest data, assuming that they just grab the logview output.

I could cron a command myself to grab it, but the best that it can get is 1 minute snapshots. Such a solution is very kludgy, at it's best.

If the kernel panics and the VM dies, I want to know why. As I said, I do not have access to ssh at all times, but I always have web access.

But if you run the command I suggested you will have a textfile that grows by itself in real time. You would only need to run the command once and the text file would just keep growing.

There could of course be a problem if you get a huge amount of console messages. Then the text file would grow extremely big.

EDIT 1:
btw: Is "logview output" the same thing as "console messages"?

EDIT2:
Kernel panics you say. Well. My suggestion would not work in those cases.

% ssh myid@myhost.fremont.linode.com logview
myid@myhost.fremont.linode.com's password:


Showing last 250 lines from previous boot
-----------------------------------------

<logs removed>

Showing last 100 lines from current boot
-----------------------------------------

<logs removed>

Is there a way to get more than the last 250 lines of console messages prior to the last boot?

250 lines are not enough to view what the problem was ...

FYI, in addition to ports 22 and 2200, Lish listens on port 443, which shouldn't be firewalled unless your workplace is really anal.

Mine is.
They have a proxy that MITMs all SSL pages, presenting you with an internal certificate signed by the corporate CA (so browsers accept it silently). If it's not really HTTPS, all you'll see will be a proxy error.

_________________
rsk, providing useless advice on the Internet since 2005.