在 Suse SLES 11 上安装 Gitlab - 无法登录 Gitlab GUI
Gitlab Installation on Suse SLES 11 - Not able to login to Gitlab GUI
安装成功后,我仍然无法登录gitlab GUI。它不断抛出“无效的电子邮件或密码”
以下是其他人建议的推荐解决方案的输出:
sudo -u git -H bundle exec rake gitlab:check RAI LS_ENV=production
Checking Environment ...
Git configured for git user? ... yes
Has python2? ... yes
python2 is supported version? ... yes
Checking Environment ... Finished
Checking GitLab Shell ...
GitLab Shell version >= 1.7.1 ? ... OK (1.7.1)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by git:git? ... yes
Repo base access is drwxrws---? ... yes
update hook up-to-date? ... yes
update hooks in repos are links: ... can't check, you have no projects
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Checking Sidekiq ... Finished
Checking GitLab ...
Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
projects have namespace: ... can't check, you have no projects
Projects have satellites? ... can't check, you have no projects
Redis version >= 2.0.0? ... yes
Your git bin path is "/usr/bin/git"
Git version >= 1.7.10 ? ... yes (1.7.12)
Checking GitLab ... Finished
和
bundle exec rake db:seed_fu RAILS_ENV=production
== Seed from /home/git/gitlab/db/fixtures/production/001_admin.rb
INFO: Sidekiq client using redis://localhost:6379 with options {:namespace=>"resque:gitlab"}
Administrator account created:
login.........admin@local.host
password......5iveL!fe
现在的问题是我启动 url 并进入登录屏幕,但不幸的是,当我输入上面生成的凭据时,我不断收到有关无效 email/password.
的错误
您有什么建议可以克服该错误消息?
这似乎是一个反复出现的问题,紧随其后的是issue 7226。
建议的一些解决方法是:
The command gitlab-rake gitlab:setup RAILS_ENV=production
solves the problem.
It is impossible to login as root
but it is possible to sign in new standard users and they log in just fine; when this happens the command gitlab-rake gitlab:setup RAILS_ENV=production
fixes root login (possibly erasing everything else in the db, I guess).
OP KronnorK confirms 是设置问题(AD设置的用户和密码错误),修复后,setup命令恢复了系统。
安装成功后,我仍然无法登录gitlab GUI。它不断抛出“无效的电子邮件或密码”
以下是其他人建议的推荐解决方案的输出:
sudo -u git -H bundle exec rake gitlab:check RAI LS_ENV=production
Checking Environment ...
Git configured for git user? ... yes
Has python2? ... yes
python2 is supported version? ... yes
Checking Environment ... Finished
Checking GitLab Shell ...
GitLab Shell version >= 1.7.1 ? ... OK (1.7.1)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by git:git? ... yes
Repo base access is drwxrws---? ... yes
update hook up-to-date? ... yes
update hooks in repos are links: ... can't check, you have no projects
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Checking Sidekiq ... Finished
Checking GitLab ...
Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
projects have namespace: ... can't check, you have no projects
Projects have satellites? ... can't check, you have no projects
Redis version >= 2.0.0? ... yes
Your git bin path is "/usr/bin/git"
Git version >= 1.7.10 ? ... yes (1.7.12)
Checking GitLab ... Finished
和
bundle exec rake db:seed_fu RAILS_ENV=production
== Seed from /home/git/gitlab/db/fixtures/production/001_admin.rb
INFO: Sidekiq client using redis://localhost:6379 with options {:namespace=>"resque:gitlab"}
Administrator account created:
login.........admin@local.host
password......5iveL!fe
现在的问题是我启动 url 并进入登录屏幕,但不幸的是,当我输入上面生成的凭据时,我不断收到有关无效 email/password.
的错误您有什么建议可以克服该错误消息?
这似乎是一个反复出现的问题,紧随其后的是issue 7226。
建议的一些解决方法是:
The command
gitlab-rake gitlab:setup RAILS_ENV=production
solves the problem.It is impossible to login as
root
but it is possible to sign in new standard users and they log in just fine; when this happens the commandgitlab-rake gitlab:setup RAILS_ENV=production
fixes root login (possibly erasing everything else in the db, I guess).
OP KronnorK confirms