2016-05-26 3 views
0

私は談話をブートストラップにより、障害を持っている: はRuntimeError:CDの/ var/www /の談話& &のsu談話を-c 'バンドルexec rake assets:プリコンパイル'がリターン#で失敗しました。はRuntimeError:CDの/ var/www /の談話&& SU談話-c「バンドルのexecすくい資産:

171:signal-handler (1464162030) Received SIGTERM scheduling shutdown... 
     2016-05-25 07:40:30 UTC [42-2] LOG: received fast shutdown request 
     2016-05-25 07:40:30 UTC [42-3] LOG: aborting any active transactions 
     2016-05-25 07:40:30 UTC [49-2] LOG: autovacuum launcher shutting down 
     2016-05-25 07:40:30 UTC [46-1] LOG: shutting down 
     2016-05-25 07:40:30 UTC [46-2] LOG: database system is shut down 
     171:M 25 May 07:40:30.426 # User requested shutdown... 
     171:M 25 May 07:40:30.427 * Saving the final RDB snapshot before exiting. 
     171:M 25 May 07:40:30.444 * DB saved on disk 
     171:M 25 May 07:40:30.445 # Redis is now ready to exit, bye bye... 


     FAILED 
     -------------------- 
     RuntimeError: cd /var/www/discourse && su discourse -c 'bundle exec rake assets:precompile' failed with return #<Process::Status: pid 289 exit 137> 
     Location of failure: /pups/lib/pups/exec_command.rb:105:in `spawn' 
     exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --verbose --without test --without development'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bundle exec rake assets:precompile'"]} 
     b61c02fe6e3dbd6ab382d23592fab25bdcba02fc7666f20cd9874c521bf2e537 
     ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one 
     [email protected]:/var/discourse# 

また、私は再構築して破壊しようとしましたが、残念なことに助けにはなりません。

[email protected]:~# sudo ./launcher rebuild app 
sudo: ./launcher: command not found 
[email protected]:~# cd /var/discourse 
[email protected]:/var/discourse# sudo ./launcher rebuild app 
Ensuring launcher is up to date 
Fetching origin 
remote: Counting objects: 4, done. 
remote: Compressing objects: 100% (4/4), done. 
remote: Total 4 (delta 0), reused 0 (delta 0), pack-reused 0 
Unpacking objects: 100% (4/4), done. 
From https://github.com/discourse/discourse_docker 
    5819e89..8c92508 master  -> origin/master 
Updating Launcher 
Updating 5819e89..8c92508 
Fast-forward 
templates/postgres.template.yml | 1 - 
1 file changed, 1 deletion(-) 
Usage: launcher COMMAND CONFIG [--skip-prereqs] [--docker-args STRING] 
Commands: 
    start:  Start/initialize a container 
    stop:  Stop a running container 
    restart: Restart a container 
    destroy: Stop and remove a container 
    enter:  Use nsenter to get a shell into a container 
    logs:  View the Docker logs for a container 
    bootstrap: Bootstrap a container for the config based on a template 
    rebuild: Rebuild a container (destroy old, bootstrap, start new) 
    cleanup: Remove all containers that have stopped for > 24 hours 

Options: 
    --skip-prereqs    Don't check launcher prerequisites 
    --docker-args    Extra arguments to pass when running docker 

    [email protected]:/var/discourse# sudo ./launcher start app 

    + /usr/bin/docker run -d --restart=always -e LANG=en_US.UTF-8 -e RAILS_ENV=production -e UNICORN_WORKERS=3 -e UNICORN_SIDEKIQS=1 -e RUBY_GLOBAL_METHOD_CACHE_SIZE=131072 -e DISCOURSE_DB_SOCKET=/var/run/postgresql -e DISCOURSE_DB_HOST= -e DISCOURSE_DB_PORT= -e DISCOURSE_HOSTNAME=cleaneone.com -e [email protected] -e DISCOURSE_SMTP_ADDRESS=smtp.gmail.com -h ubuntu-512mb-nyc2-01-app -e DOCKER_HOST_IP=172.17.0.1 --name app -t -p 80:80 -p 443:443 -v /var/discourse/shared/standalone:/shared -v /var/discourse/shared/standalone/log/var-log:/var/log --mac-address 02:0f:a9:e5:74:fb local_discourse/app /sbin/boot 
    Unable to find image 'local_discourse/app:latest' locally 
    Pulling repository docker.io/local_discourse/app 
    /usr/bin/docker: Error: image local_discourse/app not found. 
    See '/usr/bin/docker run --help'. 

[email protected]:/var/discourse# sudo ./launcher destroy app 
+ /usr/bin/docker stop -t 10 app 
Error response from daemon: No such container: app 
app was not found 

答えて

0

あなたは談話を更新するか、最初の時間のためにそれをインストールしている場合、私は知ることができないので、私は、いくつかのヒントを書き留め:再構築起動する前に

、ランチャーとすべてが更新されていることを確認してください。

cd /var/discourse 
git pull 
./launcher rebuild app 

あなたは、コンテナを自分で起動しようとすることができる「ブートストラップに失敗しました」というエラーがあります:

./launcher start app 
をこれは、バックオンラインフォーラムを取ることドッカをチェックしない場合は

が更新されます。

docker --version 

そうでない場合は、次の

apt-get update; apt-get upgrade 
関連する問題