FAILED TO BOOTSTRAP help


(Алексей Копаев) #1

Help, what could be the problem?
:point_right: log https://pastebin.com/iiBzj7k0

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 617 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:108: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'"]}
0509c55c266678028b265fb0e084a73bad79f7f6a598d964d4896c60c372ca51
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one
root@151435:/var/discourse# 

  after_code:
- exec:
    cd: $home/plugins
    cmd:
      - git clone https://github.com/discourse/docker_manager.git

PS
Disconnected all plug-ins, but it does not start

2017-08-30 05:50:35.663 UTC [466] discourse@discourse STATEMENT:  DROP TRIGGER IF EXISTS users_email_readonly ON users;
	DROP FUNCTION IF EXISTS raise_users_email_readonly();
	
rake aborted!
PG::DependentObjectsStillExist: ERROR:  cannot drop function raise_users_email_readonly() because other objects depend on it
DETAIL:  trigger users_email_readonly on table backup.users depends on function raise_users_email_readonly()

(Alan Tan) #2

Are you on the latest branch?


(Алексей Копаев) #3

Maybe yes. Today I tried to update.


(Alan Tan) #5

This should fix it

The function was still being referenced in the backup schema which is created when you’ve done a restore.


(Алексей Копаев) #6

No, it did not help, under the link error log :disappointed_relieved:

https://pastebin.com/GkcdLTeX


(Alan Tan) #7

I don’t think you ran it with the right commit?


(Алексей Копаев) #8

Without plug-ins it all worked) Thanks.
I’ll try to download with plugins.


(Jeff Atwood) #9