Chef
廚師重新配置錯誤阻止成功執行
我對廚師很陌生,現在正試圖弄清楚為什麼以下兩個錯誤會阻止我成功安裝。
Recipe: private-chef::redis_lb * template[/var/opt/opscode/redis_lb/etc/redis.conf] action create (up to date) * template[/etc/opscode/logrotate.d/redis_lb] action create (up to date) * ruby_block[set_lb_redis_values] action create ================================================================================ Error executing action `create` on resource 'ruby_block[set_lb_redis_values]' ================================================================================ Redis::CannotConnectError ------------------------- Error connecting to Redis on 127.0.0.1:16379 (ECONNREFUSED)
還有第二個錯誤:
Recipe: private-chef::partybus * ruby_block[migration-level file sanity check] action run ================================================================================ Error executing action `run` on resource 'ruby_block[migration-level file sanity check]' ================================================================================ RuntimeError ------------ ERROR: The /var/opt/opscode/upgrades/migration-level file is missing or corrupt! Please read http://docs.opscode.com/upgrade_server_ha_notes.html#pre-flight-check and correct this file before proceeding * If this is a new installation: run: "cd /opt/opscode/embedded/service/partybus ; /opt/opscode/embedded/bin/bundle exec bin/partybus init" * If you have upgraded a previous installation: copy the /var/opt/opscode/upgrades/migration-level file from a not-yet-upgraded FrontEnd node Error message No such file or directory - /var/opt/opscode/upgrades/migration-level
請分享您對這些問題的想法和想法。
謝謝
我看到您正在嘗試安裝 Enterprise Chef 軟體包。您看到的是我們在設置時遇到的兩個錯誤(完全披露,我是 Chef 的工程師)。
我們設置 redis 的方式中的第一個錯誤,我們在 redis 啟動和配置可用之間存在競爭條件。我相信第二次重新配置解決了這個問題,因為當 redis 嘗試啟動時配置文件可用。
第二個問題是 Enterprise Chef 升級過程中的錯誤。該錯誤實際上為您提供了解決方法。假設這是一個新安裝,您需要執行:
cd /opt/opscode/embedded/service/partybus ; /opt/opscode/embedded/bin/bundle exec bin/partybus init
然後再次執行重新配置。鑑於您正在試用 Enterprise Chef,您還可以聯繫支持人員尋求幫助。這兩個問題都應該在下一個版本的 Chef 伺服器中得到解決。我很抱歉他們給你帶來了問題。