"undefined method `each' for "standard":String" on /admin/health_check page
Summary
Running on FreeBSD 10.3
gitlab-8.16.8_1
gitlab-shell-4.1.1
gitlab-workhorse-1.3.0
Steps to reproduce
Unsure, health check was 'healthy' in the past but after a recent upgrade health check reports 'unhealthy'.
What is the current bug behavior?
Health Check reports 'unhealthy' with message:
undefined method `each' for "standard":String
Other issues with gitlab are also noticed, such as:
- 'Activity' page for any repository and all sub-pages are blank.
- Submitting a comment on an issue will return an error message even though comment is saved successfully and can be seen when refreshing/renavigating to the page.
What is the expected correct behavior?
Healthy status for health check. Activity pages report activity, comments submitted successfully.
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
W, [[redacted] #80289] WARN -- : You are setting a key that conflicts with a built-in method OmniAuth::AuthHash::InfoHash#name defined at /usr/local/www/gitlab/vendor/bundle/ruby/2.3/gems/omniauth-1.3.2/lib/omniauth/auth_hash.rb:34. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method. W, [[redacted] #80289] WARN -- : You are setting a key that conflicts with a built-in method OmniAuth::Strategy::Options#method defined in Kernel. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method. [DEPRECATION] 'Rack::Attack.blacklist' is deprecated. Please use 'blocklist' instead.
System information System: Current User: git Using RVM: no Ruby Version: 2.3.3p222 Gem Version: 2.6.11 Bundler Version:1.14.6 Rake Version: 12.0.0 Sidekiq Version:4.2.10
GitLab information Version: 8.16.8 Revision: fatal: Not a git repository (or any of the parent directories): .git Directory: /usr/local/www/gitlab DB Adapter: postgresql URL: [redacted] HTTP Clone URL: [redacted] SSH Clone URL: [redacted] Using LDAP: no Using Omniauth: no
GitLab Shell Version: 4.1.1 Repository storage paths:
- default: /usr/home/git/repositories/ Hooks: /usr/local/share/gitlab-shell/hooks/ Git: /usr/local/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
W, [[redacted] #1509] WARN -- : You are setting a key that conflicts with a built-in method OmniAuth::AuthHash::InfoHash#name defined at /usr/local/www/gitlab/vendor/bundle/ruby/2.3/gems/omniauth-1.3.2/lib/omniauth/auth_hash.rb:34. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method. W, [[redacted] #1509] WARN -- : You are setting a key that conflicts with a built-in method OmniAuth::Strategy::Options#method defined in Kernel. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method. [DEPRECATION] 'Rack::Attack.blacklist' is deprecated. Please use 'blocklist' instead. Checking GitLab Shell ...
GitLab Shell version >= 4.1.1 ? ... OK (4.1.1) Repo base directory exists? default... yes Repo storage directories are symlinks? default... no Repo paths owned by git:git? default... yes Repo paths access is drwxrws---? default... yes hooks directories in repos are links: ... [redacted, all either OK or empty]
Running /usr/local/share/gitlab-shell/bin/check Check GitLab API access: OK Access to /home/git/.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 with autocrlf=input? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config outdated? ... no Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory setup correctly? ... yes Init script exists? ... no Try fixing it: Install the init script For more information see: doc/install/installation.md in section "Install Init Script" Please fix the error above and rerun the checks. Init script up-to-date? ... can't check because of previous errors projects have namespace: ... [redacted, all OK] Redis version >= 2.8.0? ... yes Ruby version >= 2.1.0 ? ... yes (2.3.3) Your git bin path is "/usr/local/bin/git" Git version >= 2.7.3 ? ... yes (2.12.1) Active users: [redacted]
Checking GitLab ... Finished
Possible fixes
Tried searching around for explanations, came up empty handed unfortunately.