Mailing List Archive: Cherokee: users

handler_fcgi.c:92 - Parsing error: unknown type

Index | Next | Previous | View Threaded

info at ppvg

Sep 27, 2009, 11:22 AM

Post #1 of 2 (327 views)
Permalink

handler_fcgi.c:92 - Parsing error: unknown type

Hello,

Over the last few weeks, I've been running Cherokee for a few very
small PHP sites. I'm running a separate FastCGI information source for
each site. These are practically identical to the one setup by the PHP
wizard, apart from the port (eg. localhost:47992) and running FastCGI
as the site's user and group.

Overall, it's been performing magnificently (cherokee really is
awesome!). Occasionally though, it crashes or fails to start a FastCGI
process. There seem to be two recurring problems.

The first one is, I think, a known one. The spawner starts spewing
error messages like "(warning) spawner.c:261 - Couldn't unlock
spawning semaphore.." into the Virtual Server's error log. The main
cherokee process and cherokee-worker start hogging CPU, and the only
remedy seems to restart cherokee completely. Is there any known way to
prevent this, aside from running cherokee-worker as root?

The second seems a bit more rare, and leaves this in the Virtual Server's log:
> Cannot bind/listen socket - [98] Address already in use.
> Couldn't create FastCGI listen socket on port localhost:47992
> [27/08/2009 18:44:50.260] (error) handler_fcgi.c:92 - Parsing error: unknown type
> [27/08/2009 18:44:52.550] (critical) server.c:1806 - PANIC: re-panic: '/usr/share/cherokee/cherokee-panic 824', status 255

This happens every now and then, sometimes even right after a reboot.
Additionally, cherokee-panic does't seem to send any email. I've got
postfix installed and /usr/sbin/sendmail is present and working (root
can receive messages sent by my user ppvg). Does anyone know why this
happening and/or how I can debug it?

Thanks!

Peter-Paul

Attachments:

cherokee.conf.excerpt (3.03 KB)

info at ppvg

Sep 30, 2009, 1:12 AM

Post #2 of 2 (301 views)
Permalink

Re: handler_fcgi.c:92 - Parsing error: unknown type [In reply to]

>
> The first one is, I think, a known one. The spawner starts spewing
> error messages like "(warning) spawner.c:261 - Couldn't unlock
> spawning semaphore.." into the Virtual Server's error log. The main
> cherokee process and cherokee-worker start hogging CPU, and the only
> remedy seems to restart cherokee completely. Is there any known way to
> prevent this, aside from running cherokee-worker as root?
>

Update: it looks like the first problem is easily resolved (or rather:
prevented). This only happened after I killed a php-cgi process. If I
perform a hard restart on Cherokee immediately afterwards, everything goes
smoothly. :-)

> The second seems a bit more rare, and leaves this in the Virtual Server's
> log:
> > Cannot bind/listen socket - [98] Address already in use.
> > Couldn't create FastCGI listen socket on port localhost:47992
> > [27/08/2009 18:44:50.260] (error) handler_fcgi.c:92 - Parsing error:
> unknown type
> > [27/08/2009 18:44:52.550] (critical) server.c:1806 - PANIC: re-panic:
> '/usr/share/cherokee/cherokee-panic 824', status 255
>
> This happens every now and then, sometimes even right after a reboot.
> Additionally, cherokee-panic does't seem to send any email. I've got
> postfix installed and /usr/sbin/sendmail is present and working (root
> can receive messages sent by my user ppvg). Does anyone know why this
> happening and/or how I can debug it?

Luckily, the second problem hasn't occurred again. I'm still wondering
though why cherokee-panic didn't send an e-mail. Does anyone know how I can
analyse/debug this?

Peter-Paul

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads