I was experiencing the same issue. I tried changing my uwsgi command options (l and z) but it didn't help. I decided to try out Alvaro's suggestion and it worked!
File descriptor is automatically set to: ulimit -n. My ulimit -n was 1024. Changed File descriptor to 10000 and it resolved the issue. I'm not sure why this is required but thanks for the help Alvaro. > > The server is a quad core 3.2GHz 32-bit x86 machine with 3GB of RAM. > > Load average during high usage is around 0.4 > > ulimit -n is set to 1024 > > lsof -n | grep cherokee | wc -l reports 750ish during high usage. > > Throughput is about 2mbyte/s > > Cherokee is barely touching the CPU (20% tops) and disk i/o wait is > hovering around 4% on a fast SCSI RAID array. > > I'm running v0.99.42 compiled under debian lenny with default options. > > > > The website serves images, css and js directly and reverse proxy's php > requests to 2 round-robin app servers on a local 100mbit network. It's the > reverse proxy requests that are producing the 504 timeout errors. The app > servers are reporting no errors and have timeouts configured 5s lower than > the reverse proxy (which is set to 60 seconds). > > Reuse connections is set to 48. > > Compression is disabled for the reverse proxies. > > > > Please help me figure out what these timeouts are occuring. I'm willing > and able to do whatever debugging is necessary to figure this out, but I'm > at the limits of my own know-how. > > > > Some further debugging steps would be really helpful. > > Have you tried to raise the file descriptor limit? In cherokee-admin, go to > Advanced ➠ Resources ➠ File Descriptors. I'd try raising it to at least 8k. > > -- > Octality > http://www.octality.com/ > > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee >
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
