How to solve a problem? and how to see the puma log? I can not find anywhere else.

The situation is this: I want to do staging for the project.

1) made a project on a test server (raspberry).

2) I restored the database (postgresql) from the production backup. Migrations did not roll, there are 1000 of them and a lot of them fall off, you have to climb and comment on the code, and this is not an option.

I use nginx, which looks at puma. I'm running

bundle exec puma -e production -b unix:///home/ivanov/www/ivanov/current/apps/www/tmp/sockets/puma.sock

and the error falls out:

 DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released. (called from <top (required)> at /home/ivanov/www/ivanov/releases/20170622115720/apps/www/config/environment.rb:9) /home/ivanov/www/ivanov/releases/20170622115720/apps/www/config/initializers/bypass_ssl_verification_for_open_uri.rb:1: warning: already initialized constant OpenSSL::SSL::VERIFY_PEER /home/ivanov/.rvm/gems/ruby-2.0.0-p247@parts-script-new-admin/gems/actionpack-3.2.13/lib/action_dispatch/http/mime_type.rb:102: warning: already initialized constant Mime::PDF /home/ivanov/.rvm/gems/ruby-2.0.0-p247@parts-script-new-admin/gems/actionpack-3.2.13/lib/action_dispatch/http/mime_type.rb:102: warning: previous definition of PDF was here ! Unable to load application: ActiveRecord::StatementInvalid: PG::Error: ОШИБКА: нет доступа к отношению site_configs : SELECT "site_configs".* FROM "site_configs" LIMIT 1 /home/ivanov/.rvm/gems/ruby-2.0.0-p247@parts-script-new-admin/gems/activerecord-3.2.13/lib/active_record/connection_adapters/postgresql_adapter.rb:1161:in `async_exec': PG::Error: ОШИБКА: нет доступа к отношению site_configs (ActiveRecord::StatementInvalid) : SELECT "site_configs".* FROM "site_configs" LIMIT 1

The database.yml specifies the owners of the table, and it has GRANT ALL privileges ON DATABASE

in application logs:

 Connecting to database specified by database.yml Connecting to database specified by database.yml Connecting to database specified by database.yml Connecting to database specified by database.yml Connecting to database specified by database.yml Connecting to database specified by database.yml Connecting to database specified by database.yml Connecting to database specified by database.yml
  • and from rails dbconsole there is an access (in a production environment)? - Mikhail Vaysman
  • you mean directly production where the application is deployed, or where do I want to deploy staging? - evans
  • I mean -e production - Mikhail Vaysman
  • To roll migrations over backup? .. but why is it even necessary? Maybe you should remove this paragraph from the question altogether? - D-side
  • I on the contrary did not roll, I understand that it is not necessary. just explained why the migration did not. - evans

0