usterki instalacji gitlab-5,0 - Rake przerwana

problemy z zainstalowaniem gitlab-5,0usterki instalacji gitlab-5,0 - Rake przerwana

https://github.com/gitlabhq/gitlabhq/blob/5-0-stable/doc/install/installation.md#initialise-database-and-activate-advanced-features

[email protected]:/home/gitlab/gitlab# bundle exec rake gitlab:setup RAILS_ENV=production 
rake aborted! 
Access denied for user 'root'@'localhost' (using password: YES) 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/mysql2-0.3.11/lib/mysql2/client.rb:44:in `connect' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/mysql2-0.3.11/lib/mysql2/client.rb:44:in `initialize' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/mysql2_adapter.rb:16:in `new' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/mysql2_adapter.rb:16:in `mysql2_connection' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/abstract/connection_pool.rb:315:in `new_connection' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/abstract/connection_pool.rb:325:in `checkout_new_connection' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/abstract/connection_pool.rb:247:in `block (2 levels) in checkout' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/abstract/connection_pool.rb:242:in `loop' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/abstract/connection_pool.rb:242:in `block in checkout' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/abstract/connection_pool.rb:239:in `checkout' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/abstract/connection_pool.rb:102:in `block in connection' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/abstract/connection_pool.rb:101:in `connection' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/abstract/connection_pool.rb:410:in `retrieve_connection' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/abstract/connection_specification.rb:171:in `retrieve_connection' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/abstract/connection_specification.rb:145:in `connection' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/model_schema.rb:308:in `clear_cache!' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/railtie.rb:104:in `block (2 levels) in <class:Railtie>' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.13/lib/active_support/callbacks.rb:418:in `_run__807030537706508428__prepare__2182945095053453794__callbacks' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.13/lib/active_support/callbacks.rb:405:in `__run_callback' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.13/lib/active_support/callbacks.rb:385:in `_run_prepare_callbacks' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.13/lib/active_support/callbacks.rb:81:in `run_callbacks' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.13/lib/action_dispatch/middleware/reloader.rb:74:in `prepare!' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.13/lib/action_dispatch/middleware/reloader.rb:48:in `prepare!' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/application/finisher.rb:47:in `block in <module:Finisher>' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/initializable.rb:30:in `instance_exec' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/initializable.rb:30:in `run' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/initializable.rb:55:in `block in run_initializers' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/initializable.rb:54:in `each' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/initializable.rb:54:in `run_initializers' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/application.rb:136:in `initialize!' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/railtie/configurable.rb:30:in `method_missing' 
/home/gitlab/gitlab/config/environment.rb:5:in `<top (required)>' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/backports-2.6.7/lib/backports/tools.rb:314:in `require' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/backports-2.6.7/lib/backports/tools.rb:314:in `require_with_backports' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.13/lib/active_support/dependencies.rb:251:in `block in require' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.13/lib/active_support/dependencies.rb:236:in `load_dependency' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.13/lib/active_support/dependencies.rb:251:in `require' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/application.rb:103:in `require_environment!' 
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/application.rb:297:in `block (2 levels) in initialize_tasks' 
Tasks: TOP => gitlab:setup => environment 
(See full trace by running task with --trace)

jakiś pomysł?

Źródło

2013-03-24 Proverbio

To jest sekcja Initialise Database and Activate Advanced Features:

sudo -u git -H bundle exec rake gitlab:setup RAILS_ENV=production

Oznacza to, że mają do wykonania tego polecenia jako git, a nie jako root (który nie został zapewniony dostęp do bazy danych).

Upewnij się, że plik konfiguracyjny database.yml wygląda jak this one (jeśli masz zainstalowany mysql i chcesz używać bazy danych mysql).

production: 
    adapter: mysql2 
    encoding: utf8 
    reconnect: false 
    database: gitlabhq_production 
    pool: 5 
    username: root 
    password: "secure password" 
    # host: localhost 
    # socket: /tmp/mysql.sock

Czyni zadeklarować dostęp do konta root, ale jest czysto deklaratywny MySQL konto (to nic wspólnego z użytkownikiem root)

Źródło

2013-03-24 10:21:40 VonC

Interesujące, że chcą cię sudo git, kiedy określają (przynajmniej teraz), że git nie powinien otrzymać hasła, więc nie może się zalogować, a więc nie ma sudo. Plus, git musiałby być w pliku sudoers. https://github.com/gitlabhq/gitlab-recipes/blob/master/install/centos/README.md – MDMoore313

Jeśli podążasz samouczek i następnie kroki dla konfiguracji bazy danych MySQL skonfigurowałeś bazę danych tak, aby używała gitlab dla nazwy użytkownika.

# Create a user for GitLab. (change $password to a real password) 
mysql> CREATE USER 'gitlab'@'localhost' IDENTIFIED BY '$password';

, ale jeśli plik database.yml próbuje zalogować się do bazy danych przy użyciu poświadczeń root.

production: 
    adapter: mysql2 
    encoding: utf8 
    reconnect: false 
    database: gitlabhq_production 
    pool: 5 
    username: root 
    password: "secure password" 
    # host: localhost 
    # socket: /tmp/mysql.sock

Dlatego właśnie zobaczysz ten błąd. Zmień plik database.yml, aby odzwierciedlić logowanie utworzone w części samouczka dotyczącej konfiguracji bazy danych.

production: 
    adapter: mysql2 
    encoding: utf8 
    reconnect: false 
    database: gitlabhq_production 
    pool: 5 
    username: gitlab 
    password: "$password" 
    # host: localhost 
    # socket: /tmp/mysql.sock

Źródło

2013-05-03 21:11:23 myappleguy

usterki instalacji gitlab-5,0 - Rake przerwana

Odpowiedz

Powiązane problemy