Just to followup.
I eventually did upgrade the installation from 0.9.4 to 1.0.2 by
installing it alongside the original directory & changing the
webwareDir config. line inside my app working directory's Launch.py.
Unfortunately, this is unrelated to the original problem.
------------------
Here's what I think was happening.
The server (somehow) made its way onto a list of open proxy web
servers. At that time, Apache2 was configured to be an open proxy...
but I didn't know it. So I changed httpd.conf to remove the proxy-
related functionality. But that didn't fix the AssertionErrors
problem, it merely stopped the server from acting as a proxy.
In fact, it caused the number of AssertionErrors to skyrocket from a
few per day to approx. 100 in 2 hours.
I'd originally had Apache configured with rewrite rules to route
"normal" URLs through the AppServer... (e.g., requests to
http://www.example.com got served through http://www.example.com/webkit/). Thinking
that the unwanted proxy requests were hitting these "normal" URLs, I
removed the rewrite rules. This had no effect on the errors; they
kept coming in droves.
Upon closer inspection of the emailed AssertionErrors, it appeared
that the proxy requests weren't actually hitting any of the
VirtualHost domains for that box, but they were explicitly connecting
to http://ipaddress:8080/. So it didn't really matter how I had the
rewrite rules or virtual hosting configured.
Finally, I changed the port number inside my app working directory/
Configs/AppServer.config.
Now (at least theoretically), the server's just kicking back 404s to
everything connecting to 8080 instead of routing anything through
WebKit & inducing the AssertionErrors.
It'll work for now. If any of you have any suggestions as to a better
way to fix the problem, I'd certainly welcome them.
Thanks,
-Gary
On Jun 8, 2009, at 4:27, Christoph Zwerschke wrote:
> Gary Perez schrieb:
>> I use MakeAppWorkDir.py after each (new) installation. Is it possible
>> to install the new version of Webware & then point the existing
>> appworkdir to it in place of the older version?
>>
>> Or should it be run again to create a fresh appworkdir, copy context
>> directories & reconfigure?
>
> This is only required if you're updating from a really old version.
> If your're running 0.9.1 or newer, you can simply update Webware
> itself
> without any changes in the app work dirs.
>
> I recommend moving the old version to /usr/local/Webware.old and then
> installing the current version as /usr/local/Webware. Then no
> changes to
> the working dirs will be needed, and if it does not work as expected,
> you can easily revert the update.
>
> -- Christoph
|