Ok, I think I have the problem narrowed down to flup. If I bypass flup I dont get any errors (it just takes a while to finish
On Friday, November 9, 2012 3:46:46 PM UTC-7, Sam Beveridge wrote: > > If enough requests are made fast enough, I get a 500 internal server error > and the following in my lighttpd error logs: > > 2012-11-09 16:17:31: (mod_fastcgi.c.3005) got proc: pid: 0 socket: tcp: > 127.0.0.1:7000 load: 10 > 2012-11-09 16:17:31: (mod_fastcgi.c.3005) got proc: pid: 0 socket: tcp: > 127.0.0.1:7000 load: 11 > 2012-11-09 16:17:31: (mod_fastcgi.c.3005) got proc: pid: 0 socket: tcp: > 127.0.0.1:7000 load: 12 > 2012-11-09 16:17:31: (mod_fastcgi.c.3005) got proc: pid: 0 socket: tcp: > 127.0.0.1:7000 load: 13 > 2012-11-09 16:17:31: (mod_fastcgi.c.3005) got proc: pid: 0 socket: tcp: > 127.0.0.1:7000 load: 14 > 2012-11-09 16:17:31: (mod_fastcgi.c.3005) got proc: pid: 0 socket: tcp: > 127.0.0.1:7000 load: 15 > 2012-11-09 16:17:32: (mod_fastcgi.c.3005) got proc: pid: 0 socket: tcp: > 127.0.0.1:7000 load: 16 > 2012-11-09 16:17:32: (mod_fastcgi.c.3005) got proc: pid: 0 socket: tcp: > 127.0.0.1:7000 load: 17 > 2012-11-09 16:17:32: (mod_fastcgi.c.1515) released proc: pid: 0 socket: > tcp:127.0.0.1:7000 load: 16 > 2012-11-09 16:17:32: (mod_fastcgi.c.3005) got proc: pid: 0 socket: tcp: > 127.0.0.1:7000 load: 17 > 2012-11-09 16:17:32: (mod_fastcgi.c.1515) released proc: pid: 0 socket: > tcp:127.0.0.1:7000 load: 16 > 2012-11-09 16:17:32: (mod_fastcgi.c.1515) released proc: pid: 0 socket: > tcp:127.0.0.1:7000 load: 15 > 2012-11-09 16:17:32: (mod_fastcgi.c.3005) got proc: pid: 0 socket: tcp: > 127.0.0.1:7000 load: 16 > 2012-11-09 16:17:32: (mod_fastcgi.c.1515) released proc: pid: 0 socket: > tcp:127.0.0.1:7000 load: 15 > 2012-11-09 16:17:32: (mod_fastcgi.c.1515) released proc: pid: 0 socket: > tcp:127.0.0.1:7000 load: 14 > 2012-11-09 16:17:32: (mod_fastcgi.c.1515) released proc: pid: 0 socket: > tcp:127.0.0.1:7000 load: 13 > 2012-11-09 16:17:32: (mod_fastcgi.c.3005) got proc: pid: 0 socket: tcp: > 127.0.0.1:7000 load: 14 > 2012-11-09 16:17:32: (mod_fastcgi.c.3005) got proc: pid: 0 socket: tcp: > 127.0.0.1:7000 load: 15 > 2012-11-09 16:17:32: (mod_fastcgi.c.2494) unexpected end-of-file (perhaps > the fastcgi process died): pid: 0 socket: tcp:127.0.0.1:7000 > 2012-11-09 16:17:32: (mod_fastcgi.c.3325) response not received, request > sent: 1252 on socket: tcp:127.0.0.1:7000 for /sm , closing connection > 2012-11-09 16:17:32: (mod_fastcgi.c.1515) released proc: pid: 0 socket: > tcp:127.0.0.1:7000 load: 14 > 2012-11-09 16:17:34: (mod_fastcgi.c.1515) released proc: pid: 0 socket: > tcp:127.0.0.1:7000 load: 13 > 2012-11-09 16:17:34: (mod_fastcgi.c.1515) released proc: pid: 0 socket: > tcp:127.0.0.1:7000 load: 12 > 2012-11-09 16:17:34: (mod_fastcgi.c.1515) released proc: pid: 0 socket: > tcp:127.0.0.1:7000 load: 11 > 2012-11-09 16:17:34: (mod_fastcgi.c.1515) released proc: pid: 0 socket: > tcp:127.0.0.1:7000 load: 10 > > Running gentoo, lighttpd, flup, webpy. > > Has anyone run into this issue before? Any help would be greatly > appreciated! > -- You received this message because you are subscribed to the Google Groups "web.py" group. To view this discussion on the web visit https://groups.google.com/d/msg/webpy/-/910Sw-Xl3CEJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/webpy?hl=en.
