Updated WordPress
Tonight I updated both blogs to WordPress 4.3.1, and consequently Aksimet to the latest version (3.1.3 comes with WordPress 4.3.1 but a new version has been released as well).
No problems whatsoever.
Next, I installed Jetpack – latest version as well – but this cannot be activated: it runs into an error:
Fatal error: Cannot find a library with slug admin-pages/class.jetpack-landing-page. in /sysblog/wp-content/plugins/jetpack/require-lib.php on line 35
The reason is that this plugin seems to require a directorypath [.INC.LIB]. That is: this does exists in the root of this plugin, and accessing it deeper into the structure, the required file does exist:
$ set def wp431:[wp-content.plugins]
$ dir


AKISMET.DIR;1       hello.php;1         index.php;1         JETPACK.DIR;1

Total of 4 files.
$ set def [.jetpack]
$ dir .dir


^.INC.DIR;1         3RD-PARTY.DIR;1     CSS.DIR;1           IMAGES.DIR;1
SCSS.DIR;1          VIEWS.DIR;1

Total of 9 files.
$ dir [.^.INC]


FONTS.DIR;1         footer.php;1        gallery-settings.js;1
GENERICONS.DIR;1    genericons.php;1    header.php;1        IMAGES.DIR;1
IMG.DIR;1           jetpack-admin.js;1  JETPACK-ICONS.DIR;1 jetpack-jitm.js;1
jetpack-modules.js;1                    jetpack-modules^.models.js;1
jetpack-modules^.views.js;1             jetpack.js;1        jp-my-jetpack.js;1
jp.js;1             jquery^.inview.js;1 jquery^.jetpack-resize.js;1
jquery^.jetpack-sync.js;1               jquery^.spin.js;1   LIB.DIR;1
postmessage.js;1    SCSS.DIR;1          spin.js;1

Total of 25 files.
$ dir [.^.INC.lib]


ADMIN-PAGES.DIR;1   class^.color.php;1  MARKDOWN.DIR;1      tonesque.php;1

Total of 4 files.

but for some reason, this file is not reachable. It’s not a matter of protection since all directories are W:RE and files W:R so that should not be a problem..
There must be something within the plugin code that needs to be adapted before this can be used on VMS. The code where the error is generated uses a variable lib_dir , set to WP_CONTENT_DIR and additions:

