- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: CSWS 2.0 & OSU scripting
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2004 12:44 AM
05-26-2004 12:44 AM
CSWS 2.0 & OSU scripting
Currently playing with the CSWS 2.0 on VMS 7.3-2 (TCP/IP 5.4, DECnet OSI).
Since (almost) all of the CGI-scripts here are written for the OSU server, I tried to enable the OSUscript handler (mod_osuscript) as described in the "Secure Web Server for OpenVMS Installation and Configuration Guide", paragraph 3.5.12.
Unfortunately, so far no luck.
Each time I do a request for "http://host/htbin/whatever.com", one of the servers dies with an ACCVIO.
The CSWS configuration is out of the box, with the exception of a LoadModule directive for mod_osuscript, and I also uncommented the "" directive.
As described in the installation guide, the necessary OSU scripts (WWWEXEC.COM, etc.) and executables (CGI_SYMBOLS.EXE) are present at their designated location.
Furthermore the APACHE$WWW account is owner of all directories and files in its "DocumentRoot" including the OSUscript directory & command procs.
In the APACHE$ROOT:[LOGS]error_log.;1 file, I get the following entry:
[Wed May 26 14:34:20 2004] [notice] child pid 23458 exit signal Bad system call (12)
In the log file of the deceased server (excerpt):
$ httpd -f apache$common:[conf]httpd.conf -p 24993 -w 0
$ httpd_status = $STATUS
...
$ Exit %X1000000C
Someone any ideas?
All hints greatly appreciated.
Kris.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2004 06:40 PM
05-26-2004 06:40 PM
Re: CSWS 2.0 & OSU scripting
Don't you agree this again is prove of bad porting (IMHO) since it doesn't tell you ANYTHING...
APACHE$WWW should have at least READ access to all files, and READ/EXECUTE on all directories and executables that eventually can be accessed.
Another possibility: is mod_osuscript the one for SWS 2.0, or the one you use for 1.3 as well? I don't know if the latter is compatible with SWS 2.0. I'm just guessing, but mod_perl has been rebuilt as well (ECO3 is for SWS 2.0 only) so it wouldn't surprise me if this were required for mod_osuscript as well. In that case, you should use the SWS 2.0-version of this module as well (if it exists)
Willem
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2004 07:43 PM
05-26-2004 07:43 PM
Re: CSWS 2.0 & OSU scripting
I agree with you in that SWS 2.0 is not a mature port yet.
As for your other comments:
VMS 7.3-2 freshly installed (not upgraded), SWS 2.0 installed (so no inheritance of a previous version), and NO perl installed (according to the installation guide, I don't need it).
APACHE$WWW is owner of all files & directories, so has Read & Execute rights.
Greetz,
Kris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-22-2004 02:52 PM
07-22-2004 02:52 PM
Re: CSWS 2.0 & OSU scripting
TCPIP V5.4-ECO2. No update on this yet?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-22-2004 08:06 PM
07-22-2004 08:06 PM
Re: CSWS 2.0 & OSU scripting
We received a very unofficial patch for MOD_OSUSCRIPT.EXE in APACHE$COMMON:[MODULES].
If HP technical support here in Brussels can give us that, you might get hold of it thru your channels.
Btw, the Stream_LF issues has not been taken care of.
Greetz,
Kris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2004 01:44 PM
07-24-2004 01:44 PM
Re: CSWS 2.0 & OSU scripting
the last Apache update is more than 6 months old. I do suppose they are busy porting to
Itanium and getting The stream-LF problem
finally fixed. Also no VMS changes have made it into the offical code base at least up to
2.0.50 AFAIK, so there is definitly some catching up to do. For the time being I will stick with OSU for my production servers and only use CSWS for test purposes.
Greetings, Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2004 07:18 PM
07-25-2004 07:18 PM
Re: CSWS 2.0 & OSU scripting
As you suggest, we kept most of our production servers on OSU, only the new ones have Apache (either V1.3 or V2.0). The unofficial patch now works as a charm, and for now we try to live with the Stream_LF issue.
Thanx for your input.
Kris