Lawrence Pit <[email protected]> wrote:
> 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.
Thanks Lawrence, the following line looks suspicious to me:
reaped #<Process::Status: pid=4382,exited(0)> exec()-ed
Which makes it seem like
http://git.bogomips.org/cgit/unicorn.git/commit/?id=3f0f9d6 didn't get
applied (and I just checked the 1.1.2 gem and it looks good to me)
Can you dump out the ENV hash in your before_exec hook of your
unicorn.conf.rb? I'm wondering if GEM_HOME or GEM_PATH is set
and doing anything funky, causing you to load an old version
of Unicorn:
before_exec do |server|
ENV.each do |key,value|
server.logger.info "#{key}=#{value}"
end
end
> 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?
It does, I create a similar line in the unicorn_setup() function of
test-lib.sh
--
Eric Wong
_______________________________________________
Unicorn mailing list - [email protected]
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
