Tag: Updates

Updates
The first of a number of updates and upgrades: PMAS is now at 3.2, fairly new (released in July 2010), there is just one change that I have to take care of: the action taken on the message, which is stored in the log file, can now be two characters: The first states what action was performed on the message, the second states the source: by a user rule or a system rule and so on. The changes won’t be a big: just that the first (and probably only) character of the action taken, the rest of the code is not effected. Or perhaps I could note the difference in the statistics but that’s hardly significant in my case.
Second – and just in time, the license has been renewed. That is: the new license that I had around already, has been applied before the old one expired – today. So I’m protected for another year.
Another “upgrade” has to do with storage.
The logical device where I store most of the web-content, had been set up to be 8 Gb, but it filled up to well over 85%. I extended the file to twice it’s size ($ LD/EXTEND/SIZE=33600000) but the actual size reported remained the previous 16800000 blocks and still over 85% full). I couldn’t find a way to get around it and so I asked on ITRC when I was elsewhere. I got the answer, the only one without taking everything down for a prolonged period, as was proposed by Jon Pinkley and Hein van den Heuvel: Simply using this sequence:

$ DISMOUNT LDA1 ! I had to add /ABORT since some process kept a file open.
$ MOUNT/OVER = ID LDA1
$ SET VOLUME/LIMIT=33600000
$ SET VOLUME/SIZE=33600000
$ DISMOUNT LDA1
$ MOUNT/SYSTEM LDA1


gave me the full 16Gb containerfile available. Lots of storage to publish tracking data and photographs.

More to come soon:
VMS updates – perhaps an upgrade to 8.4, when I get hold of media….(and patches!)
Webserver update (WASD 10.0.2)
PHP (the Mark Berryman 5.2.13 version)
WP (3.0.1)
MySQL (5.1.49)
PhpMyAdmin (3.whatever)

It also means a somewhat new configuration of the web server….But that is under construction.

Updates
It’s been some time that I installed updates – and I have donwloaded the latest ones some time ago but nevber found time to install them.
Today it had to be done.
It went smoothly. First, the major update (UPDATE_V0012) was installed, after I changed SYSTARTUP_VMS a bit – it should just reboot and not start everything else. After reboot, I installed all that was superseeded – about 8 patches – and the latest TCPIP ECO. I decieded to have everything started, and rebooted again.
For some reason, it did took some time for TCPIP-services to start, but in the end, all was up and running. At least, ik looked that way, but TCPIP$BIND – the BIND server – wasn’t and therefore, WASD could start properly either. It did – but on port 82….
Checking why BIND didn’t start, I found the logfile stated:

$ Set NoOn
$ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY"))
%DCL-W-ACTIMAGE, error activating image SYS$SYSTEM:TCPIP$BIND_SERVER.EXE
-CLI-E-IMGNAME, image file $116$DKA100:[SYS0.][SYSEXE]TCPIP$BIND_SERVER.EXE;
-RMS-F-NOPRIV, insufficient privilege or object protection violation
 TCPIP$BIND  job terminated at 18-APR-2010 19:07:25.69
 Accounting information:
 Buffered I/O count:                43     Peak working set size:       2368
 Direct I/O count:                  47     Peak virtual size:         173088
 Page faults:                       223      Mounted volumes:                0

 Charged CPU time:        0 00:00:00.07      
Elapsed time:       0 00:00:00.28


This is weird, and I checked the protection of the image, but it seemed all OK.
Except: It shouldn’t be running off [SYS0.SYSEXE] but from SYS$COMMON.SYSEXE] – and indeed, I found two instances of the image. I removed the one in [SYS0.SYSEXE] and restarted BIJD – and it worked. Next, I stopped the WASD server on port 82 (the right way) and restarted the webserver.

All seems well.
The only point is I’ll have to rewrite a frontpage article…