As reported to the Debian bug tracking system:
---
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=330798
a dangling symlink in a directory will causes Cherokee to either
display a partial directory listing (this was the behavior in
0.4.25) or just hang indefinitely trying to display the directory
(behavior experienced with 0.4.26 built locally). There's
definitely a bug someplace in the autoindex code someplace.
I also saw 0.4.25 eating up all available CPU time
earlier along with 37MB or so of memory, but it may have been
related to some of the bugs in 0.4.25. And conveniently enough,
as I write this, 0.4.26 has achieved the same state on my server:
---
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
24955 www-data 16 0 85684 5908 2964 S 99.9 0.6 113:07.01 cherokee
Unfortunately, I have no log files in /var/log because
upgrading from 0.4.25 to 0.4.26 seemingly broke that feature. I
thought it may have been a permission issue initially as I run
the process as www-data:www-data, but I tried chown'ing the files
and the process still doesn't write anything to cherokee.error or
cherokee.access which I have set up in my config file:
---
Log combined {
AccessLog /var/log/cherokee.access
ErrorLog /var/log/cherokee.error
}
So unless something changed with the syntax of the file
format, it looks like 0.4.26 may have some logging issues (or my
build of it anyway). Oddly enough, cherokee is still serving
pages. It just has gone a little crazy in the process and is
bogging other processes down on the server (specifically my slapd
process).
Lastly, I'm also seeing some buggy behavior while serving
requests. I saw this with both 0.4.25 and 0.4.26 also. The
server in question mirrors a bunch of Linux distributions and
whenever I run dselect from Debian and update my list of
available packages from the mirror server running cherokee, I get
errors:
---
Failed to fetch http://mirror.tamu.edu/debian/dists/unstable/Release.gpg The
HTTP server sent an invalid Content-Range header
Failed to fetch http://mirror.tamu.edu/debian/dists/experimental/Release.gpg
The HTTP server sent an invalid Content-Range header
What is really strange about this is that I only get this
error every other time I run update. So it seems that cherokee
generates a valid Content-Range header the first time the
request comes across, and then generates trash the next time, ad
infinitum.
So, let me know if anyone has any input on all of this.
I'm happy to recompile Cherokee and do a little debugging if
necessary.
--
Mark Nipper e-contacts:
832 Tanglewood Drive [EMAIL PROTECTED]
Bryan, Texas 77802-4013 http://nipsy.bitgnome.net/
(979)575-3193 AIM/Yahoo: texasnipsy ICQ: 66971617
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GG/IT d- s++:+ a- C++$ UBL++++$ P--->+++ L+++$ !E---
W++(--) N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--)
Y+ PGP t+ 5 X R tv b+++@ DI+(++) D+ G e h r++ y+(**)
------END GEEK CODE BLOCK------
---begin random quote of the moment---
"Puritanism: The haunting fear that someone, somewhere, may be
happy."
-- H. L. Mencken, _A Book of Burlesques_, "Sententiae", 1920
----end random quote of the moment----
_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
