The key is in the error messages you logged in watch.

First, you did not clean out the old extension files when you installed the new PHP kit.  I should probably make an explicit reference to the need for that but you are trying to load 5.2 extensions with 5.3.  That is the cause of all of the SYSTEM-F-SHRIDMISMAT errors.

Second, you are still trying to load extensions in the PHP.INI file that are now built into the PHPSHR image itself (because other extensions reference them).  Take a look at the php.ini-* files that came with the kit to see which extensions are still dynamic (or, just look at the list of php_*.exe files in the zip file).  Once you have the kit installed you can issue the command 'php -nm' to see the list of built-in extensions.

Third, you should probably take a look at the PHP.NET web site and look at the differences between PHP 5.2 and 5.3.  Specifically, you need to edit your php.ini file so that you no longer get the various 'deprecated' warning messages (the included php.ini-* files can help with this).  As long as the warning messages are appearing, WASD will not see a proper CGI response and will issue the 502 error.

Mark Berryman

On Mar 25, 2012, at 11:54 AM, Willem Grooters wrote:

> In  addition:
> 
> I copied all files from MB's distribution to the right spot - and got error mesaages about
> depricated code, and about a missing extension - probably php_mysqli.exe; This wasn't in the
> list previously, so I added it.
> Next start also ends in the smae 302-error, but now the messages appear in the WATCH output:
> see attachement.
> 
> Willem
> 
> On Sun, 25 Mar 2012 19:24:47 +0200 Willem Grooters <Willem@grootersnet.nl> wrote:
>> I have been attempting to update PHP and all related stuff.
>> Having used Mark Berryman's port, I downloaded tha latest version form his site, and PHPWASDD
>> 1.4.3 from WASD.
>> I installed the PHP port on ht_root:[php.AXP]. put the main sources in [.BIN] and the scripts
>> in [.SCRIPTS]. Since the kit didn't come with extensions, I first didn't bother too much. The
>> startup file was left ion HT_ROOT:[PHP], from where I executed the procedure to set logicals
>> right:
>> 
>> $ sho log php*/full
>> 
>> (LNM$PROCESS_TABLE)     [kernel]
>>                       [no protection information]
>> 
>> (LNM$JOB_82678B40)      [kernel]  [shareable]  [Quota=(59152,60000)]
>>                       [Protection=(RWCD,RWCD,,)]  [Owner=[SYSTEM]]
>> 
>> (LNM$GROUP_000001)      [kernel]  [shareable,group]
>>                       [Protection=(RWCD,R,R,)]  [Owner=[1,*]]
>> 
>> (LNM$SYSTEM_TABLE)      [kernel]  [shareable,system]
>>                       [Protection=(RWC,RWC,R,R)]  [Owner=[SYSTEM]]
>> 
>> "PHP-BIN" [exec] = "php_root:[scripts]"
>> "PHPMYADMIN" [exec] = "web_disk2:[private.phpmyadmin.]" [concealed]
>> "PHPSHR" [exec] = "php_root:[bin]phpshr.exe"
>> "PHPWASDSHR" [exec] = "php_root:[bin]phpshr.exe"
>> "PHP_ROOT" [exec] = "$116$DKA100:[WEB.HT_ROOT.php.AXP.]" [concealed]
>> "PHP_VERSION" [exec] = "5.3"
>> 
>> (LNM$SYSCLUSTER_TABLE)  [kernel]  [shareable,system]
>>                       [Protection=(RWC,RWC,R,R)]  [Owner=[SYSTEM]]
>> 
>> (DECW$LOGICAL_NAMES)    [exec]  [shareable]
>>                       [Protection=(RWCD,RWCD,R,R)]  [Owner=[SYSTEM]]
>> $
>> 
>> Next, PHPWASD was installed in place: HT_ROOT:[SRC.PHP], and BUILD_PHPWASD executed. This
>> leaves PHPWASD on te HT_EXE directory so I copied the file to CGI_EXE, being:
>> 
>> $ sho log cgi_exe
>>  "CGI_EXE" = "HT_ROOT:[AXP-BIN]" (LNM$SYSTEM_TABLE)
>> 
>> because the maping states the same location for this file:
>> 
>> exec /tracks/**.php (cgi_exe:phpwasd.exe)/tracks/*.php \
>>      ods=5 script=syntax=unix script=query=none map=once
>> 
>> I restarted the webserver, but now all my blogs return 
>> 
>> ERROR 502  -  External agent did not respond (or not acceptably). 
>> 
>> Mark Berryman's kit comes with PHP5WASD executable so I tried that, but that is unusable
>> without changing the configuration files...
>> 
>> I have found two problems:
>> 
>> First, the file PHPWASDSHR could not be started. Which is weird since the file does exists and
>> is executable:
>> 
>> $ sho log phpwasdshr
>>  "PHPWASDSHR" = "php_root:[bin]phpshr.exe" (LNM$SYSTEM_TABLE)
>> $ dir/sec/dat phpwasdshr
>> 
>> Directory PHP_ROOT:[bin]
>> 
>> PHPSHR.EXE;2          7-AUG-2011 20:48:22.15  [SYSTEM]                         (
>> RWED,RWED,RE,RE)
>> 
>> Total of 1 file.
>> $ sho log php_root
>>  "PHP_ROOT" = "$116$DKA100:[WEB.HT_ROOT.php.AXP.]" (LNM$SYSTEM_TABLE)
>> $ dir ht_root:[000000]php.dir/sec
>> 
>> Directory HT_ROOT:[000000]
>> 
>> php.DIR;1            [SYSTEM]                         (RWE,RWE,RE,RE)
>>         (DEFAULT_PROTECTION,SYSTEM:RWED,OWNER:RWED,GROUP:RE,WORLD:RE)
>> 
>> Total of 1 file.
>> 
>> I have no clue why this was signalled, and I cannot reproduce is, because after some
>> experiments - including trying MB's PHP5WASD.EXE - I run into an access violation - see
>> attached WATCH file (zipped to conserve space)
>> 
>> I use PHP.INI as is in MB's kit: no extensions enabled ans still 8Mb of storage (in the full
>> set, I will need extensions and will extend the space, as I had before)
>> 
>> How do I get it all running again?
>> 
>> WIllem
>> 
>> [[WATCH1.zip]]
> <WATCH2.zip>