Mailing List Archive

Issue 865 in cherokee: Acunetix WVS kill cherokee worker
Status: New
Owner: ----

New issue 865 by peter.donka: Acunetix WVS kill cherokee worker
http://code.google.com/p/cherokee/issues/detail?id=865

What steps will reproduce the problem?
1. test my web page with acunetix web vulnerability scanner 6.0
2.
3.

What is the expected output? What do you see instead?
cherokee and cherokee-worker killed (no syslog message)

What version of the product are you using? On what operating system?
ubuntu 10.04 and cherokee 1.0

Please provide any additional information below.


_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev
Re: Issue 865 in cherokee: Acunetix WVS kill cherokee worker [ In reply to ]
Comment #1 on issue 865 by peter.donka: Acunetix WVS kill cherokee worker
http://code.google.com/p/cherokee/issues/detail?id=865

i reproduce the problem. here is my clean log.

this is the end of the log

cherokee.access (only containing this):
[11/May/2010:16:26:42 +0200] "GET / HTTP/1.0" 200 2140 "-" "Mozilla/4.0
(compatible;
MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)"
[11/May/2010:16:29:06 +0200] "GET /acunetix_file_inclusion_test HTTP/1.1"
404 0 "-" ""

website.error (last mod time: 16:32):
Cannot bind/listen socket - [98] Address already in use.
Couldn't create FastCGI listen socket on port 127.0.0.1:47991
Cannot bind/listen socket - [98] Address already in use.
Couldn't create FastCGI listen socket on port 127.0.0.1:47991



_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev
Re: Issue 865 in cherokee: Acunetix WVS kill cherokee worker [ In reply to ]
Comment #2 on issue 865 by ste...@konink.de: Acunetix WVS kill cherokee
worker
http://code.google.com/p/cherokee/issues/detail?id=865

Tried the tests on the free edition. No crash here...

If it gets killed, check if there is a memory leak (valgrind) or another
reason for
the kill (gdb).

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev
Re: Issue 865 in cherokee: Acunetix WVS kill cherokee worker [ In reply to ]
Comment #3 on issue 865 by alobbs: Acunetix WVS kill cherokee worker
http://code.google.com/p/cherokee/issues/detail?id=865

Looks like the backend (php-cgi?) is blocked/dying/crashing.. and that's
why Cherokee tries to launch a new
instance - but fails because the port is already in use.

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev
Re: Issue 865 in cherokee: Acunetix WVS kill cherokee worker [ In reply to ]
Comment #4 on issue 865 by dziastinux: Acunetix WVS kill cherokee worker
http://code.google.com/p/cherokee/issues/detail?id=865

This still exists in v1.0.1

Removing inherit environment flag (Whether the new child process should
inherit the environment variables from the server process. Default: yes.)
from PHP interpreter configuration actually solved the problem.

Default PHP_FCGI_CHILDREN value is set to 1 as only one php-cgi process
tries to handle all the requests. Of course with no luck.

I suggest to increase default value at least to 5 in order to avoid this
situation.


_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev
Re: Issue 865 in cherokee: Acunetix WVS kill cherokee worker [ In reply to ]
Updates:
Status: WontFix

Comment #5 on issue 865 by ste...@konink.de: Acunetix WVS kill cherokee
worker
http://code.google.com/p/cherokee/issues/detail?id=865

I have never able to reproduce this issue :(

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev