Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Mon May 23 03:57 PM > root@[censored].com [/home/git/gitlab]#: sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
- System information
- System: Debian 7.10
- Current User: git
- Using RVM: no
- Ruby Version: 2.1.2p95
- Gem Version: 2.2.2
- Bundler Version:1.10.6
- Rake Version: 10.4.2
- Sidekiq Version:3.3.0
- GitLab information
- Version: 8.0.5
- Revision: 2c03667
- Directory: /home/git/gitlab
- DB Adapter: mysql2
- URL: https://git.[censored].com
- HTTP Clone URL: https://git.[censored].com/some-group/some-project.git
- SSH Clone URL: ssh://git@git.[censored].com:7889/some-group/some-project.git
- Using LDAP: no
- Using Omniauth: no
- GitLab Shell
- Version: 2.6.5
- Repositories: /home/git/repositories/
- Hooks: /home/git/gitlab-shell/hooks/
- Git: /usr/bin/git
- Mon May 23 03:57 PM > root@[censored].com [/home/git/gitlab]#: sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
- Checking GitLab Shell ...
- GitLab Shell version >= 2.6.5 ? ... OK (2.6.5)
- 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
- hooks directories in repos are links: ...
- Blackterminal / Cronjob ... ok
- Blackterminal / Badterminal ... ok
- ELF / HFS bashing ... ok
- wirehack7 / Against ... ok
- Blackterminal / Badterminal.org Mini Site ... ok
- wopot / blacklistchecker ... ok
- wirehack7 / ipconfig ... ok
- shibumi / virustotal ... ok
- Blackterminal / Pastebin Crawler ... ok
- shibumi / scan.sh ... ok
- Running /home/git/gitlab-shell/bin/check
- Check GitLab API access: FAILED. code: 503
- gitlab-shell self-check failed
- Try fixing it:
- Make sure GitLab is running;
- Check the gitlab-shell configuration file:
- sudo -u git -H editor /home/git/gitlab-shell/config.yml
- Please fix the error above and rerun the checks.
- 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
- Database is SQLite ... no
- 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? ... yes
- Init script up-to-date? ... yes
- projects have namespace: ...
- Blackterminal / Cronjob ... yes
- Blackterminal / Badterminal ... yes
- ELF / HFS bashing ... yes
- wirehack7 / Against ... yes
- Blackterminal / Badterminal.org Mini Site ... yes
- wopot / blacklistchecker ... yes
- wirehack7 / ipconfig ... yes
- shibumi / virustotal ... yes
- Blackterminal / Pastebin Crawler ... yes
- shibumi / scan.sh ... yes
- Redis version >= 2.4.0? ... yes
- Ruby version >= 2.1.0 ? ... yes (2.1.2)
- Your git bin path is "/usr/bin/git"
- Git version >= 1.7.10 ? ... yes (1.7.10)
- Active users: 10
- Checking GitLab ... Finished
- Mon May 23 03:57 PM > root@[censored].com [/home/git/gitlab]#: cat /home/git/gitlab-shell/config.yml
- #
- # If you change this file in a Merge Request, please also create
- # a Merge Request on https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests
- #
- # GitLab user. git by default
- user: git
- # Url to gitlab instance. Used for api calls. Should end with a slash.
- # Default: http://localhost:8080/
- # You only have to change the default if you have configured Unicorn
- # to listen on a custom port, or if you have configured Unicorn to
- # only listen on a Unix domain socket.
- gitlab_url: "https://git.[censored].com"
- # See installation.md#using-https for additional HTTPS configuration details.
- http_settings:
- # user: someone
- # password: somepass
- # ca_file: /etc/ssl/cert.pem
- # ca_path: /etc/pki/tls/certs
- self_signed_cert: false
- # Repositories path
- # Give the canonicalized absolute pathname,
- # REPOS_PATH MUST NOT CONTAIN ANY SYMLINK!!!
- # Check twice that none of the components is a symlink, including "/home".
- repos_path: "/home/git/repositories"
- # File used as authorized_keys for gitlab user
- auth_file: "/home/git/.ssh/authorized_keys"
- # File that contains the secret key for verifying access to GitLab.
- # Default is .gitlab_shell_secret in the root directory.
- # secret_file: "/home/git/gitlab-shell/.gitlab_shell_secret"
- # Redis settings used for pushing commit notices to gitlab
- redis:
- bin: /usr/bin/redis-cli
- # host: 127.0.0.1
- # port: 6379
- # pass: redispass # Allows you to specify the password for Redis
- database: 0
- socket: /var/run/redis/redis.sock # Comment out this line if you want to use TCP
- namespace: resque:gitlab
- # Log file.
- # Default is gitlab-shell.log in the root directory.
- # log_file: "/home/git/gitlab-shell/gitlab-shell.log"
- # Log level. INFO by default
- log_level: INFO
- # Audit usernames.
- # Set to true to see real usernames in the logs instead of key ids, which is easier to follow, but
- # incurs an extra API call on every gitlab-shell command.
- audit_usernames: false
- # Enable git-annex support
- # git-annex allows managing files with git, without checking the file contents into git
- # See https://git-annex.branchable.com/ for documentation
- # If enabled, git-annex needs to be installed on the server where gitlab-shell is setup
- # For Debian and Ubuntu systems this can be done with: sudo apt-get install git-annex
- # For CentOS: sudo yum install epel-release && sudo yum install git-annex
- git_annex_enabled: false
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement