ajft

Cow-orkers back in Australia deal me another frustrating blow — rather than sending me an application setup that I asked for, the configuration that I know already works, someone decided to regenerate it in a spectacularly bad fashion. Not only does it not work, but because I stupidly assumed they had sent me what I'd asked for, I didn't check it before running it and it broke other things.

[2008-Apr-10] Not sure why this is still here, sometime in 2005 I moved all my work-related posts to a work log

ITS-ZA2 had rebooted 01:24, no messages in CONSOLE.LOG or SYS$LOG.ERR. There is an ABEND.LOG generated at 01:24, but it is completely full of "1" characters, server must have rebooted before it was written.

While running Netfinity manager on the workstation and connecting to ITS-ZA1, exiting the 'RAID Manager' component caused the following error to occur on the server console:

2000-01-17 10:51:51: SERVER-5.0-834 [nmID=2000D]
  Free detected corrupt trailing redzone for node 0xD02E9120, node size 2296

Started 'System Information Tool' from Netfinity manager, the server printed a few error message regarding corrupt memory, but then automatically restarted before these could be recorded.

Finally got organised and started to read up on some of the material I've brought with me to South Africa... exactly how are we going to do all this?

Spent 10R and 20 minutes at the internet café and caught up on my email, nothing special to look at, mostly just friends discussing holidays in July. The version of Internet Explorer on the machines kept generating errors in the javascript, both on the my.monash portal login page and after nearly every action on the web-mail pages.