Updates
I had some trouble with PMAS – the anti-Spam gateway: Crash of a server project due to AccVIO somewhere. No real problem since a new worker process is started automatically. But this time, no data, just that message.
I had two workers running: 0003 and 0008.
%%%%%%%%%%% OPCOM 10-JAN-2008 02:50:16.38 %%%%%%%%%%%
Message from user SYSTEM on DIANA
%PTSMTP-E-WORKERDIED, worker PTSMTP 0003 (20200B22) terminated unexpectedly
-SYSTEM-F-ACCVIO, access violation, reason mask=!XB, virtual address=!XH, PC=!XH, PS=!XL
-PTSMTP-I-WORKERCONN, while processing connection from 200.53.81.174,4161
and down went worker with ID 0003. Worker 0009 was started. but at the next message, 0008 crashed with the same error. 000A was started, and the next message crashed 0009.
this went on, until the last:
%%%%%%%%%%% OPCOM 10-JAN-2008 10:34:42.87 %%%%%%%%%%%
Message from user SYSTEM on DIANA
%PTSMTP-E-WORKERDIED, worker PTSMTP 0013 (20204195) terminated unexpectedly
-SYSTEM-F-ACCVIO, access violation, reason mask=!XB, virtual address=!XH, PC=!XH, PS=!XL
-PTSMTP-I-WORKERCONN, while processing connection from 122.164.19.249,2681
and only worker with ID 0014 remained. Just that one where I normally have two at hand.
Ni idea why this happened.
There were som eother crashed before that I signalled to process, and it seems some code has changed just to prevent the formerly signalled ACCVIO crashes. So I downloaded the latest update. It just meant replacement of three executables, stopping and starting the software. Now it’s a matter of wait and see.
VMS updates and new services
There are a number of patches to be installed on VMS. One is obligatoty if you want to run CIFS – Samba, that is – and I wanted to have that installed it on Persophone first, for easy exchnage of files between the emulated Alpga and the Windows environment it runs on. It requires UPDATE 5 – a patch consolidating a number of earlier patches to VMS. So I did install it first, and since it requires a reboot, I did. Alas: VMS bugchecked on startup due to a spinlock error….
It happened a colleague before. He contacted Emulators International and it turned out that he used an old version of IDLE – the software that allows Windows to use the processor is the emulated processor is in IDLE state – doing nothing.
A new version of the software is included in this version of the emulator and there was no mention of the new IDLE image required – so we didn’t install it. Luckily, Emulators International came up with a solution that we could use without reversing the installation – something troublesome when you hadn’t made a copy of the systemdisk-container before applying the update. It is descrtibed on the Personal Alpha Forum
Anyway: It’s installed on Persephone now, not yet configured. One thing NOT to try here, is setting the emulator as PDC, and require Windows login in that domain. It will fail for the obvious reason that the PDC cannot be found – because it can only be found after the emulator is started….DUH