backgroundrb - failed to find slave socket October 13th, 2007
Ugh. Another madness inducing bug that I post in hopes that others will have easier Googling.
I was trying to spawn backgroundrb processes. Scheduled processes worked, but when I spawned new ones they sometimes do, sometimes don't work. And I was seeing the "failed to find slave socket" error. Couldn't figure it out and Google wasn't immediately helpful. But here is what it appears to break down to.
When it creates socket files in /tmp to it truncates the worker key onto the end of your workers name. Well, there is a limit to how long that file name can be before it blows up. Looks like the name of your worker class, including underscores, needs to be 25 or less characters or it will create an invalid file name and blow up.
See also this ticket, which doesn't mention this error specifically but pointed me to the apparent answer. Hope it saves others my headache for the last week or so.
Sorry, comments are closed for this article.