The vulnerability is only log4j 2
> On Dec 13, 2021, at 05:26, Daniele Corti via Webobjects-dev
> wrote:
>
>
> Hi List!
> Today the vulnerability CVE-2021-44228 details (log4j) are out and looks like
> all log4j versions are affected!
>
> I’ve seen many attempt on the logs of the servers,
No, you’re definitely using too much CPU.
I had a problem recently moving a webobjects implementation with a similar
problem. The issue was a wonky DNS problem where the hostname wasn’t always
returning the correct address (still haven’t figured that out). I put the
correct address in
I never bounce them - even with EOF ;)
> On Aug 5, 2020, at 07:07, Jesse Tayler via Webobjects-dev
> wrote:
>
> What do you use to keep an eye on memory? JAVA has such an old-school
> approach with the VM I use AWS and really don’t have any good automated
> visualizing report on how
Michael,
This looks suspiciously like what I complained about recently. The issue was
this line in the httpd.conf file:
ScriptAlias /cgi-bin/ “/var/www/cgi-bin/“
If this line is still in your httpd.conf file, comment it out. This doesn’t
affect people that rename the URL to be something like
OK, so the problem was, this line in the regular https.conf file:
ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"
Since I have WO using cgi-bin, this was apparently taking precedence. When I
comment out the above line, all works again.
Ken
> On Apr 6, 2020, at 4:43 PM, Ken
ebsite with your app? I’m no good with apache rules
> myself, but your setup is different than what I typically do.
>
> I’d fuss with apache first-there’s output logs listed in the config somewhere
> you might make sure there’s nothing printed there.
>
>
>
>>
Hi everyone!
Well, I’ve circled back to a project I was half way through a year ago… and I’m
a little stuck. Trying to get a WO project off of AWS and running on a home
server.
CentOS 7
Apache 2.4
Wotaskd running
WOMonitor running
App installed and running
Unfortunately, when I go to the
