Thanks bro for the comment. You sure did make this...

2008-05-05T09:38:00.000+05:30

Thanks bro for the comment. You sure did make this post more interesting. And yes, we do make silly mistakes sometimes. :) But that's part of the job.

Hi Gaveen,Thanks for the informational post, this ...

2008-05-03T05:32:00.000+05:30

Hi Gaveen,

Thanks for the informational post, this would surely help anxious SysAdmin's from pulling out their hair :)

Reading the 2nd issue with Proxies, reminds me such a tricky situation which haunted me for few days.

Excited by Thin's support for Unix domain sockets, I decided to use it for one of our deployments. The app was done in Merb and I used the command "merb -a thin -h /tmp/thin.sock -p 0 -c 4" to start the merb cluster. In Load Balancer of Nginx I was calling each socket with
"server unix:/tmp/thin.0.sock".

For my frustration Load Balancer doesn't seem to forward traffic to the thin. After digging through the Nginx configs, I found it cannot find the sockets. But my thin status indicated the sockets were running fine. This made me to juggle with various configuration options without any success (Also my ego didn't want to retreat from Unix Domain sockets to standard IP ports).

I only figured the error when I manually went inside the /tmp directory. Sockets did exist!, but in a different naming scheme ;). Instead of Thin's standard naming scheme, Sockets created by Merb were named like this -
"server unix:/tmp/thin.sock-0".

It was really a dumb issue and I was cursing my self for wasting time with it. But now it seems such an issues are part and parcel of every SysAdmin process ;)

Comments on Gaveen's Blog: Errno::EPIPE (Broken pipe) MySQL Error in Rails

Thanks bro for the comment. You sure did make this...

Hi Gaveen,Thanks for the informational post, this ...