Failing to bootstrap after configuring SSL


(Andrew Kraut) #1

I added the web ssl template, then issued ./launcher rebuild app and now it fails to bootstrap:

FAILED
--------------------
RuntimeError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 362 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:105:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"web", "cmd"=>["gem update bundler", "chown -R discourse $home", "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'"]}
0ffcf6cbc3b36241997d17f99638c61fb8405441417adcb75aade0305c1acf9b
FAILED TO BOOTSTRAP

Further up, I also see this:

I, [2014-10-25T07:58:38.004253 #45]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'
rake aborted!
NoMethodError: undefined method `after_after_initialize' for #<Plugin::Instance:0x007f161e6b0ab8>
/var/www/discourse/plugins/discourse-plugin-permalink/plugin.rb:12:in `activate!'
/var/www/discourse/lib/plugin/instance.rb:171:in `instance_eval'
/var/www/discourse/lib/plugin/instance.rb:171:in `activate!'
/var/www/discourse/lib/discourse.rb:84:in `block in activate_plugins!'
/var/www/discourse/lib/discourse.rb:84:in `each'
/var/www/discourse/lib/discourse.rb:84:in `activate_plugins!'
/var/www/discourse/config/application.rb:149:in `<class:Application>'
/var/www/discourse/config/application.rb:19:in `<module:Discourse>'
/var/www/discourse/config/application.rb:18:in `<top (required)>'
/var/www/discourse/Rakefile:5:in `require'
/var/www/discourse/Rakefile:5:in `<top (required)>'
(See full trace by running task with --trace)

Any ideas what’s going wrong?


(Sam Saffron) #2

Looks like a bug in your container config


(Andrew Kraut) #3

This morning I reverted my container config to the Pre-SSL config and I’m still having the same issue. Looking at that second snippet, doesn’t it look like a bug within discourse-plugin-permalink?


(Sam Saffron) #4

I can’t help debugging this without seeing the container definition

It looks like a typo in the hooks section