From Progzoo
Revision as of 16:03, 16 September 2008 by Andr3w (Talk | contribs) (Restart the virtual server)

Jump to: navigation, search

Things can go wrong at You may be able to fix them

Corruption at the server

This is mostly caused by a queue getting corrupted. Progzoo queues all requests so that there are only a limited number of jobs running at any one time.

  • The queue is stored in JSON format - due to Andrew's dumbness this can get corrupted.
  • In that case you can trash the queue.
    • This means that all waiting jobs will be lost so don't trash it unless
      • it is corrupt (because when it is corrupt no one is going to get served)
      • you are authorised to do this
      • you really, really want to

You can see the queue by visiting Change lang to one of java cs cpp pl php py rb vb

You can trash the queue by visiting - but change the 0 to 1.

Before trashing the queue please copy it and send it to me at with any other information that might be useful.

Server Health Check


The other machines are listed at User:Andr3w#Hardware

Restart the virtual server

The command /home/andrew/ contains the following:

rm pz.fs.cow
screen -d -m /home/andrew/kernel64-2.6.24 ubda=/home/andrew/pz.fs.cow,/home/andrew/pz.fs mem=228M eth0=tuntap,tap1 umid=umid

Another way to kill the guest server(s) (if you don't have mconsole)

kill `cat .uml/*/pid`