Month: May 2018

Iris setup continued
Startup procedures have been adapted – there were still a few things wrong: Since there was no real database yet (I created one but didn’t load it with any data) shutdown would fail since the login-information – using password – was wrong: There were no passwords yet. WASD wouldn’t start because of a typo in one of the startup-procedures, and the PHP-environment had to be set up – and adapted – as well.
All these things have now been done: The database can be started (and stopped), WASD starts up – there is one more thing to check: LIBZ must still be located and installed – and PHP (7.0, to begin with) has been installed and is available: All required logicals are now set.
Next, I copied the MySQL backup from Diana, which is actually a SQL file. Sourced it into the database (have to revert the changes in startup to hold the original login-information which has been restored…) and installed the latest version of WordPress (4.9.5), and copied the security information to Iris as well.

Next stage: change startup-procedure, install the blogs and tracking-images from Diana, and the WASD configuration files – change the so I can access the blogs – have to set things up in the router as well to address the right servers.

Maintenance jobs
No suprises in the monthly run. Mail is OK:

PMAS statistics for April
Total messages    :   2932 = 100.0 o/o
DNS Blacklisted   :      0 =    .0 o/o (Files:  0)
Relay attempts    :    410 =  13.9 o/o (Files: 30)
Accepted by PMAS  :   2522 =  86.0 o/o (Files: 30)
  Handled by explicit rule
         Rejected :   1916 =  75.9 o/o (processed),  65.3 o/o (all)
         Accepted :    140 =   5.5 o/o (processed),   4.7 o/o (all)
  Handled by content
        Discarded :    274 =  10.8 o/o (processed),   9.3 o/o (all)
     Quarantained :    163 =   6.4 o/o (processed),   5.5 o/o (all)
        Delivered :     29 =   1.1 o/o (processed),    .9 o/o (all)

Even the number of relay attempts is low: 2nd and 26th had about 190 attempts – both files are 56 blocks in size:
Again, using a dummy user within this account, and trying to reach a gmail-address:
02-Apr-2018 189 attempts between 06:28:36.69 and 06:32:07.00, address 104.168.152.83, to 1029mandaditos@gmail.com
26-Apr-2018 191 attempts between 17:11:35.46 and 17:15:35.00, address 104.168.158.48 to 1029mandaditos@gmail.com
The address is hosted as hostswinds.com – again….

Webserver update gone wrong
05-Apr-2018 the webserver had been updated but it was only last Monday I noted something was very wrong: None of the imeages in the Tracks environmemt was accessable: It all ran into 404 error (File not found). It started when the old version (that failed to react on exit command…) kept the newly installed version from starting. Nothing was wrong at that moment – until I forced it to stop: And from one moment to another, all accesses to these files were gone. You could note it in the access log:


54.36.148.95 - - [05/Apr/2018:10:45:57 +0000] "GET /Tracks/donauradweg2/11-05/slides/38-Pavement.html HTTP/1.1" 200 3652
54.36.149.25 - - [05/Apr/2018:10:46:45 +0000] "GET /Tracks/donauradweg2/18-05/CastleHill/55-TheFront.jpg HTTP/1.1" 200 1111326
180.76.15.153 - - [05/Apr/2018:10:47:01 +0000] "GET /Tracks/USA2004/31-Jul/slides/04-BlueUoachitaRange.html HTTP/1.1" 200 4382
46.229.168.71 - - [05/Apr/2018:10:47:09 +0000] "GET /tracks/italy2009/26-05-SwissWalk/slides/23-HangingGarden.html HTTP/1.1" 200 3638
54.36.148.11 - - [05/Apr/2018:10:47:22 +0000] "GET /Tracks/Scotland2007/10-Jun/slides/08-Quai-orig.html HTTP/1.1" 200 3870
46.229.168.68 - - [05/Apr/2018:10:47:38 +0000] "GET /Tracks/GroeneHart/Woerden_IJsselstein/slides/10-MontfoortEntrance.html HTTP/1.1" 200 4289
46.229.168.73 - - [05/Apr/2018:10:48:36 +0000] "GET /tracks/rheinsteig-2/03-09/slides/02-Tree.html HTTP/1.1" 200 4725
54.36.148.118 - - [05/Apr/2018:10:49:26 +0000] "GET /tracks/havezatenpad/dalfsen-zwolle/31-Stadion_jpg_orig.html HTTP/1.1" 200 1283


Here (10:49:42, according server log, I killed WASD by STOP/ID, the new version starts up. Next lines are of this server.


180.76.15.157 - - [05/Apr/2018:10:49:46 +0000] "GET /Tracks/Scotland2007/08-Jun/slides/06-LochTulla.html HTTP/1.1" 404 921
46.229.173.137 - - [05/Apr/2018:10:49:53 +0000] "GET /Tracks/USA2004/23-Jul/09-GoingRound/slides/04-Tower-orig.html HTTP/1.1" 404 921
180.76.15.21 - - [05/Apr/2018:10:50:41 +0000] "GET /Tracks/USA2004/21-Jul/slides/08-KimLooksOut.html HTTP/1.1" 404 921
46.229.168.74 - - [05/Apr/2018:10:52:09 +0000] "GET /tracks/rheinsteig-2/01-09/slides/13-StateBorder-orig.html HTTP/1.1" 404 921
46.229.168.74 - - [05/Apr/2018:10:52:22 +0000] "GET /tracks/italy2009/24-05-MainLand/slides/41-AlongTheCanal.html HTTP/1.1" 404 921
46.229.168.78 - - [05/Apr/2018:10:52:54 +0000] "GET /Tracks/Havezatenpad/Oldenzaal-Drienerlo/slides/06-WayUp.html HTTP/1.1" 404 921
46.229.168.76 - - [05/Apr/2018:10:53:50 +0000] "GET /tracks/lahnsteig/0410/slides/17-Fruit.html HTTP/1.1" 404 921
46.229.168.80 - - [05/Apr/2018:10:54:17 +0000] "GET /Tracks/Scotland2007/13-Jun/JedburghAbbey/slides/24-Artwork.html HTTP/1.1" 404 921


I notified Mark Daniel and he located the bug within days (he’s on vacation…(, sent out a fix to be applied and this was applied this morning, restarted this new version. The problem os now solved.

However, he found something in IP traffic that causes delay: RTT of about 300Ms – probably caused by the fact that about 50% of thepackets are dropped.

What causes this: router, system??? Something to be investigated…