SYSMGR

We're a bunch of Computers: Diana, Daphne, and Dido, called the 3D-cluster, running OpenVMS, Io running OpenVMS as well (in some obscure role in the network) Aphrodite, Athene and Irene running WindowsXP-Pro (SP2, of course) and Cerberus at the edge of the Network, with Charon, also running Linux, as standby. SYSMGR takes care of us.

Monday, April 24

24-Apr-2006

PHP_MYSQL - another try
Had contact with Jean Francois Pieronne about PHP_MYSQL. I already found out that the shared images of OpenSSL MUST (!) reside on SYS$LIBRARY for PHP to find them. There'se one more: LIBZ_SHR32. But locating them on SYS$LIBRARY alone didn't help.
On JFP's suggestion tried to use static linking - started with LIBZ but that releaved two undefined references: COMPRESS and UNCOMPRESS.

Idea: Since it seemed required that these shared images reside on SYS$LIBRARY, added references to both OPENSSL-images and LIBZ - all residing on SYS$LIBRARY - in the build commandfile, using the names as mentioned by all the errors ruuning PHP manually (which can be different from the source names: LIBSSL for OPENSSL098A_LIBSSL_SHR32. EXE and and LIBCRIPTO for OPENSSL098A_LIBCRYTO_SHR32.EXE), and added these in the option file for building, and building went OK. Next the same references were added in PHP_SETUP.COM, just to be sure. Restarted Apache - and now it works!

The whole seqence can be read on his MySQL forum at http://www.pi-net.dyndns.org/phpbb/viewtopic.php?t=64 - and it has been mentioned to ITRC since it's mainly PHP that causes the problem, I think, by requiring any shared image to reside on SYS$LIBRARY. Not exactly VMS-like!

Now I could make a backup of the Wordpress database - and indeed, the problems using the RSS feeds that caused problems before, are now gone. But the look and feel still cannot be changed. Likely it has to be re-installed. Ok, no problem.

DECNet issue
In the restart yesterday, it was forgotton to disable the secondary NIC - not yet connected this causes a massive amount of OPCOM messages - and DTSS was kept running as well - and since it looks for 2 additional servers, this gives a large number of messages as well. This morning, I corrected that error - after finding an Operator log of a massive 26Mb, where it usually is about just 10K
It should be in the startup sequence ....

0 Comments:

Post a Comment

<< Home