07-Feb-2016

Maintenance
Too busy to add the result of the monthly maintenance job – there were no issues except (of course) quite a number of relay attempts from China…


PMAS statistics for January
Total messages    :   3263 = 100.0 o/o
DNS Blacklisted   :      0 =    .0 o/o (Files:  0)
Relay attempts    :   1841 =  56.4 o/o (Files: 31)
Accepted by PMAS  :   1422 =  43.5 o/o (Files: 31)
  Handled by explicit rule
         Rejected :    527 =  37.0 o/o (processed),  16.1 o/o (all)
         Accepted :    231 =  16.2 o/o (processed),   7.0 o/o (all)
  Handled by content
        Discarded :    224 =  15.7 o/o (processed),   6.8 o/o (all)
     Quarantained :    179 =  12.5 o/o (processed),   5.4 o/o (all)
        Delivered :    261 =  18.3 o/o (processed),   7.9 o/o (all)

Most relay attempts were on three days:

02-JAN-2016 04:58:48.40 - 05:36:50.75 : 112.90.183.133 (363)
12-JAN-2016 16:56:59.42 - 18:14:59.84 : 112.90.146.241 (720)
14-JAN-2016 19:54:54.38 - 21:10:08.53 : 112.90.237.94 (720)

In addition, there were a few from another address – but far less:
21-JAN-2016 07:23:38.68 - 07:24:23.62 : 189.199.26.223 (11)
so less harmful – I don’t bother too much on that one.

(Would I need to pass these indications to law enforcement? For businesses it is an obligation today)

Update of WordPress failed
I downloaded the latest version (4.4.2) and installed it, but upgrading the blogs failed. I still have to some more investigation, but I found one issue: Where underscores weren’t used in the names up to 4.3.1, but in 4.4.2 (and probably 4.4 as well) there is one directory that contains an underscore in the name (.wp-includes.random_compat). This causes problems with the script to revert translation of multiple dots in a filename to underscores; VMS translates the these to underscore and the script reveres this: it becomes (.wp-includes.random^.compat).
So here I have a problem in the script; If this the only one, it is easy to prevent. I could ask to change this to hyphen instead but I doubt it will even happen (I will aslk but won’t rely o the change).
Another – far more nasty issue, is a stack overflow just before I get the PHP warnings: WATCH spits out the details – I removed the extra data, so this is basically what happens:

|19:20:02.16 ERROR    0434 **** NOTICED    CGI:2107, not a strict CGI response|
|19:20:02.17 ERROR    1121 0002 RESPONSE   DCL:5220 (basic-only) 502(502)

 "Script did not provide an acceptable response."|
|19:20:02.17 DCL      4967 0002 DCL        READ SYS$OUTPUT %X00000001 47 bytes|

%TRACE-F-TRACEBACK, symbolic stack dump follows
  image    module    routine             line      rel PC           abs PC      
%SYSTEM-F-STKOVF, stack overflow, PC=FFFFFFFF8083B42C, PS=0000001B
  Improperly handled condition, image exit forced.
    Signal arguments:   Number = 0000000000000003
                        Name   = 0000000000000554
                                 FFFFFFFF8083B42C
                                 000000000000001B
    Register dump:   
     R0  = 0000000000000207  R1  = 0000000000000008  R2  = 000000007B64D550
     R3  = 000000007B68A010  R4  = 000000007B68A018  R5  = 0000000000000090
     R6  = 0000000000000090  R7  = 0000000000000041  R8  = 0000000000000000
     R9  = 000000007CAF9820  R10 = 0000000000000020  R11 = 0000000002055088
     R12 = 000000007ADBA4A6  R13 = FFFFFFFF81951C10  R14 = 0000000000000001
     R15 = 0000000000000007  R16 = 000000007B68A064  R17 = 000000007B68A8A8
     R18 = 0000000064616F6C  R19 = 0000017964616F6C  R20 = 0000000064616F6C
     R21 = 0000000000000000  R22 = 000000000000017A  R23 = 000000007BF9A660
     R24 = 0000000000010001  R25 = 0000000000000001  R26 = 000000007B68A018
     R27 = 0000000000000001  R28 = FFFFFFFF802E373C  R29 = 000000007ADB94E0
     SP  = 000000007ADB94E0  PC  = FFFFFFFF8083B42C  PS  = 200000000000001B

So I reverted to the version that works – have to find out first what’s going on…

Leave a Reply

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