>Number:         1664
>Category:       os-os2
>Synopsis:       Failure to properly startup every time
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Tue Jan 13 13:10:01 PST 1998
>Last-Modified:
>Originator:     [EMAIL PROTECTED]
>Organization:
apache
>Release:        1.3b3
>Environment:
Binary distribution of 1.3b3 for OS/2 from Apache
web site.

I'm currently running OS/2 Warp 4.0 Client with no
fixpaks installed.  Full LAN support is installed.
>Description:
This occurs only once out of every few (4-5) startups.
When I kill the server and restart it quickly (in a
command file), the server sometimes fails to start 
properly.  Before being accessed, the number of httpd
processes quickly drops to one.  If a port 80 request
is made by a browser, that process dies.

This appears to be new in the 1.3b3 beta.  It didn't 
appear in the 1.2.4 release from Softlink.

BTW:  1.3b3 seems to be a lot snappier than 1.2.4
>How-To-Repeat:
I terminate the running process using the terminate.cmd
file provided in the Softlink distribution.  The new
process is started with a 'detach httpd'.

Basically, you run it and watch the process list.
If it drops to a single process in ten seconds or
so, it failed.  If the processes remain, you're ok.

The exact command script is as follows:
/* BEGIN HTTPD COMMAND SCRIPT */
/* */
CALL RxFuncAdd 'SysLoadFuncs', 'RexxUtil', 'SysLoadFuncs'
CALL RxFuncAdd 'SysCurPos', 'RexxUtil', 'SysCurPos'
CALL RxFuncAdd 'SysCls', 'RexxUtil', 'SysCls'
CALL SysLoadFuncs

'c:'
'cd \os2httpd'
hostfile = 'hostname';

'hostname >' hostfile
hostname = LINEIN(hostfile)
CALL STREAM hostfile 'c' 'close'
say 'HOSTNAME =' hostname
'set HOSTNAME='hostname

'cd os2'
'call terminate.cmd'
'cd ..'

'detach httpd.exe'
/* END HTTPD COMMAND SCRIPT */

If I can provide more informatin let me know.
>Fix:

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]



Reply via email to