New target
Checking the WASD log files, I found mainly one attempt do do harm:
"POST /contact.php HTTP/1.1" and paging back, I found the event started about 20-Jun-2010, and seems to be a follow-up of "GET /pingserver.php HTTP/1.1" that has been around now for a while.
Since that day, the number of attempts have increased – and I estimate that last week, there have been over 10.000 such requests. Apart from quite a lot of attempts to abuse phpmyadmin – any version 2.x – and none would succeed since though I have it on the system, it’s not available on port 80 – for obvious reasons (nor is it installed in a directory “phpmyadmin.major.minor.whatever”).
Typical: all requests try to access /scripts/setup.php… Who didn’t remove it from the site deserves to be hacked. It’s in the manual you should REMOVE that script…..
Well, it’s all rejected 🙂
Performance
To be expected – with twice as much memory and a faster processor (though the clock is the same: proof that MHz in itself doesn’t mean anything) you may expect better performance. Where the old hardware (with 256 MB of memory) consumed about 25% of page-file space, the new environment hardly tips 5. PHP seems to run better (and faster) as well, and the same applies to Python – it’s MUCH faster – almost instantaneous.
More good news on performance: we’ll get fiber some time – earliest about November, but some time next year is more feasible. It means that my upload connection – the one you experience accessing the site – will grow 10-fold: 10Mb in stead of 1 (and often less), potentially 50. And, when cost wouldn’t be a problem, it could be extended to 100, or 200 bps – but the price tag is significant.
17-Jul-2010
New hardware running
I had to power off all systems for some time, because work needed to be done on the power grid at home – and given the structure of the system, it meant I had to shutdown the PWS and storage for some time.
It gave me the opprotunity to install the new DS10 in stead of the PWS.
While the systems were down, I installed one of the KZPBA-CY controllers I still had available, and removed the SCSI cable from the PWS – together with it’s disk. But where the workstation has a built-in SCSI controller, the DS10 lacks such a device. But I had a KZPBA-CX somewhere so that was installed instead.
The system booted from the local disk so it looked fine.
Next, I connected the system to the shared SCSI bus, like the workstation was connected. But no disks showed up!
Next I booted, again, from the local disk and foud that the KZPBA-CY that connects to the HSZ50 of shared SCSI had 360 errors: teh device was bad! That explains teh problems I had with this device as well.
The card was swapped with the one from the workstation, which has proven to work fine. And that helped – the new incarnation of Diana now runs fine – as long as the system doen’t get overheated: the older hardware is less sensitive, I think. Well, we’ll see.
And what’s fine: the new machine holds a far more sophisticated video card: ATI RADEON 7500, allowing me to write this from the console 😉
I just have to create a new home-page file…
16-Jul-2010
WP almost done
Last tests for WordPress 3.0 under WASD 10.0.2 show no real big issues. There are some weird reactions, though: stylesheets not being loaded sometimes, and drag&drop that doesn’t work in all cases where I tried it.
One thing I tested today was themes. I checked the ones I use for the major blogs on site, but it looks these are not supported under 3.0 – at least, I couldn locate them anymore, I may have to copy the files and simply test them.
On the other hand, I found some nice ones I could use instead, so the presence of the blogs may change when the whole lot comes to life.
On the performence side: today I didn’t disable caching on the server, and that seems to make a big difference. Without enhancing the size of the pagefile, the Admin page now appears rather quick, without excessive paging: the disk is quite silent now, the number of processes has dropped significantly.
More new hardware
I obtained a rather new DS10 system, equipped with EV67 Alpha processor and 512 Mb memory: twice as fast, though the external clock is still 600 Mhz, but simply by the processor – and twice as much memory; CD and DVD (readers, that is) are included – but no SCSI controller and disks. Bo big deal, I do have some SCSI controllers available and some disks – but the cables to connect the disk to the controller is missing…
So I installed an older IDE disk in the system, was able to INIT the drive and install VMS 8.3 on it, but the system fails to boot. That is: it does start reading the initial boot loader, but there it ends. I still have to find out what’s going on there.
Or I could install a KZPSA, or KZPBA-CY (or both) in the box, and hook it onto the shared SCSI.Since this is a newer machine than the AlphaServer I tried earlier, it may do the trick.
11-Jul-2010
A bit more on WP
One more mapping line was required to have WP 3.0 working:
map /wp30/wp-admin/ /wp30/wp-admin/index.php
otherwise, the admin page didn’t show up properly.
The biggest problem is with the PHP-engines now. It seems that almost every request launches a new WASD process. These all require a lot of resources – mainly memory, the pagefault rate peaks over 20.000….
10-Jul-2010
A first result
I didn keep sufficient track of things when the main page of WP showed up, although as a plain, non-css’d site, so it took quite some re-searching and trial-and-error – with some good deduction, to get the main page of WordPress3 fully shown. It looks like all of it is working – using the supplied form. Now testing the two I use for the sysmgr and tracks blogs…
I also checked the Admin page – it loads, but with a few errors that may be related to the URL of the ‘site’ – Iĺl have to check that. Also, there is a widget ‘Quickpress’ that took a lot of time to be displayed – and, according the grinding sounds of the disk, it requires a lot of memory: it hardly did the trick:
$
%SYSTEM-W-PAGEFRAG, page file filling up; please create more space
$
%SYSTEM-W-PAGECRIT, page file nearly full; system trying to continue
$
%SYSTEM-W-PAGEFILEFULL, all page or swap files are full; system trying to continue
Ok, pageing IS just basic:
$ sho mem/file
System Memory Resources on 10-JUL-2010 18:40:09.75
Swap File Usage (8KB pages): Index Free Size
DISK$DAPHNE84EFT:[SYS0.SYSEXE]SWAPFILE.SYS
1 1528 1656
Paging File Usage (8KB pages): Index Free Size
DISK$DAPHNE84EFT:[SYS0.SYSEXE]PAGEFILE.SYS
254 15956 33280
Total committed paging file usage: 27142
$
But at least, the admin page came up as well.
This is the current configuration for WP30 that works so far:
redirect /wp30 /wp30/index.php
#redirect /wp30/ /wp30/index.php?
#redirect /wp30/**/ /wp30/**
map /wp30/ /wp30/index.php
set /wp30/*.php script=query=relaxed ods=5
set /wp30/*/*.php* script=query=relaxed ods=5
exec /wp30/*.php (@cgi-bin:[000000]phpwasd.com)/wp30/*.php \
ods=5 script=syntax=unix script=query=none map=once
pass /wp30/* /wp30/* ods=5 search=none dir=noaccess
The out-commented REDIRECT lines cannot be enabled – it will cause the main page run into a loop; but a mapping from /wp30/ to /wp30/index/php seems to be required…