topic Re: WASD - PHP problem in Operating System - OpenVMS

WASD - PHP problem

Willem Grooters — Thu, 05 Oct 2006 15:23:38 GMT

(Crossposted to info-wasd-request@vsm.com.au)

Since I have no support contract and PHPSHR from CSWS_PHP 1,3 is involved, HP might be interested (?):

I got a crash of WASDPHP.EXE....

The package I tried is E107 version 0.7.5 (www.e107.org).

Installation, including creation of a MySQL database - went flawlessly, but as soon as I try to access it's start-script (index.php) it causes problems. Since this is PHP code I traced the PHP code where I discovered that WASDPHP crashed in DECCRRTL_V56 even before executing ANY PHP code.

I did some investigation and found that the package had created MyISAM tables in an otherwise INNODB MySQL database (MySQL 4.1). So I changed all references in the code where MySql is mentioned, to InnoDB amd
recreated the database - but that made no difference. Next I checked the format of the php CODE - it's all Stream-LF, max record size
32767, but carriage return carriage control. Next, I chnaged RAT to NONE but there was no difference either.

PHPMYADMIN - as it says: PHP code as well, has no problem and runs fine.

Attached: WATCH en PHP-verification output (as WASD will deliver REALTIME).

Re: WASD - PHP problem

Karl Rohwedder — Sat, 07 Oct 2006 03:35:29 GMT

Willem,

no specific clue to your problem, but there is an update kit for CSWS_PHP available and Mark Daniels has written some notes on how to integrate that into WASD. Perhaps you should try this one 1st?

regards Kalle

Re: WASD - PHP problem

Jean-François Piéronne — Sun, 08 Oct 2006 05:19:37 GMT

Hi Willem,

be sure to use the lastest WASDPHP RTE, if I remember correctly Mark has fix some problems around accvio in recent kit.

Creating MyISAM table instead of InnoDB table is not related, only the server use this information to call the correct engine to retreive data. You can only expect various data corruption...

Not related, I have a MySQL 5.1.11 kit, if you want to try it let me know? This is the latest 5.1 beta verson available.

JF

Re: WASD - PHP problem

Willem Grooters — Sun, 08 Oct 2006 13:57:33 GMT

WASD 9.1.4, latest version of Mark's PHP engine (1.3.3) and the patch of CSWS PHP - and I did an @INSTALL UPDATE after that. (but I agree that there might ave been a little glitch there. But given the release notes, this would have happened without the PHPSHR update (I guess), though this is one area to investigate (get the new sources...)

I'll try to dig deeper into this - getting mode detailsed information.

Re: WASD - PHP problem

Willem Grooters — Sun, 08 Oct 2006 14:35:45 GMT

For what it's worth:

I rebuilt PHPWASD but now with LIST and MAP, using the original CSWS-PHP 1.3 files, got somehat different locations it these make more sense than what I got before. As you can see, it's a call to some PHPSHR routine that causes havock:

php_execute_script (&ZendFileHandle CLS_CC ELS_CC PLS_CC)

in this particular case.

Re: WASD - PHP problem

Wim Van den Wyngaert — Mon, 09 Oct 2006 03:06:34 GMT

Willem,

I gave up on PHP. See also http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=792770

You can try to do a set watch to see what is being accessed. Might help.

Wim

Re: WASD - PHP problem

Willem Grooters — Tue, 10 Oct 2006 04:24:57 GMT

I did that (see attachement on first entry) but that just showed that EXECUTE will cause a crash - which is confirmed after rebuilding this program (see othet attachement). It must have been somewhere inside PHPSHR calling a DECC function, given the call stack. I do have a full MAP file of the WASDPHP image but that didn't tell me very much more. I'll need the full code of PHPSHR (latest release - and that isn't available yet (I think)).

Re: WASD - PHP problem

Wim Van den Wyngaert — Tue, 10 Oct 2006 06:33:55 GMT

Willem,

I mean "set watch file/class=all" in dcl. Just before the execution of the exe that crashes.

Wim

Re: WASD - PHP problem

Willem Grooters — Thu, 26 Oct 2006 14:51:37 GMT

Wim,
As you will see (see attachement on previous post) it is myt impression that there is nothing wrong in the files themselves. As stated, other PHP packages have no trouble at all in running, and protection et all are all the same (W:RE on ALL files, including directories). My impression therefore is that there must be something wrong in the code that handles execution. Since PHPSHR (as delivered by HP!) is deeply involved, I'm afraid I'll have to wait for Engineering's good will (and time).
JF,
I would like to try MySQL5.1 - if I could rebuilt the PHPMYSQL module. (I know how to do that ;-))

Re: WASD - PHP problem

Jean-François Piéronne — Fri, 27 Oct 2006 00:37:48 GMT

Willem,

I will send you, by email, how to download and install MySQL 5.1.

JF

Re: WASD - PHP problem

Willem Grooters — Fri, 10 Aug 2007 05:58:46 GMT

Some more problems found, causing problems, have asked HP when a new release can be expected without these problems. We'll have to live with an incomplete and, in some cases, errenous version of PHPSHR until this new version arrives (no timneframe known)