I upgraded from Gitlab 7.0 to 7.5.3 following the guidelines.
All went well but one issue remaining is that the automatic sync of sidekiq with gitlab-shell authorized_keys file is not working anymore.
Neither add nor delete.
Log files did not state anything, after e.g. adding a key I only see GitlabShellWorker executing successfully:
sidekiq.log:
2015-01-06T08:31:26Z 3292 TID-kjwek GitlabShellWorker JID-3b65f0ad00be156f30a22a62 INFO: start
2015-01-06T08:31:27Z 3292 TID-kjwek GitlabShellWorker JID-3b65f0ad00be156f30a22a62 INFO: done: 0.589 sec
2015-01-06T08:35:00Z 3292 TID-kjwek Sidekiq::Extensions::DelayedMailer JID-9c4837cd0acb34cb78cf5148 INFO: start
2015-01-06T08:35:28Z 3292 TID-kjwek Sidekiq::Extensions::DelayedMailer JID-9c4837cd0acb34cb78cf5148 INFO: done: 27.98 sec
No errors or hints in other logs.
System Information:
git#aux-git:~/gitlab> sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically loaded 2.9.1
Checking Environment ...
Git configured for git user? ... yes
Checking Environment ... Finished
Checking GitLab Shell ...
GitLab Shell version >= 2.2.0 ? ... OK (2.2.0)
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
Satellites access is drwxr-x---? ... yes
hooks directories in repos are links: ...
2/30 ... ok
2/47 ... ok
5/51 ... ok
2/53 ... ok
5/55 ... ok
2/56 ... ok
5/57 ... ok
2/58 ... ok
10/60 ... ok
32/61 ... ok
6/62 ... ok
9/64 ... ok
6/65 ... ok
2/66 ... ok
2/67 ... ok
2/68 ... ok
2/69 ... ok
2/70 ... ok
41/72 ... ok
2/74 ... ok
2/76 ... ok
Running /home/git/gitlab-shell/bin/check
Check GitLab API access: OK
Check directories and files:
/var/git/repositories: OK
/home/git/.ssh/authorized_keys: OK
Test redis-cli executable: redis-cli 2.8.6
Send ping to redis server: PONG
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking LDAP ...
LDAP users with access to your GitLab server (only showing the first 100 results)
Server: ldapmain
[..]
Checking LDAP ... Finished
Checking GitLab ...
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
Init script exists? ... yes
Init script up-to-date? ... yes
projects have namespace: ...
2/30 ... yes
2/47 ... yes
5/51 ... yes
2/53 ... yes
5/55 ... yes
2/56 ... yes
5/57 ... yes
2/58 ... yes
10/60 ... yes
32/61 ... yes
6/62 ... yes
9/64 ... yes
6/65 ... yes
2/66 ... yes
2/67 ... yes
2/68 ... yes
2/69 ... yes
2/70 ... yes
41/72 ... yes
2/74 ... yes
2/76 ... yes
Projects have satellites? ...
2/30 ... yes
2/47 ... yes
5/51 ... yes
2/53 ... yes
5/55 ... yes
2/56 ... yes
5/57 ... yes
2/58 ... yes
10/60 ... yes
32/61 ... yes
6/62 ... yes
9/64 ... yes
6/65 ... yes
2/66 ... yes
2/67 ... yes
2/68 ... yes
2/69 ... yes
2/70 ... yes
41/72 ... yes
2/74 ... yes
2/76 ... yes
Redis version >= 2.0.0? ... yes
Ruby version >= 2.0.0 ? ... yes (2.0.0)
Your git bin path is "/usr/bin/git"
Git version >= 1.7.10 ? ... yes (1.8.4)
Checking GitLab ... Finished
git#aux-git:~/gitlab> sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically loaded 2.9.1
System information
System: openSUSE project 13.1
Current User: git
Using RVM: no
Ruby Version: 2.0.0p247
Gem Version: 2.0.3
Bundler Version:1.6.2
Rake Version: 10.3.2
Sidekiq Version:2.17.0
GitLab information
Version: 7.5.3
Revision: b656b85
Directory: /home/git/gitlab
DB Adapter: mysql2
URL: http://aux-git
HTTP Clone URL: http://aux-git/some-project.git
SSH Clone URL: git#aux-git:some-project.git
Using LDAP: yes
Using Omniauth: no
GitLab Shell
Version: 2.2.0
Repositories: /var/git/repositories/
Hooks: /home/git/gitlab-shell/hooks/
Git: /usr/bin/git
Any ideas? Is it a Gitlab bug? I saw some changes in shell.rb since 7.0.
Thanks
Christian
So, sidekiq got updated from 2.17.1 to 2.17.2, and the changelog mentions a bug fix that changes how sidekiq can be invoked.
It's likely that your GitLab installation is still invoking sidekiq using the old style, something like the following.
sidekiq -q post_receive,mailer,system_hook,project_web_hook,gitlab_shell,common,default -e production
This no longer works. If that's the case you need to fix your launch scripts to invoke sidekiq as follows, instead.
sidekiq -q post_receive -q mailer -q system_hook -q project_web_hook -q gitlab_shell -q common -q default -e production
Related
Is there any way currently to install tiny_tds on a rails 7 app in Heroku on the latest stack? All the workarounds seem to be quite old / inoperable. I am trying to get an Azure MSSQL plugin up and running on Heroku.
I have been able to get the buildpack installed, but every time I use TDS (even making a connection via a heroku rails console), I get a timeout error. If I run the exact same command locally, it works.
client = TinyTds::Client.new host: '<host>.database.windows.net', database: "<database>",username: "<username>#<host>.database.windows.net",password: "<password>", port: 1433, azure: tr
ue, tds_version: 7.4, timeout: 300, login_timeout: 300
Adaptive Server connection timed out ([server].database.windows.net:1433)
Additionally, I can run the following successfully on a heroku bash prompt:
~ $ nslookup
> <host>.database.windows.net
Server: <server ip address>
Address: <server ip address>#53
Non-authoritative answer:
<host>.database.windows.net canonical name = <other host name>.eastus.database.windows.net.
<other host name>.eastus.database.windows.net canonical name = <other host name>.trafficmanager.net.
<other host name>.trafficmanager.net canonical name = <another host name>.control.database.windows.net.
Name: <another host name>.control.database.windows.net
Address: <ip address>
~ $ nc -zv <host>.database.windows.net 1433
Connection to <host>.database.windows.net (<ip address>) 1433 port [tcp/ms-sql-s] succeeded!
I have also tried using freetds on heroku (which is required for tinytds) and get timeouts, so I believe the error traces back to freetds' interaction with heroku or the heroku buildpack, of which I have tried a variety of versions (https://github.com/rails-sqlserver/heroku-buildpack-freetds):
On my local macbook, I can run the freetds tsql connection command to connect almost instantaneously to a variety of mssql databases (one on ec2 and two on azure), but the same command times out on heroku bash prompt:
~ $ tsql -H ***.rds.amazonaws.com -p 1433 -U *** -P ***
locale is "en_US.UTF-8"
locale charset is "UTF-8"
using default charset "UTF-8"
103Error 20002 (severity 9):
Adaptive Server connection failed
Error 20002 (severity 9):
Adaptive Server connection failed
There was a problem connecting to the server
FreeTDS version local and remote. I did no special "configuration" file settings other than setting the TDS_VERSION to 7.3 when installing the buildpack on heroku.
# LOCAL:
$ tsql -C
Compile-time settings (established with the "configure" script)
Version: freetds v1.3.13
freetds.conf directory: /opt/homebrew/etc
MS db-lib source compatibility: no
Sybase binary compatibility: yes
Thread safety: yes
iconv library: yes
TDS version: 7.3
iODBC: no
unixodbc: yes
SSPI "trusted" logins: no
Kerberos: yes
OpenSSL: yes
GnuTLS: no
MARS: yes
# Heroku:
$ heroku run bash -a <app>
Running bash on ⬢ <app>... up, run.4557 (Hobby)
~ $ tsql -C
Compile-time settings (established with the "configure" script)
Version: freetds v1.3.13
freetds.conf directory: /app/freetds/etc
MS db-lib source compatibility: no
Sybase binary compatibility: no
Thread safety: yes
iconv library: yes
TDS version: 7.3
iODBC: no
unixodbc: no
SSPI "trusted" logins: no
Kerberos: no
OpenSSL: yes
GnuTLS: no
MARS: yes
Any ideas would be greatly appreciated!
This was due to a TLS/openssl compatibility issue. Using gnutls fixes the issue for now.
Some other notes on the issue:
https://github.com/FreeTDS/freetds/issues/336
https://github.com/FreeTDS/freetds/issues/299
If you need to use freetds on heroku-22, see this pull request.
https://github.com/rails-sqlserver/heroku-buildpack-freetds/pull/20
Many thanks to #engineersmnky for some great questions that led to discovering this answer.
I am trying to install NVIDIA Driver for Titan Xp. I type the following for installation:
sudo apt-get install nvidia-418
The installation runs with no errors. However, after rebooting the driver is not loaded. Here is the error that nvidia-smi command gives:
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
Here is the complete installation log (in the terminal):
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
cuda-command-line-tools-10-1 cuda-command-line-tools-8-0 cuda-command-line-tools-9-0 cuda-command-line-tools-9-2 cuda-compiler-10-1 cuda-compiler-9-2
cuda-core-8-0 cuda-core-9-0 cuda-cublas-8-0 cuda-cublas-9-0 cuda-cublas-9-2 cuda-cublas-dev-8-0 cuda-cublas-dev-9-0 cuda-cublas-dev-9-2 cuda-cudart-10-1
cuda-cudart-8-0 cuda-cudart-9-0 cuda-cudart-9-2 cuda-cudart-dev-10-1 cuda-cudart-dev-8-0 cuda-cudart-dev-9-0 cuda-cudart-dev-9-2 cuda-cufft-10-1
cuda-cufft-8-0 cuda-cufft-9-0 cuda-cufft-9-2 cuda-cufft-dev-10-1 cuda-cufft-dev-8-0 cuda-cufft-dev-9-0 cuda-cufft-dev-9-2 cuda-cuobjdump-10-1
cuda-cuobjdump-9-2 cuda-cupti-10-1 cuda-cupti-9-2 cuda-curand-10-1 cuda-curand-8-0 cuda-curand-9-0 cuda-curand-9-2 cuda-curand-dev-10-1 cuda-curand-dev-8-0
cuda-curand-dev-9-0 cuda-curand-dev-9-2 cuda-cusolver-10-1 cuda-cusolver-8-0 cuda-cusolver-9-0 cuda-cusolver-9-2 cuda-cusolver-dev-10-1 cuda-cusolver-dev-8-0
cuda-cusolver-dev-9-0 cuda-cusolver-dev-9-2 cuda-cusparse-10-1 cuda-cusparse-8-0 cuda-cusparse-9-0 cuda-cusparse-9-2 cuda-cusparse-dev-10-1
cuda-cusparse-dev-8-0 cuda-cusparse-dev-9-0 cuda-cusparse-dev-9-2 cuda-documentation-10-1 cuda-documentation-8-0 cuda-documentation-9-0 cuda-documentation-9-2
cuda-driver-dev-10-1 cuda-driver-dev-8-0 cuda-driver-dev-9-0 cuda-driver-dev-9-2 cuda-gdb-10-1 cuda-gdb-9-2 cuda-gpu-library-advisor-10-1
cuda-gpu-library-advisor-9-2 cuda-libraries-10-1 cuda-libraries-9-0 cuda-libraries-9-2 cuda-libraries-dev-10-1 cuda-libraries-dev-9-0 cuda-libraries-dev-9-2
cuda-license-10-1 cuda-license-8-0 cuda-license-9-0 cuda-license-9-2 cuda-memcheck-10-1 cuda-memcheck-9-2 cuda-misc-headers-10-1 cuda-misc-headers-8-0
cuda-misc-headers-9-0 cuda-misc-headers-9-2 cuda-npp-10-1 cuda-npp-8-0 cuda-npp-9-0 cuda-npp-9-2 cuda-npp-dev-10-1 cuda-npp-dev-8-0 cuda-npp-dev-9-0
cuda-npp-dev-9-2 cuda-nsight-10-1 cuda-nsight-9-2 cuda-nsight-compute-10-1 cuda-nsight-systems-10-1 cuda-nvcc-10-1 cuda-nvcc-9-2 cuda-nvdisasm-10-1
cuda-nvdisasm-9-2 cuda-nvgraph-10-1 cuda-nvgraph-8-0 cuda-nvgraph-9-0 cuda-nvgraph-9-2 cuda-nvgraph-dev-10-1 cuda-nvgraph-dev-8-0 cuda-nvgraph-dev-9-0
cuda-nvgraph-dev-9-2 cuda-nvjpeg-10-1 cuda-nvjpeg-dev-10-1 cuda-nvml-dev-10-1 cuda-nvml-dev-8-0 cuda-nvml-dev-9-0 cuda-nvml-dev-9-2 cuda-nvprof-10-1
cuda-nvprof-9-2 cuda-nvprune-10-1 cuda-nvprune-9-2 cuda-nvrtc-10-1 cuda-nvrtc-8-0 cuda-nvrtc-9-0 cuda-nvrtc-9-2 cuda-nvrtc-dev-10-1 cuda-nvrtc-dev-8-0
cuda-nvrtc-dev-9-0 cuda-nvrtc-dev-9-2 cuda-nvtx-10-1 cuda-nvtx-9-2 cuda-nvvp-10-1 cuda-nvvp-9-2 cuda-samples-10-1 cuda-samples-8-0 cuda-samples-9-0
cuda-samples-9-2 cuda-sanitizer-api-10-1 cuda-toolkit-10-1 cuda-toolkit-9-0 cuda-toolkit-9-2 cuda-tools-10-1 cuda-tools-9-2 cuda-visual-tools-10-1
cuda-visual-tools-9-0 cuda-visual-tools-9-2 fonts-font-awesome fonts-lato fonts-mathjax freeglut3 freeglut3-dev ipython-notebook-common libcublas-dev
libcublas10 libcublas7.5 libcudart7.5 libcufft7.5 libcufftw7.5 libcurand7.5 libcurl4-openssl-dev libcusolver7.5 libcusparse7.5 libjs-highlight
libjs-highlight.js libjs-marked libjs-mathjax libjs-underscore libnppc7.5 libnppi7.5 libnpps7.5 libnvblas7.5 libnvrtc7.5 libnvtoolsext1 libnvvm3
libpython-all-dev libpython3-dev libpython3.5-dev libssl-doc libthrust-dev libvdpau-dev libvncserver1 libxmu-dev libxmu-headers libxt-dev
linux-headers-4.15.0-47 linux-headers-4.15.0-47-generic linux-headers-4.15.0-50 linux-headers-4.15.0-50-generic linux-headers-4.15.0-51
linux-headers-4.15.0-51-generic linux-headers-4.15.0-52 linux-headers-4.15.0-52-generic linux-image-4.15.0-47-generic linux-image-4.15.0-50-generic
linux-image-4.15.0-51-generic linux-image-4.15.0-52-generic linux-modules-4.15.0-47-generic linux-modules-4.15.0-50-generic linux-modules-4.15.0-51-generic
linux-modules-4.15.0-52-generic linux-modules-extra-4.15.0-47-generic linux-modules-extra-4.15.0-50-generic linux-modules-extra-4.15.0-51-generic
linux-modules-extra-4.15.0-52-generic nsight-compute-2019.4.0 nsight-systems-2019.3.7 python-all python-all-dev python-jinja2 python-markupsafe python-pymysql
python-wheel python3-wheel python3.5-dev ruby-did-you-mean ruby-minitest ruby-net-telnet ruby-power-assert ruby-test-unit x11vnc-data
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
libcuda1-418 nvidia-opencl-icd-418 nvidia-prime
The following packages will be REMOVED:
libcuda1-304 nvidia-304 nvidia-current nvidia-opencl-icd-304
The following NEW packages will be installed:
libcuda1-418 nvidia-418 nvidia-opencl-icd-418 nvidia-prime
0 upgraded, 4 newly installed, 4 to remove and 194 not upgraded.
Need to get 0 B/112 MB of archives.
After this operation, 314 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 940544 files and directories currently installed.)
Removing libcuda1-304 (304.137-0ubuntu0~gpu16.04.1) ...
Removing nvidia-current (304.137-0ubuntu0~gpu16.04.1) ...
Removing nvidia-304 (304.137-0ubuntu0~gpu16.04.1) ...
Removing all DKMS Modules
Done.
update-alternatives: using /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto mode
INFO:Disable nvidia-304
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
update-initramfs: deferring update (trigger activated)
Removing nvidia-opencl-icd-304 (304.137-0ubuntu0~gpu16.04.1) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for initramfs-tools (0.122ubuntu8.14) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-70-generic
Selecting previously unselected package nvidia-418.
(Reading database ... 940327 files and directories currently installed.)
Preparing to unpack .../nvidia-418_418.87.01-0ubuntu1_amd64.deb ...
Unpacking nvidia-418 (418.87.01-0ubuntu1) ...
Selecting previously unselected package libcuda1-418.
Preparing to unpack .../libcuda1-418_418.87.01-0ubuntu1_amd64.deb ...
Unpacking libcuda1-418 (418.87.01-0ubuntu1) ...
Selecting previously unselected package nvidia-opencl-icd-418.
Preparing to unpack .../nvidia-opencl-icd-418_418.87.01-0ubuntu1_amd64.deb ...
Unpacking nvidia-opencl-icd-418 (418.87.01-0ubuntu1) ...
Selecting previously unselected package nvidia-prime.
Preparing to unpack .../nvidia-prime_0.8.2_amd64.deb ...
Unpacking nvidia-prime (0.8.2) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Setting up nvidia-418 (418.87.01-0ubuntu1) ...
update-alternatives: using /usr/lib/nvidia-418/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto mode
update-alternatives: warning: skip creation of /usr/share/grub-gfxpayload-lists/blacklist/10_proprietary-graphics-drivers because associated file /usr/share/nvidia-418/nvidia-418.grub-gfxpayload (of link group x86_64-linux-gnu_gl_conf) doesn't exist
update-alternatives: using /usr/lib/nvidia-418/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf (x86_64-linux-gnu_egl_conf) in auto mode
update-alternatives: using /usr/lib/nvidia-418/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in auto mode
update-alternatives: using /usr/lib/nvidia-418/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf (i386-linux-gnu_egl_conf) in auto mode
update-alternatives: using /usr/share/nvidia-418/glamor.conf to provide /usr/share/X11/xorg.conf.d/glamoregl.conf (glamor_conf) in auto mode
update-initramfs: deferring update (trigger activated)
A modprobe blacklist file has been created at /etc/modprobe.d to prevent Nouveau from loading. This can be reverted by deleting /etc/modprobe.d/nvidia-graphics-drivers.conf.
A new initrd image has also been created. To revert, please replace /boot/initrd-4.15.0-70-generic with /boot/initrd-$(uname -r)-backup.
*****************************************************************************
*** Reboot your computer and verify that the NVIDIA graphics driver can ***
*** be loaded. ***
*****************************************************************************
INFO:Enable nvidia-418
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
Adding system user `nvidia-persistenced' (UID 121) ...
Adding new group `nvidia-persistenced' (GID 129) ...
Adding new user `nvidia-persistenced' (UID 121) with group `nvidia-persistenced' ...
Not creating home directory `/'.
Loading new nvidia-418-418.87.01 DKMS files...
First Installation: checking all kernels...
Building only for 4.15.0-70-generic
Building for architecture x86_64
Building initial module for 4.15.0-70-generic
Done.
nvidia_418:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.15.0-70-generic/updates/dkms/
nvidia_418_modeset.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.15.0-70-generic/updates/dkms/
nvidia_418_drm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.15.0-70-generic/updates/dkms/
nvidia_418_uvm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.15.0-70-generic/updates/dkms/
depmod.........
DKMS: install completed.
Setting up libcuda1-418 (418.87.01-0ubuntu1) ...
Setting up nvidia-opencl-icd-418 (418.87.01-0ubuntu1) ...
Setting up nvidia-prime (0.8.2) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for initramfs-tools (0.122ubuntu8.14) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-70-generic
Processing triggers for ureadahead (0.100.0-19) ...
I would really appreciate your help!
I am trying to create an EC2 using knife and knife-ec2 gem
command example :
knife ec2 server create --image ami-f7f03d80 -i --flavor t2.micro -x root -i /root/europe.pem —sud —groups chef-client -Z eu-west-1a -r “role[xmpp]”
Error output :
ERROR: Excon::Errors::SocketError: getaddrinfo: Name or service not known (SocketError)
knife.rb :
log_level :info
log_location STDOUT
node_name 'ec2-user'
client_key '/root/.chef/ec2-user.pem'
validation_client_name 'chef-validator'
validation_key '/etc/chef-server/chef-validator.pem'
chef_server_url 'https://ip-****.eu-west-1.compute.internal:443'
syntax_check_cache_path '/root/.chef/syntax_check_cache'
knife[:aws_access_key_id] = '*****'
knife[:aws_secret_access_key] = '*****'
knife[:region] = 'eu-west-1a'
--
gem list knife-ec2
*** LOCAL GEMS ***
knife-ec2 (0.8.0)
Can any one put me on the right direction, i a m suspecting an issue with the ruby gems.
PS :
for some reason knife ec2 flavor list works fine.
Thanks in advance.
regards,
Amine
>
SOLUTION :
fixed by : - reinstalling the ruby gems - reusing the patched version of ec2 create .rb
That error means it's not able to resolve the hostname I believe. I'd start there.
Can I skip the email confirmation step and enable the user ?
I followed by https://github.com/gitlabhq/gitlabhq/blob/6-4-stable/doc/install/installation.md
followed by each step.
But I can not get email confirmation so that no user can be confirmed.
Then I run the server by rails s -p 1987 -e production on the port 1987
The identical setting, I can receive email by my own rails app on other machines,
it's annoying me very much.
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically loaded 2.7.8
Checking Environment ...
Git configured for git user? ... yes
Checking Environment ... Finished
Checking GitLab Shell ...
GitLab Shell version >= 1.9.3 ? ... OK (1.9.3)
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
Satellites access is drwxr-x---? ... yes
update hook up-to-date? ... yes
update hooks in repos are links: ... can't check, you have no projects
Running /home/git/gitlab-shell/bin/check
Check GitLab API access: OK
Check directories and files:
/home/git/repositories: OK
/home/git/.ssh/authorized_keys: OK
Test redis-cli executable: redis-cli 2.2.12
Send ping to redis server: PONG
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
Database contains orphaned UsersGroups? ... no
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/local/bin/git"
Git version >= 1.7.10 ? ... yes (1.8.5)
Checking GitLab ... Finished
production.rb
config.action_mailer.delivery_method = :smtp
config.action_mailer.raise_delivery_errors = true
config.action_mailer.default :charset => "utf-8"
config.action_mailer.smtp_settings = {
:address => "74.125.129.109",
# :address => "smtp.gmail.com",
:port => 587,
:domain => "localhost",
:authentication => 'plain',
:user_name => XXX,
:password => XXX,
:enable_starttls_auto => true,
:openssl_verify_mode => 'none'
}
Don't know how to skip email confirmation and enable user, but with gitlab 6.7.5 these are my smtp settings (for icloud email server. Make sure you have logged in first into iCloud's web-email app, at least once):
file: /Users/git/gitlab/config/initializers/smtp_settings.rb
# To enable smtp email delivery for your GitLab instance do next:
# 1. Rename this file to smtp_settings.rb
# 2. Edit settings inside this file
# 3. Restart GitLab instance
#
if Rails.env.production?
Gitlab::Application.config.action_mailer.delivery_method = :smtp
ActionMailer::Base.smtp_settings = {
address: "smtp.mail.me.com",
port: 587,
user_name: "youraccount#icloud.com",
password: "yourpasswd",
domain: "me.com",
authentication: "plain",
enable_starttls_auto: true
}
end
Also remember to change the email_from attrbiute in your gitlab.yml file:
file: /Users/git/gitlab/config/gitlab.yml
## Email settings
# Email address used in the "From" field in mails sent by GitLab
email_from: youraccount#icloud.com
After changing the smtp file, restart the gitlab service.
Hope this helps.
Cheers,
I just installed Gitlab and I have an error during the gitlab-shell self check.
The command returns :
root#git:/home/git/gitlab# sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
Checking Environment ...
Git configured for git user? ... yes
Checking Environment ... Finished
Checking GitLab Shell ...
GitLab Shell version >= 1.9.3 ? ... OK (1.9.3)
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
Satellites access is drwxr-x---? ... yes
update hook up-to-date? ... yes
update hooks in repos are links: ...
Thibaud / thibaud-dauce ... repository is empty
Running /home/git/gitlab-shell/bin/check
Check GitLab API access: /usr/local/lib/ruby/2.0.0/net/http.rb:878:in `initialize': Connection timed out - connect(2) (Errno::ETIMEDOUT)
from /usr/local/lib/ruby/2.0.0/net/http.rb:878:in `open'
from /usr/local/lib/ruby/2.0.0/net/http.rb:878:in `block in connect'
from /usr/local/lib/ruby/2.0.0/timeout.rb:52:in `timeout'
from /usr/local/lib/ruby/2.0.0/net/http.rb:877:in `connect'
from /usr/local/lib/ruby/2.0.0/net/http.rb:862:in `do_start'
from /usr/local/lib/ruby/2.0.0/net/http.rb:851:in `start'
from /home/git/gitlab-shell/lib/gitlab_net.rb:76:in `get'
from /home/git/gitlab-shell/lib/gitlab_net.rb:43:in `check'
from /home/git/gitlab-shell/bin/check:11:in `<main>'
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 LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
Database contains orphaned UsersGroups? ... no
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: ...
Thibaud / thibaud-dauce ... yes
Projects have satellites? ...
Thibaud / thibaud-dauce ... can't create, repository is empty
Redis version >= 2.0.0? ... yes
Your git bin path is "/usr/bin/git"
Git version >= 1.7.10 ? ... yes (1.7.10)
Checking GitLab ... Finished
Of course, Gitlab is running :
root#git:/home/git/gitlab# service gitlab status
The GitLab Unicorn web server with pid 1543 is running.
The GitLab Sidekiq job dispatcher with pid 1736 is running.
GitLab and all its components are up and running.
And my config file :
root#git:/home/git/gitlab# sudo -u git -H cat /home/git/gitlab-shell/config.yml
# GitLab user. git by default
user: git
# Url to gitlab instance. Used for api calls. Should end with a slash.
gitlab_url: "http://git.thibaud-dauce.fr/"
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"
# Redis settings used for pushing commit notices to gitlab
redis:
bin: /usr/bin/redis-cli
host: 89.234.146.59
port: 6379
# socket: /tmp/redis.socket # Only define this if you want to use sockets
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
I already try to replace in Redis conf host: 127.0.0.1 to host: 89.234.146.59
I also try to add 89.234.146.59 git.thibaud-dauce.fr in /etc/hosts
I have a server running Debian 7 32bits with a container LXC for Gitlab, Ruby is version 2.0.0. I have the same error when I try to push a repo (but I can create one online with the web app)
Do you have any idea ? I really look everywhere and found no solution...