26-Oct-2015

A few issues
There was too little time last week to look if everything works properly, so it was only this morning that I found that there are a few issues, but only in the operational site (so far), that needs to be looked at: The list op OPERATOR logs won’t show up (gives me an extract of the access log), for instance, though the link is all right. So there may be more that’s not working as it should. The question is, however, why this happened. There was no change in environment that I’m aware of. So there is some investigation to do.
The result:
Running the procedure that creates the index file, didn’t finish as intended:

$ @SMAN:[com]indexoperlogs.com
Creating index file of operator and FTP logs
%RMS-F-FUL, device full (insufficient space for allocation)

So where has the space gone? Creating a list on this device won’t work either. so put it elsewhere (with enough free space):
$ dir/out=$116$dka106:[000000]x.x/size web_disk2:[000000...]
$

to get a full view on all what’s on the disk (which is actually a logical one).

No matter what, I can remove the old WordPress versions, saving me some 100.000 blocks. the big win however is removing all images of Trips, Tracks and Travels from the disk, because these are moved a few weeks ago to another disk, and it seems to work fine. That means 10 Gb….. Of course, I used a script (Q&D) for this operation.
Why the disk was so full: I added a view videos to Tessa and som eother stuff on a disk that was already pretty filled up. It fitted – until the operatorlog.html file was once more created – a week ago… The logfiles were a bit larger than normal because Daphne was started (and this logs on Diana as well).

And the text on the home page needs to be updated and set s well, this is not done automatically, and I didn’t add this on the last reboot.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.