if ( defined( 'ABSPATH' ) && ! defined( 'WP_CONTENT_DIR' ) ) {
define( 'WP_CONTENT_DIR', ABSPATH . 'wp-content' ); // no trailing slash, full paths only - WP_CONTENT_URL is defined further down

$lib_dir = WP_CONTENT_DIR . '/lib';

and somewhat further down:

$lib_dir = apply_filters( 'jetpack_require_lib_dir', $lib_dir );
$choices = array(

so probably there is something wrong here that needs to be addressed. to have it working on VMS.
For the time being, I can live without this plugin but it would be nice to have it working as well.


Router issue?
Yesterday, I had a large download – almost 6Gb – that I had to retrieve from a site that is connected through a ADSL line – which is a-symmetric – and that showed. It took about 5 hours to get the file – and that shows in the router’s statistics:

Traffic graph
Traffic graph

This morning, I had to restart the router since it had become a bit sluggish, and the NAT session table showed more sessions from my work address than are feasible; so it looks as if dropped connections are not freed where they should. Perhaps I could schedule a reboot of the router once a week, when it usually quiet…


No surprises. The system is stable, the amount of memory in use is constantly about 75%, the number of processes keeps within range (typically somewhere between 60 and 65, but at times less or more, but never over a prolonged period).
Mail holds no surprises either:

Saving PMAS logs to DKA0:[LOGSARCHIVE]PMASSEP2015.zip
PMAS statistics for September
Total messages    :   2499 = 100.0 o/o
DNS Blacklisted   :      0 =    .0 o/o (Files:  0)
Relay attempts    :   1401 =  56.0 o/o (Files: 30)
Accepted by PMAS  :   1098 =  43.9 o/o (Files: 30)
 Handled by explicit rule
        Rejected :    595 =  54.1 o/o (processed),  23.8 o/o (all)
        Accepted :    194 =  17.6 o/o (processed),   7.7 o/o (all)
 Handled by content
       Discarded :    145 =  13.2 o/o (processed),   5.8 o/o (all)
    Quarantained :    138 =  12.5 o/o (processed),   5.5 o/o (all)
       Delivered :     26 =   2.3 o/o (processed),   1.0 o/o (all)

The vast majority of relay attempts was on 13-Sep, from one address and different senders (or recepients – I’ve asked Process on the layout of this logfile):

13-SEP-2015 07:41:42.43|R||rvaeh@grootersnet.nl|xiaonanzi11162@163.com|550 5.7.1 Relaying not allowed: xiaonanzi11162@1`
13-SEP-2015 07:42:08.01|R||ptxc@grootersnet.nl|z13699753428@vip.163.com|550 5.7.1 Relaying not allowed: z13699753428@vi`
13-SEP-2015 09:29:55.50|R||lpd@grootersnet.nl|z13699753428@vip.163.com|550 5.7.1 Relaying not allowed: z13699753428@vip ...

On what Hunter explained, the sender at forges the FROM: line to mimic my domain (so NONE of these messages are actually sent by me) and tries to reach the next person. Quite likely this is the offender trying to get through, or a system to be breached. So now I know the route for investigation.
End Update

Apart from these, there were a few that, according the addresses, were control-messages:

13-SEP-2015 12:08:37.00|R||admin@goodservers.com|joneslarry481@gmail.com|550 5.7.1 Relaying not allowed: joneslarry481`
13-SEP-2015 13:10:19.79|R||server@checking.net|csclus.smtp@gmail.com|550 5.7.1 Relaying not allowed: csclus.smtp@gmail.`
13-SEP-2015 14:27:37.43|R||support@microsoft.com|support@microsoft.com|550 5.7.1 Relaying not allowed: support@microsoft`
13-SEP-2015 14:33:39.42|R||cpanel@www.grootersnet.nl|arcadio.setimmi@yahoo.com|550 5.7.1 Relaying not allowed: arcadi`

That’s fine with me :)

Furthermore, there a a few updates to be installed, no big deal (have done it before) but it just takes time – that I need to make free.

Development system
I got a new version of nxtWare-Remote to test.
Robert’s reply on my issues was I should $ SET PROCESS/PARSE=EXTENDED before installing GNV, Java and NxtWare – and that failing to do so may cause the problems. I’m pretty sure this is set by my LOGIN.COM file – or even SYLOGIN.COM – but it is no problem to double-check.

PHP still bloating
It’s mainly during the admin pages of the blog, that WordPress spits out an error:

%HTTPD-W-NOTICED, 01-OCT-2015 13:28:02, CGI:2107, not a strict CGI response
-NOTICED-I-SERVICE, http://www.grootersnet.nl:80
-NOTICED-I-URI, POST (32 bytes) /sysblog/wp-admin/admin-ajax.php
-NOTICED-I-SCRIPT, /sysblog/wp-admin/admin-ajax.php sysblog:[wp-admin]admin-ajax.php (phpwasd:) SYSBLOG:[WP-ADMIN]admin-ajax.php
-NOTICED-I-CGI, 504850205761726E696E673A20204D6F64756C652027646F (289 bytes) PHP Warning: Module 'dom' already loaded in Unknown on line 0.
-NOTICED-I-RXTX, err:0/0 raw:1321/0 net:1088/0

Quite a number of these, and just in the same PHP source (other ones are now seldom so the reader won’t get such errors any more; Or far less).
I should probably look at this PHP source to find out what’s causing the error, perhaps it is gone after the update?? Or mention it on the WordPress site…

Only one today: It seems this script tried to output something but cannot write (of course: theer is no need to write in the directory that holds the PHP-code: So it is set ReadOnly – as it should be):

%HTTPD-W-NOTICED, 01-OCT-2015 13:36:02, CGI:2107, not a strict CGI response
-NOTICED-I-SERVICE, http://www.grootersnet.nl:80
-NOTICED-I-URI, POST (32 bytes) /sysblog/wp-admin/admin-ajax.php
-NOTICED-I-SCRIPT, /sysblog/wp-admin/admin-ajax.php sysblog:[wp-admin]admin-ajax.php (phpwasd:) SYSBLOG:[WP-ADMIN]admin-ajax.php
-NOTICED-I-CGI, 556E61626C6520746F206F70656E2027707468726561645F (71 bytes) Unable to open 'pthread_dump.log' for write, using standard output only
-NOTICED-I-RXTX, err:0/0 raw:1088/0 net:1088/0

so there is something to be changed in that script anyway…


Moved the images of Trips, Tracks and Travels
The size of the logical disk containing the images of our “expeditions” was extended once before to 15 Gb, but even that is not sufficient; the next bit: our fall trip into Germany (2 years ago – it’s finally done) won’t fit, let alone what is still to come (there still is some work to be done). I do have spare 32Gb disks available so I decided to $ INIT one of them and move the whole directory tree containing the images over to a new directory on that disk, and add the latest album. To access them, I added this directory into the logical that contains all that is part of this environment (including the blog), leaving the now (hopefully) obsolete tree intact:


Because of this, there was no need at all to add anything in the WASD configuration because all that is referred to is this logical configuration:
redirect /tracks /tracks/index.php
map /tracks**/ /tracks*/index.php
exec+ /tracks/**.php* (phpwasd:)/tracks/*.php* ods=5
pass /tracks/000000/* /tracks/* ods=5 search=none dir=noaccess
pass /tracks/* /tracks/* ods=5 search=none dir=noaccess

Of course, this double definition of the image directory isn’t needed at all. Since all data is copied, the old environment can simply be made inaccessible, by one simple DCL statemnent:

$ def/sys/exec tracks web2016:[trackimages.]/transs=conc, -
_$ web_disk2:[blogs.tracks.]/trans=conc, -
_$ wp43:/trans=conc

without touching anything else.

How I love the elegance of OpenVMS :)

Setting up a development environment
For some contrast…
I have two Personal Workstations at had: both 256 Mb, Alpha EV56 at 500 Mh – though one has been speeded up to run at the top available: 600 Mhz – it means that the PCI and memory busses are at full speed as well.
This machine got the memory of the other so it now has a whopping 512 Mb of memory :)
Meet Daphne: OpenVMS 8.4, booted in the cluster but with it’s own environment, compilers at all. The disk was thought to be 9Gb but turned out to be a 4.3 Gb one. It contained MySQL, SWS, WASD and WordPress versions so there was little room left. So all this was removed as well as any other data – since the system is booted into the cluster and all disks are designed to be mounted clusterwide, I can use the abundant space on Diana for storage, but have the work done on Daphne.
So far, it’s all as expected.
I could stop here and start developing, but I promised eCube half a year ago to do some testing on their development (Eclipse-based) platform; I proposed a small addition (to be abled to use it on a rooted environment where different parts of an application are stored in separate sub-trees) so I needed to install some extra software: the Nxtware Remote toolsuite. That needs Java and GNV, the toolbox to Unixify an OpenVMS environment to ease porting of *x based software more easily.
Installing the IDE (eCube Nxtware) is no problem.
Installing JAVA is no problem.
Installing GNV is no problem. Well, mostly; there are a few updates to be installed but the question is where to get them? There are several places on Sourceforge and the documentation on the site isn’t exactly helping… Installed these, but it is questionable whether these are really the lastest versions (I found newer ones yesterday…)
Configuring Nxtware shows I need to change a few system and process parameters. Process parameters for Java (otherwise it may not work), system parameters likely for the Nxtware server process. After that, configuration starts with extracting files that will be needed by either the server or clients – and there trouble starts: It cannot extract and process < .PAS> en < .COB> files; but otherwise it seems to run ton the end. Starting the server will tall….

But first, I’ll read the docs.


This shows that after the last reboot (when the new memory was installed) the load on CPU, process slots and memory has stablelized:

Load in one week
Load in one week

So it’s only memory usage that increased up to the current level and doesn’t change very much – just a spike that is consistent with the extra processes, and so is paging: New processes require memory and of course, this must be acquired and distributed – hence tis paging.
These spikes in number of processes. memory usage and paging occur between 6:45 and 7:00, and between 18:45 and 19:00, every day. You might expect (as I did :)) that there is a batch job that runs at these moments, but $SHO QUE shows none:
$ sho que
Batch queue BACKUP, idle, on DIANA::

Printer queue DCPS_QUEUE, idle, on DIANA::"IP_RawTCP/",
  mounted form DCPS$DEFAULT (stock=DEFAULT)

Printer queue HPTN2100, stopped, on DIANA::"",
  mounted form DEFAULT

Batch queue NORMAL, idle, on DIANA::

Generic batch queue SYS$BATCH

  Entry  Jobname         Username             Status
  -----  -------         --------             ------
    218  PreciseMail Stats
                         SYSTEM               Holding until  9-SEP-2015 15:05:00
    207  PreciseMail Notify
                         SYSTEM               Holding until  9-SEP-2015 15:30:00
    190  reset_syslog    SYSTEM               Holding until 10-SEP-2015 00:00:00
    191  scan_log        SYSTEM               Holding until 10-SEP-2015 00:00:00
    192  do_backup       SYSTEM               Holding until 10-SEP-2015 00:00:00
    195  PreciseMail Nightly
                         SYSTEM               Holding until 10-SEP-2015 00:05:00
    200  PreciseMail AutoUpdate
                         SYSTEM               Holding until 10-SEP-2015 02:00:00
    810  save_logs       SYSTEM               Holding until  1-OCT-2015 01:00:00

Generic printer queue SYS$PRINT

Batch queue SYS$START, stopped, on DIANA::

Batch queue T4$BATCH, available, on DIANA::

  Entry  Jobname         Username             Status
  -----  -------         --------             ------
    143  T4$COLLECT      SYSTEM               Executing
    189  T4$COLLECT      SYSTEM               Holding until  9-SEP-2015 23:59:00

Generic server queue TCPIP$SMTP

Generic server queue TCPIP$SMTP_DIANA_00

Server queue TCPIP$SMTP_DIANA_01, stopped, on DIANA::, mounted form DEFAULT

Server queue TCPIP$SMTP_DIANA_1, idle, on DIANA::, mounted form DEFAULT

So now it is a matter of looking for logfiles created on these moments; perhaps $ ACCor $ ANA/AUDIT will show something :)
Track images moved
The images of all our trips, tracks and travels now take about 10 Gb – almost the full size of the logical disk that contains all of the web data. Adding another 1 Gb (or more) of the Lahn Wanderweg (walked in 2014), now (almost) ready for publication, would not fit. So I added another 32Gb disk to the system, initialized it and mover all the images to that physical disk. I could of course have created a logical disk of sufficient size (say 20Gb) which is, indeed, easier to move, and backup (just a single file); but I can do so on the current disk, once the files have been removed, the original logical disk could be used as well; just adding the other files to this drive as well – bit by bit – and re-create the disk-containers on that disk once more – in the appropriate size.
This move however gives me time and space to maneuver.
Another addition: Images and videos of Tessa – our Little Black Devil. Video won’t show fluently at the moment because the disk is heavily loaded (because backup of the track-images).


PHP messages
Over the last week – running without throttle, an elevated execution time for PHP scripts and the max of internal memory, PHP seems to work fine; it may be faster (and probably will be) if PHPSHR.EXE is installed, a step to be taken this weekend.
All messages I had in this period:
6 times:

%%%%%%%%%%% OPCOM 1-SEP-2015 09:48:06.60 %%%%%%%%%%%
Message from user HTTP$SERVER on DIANA
Process WASD:80 reports
%HTTPD-W-NOTICED, CGI:1997, not a strict CGI response
-HTTPD-I-SCRIPT, /sysblog/wp-admin/admin-ajax.php (sysblog:[wp-admin]admin-ajax.php) phpwasd:
-HTTPD-I-CGI, 504850205761726E696E673A20204D6F64756C652027646F (2048 bytes) PHP Warning: Module 'dom' already loaded in Unknown on line 0.

(of course on different times, but always in the same module)
and one:

%%%%%%%%%%% OPCOM 3-SEP-2015 13:11:24.71 %%%%%%%%%%%
Message from user HTTP$SERVER on DIANA
Process WASD:80 reports
%HTTPD-W-NOTICED, CGI:2107, not a strict CGI response
-HTTPD-I-SCRIPT, /sysblog/index.php (sysblog:[000000]index.php) phpwasd:
-HTTPD-I-CGI, 2553595354454D2D462D41434356494F2C20616363657373 (118 bytes) %SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=000000000592C000, PC=FFFFFFFF8083D9B8, PS=0000001B

Of course the reason may have been that there was no traffic – but that is not the case: WASD logfiles do show quite a number of entries to SYSBLOG and TRACKS- and not just the ones by the worker processes (since these originate from my address, they won’t be shown there, these are filtered out).


The regular maintenace job has shown no surprises, except that the number of messages is low – less than 1000:

PMAS statistics for August
Total messages    :    976 = 100.0 o/o
DNS Blacklisted   :      0 =    .0 o/o (Files:  0)
Relay attempts    :    128 =  13.1 o/o (Files: 26)
Accepted by PMAS  :    848 =  86.8 o/o (Files: 29)
  Handled by explicit rule
         Rejected :    308 =  36.3 o/o (processed),  31.5 o/o (all)
         Accepted :    229 =  27.0 o/o (processed),  23.4 o/o (all)
  Handled by content
        Discarded :    160 =  18.8 o/o (processed),  16.3 o/o (all)
     Quarantained :    124 =  14.6 o/o (processed),  12.7 o/o (all)
        Delivered :     27 =   3.1 o/o (processed),   2.7 o/o (all)

System usage shows the changes in memory of last month: from 512 Mb to 2 Gb, back to 512 Mb due to memory issues, up to to 1.5 Gb after the big outage and latest to 2 Gb valiud memory (where all has been replaced. The differences in CPU-usage haven’t changed much, nor has IO, direct (being disk), buffered and network (mainly internet) though there are slightly less buffered IO’s since throttling has been disabled:

Hyperspy data over August
Hyperspy data over August

The system seems to be very stable now, so AUTOGEN can be run shortly…


New memory
New memory has arrived: the full 2 Gb, now stated “Compaq branded”. I installed it all tonight and so far it’s all in working order. The first set will be destroyed, because it is too unreliable containing these bad buffers.
Throttle and Max-execution-time
The problems with WordPress seems twofold.
First, as I expected, WASD’s throttle causes problems. Immediately after Diana was started, I started the blog. It stated showing up but ended halfway the calendar or the links, or gave me a 503 error (too many processes in FIFO) but never showed the text. And there were no other processes accessing the blog except for this site itself:
First of all, I trued to give the processes a bit more room: all three times as much. That did help a bit, but now it became clear that the maximum execution time (set to 90 seconds) was too low. So I gave the process two minutes to execute, and disabled throttling – for now, until I find a solution to throttle only incoming requests from other sites than my own.
Somethin like:
if (!remote-addr:(my address) throttle=5,0,0,8,00:02:00, 00:05:00
So the same rule as before, but limited to ‘foreign’ addresses, to prevent an overload.
The overall effect seems dramatic, especially in the number of processes: this dropped!
but it shows that WordPress – at least: most likely – may start more than just a few processes…


Most definitely.
It shows when looking at the logs:
%HTTPD-W-NOTICED, 27-AUG-2015 06:24:04, CGI:2107, not a strict CGI response
-NOTICED-I-SERVICE, http://www.grootersnet.nl:80
-NOTICED-I-URI, GET (18 bytes) /sysblog/?m=201201
-NOTICED-I-SCRIPT, /sysblog/index.php sysblog:[000000]index.php (phpwasd:) SYSBLOG:[000000]index.php
-NOTICED-I-CGI, 2553595354454D2D462D41424F52542C2061626F7274 (22 bytes) %SYSTEM-F-ABORT, abort
-NOTICED-I-RXTX, err:0/0 raw:194/0 net:194/0
%HTTPD-W-NOTICED, 27-AUG-2015 06:27:36, CGI:2107, not a strict CGI response
-NOTICED-I-SERVICE, http://www.grootersnet.nl:80
-NOTICED-I-URI, GET (9 bytes) /sysblog/
-NOTICED-I-SCRIPT, /sysblog/index.php sysblog:[000000]index.php (phpwasd:) SYSBLOG:[000000]index.php
-NOTICED-I-CGI, 2553595354454D2D462D41424F52542C2061626F7274 (22 bytes) %SYSTEM-F-ABORT, abort
-NOTICED-I-RXTX, err:0/0 raw:357/0 net:357/0
%HTTPD-W-NOTICED, 27-AUG-2015 06:27:52, CGI:2107, not a strict CGI response
-NOTICED-I-SERVICE, http://www.grootersnet.nl:80
-NOTICED-I-URI, GET (9 bytes) /sysblog/
-NOTICED-I-SCRIPT, /sysblog/index.php sysblog:[000000]index.php (phpwasd:) SYSBLOG:[000000]index.php
-NOTICED-I-CGI, 2553595354454D2D462D41424F52542C2061626F7274 (22 bytes) %SYSTEM-F-ABORT, abort
-NOTICED-I-RXTX, err:0/0 raw:357/0 net:357/0
%HTTPD-W-NOTICED, 27-AUG-2015 06:27:54, CGI:2107, not a strict CGI response
-NOTICED-I-SERVICE, http://www.grootersnet.nl:80
-NOTICED-I-URI, GET (18 bytes) /sysblog/index.php
-NOTICED-I-SCRIPT, /sysblog/index.php sysblog:[000000]index.php (phpwasd:) SYSBLOG:[000000]index.php
-NOTICED-I-CGI, 2553595354454D2D462D41424F52542C2061626F7274 (22 bytes) %SYSTEM-F-ABORT, abort
-NOTICED-I-RXTX, err:0/0 raw:366/0 net:366/0
%HTTPD-W-NOTICED, 27-AUG-2015 06:28:17, CGI:2107, not a strict CGI response
-NOTICED-I-SERVICE, http://www.grootersnet.nl:80
-NOTICED-I-URI, GET (16 bytes) /sysblog/?p=1095
-NOTICED-I-SCRIPT, /sysblog/index.php sysblog:[000000]index.php (phpwasd:) SYSBLOG:[000000]index.php
-NOTICED-I-CGI, 2553595354454D2D462D41424F52542C2061626F7274 (22 bytes) %SYSTEM-F-ABORT, abort
-NOTICED-I-RXTX, err:0/0 raw:357/0 net:357/0

The address is my own. And when looking at the active processes, there is a number of WASD processes that run SYSBLOG, and some of them have the same address. Some of them show up in the list that is throttled.

Settings for the blogs show it can take some time for such a process to continue:

Throttle Report
Throttle Report

and it may be that this causes problems if one or some of the worker processes (there may be several, concurrent or in sequence) are stuck in the FIFO queue and time out. Likely scenario, given the number of entries that got into the FIFO queue; it exceeds any number I’ve seen with the older WordPress version – even with PHP 5.2-13…

This is something that definitely needs more investigation: the combination of throttle and PHP to begin with, but it is very likely caused by WordPress: What to look for are the number of processes are actually involved, what they do and how they interact. IIRC, in earlier investigations I found that WordPress will cause several WASD worker processes to be started, apparently either processing PHP code, or executing the results. If these processes depend on each other, where one waits for another to finish, and the one executing is held in the FIFO queue, of just rejected because the queue is exhausted, there is trouble.
For this, I set up my old Personal WorkStation 600au again as Daphne, after adding memory (to a whopping 512 Mb) and booted it into the cluster. Now it’s setting up the test environment (MySQL is already installed, need the same WASD, PHP and WordPress versions and setup, and data as on the main system) and see how it behaves: so there will also be a need for some software to keep track of all processes in the system.

Since it is within the cluster, I could easily refer to the real stuff as well, but execute it here. Just a matter of the right logicals and WASD mapping..
A difference in load
some days, I check the load of the previous day. Yesterday’s load was quite different than the one a few days back:

Load over26-Aug-2015
Load over26-Aug-2015

I did notice a site from Russia that constantly poked one of the WordPress files and that forced me to restart WASD (silently) on that day about 11:00 UTC, and after that, the load has been fairly even, like this one.
This ‘ user’ may have caused problems by continuously sending these requests, causing the FIFO queue to be constantly exhausted (some requests returned a 503-error – “Server unavailable” – as a result).
So yet another thing toe look at.
On the memory
I contacted the supplier on the memory issues, and he will replace the bad one (well, two of them to have the same batch in that bank). But shortly afterwards, he asked me to send him a picture of one of the chips on the DIMM:
Buffer chip
Buffer chip

Within a few hours, I got the answer:

And there is the problem.
These DIMMS (we purchased these from HP!) are bad. The buffer chips are some that were intermittently defective
causing no apparent reason for failure.
I am sending 2GB of memory. Please do not resell the memory. please destroy it and send me a photo of it crushed or damaged as it should not find its way back into the marketplace

First of all: Shame on HP. David is right: These should be removed from the circuit.
As soon as the new memory has arrived and is installed and has proven to be functioning well, these DIMMs will be destroyed. There is however one problem I have to tackle: VAT. This is a repair but customs won’t buy that. It may be circumvented by using mail, but:

I will send Fedex. I have had people hit up for large fees to with the mail service. I did notate that it was a repair return so you can tell Fedex to check their records.
You will need to reference the original fedex tracking no.

That’s to be done….(luckily I did’t remove the original mail).


Changes in load
Something has changed: where over a day there was a continuous change in CPU usage, it changed to peak every 90 minutes or so; drop significantly and gradually increase to about 80% – an drop again:
2015-08-24_09-29-33.No idea yest where this comes from….
Changing the execution time of the PHP processes didn’t help much. But before I could add something, the blog didn’t show up; that is: it started displaying but broke halfway. So I started the admin pages and found that there were quite a lot of requests that succeeded, others stalled, or simply broke: network connections dropped, processes exited…So there is another possible cause: the throttle; intended to prevent overload, it now bites back: PHPWASD does start a number of worker processes and I already noticed that this version of wWordpress puts quite a load on the resources. So a max of 5 may be too low.
So I’ll increase that.