"unicorn -D" always returns 0 "success" (even when failed to load)
normalperson at yhbt.net
Sun Dec 27 22:29:02 EST 2009
Iñaki Baz Castillo <ibc at aliax.net> wrote:
> El Domingo, 27 de Diciembre de 2009, Eric Wong escribió:
> > > Hi, I've improved it a bit with your suggestions and also simplified
> > > it a lot. Now there is no a "controller process". Instead, if
> > > "Unicorn.run" raises then master process rescues the exception and
> > > sends USR1 to parent process so it exists with 1.
> > Hi, I realized Unicorn.run inside the daemonize method doesn't work.
> Strange, it works for me...
"Doesn't work" as in it's not friendly to servers based on Unicorn (like
> > However, I've reimplemented much of your idea here so it does not
> > involve sleeping at all, but rather shares a pipe with the grandparent
> > (started by the user) and Unicorn master process. The added benefit of
> > using a pipe is that there's no fuzzy sleeping involved at or grace
> > periods to worry about, too.
> > Also pushed out to the "ready_pipe" branch of
> > git://git.bogomips.org/unicorn.git
> > Let me know how it goes.
> > If everything looks good, I'll consider merging for 0.96.0.
> It's really awesome! I've tested it and it works great, and avoids the
> sleeping stuff and a new commandlline option. Congratulations :)
The current version is actually slightly buggy in that it leaks
the pipe descriptor...
> However there is still a not solved case. Let me please explain it with two
> 1) In "after_fork" I set:
> The master process would start properly and would notify "success" to
> grandparent. (so the init script returns 0). But the fact is that all the
> workers fail to start and are respawned again and again.
For that particular case there'll be a Unicorn::Configurator#user
But really, there's absolutely no good reason to use user switching in a
backend application server like Unicorn.
I only added that feature to support derivative servers like Rainbows!,
and even then it's debatable since using things like iptables or load
balancers can be used to redirect port 80 to arbitrary ports anyways.
> 2) I use "Clogger" in my Rack config.ru. But I set a log file in a path that
> doesn't exist. Clogger raises due to this (it doesn't try to create the full
> Again the master process has notified "success" to grandparent (exis status 0
> then) but the workers are respawned again and again.
There's really an infinite number of ways to screw things up badly in
workers and cause them to flap. It's not possible to protect careless
users from all of them, so attempting to do so would be a waste of
Avoiding user-switching in an app server is a great first step, as it
eliminates an entire class of problems :)
More information about the mongrel-unicorn