帶符號鏈接的獨角獸working_directory

我們無法使用獨角獸進行熱部署。我們幾乎使用規範unicorn.rb配置，將working_directory設置爲指向符號鏈接的文件夾，但不知怎的，它在第一次啓動時似乎停留在實際文件夾中，並且無法遵循符號鏈接。帶符號鏈接的獨角獸working_directory

# config/unicorn.rb 
if ENV['RAILS_ENV'] == 'production' 
    worker_processes 4 
else 
    worker_processes 2 
end 

working_directory "/var/local/project/symlinkfolder" 

# Listen on unix socket 
listen "/tmp/unicorn.sock", :backlog => 64 

pid "/var/run/unicorn/unicorn.pid" 

stderr_path "/var/log/unicorn/unicorn.log" 
stdout_path "/var/log/unicorn/unicorn.log" 

preload_app true 

before_fork do |server, worker| 
    # the following is highly recomended for Rails + "preload_app true" 
    # as there's no need for the master process to hold a connection 
    if defined?(ActiveRecord::Base) 
    ActiveRecord::Base.connection.disconnect! 
    end 

    # Before forking, kill the master process that belongs to the .oldbin PID. 
    # This enables 0 downtime deploys. 
    old_pid = "/var/run/unicorn/unicorn.pid.oldbin" 
    if File.exists?(old_pid) && server.pid != old_pid 
    begin 
     Process.kill("QUIT", File.read(old_pid).to_i) 
    rescue Errno::ENOENT, Errno::ESRCH 
     # someone else did our job for us 
    end 
    end 
end 

after_fork do |server, worker| 
    # the following is *required* for Rails + "preload_app true", 
    if defined?(ActiveRecord::Base) 
    ActiveRecord::Base.establish_connection 
    end 

    # this makes sure the logging-rails framework works when preload_app = true 
    Logging.reopen 
    # if preload_app is true, then you may also want to check and 
    # restart any other shared sockets/descriptors such as Memcached, 
    # and Redis. TokyoCabinet file handles are safe to reuse 
    # between any number of forked children (assuming your kernel 
    # correctly implements pread()/pwrite() system calls) 
end

當我們發起USR2，我們看到這麒麟日誌：6版本

executing ["/var/local/project/project.d/6/vendor/bundle/ruby/1.9.1/bin/unicorn_rails", "-E", "staging", "-D", "-c", "/var/local/project/symlinkfolder/config/unicorn.rb"│· 
, {12=>#<Kgio::UNIXServer:fd 12>}] (in /var/local/project/project.d/8)

所以麒麟是某種「卡住」，而實際的符號鏈接文件夾是在8版本.. 。這個問題一旦我們刪除文件夾的版本6後幾個部署...

working_directory設置爲symlink'd fol明鏡
的符號鏈接指向的/var/local/project/project.d/[id]文件夾正確
我們之前發送USR2信號

什麼，我們錯過更新符號鏈接？

來源

2013-02-21 gingerlime

的解決方案是明確設置麒麟二進制路徑，作爲http://unicorn.bogomips.org/Sandbox.html

app_root = "/var/local/project/symlinkfolder" 
working_directory app_root 
# see http://unicorn.bogomips.org/Sandbox.html 
Unicorn::HttpServer::START_CTX[0] = "#{app_root}/vendor/bundle/ruby/1.9.1/bin/unicorn_rails"

解釋（在有些混亂的方式），然後，我們需要發出unicorn reload（kill -HUP）命令，因此麒麟重新加載配置文件。從此，發出USR2信號正常工作。

來源

2013-02-25 16:10:46 gingerlime

帶符號鏈接的獨角獸working_directory

回答

相關問題