I just want to make sure you are using the source from apache.org, not
the source rpm. Redhat's source uses the older apache2 plugin
architecture, with security patches rolled into it.
Otherwise, no I don't have any issues with witango 5.0.1.065/apache2 on
redhat 9
>
>Hi all,
>
>I've searched the achive of this list but haven't found mention of the
>problem that I'm seeing:
>
>Our new installation of Witango 5.0.1.065 is giving us trouble on a
>RedHat 9 box.
>
>The symptom:
>
>the witango daemon (witangod) starts up and serves requests, but after
>about 5 minutes it just freezes. The tango client eventually times out
>(after a few minutes) and displays this message:
>
> Client/Plug-in Error
>
> The client encountered problems in communicating with the application
> server. Please check witangoevents.log for further information.
>
>The witangoevents.log doesn't have anything particularly interesting in
>it. The last lines look like this:
>
> [10742] 2004-02-02 17:08:20 START INFO Oracle Call Interface
>(OCI):
>Enabled
> [10742] 2004-02-02 17:08:20 START INFO Listener Address: Any
> [10742] 2004-02-02 17:08:20 START INFO Listener Port: 18100
> [10742] 2004-02-02 17:08:20 START INFO Allocated 20 worker
>threads
> [10742] 2004-02-02 17:08:21 RUNTIME INFO Skipping empty startup
>URL
> [10742] 2004-02-02 17:08:22 RUNTIME INFO Started accepting user
>requests
>
>We're using an apache2 built from source. Have tried the recommended
>version 2.0.46 as well as the current release (2.0.48). We're seeing
>the same problem with both versions of apache.
>
>An strace of the catatonic witangod process shows me this sort of thing
>over and over:
>
>gettimeofday({1075922257, 962880}, NULL) = 0
>gettimeofday({1075922257, 963070}, NULL) = 0
>futex(0x82d2964, FUTEX_WAIT, 150248, {0, 999810000}) = -1 ETIMEDOUT
>(Connection
>timed out)
>gettimeofday({1075922258, 972906}, NULL) = 0
>gettimeofday({1075922258, 973101}, NULL) = 0
>futex(0x82d2964, FUTEX_WAIT, 150249, {0, 999805000}) = -1 ETIMEDOUT
>(Connection
>timed out)
>
>Although an strace of a functioning witangod process looks much the
>same. I think that just tells me that strace isn't seeing witangod's
>threads very well.
>
>Restarting the witango daemon fixes the problem for another 5 minutes or
>so.
>
>Anyone else out there seen this sort of problem?
>
>Ben
>
>--
>---------------------------------------------------------------------------
>Ben Poliakoff email: <[EMAIL PROTECTED]>
>Reed College tel: (503)-788-6674
>Unix System Administrator PGP key: http://www.reed.edu/~benp/key.html
>---------------------------------------------------------------------------
>0x6AF52019 fingerprint = A131 F813 7A0F C5B7 E74D C972 9118 A94D 6AF5 2019
>
>________________________________________________________________________
>TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
>
Bill Conlon
To the Point
345 California Avenue Suite 2
Palo Alto, CA 94306
office: 650.327.2175
fax: 650.329.8335
mobile: 650.906.9929
e-mail: mailto:[EMAIL PROTECTED]
web: http://www.tothept.com
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
