Hi Eric,
Thanks mate. Unfortunately this still doesn't seem to work for me.
I went through the process manually, you can see a transcript at
http://pastie.org/1043347.txt
The indented text is what I see appearing in the unicorn stderr.log.
As you can see it reports two errors during the process, saying
unicorn.pid is stale.
I wonder whether this is because in my unicorn config file I mention:
pid "/var/www/staging/current/tmp/pids/unicorn.pid"
whereas in your back_out_of_upgrade test you don't have such a line?
Cheers,
Lawrence
Changes:
Theses release fix a long-standing bug where the original PID
file is not restored when rolling back from a USR2 upgrade.
Presumably most upgrades aren't rolled back, so it took over a
year to notice this issue. Thanks to Lawrence Pit for
discovering and reporting this issue.
About Unicorn:
Unicorn is an HTTP server for Rack applications designed to only serve
fast clients on low-latency, high-bandwidth connections and take
advantage of features in Unix/Unix-like kernels. Slow clients should
only be served by placing a reverse proxy capable of fully buffering
both the the request and response in between Unicorn and slow clients.
* http://unicorn.bogomips.org/
* [email protected]
* git://git.bogomips.org/unicorn.git
_______________________________________________
Unicorn mailing list - [email protected]
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
