Fresh install (CentOS 7), cannot set password: "422 The change you requested was rejected"
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Hi,
I installed GitLab CE on a brand new CentOS 7 VM yesterday, I tried 3 times actually (create VM with CentOS 7, install GitLab). I followed the official instructions for CentOS 7 with Omnibus. During the installation everything goes fine, the gitlab-ctl reconfigure runs without errors, I also tried restarting GitLab after that. I then fire-up my browser, GitLab loads and I get a page asking me to change the root password. I comply and then I get this error: "422 The change you requested was rejected". I also tried updating the OS. When I look for errors in the log folder I get:
$ sudo grep -r ERROR /var/log/gitlab/*
Error fetching job: No such file or directory - connect(2) for /var/opt/gitlab/redis/redis.socket
ERROR: /opt/gitlab/embedded/lib/ruby/2.3.0/socket.rb:1207:in '__connect_nonblock'
ERROR: /opt/gitlab/embedded/lib/ruby/2.3.0/socket.rb:1207:in 'connect_nonblock'
ERROR: /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/redis-3.3.3/lib/redis/connection/ruby.rb:257:in 'connect'
ERROR: /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/redis-3.3.3/lib/redis/connection/ruby.rb:308:in 'connect'
ERROR: /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/redis-3.3.3/lib/redis/client.rb:336:in 'establish_connection'it seems to somehow get back on its legs later on though:
ERROR: /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/sidekiq-5.0.0/lib/sidekiq/util.rb:26:in 'block in safe_thread'
INFO: Shutting down
INFO: Scheduler exiting...
INFO: Terminating quiet workers
INFO: Scheduler exiting...
INFO: Pausing to allow workers to finish...
INFO: Bye!
INFO: Booting Sidekiq 5.0.0 with redis options {:path=>"/var/opt/gitlab/redis/redis.socket", :namespace=>"resque:gitlab", :url=>nil}
INFO: Cron Jobs - add job with name: stuck_ci_jobs_worker
INFO: Cron Jobs - add job with name: expire_build_artifacts_worker
INFO: Cron Jobs - add job with name: pipeline_schedule_worker
INFO: Cron Jobs - add job with name: repository_check_worker
INFO: Cron Jobs - add job with name: admin_email_worker
INFO: Cron Jobs - add job with name: repository_archive_cache_worker
INFO: Cron Jobs - add job with name: import_export_project_cleanup_worker
INFO: Cron Jobs - add job with name: requests_profiles_worker
INFO: Cron Jobs - add job with name: remove_expired_members_worker
INFO: Cron Jobs - add job with name: remove_expired_group_links_worker
INFO: Cron Jobs - add job with name: prune_old_events_worker
INFO: Cron Jobs - add job with name: trending_projects_worker
INFO: Cron Jobs - add job with name: remove_unreferenced_lfs_objects_worker
INFO: Cron Jobs - add job with name: stuck_import_jobs_worker
INFO: Cron Jobs - add job with name: gitlab_usage_ping_worker
INFO: Cron Jobs - add job with name: schedule_update_user_activity_worker
INFO: Cron Jobs - add job with name: remove_old_web_hook_logs_worker
INFO: Running in ruby 2.3.3p222 (2016-11-21 revision 56859) [x86_64-linux]
INFO: See LICENSE and the LGPL-3.0 for licensing details.
INFO: Upgrade to Sidekiq Pro for more features and support: http://sidekiq.org
INFO: Starting processing, hit Ctrl-C to stop
StuckImportJobsWorker JID-ad9e9f720fe8508614e23008 INFO: start
StuckImportJobsWorker JID-ad9e9f720fe8508614e23008 INFO: done: 0.054 sec
PipelineScheduleWorker JID-d829cd62e64fde9105339983 INFO: start
PipelineScheduleWorker JID-d829cd62e64fde9105339983 INFO: done: 0.037 sec
RepositoryCheck::BatchWorker JID-b5bbb22dd4eb83421acc72ce INFO: start
RepositoryCheck::BatchWorker JID-b5bbb22dd4eb83421acc72ce INFO: done: 0.044 sec
ExpireBuildArtifactsWorker JID-21741acdb51109b199023d5f INFO: start
ExpireBuildArtifactsWorker JID-21741acdb51109b199023d5f INFO: done: 0.048 sec
RepositoryArchiveCacheWorker JID-9f7ca83e1ffa9f5a4fe3f1ff INFO: start
RepositoryArchiveCacheWorker JID-9f7ca83e1ffa9f5a4fe3f1ff INFO: done: 0.014 sec
ImportExportProjectCleanupWorker JID-b196a1036ae224dfb7962d00 INFO: start
ImportExportProjectCleanupWorker JID-b196a1036ae224dfb7962d00 INFO: done: 0.014 sec
PruneOldEventsWorker JID-35d8598d4e5d0427bb3a2781 INFO: start
RequestsProfilesWorker JID-9ded3ea0f23b3db9e74ab7d9 INFO: start
RequestsProfilesWorker JID-9ded3ea0f23b3db9e74ab7d9 INFO: done: 0.011 sec
StuckCiJobsWorker JID-f90001b004ab2de315c699cb INFO: start
PruneOldEventsWorker JID-35d8598d4e5d0427bb3a2781 INFO: done: 0.053 sec
StuckCiJobsWorker JID-f90001b004ab2de315c699cb INFO: done: 0.051 sec
RemoveExpiredMembersWorker JID-54e878f0c6fa04893f8bc67c INFO: start
RemoveExpiredGroupLinksWorker JID-18e606aa08793d31703c80ff INFO: start
RemoveExpiredMembersWorker JID-54e878f0c6fa04893f8bc67c INFO: done: 0.045 sec
RemoveExpiredGroupLinksWorker JID-18e606aa08793d31703c80ff INFO: done: 0.031 sec
StuckImportJobsWorker JID-696827eb5118983618ee9f51 INFO: start
StuckImportJobsWorker JID-696827eb5118983618ee9f51 INFO: done: 0.036 sec
PipelineScheduleWorker JID-20223d583a5195e3d29cfd19 INFO: start
PipelineScheduleWorker JID-20223d583a5195e3d29cfd19 INFO: done: 0.036 sec
RemoveUnreferencedLfsObjectsWorker JID-3021086eb4c48a80aa6b7c88 INFO: startso I am not sure this is the issue. My VM has on particularity, I am not sure this is relevant though since it should be transparent; my /var, /home, /opt are all mounted using bind, the target directories are all in /data, which is itself a partition on another drive. The OS itself has no issues and I don't see how this would cause issues. This is the only particularity. Here is the output from some commands I have seen you ask for:
$ sudo gitlab-rake gitlab:check
Checking GitLab Shell ...
GitLab Shell version >= 5.1.1 ? ... OK (5.1.1)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ... can't check, you have no projects
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
Send ping to redis server: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Reply by email ...
Reply by email is disabled in config/gitlab.yml
Checking Reply by email ... Finished
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads director y tmp has correct permissions? ... skipped (no tmp uploads folder yet)
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ... can't check, you have no projects
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.3 ? ... yes (2.3.3)
Git version >= 2.7.3 ? ... yes (2.13.0)
Active users: ... 1
Checking GitLab ... Finishedand
$ sudo gitlab-rake gitlab:env:info
System information
System:
Current User: git
Using RVM: no
Ruby Version: 2.3.3p222
Gem Version: 2.6.6
Bundler Version:1.13.7
Rake Version: 10.5.0
Redis Version: 3.2.5
Git Version: 2.13.0
Sidekiq Version:5.0.0
Go Version: unknown
GitLab information
Version: 9.3.5
Revision: 0c9ceb3
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: http://example.com
HTTP Clone URL: http://example.com/some-group/some-project.git
SSH Clone URL: git@example.com:some-group/some-project.git
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 5.1.1
Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks
Git: /opt/gitlab/embedded/bin/gitThank you for your help, Gabriel
Edited by 🤖 GitLab Bot 🤖