[Info-vax] WASD demo issues

issinoho iain at issinoho.com
Fri Jan 28 05:16:26 EST 2022


On Friday, 28 January 2022 at 10:10:20 UTC, issinoho wrote:
> On Friday, 28 January 2022 at 02:44:43 UTC, Mark Daniel wrote: 
> > On 28/1/22 10:52 am, Mark Daniel wrote: 
> > > On 28/1/22 9:54 am, issinoho wrote: 
> > >> On Thursday, 27 January 2022 at 13:31:29 UTC, issinoho wrote: 
> > >>> On Tuesday, 25 January 2022 at 21:59:16 UTC, Mark Daniel wrote: 
> > >>>> On 26/1/22 3:53 am, issinoho wrote: 
> > > 8< snip 8< 
> > >>> Ok, I have no idea what was going on. Flattened the install, rebuilt 
> > >>> and now everything is good (even with SSL) - so now just trying to 
> > >>> get PHP running. Got all the components installed and just trying now 
> > >>> to figure out what I need in the map and global files - anyone got 
> > >>> any Dummies Guides for this?? 
> > >> 
> > >> Ok, the root cause of the issue seems to be in the host name 
> > >> resolution, specifically with regard to case sensitivity. Setting an 
> > >> alias with the specific case that WASD is expecting solves the problem. 
> > > 
> > > Hmmmm. So after the rebuild the local host database remained unchanged? 
> > > Should have exhibited the same behaviour. 
> > Can't seem to reproduce this. 
> > 
> > X86VMS$ tcpip show host /local 
> > 
> > LOCAL database 
> > 
> > Host address Host name 
> > 
> > 127.0.0.1 LOCALHOST, localhost 
> > 192.168.1.86 x86vms 
> > 
> > $ @wasd_root:[install]demo 
> > 8< snip 8< 
> > %DCL-S-SPAWNED, process SYSTEM_64379 spawned 
> > %DCL-S-ATTACHED, terminal now attached to process SYSTEM_5389 
> > %HTTPD-I-SOFTWAREID, HTTPd-WASD/12.0.0 OpenVMS/X86 SSL 
> > 8< snip 8< 
> > %HTTPD-I-SERVICE, http://x86vms.lan:7080 
> > %HTTPD-I-SERVICE, https://x86vms.lan:7443 
> > %HTTPD-I-SSL, x86vms.lan:7443 
> > Generate x86vms.lan 2048 bit private key: 
> > ...........................+++++ 
> > ................................................................................ 
> > ........................................................+++++ 
> > ......+++++ 
> > %HTTPD-I-DEMO, demonstration mode 
> > 8< snip 8< 
> > 
> > X86VMS$ tcpip show host /local 
> > 
> > LOCAL database 
> > 
> > Host address Host name 
> > 
> > 127.0.0.1 LOCALHOST, localhost 
> > 192.168.1.86 X86VMS 
> > 
> > $ @wasd_root:[install]demo 
> > 8< snip 8< 
> > %DCL-S-SPAWNED, process SYSTEM_64379 spawned 
> > %DCL-S-ATTACHED, terminal now attached to process SYSTEM_64379 
> > %HTTPD-I-SOFTWAREID, HTTPd-WASD/12.0.0 OpenVMS/X86 SSL 
> > 8< snip 8< 
> > %HTTPD-I-SERVICE, http://x86vms.lan:7080 
> > %HTTPD-I-SERVICE, https://x86vms.lan:7443 
> > %HTTPD-I-SSL, x86vms.lan:7443 
> > Generate x86vms.lan 2048 bit private key: 
> > ................................................................+++++ 
> > ......+++++ 
> > %HTTPD-I-DEMO, demonstration mode 
> > 8< snip 8< 
> > 
> > What was the original failure entry, and now the current entry? 
> > 
> > Thanks. 
> > -- 
> > Anyone, who using social-media, forms an opinion regarding anything 
> > other than the relative cuteness of this or that puppy-dog, needs 
> > seriously to examine their critical thinking.
> Mark, thanks a million for the PHP pointers, that's tremendous - I'll give that a try today at some point. 
> 
> In terms of the errors, here is my hosts database... 
> 
> AXPBOX::tcpip sho hosts
> LOCAL database 
> 
> Host address Host name 
> 
> 127.0.0.1 LOCALHOST, localhost
> 192.168.0.47 axpbox.Home, axpbox.home 
> 
> This ^^^ works. If the "axpbox.home" alias is *not* defined then we have the problem. Following this, I actually found an entry in the VSI TCP/IP manual which states that when hosts have a mixed-case then a uniform case alias should/must be defined. So it seems like a known situation.

WATCHER is excellent - what a superb diagnostic tool.

One question: after authorizing with, "HTTPD /DO=AUTH=SKELKEY=_username:password" this works; however obviously times out after a period at which point the page URL returns a 403. What is the recommended way to get WATCHER going again after this? Resubmitting the skeleton key doesn't seem to work - the only way I've found is to restart the web service. Any pointers would be appreciated - thanks.


More information about the Info-vax mailing list