If you are using PostgreSQL you can solve this by logging in to the GitLab database (gitlabhq_production) using a super user and running: ALTER git WITH SUPERUSER For MySQL you instead need to run: GRANT ALL PRIVILEGES ON *.* TO Both queries will grant the user super user permissions, ensuring you don't run into similar problems in the future (e.g. opt/git/gitlab/lib/gitlab/database/migration_helpers.rb:638:in `check_trigger_permissions!' /opt/git/gitlab/lib/gitlab/database/migration_helpers.rb:361:in `rename_column_concurrently' /opt/git/gitlab/db/migrate/20170629171610_rename_application_settings_signin_enabled_to_password_authentication_enabled.rb:9:in `up' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/migration.rb:611:in `exec_migration' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/migration.rb:592:in `block (2 levels) in migrate' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/migration.rb:591:in `block in migrate' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:292:in `with_connection' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/migration.rb:590:in `migrate' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/migration.rb:768:in `migrate' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/migration.rb:998:in `block in execute_migration_in_transaction' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/migration.rb:1046:in `ddl_transaction' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/migration.rb:997:in `execute_migration_in_transaction' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/migration.rb:959:in `block in migrate' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/migration.rb:955:in `each' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/migration.rb:955:in `migrate' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/migration.rb:823:in `up' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/migration.rb:801:in `migrate' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/tasks/database_tasks.rb:137:in `migrate' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/railties/databases.rake:44:in `block (2 levels) in ' /opt/git/gitlab/vendor/bundle/ruby/2.3.0/gems/rake-12.0.0/exe/rake:27:in `' Your database user is not allowed to create, drop, or execute triggers on the table application_settings.
Similarly, to reset a user’s password, open the user’s More menu and select Reset password.= 20170629171610 RenameApplicationSettingsSigninEnabledToPasswordAuthenticationEnabled: migrating - transaction_open?() -> 0.0000s rake aborted! StandardError: An error has occurred, all later migrations canceled: Your database user is not allowed to create, drop, or execute triggers on the table application_settings. You can also delete a user here by opening the user’s More menu, clicking Delete, and then confirming the deletion. However, you cannot grant users some superuser permissions. You can then add user privileges using third-party tools like psql.
New users receive minimal permissions by default. You can also delete a database here by opening its More menu, clicking Delete, and then confirming the deletion.Ĭreate new users in the Users section by entering a name in the Add new user field and clicking Save. To add or delete users or databases to a database cluster, click the name of the database to go to its Overview page, then select the Users & Databases tab.Ĭreate a new database in the Databases section by entering a name in the Add new database field and clicking Save.
To delete a database user with Godo, use the The official DigitalOcean V2 API client for Go. H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \ To delete a database user with cURL, call:
0 kommentar(er)
