I'm seeing an occasional problem with truncated FCGI requests; I haven't been able to nail down the exact source yet but wanted to run this by the folks here to see if it rings any bells.
I've got two frontend machines running Cherokee that are configured with virtual IPs managed by wackamole. Client access is via a name with 2 A records that point at the pair of IP addresses. I have a vhost on each of the frontends that points at a third machine running a pool of compute server scripts that are started with spawn-fcgi and managed with multiwatch. This particular service is providing an XMLRPC-like RPC service (it's a custom protocol using YAML instead of XML so we can stream large data structures, but that's a different discussion). The problem we're seeing is that for a particular test script on the client side, one of the exchanges is failing. Looking at packet traces, I see the client sending a complete request to cherokee. Cherokee sends the request to the compute server, but it appears to be truncating the request one packet shy of finishing it. the compute server then reports a bad parse in response. The problem initially showed up fairly reliably only when both front ends were running. If I killed wackamole on one of them (pushing both IPs over to a single server) the problem vanished. However later on in the day, the problem cropped back up with just the single server. I'm still trying to get a set of packet traces from all parties involved plus a strace log of cherokee while it happens to see if I can figure out what's at fault. Let me know if you have any ideas. Thanks, --bob _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
