Should I upgrade to gitlabshell 2.2.0 (http://doc.gitlab.com/ce/install/installation.html) ? If so, it would be great to do include it bin/upgrade.rb
2014-11-27 11:00 GMT+01:00 Henri Gomez <henri.go...@gmail.com>: > gitlab-shell.log reports : > > E, [2014-11-27T10:57:19.199679 #2918] ERROR -- : API call <GET > http://swf-gitlab-preprod.mycorp.com//api/v3/internal/discover?key_id=3> > failed: 401 => <{"message":"401 Unauthorized"}>. > > ssh key is discovered but discover API call fail, with 401. > Should gitlab-shell be authenticated ? > > > 2014-11-27 10:33 GMT+01:00 Henri Gomez <henri.go...@gmail.com>: >> Problem strike back when upgrading from 7.4.3 to 7.5.1 >> >> git clone g...@swf-gitlab-preprod.mycorp.com:hgomez/ecd-catalog.git >> Cloning into 'ecd-catalog'... >> >> Access denied. >> fatal: Could not read from remote repository. >> >> Please make sure you have the correct access rights >> and the repository exists. >> [10:30] henri@envy-rico:Bureau $ >> >> Tested ssh access : >> >> ssh g...@swf-gitlab-preprod.mycorp.com >> PTY allocation request failed on channel 0 >> Welcome to GitLab, Anonymous! >> Connection to swf-gitlab-mycorp.com closed. >> >> ssh public keys not found anymore ? >> >> -- >> >> GitLab 7.5.1 >> GitLab Shell 2.0.1 >> GitLab API v3 >> Ruby 2.0.0p247 >> Rails 4.1.1 >> >> 2014-11-03 15:16 GMT+01:00 Henri Gomez <henri.go...@gmail.com>: >>> Fixed by reverting to 2.0.1 >>> >>> >>> 2014-11-03 14:54 GMT+01:00 Henri Gomez <henri.go...@gmail.com>: >>>> /find/fix/ >>>> >>>> 2014-11-03 14:53 GMT+01:00 Henri Gomez <henri.go...@gmail.com>: >>>>> ok >>>>> >>>>> How could I find it ? >>>>> >>>>> sudo -u git -H git checkout v`cat /home/git/gitlab/1.7.9 ??? >>>>> >>>>> 2014-11-03 0:05 GMT+01:00 Sytse Sijbrandij <sy...@gitlab.com>: >>>>>> Hi Henry, >>>>>> >>>>>> You probably upgraded GitLab Shell to a too recent version. This was >>>>>> due to a problem in the patch upgrade guide, fixed in >>>>>> https://gitlab.com/gitlab-org/gitlab-ce/commit/1d0f638248edc12c1e36f3276e895eee31584601 >>>>>> >>>>>> Best regards, >>>>>> Sytse Sijbrandij >>>>>> CEO GitLab B.V. >>>>>> >>>>>> >>>>>> On Fri, Oct 31, 2014 at 2:48 AM, Henri Gomez <henri.go...@gmail.com> >>>>>> wrote: >>>>>>> Hi all >>>>>>> >>>>>>> I updated to 7.4.2 and later 7.4.3 and I cannot clone from SSH anymore. >>>>>>> >>>>>>> Only http access is working now. >>>>>>> >>>>>>> GitLab7.4.3 >>>>>>> >>>>>>> GitLab Shell1.9.7 >>>>>>> >>>>>>> GitLab APIv3 >>>>>>> >>>>>>> Ruby2.0.0p247 >>>>>>> >>>>>>> Rails4.1.1 >>>>>>> >>>>>>> I notice many errors in sidekick.log : >>>>>>> >>>>>>> 2014-10-31T09:45:01Z 22436 TID-93a0s INFO: Booting Sidekiq 2.17.0 with >>>>>>> redis options {:url=>"redis://localhost:6379", >>>>>>> :namespace=>"resque:gitlab"} >>>>>>> 2014-10-31T09:45:01Z 22436 TID-93a0s INFO: Running in ruby 2.0.0p247 >>>>>>> (2013-06-27) [x86_64-linux] >>>>>>> 2014-10-31T09:45:01Z 22436 TID-93a0s INFO: See LICENSE and the >>>>>>> LGPL-3.0 for licensing details. >>>>>>> >>>>>>> 2014-10-31T09:46:53Z 22436 TID-rghc8 >>>>>>> Sidekiq::Extensions::DelayedMailer JID-bcbac3b34ee35f4fc9147b72 INFO: >>>>>>> start >>>>>>> 2014-10-31T09:46:53Z 22436 TID-rghc8 >>>>>>> Sidekiq::Extensions::DelayedMailer JID-bcbac3b34ee35f4fc9147b72 INFO: >>>>>>> arguments: ["---\n- !ruby/class 'Notify'\n- :new_ssh_key_email\n- - >>>>>>> 3\n"] >>>>>>> 2014-10-31T09:46:58Z 22436 TID-rghc8 >>>>>>> Sidekiq::Extensions::DelayedMailer JID-bcbac3b34ee35f4fc9147b72 INFO: >>>>>>> fail: 5.526 sec >>>>>>> 2014-10-31T09:46:58Z 22436 TID-rghc8 WARN: {"retry"=>true, >>>>>>> "queue"=>"default", "class"=>"Sidekiq::Extensions::DelayedMailer", >>>>>>> "args"=>["---\n- !ruby/class 'Notify'\n- :new_ssh_key_email\n- - >>>>>>> 3\n"], "jid"=>"bcbac3b34ee35f4fc9147b72", >>>>>>> "enqueued_at"=>1414747992.212935, "error_message"=>"end of file >>>>>>> reached", "error_class"=>"EOFError", "failed_at"=>"2014-10-31 09:33:34 >>>>>>> UTC", "retry_count"=>5, "retried_at"=>2014-10-31 09:46:58 UTC} >>>>>>> 2014-10-31T09:46:58Z 22436 TID-rghc8 WARN: end of file reached >>>>>>> 2014-10-31T09:46:58Z 22436 TID-rghc8 WARN: >>>>>>> /usr/lib64/ruby/2.0.0/net/protocol.rb:153:in `read_nonblock' >>>>>>> /usr/lib64/ruby/2.0.0/net/protocol.rb:153:in `rbuf_fill' >>>>>>> /usr/lib64/ruby/2.0.0/net/protocol.rb:134:in `readuntil' >>>>>>> /usr/lib64/ruby/2.0.0/net/protocol.rb:144:in `readline' >>>>>>> /usr/lib64/ruby/2.0.0/net/smtp.rb:931:in `recv_response' >>>>>>> /usr/lib64/ruby/2.0.0/net/smtp.rb:917:in `block in getok' >>>>>>> /usr/lib64/ruby/2.0.0/net/smtp.rb:941:in `critical' >>>>>>> /usr/lib64/ruby/2.0.0/net/smtp.rb:915:in `getok' >>>>>>> /usr/lib64/ruby/2.0.0/net/smtp.rb:909:in `quit' >>>>>>> /usr/lib64/ruby/2.0.0/net/smtp.rb:615:in `do_finish' >>>>>>> /usr/lib64/ruby/2.0.0/net/smtp.rb:522:in `ensure in start' >>>>>>> /usr/lib64/ruby/2.0.0/net/smtp.rb:522:in `start' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/mail-2.5.4/lib/mail/network/delivery_methods/smtp.rb:112:in >>>>>>> `deliver!' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/mail-2.5.4/lib/mail/message.rb:2129:in >>>>>>> `do_delivery' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/mail-2.5.4/lib/mail/message.rb:232:in >>>>>>> `block in deliver' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.1.1/lib/action_mailer/base.rb:527:in >>>>>>> `block in deliver_mail' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/notifications.rb:159:in >>>>>>> `block in instrument' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/notifications/instrumenter.rb:20:in >>>>>>> `instrument' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/notifications.rb:159:in >>>>>>> `instrument' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.1.1/lib/action_mailer/base.rb:525:in >>>>>>> `deliver_mail' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/mail-2.5.4/lib/mail/message.rb:232:in >>>>>>> `deliver' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/extensions/action_mailer.rb:20:in >>>>>>> `perform' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/processor.rb:49:in >>>>>>> `block (3 levels) in process' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/middleware/chain.rb:122:in >>>>>>> `call' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/middleware/chain.rb:122:in >>>>>>> `block in invoke' >>>>>>> /var/lib/mycorp/gitlab/gitlab/lib/gitlab/sidekiq_middleware/arguments_logger.rb:6:in >>>>>>> `call' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/middleware/chain.rb:124:in >>>>>>> `block in invoke' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/middleware/server/active_record.rb:6:in >>>>>>> `call' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/middleware/chain.rb:124:in >>>>>>> `block in invoke' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/middleware/server/retry_jobs.rb:62:in >>>>>>> `call' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/middleware/chain.rb:124:in >>>>>>> `block in invoke' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/middleware/server/logging.rb:11:in >>>>>>> `block in call' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/logging.rb:22:in >>>>>>> `with_context' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/middleware/server/logging.rb:7:in >>>>>>> `call' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/middleware/chain.rb:124:in >>>>>>> `block in invoke' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/middleware/chain.rb:127:in >>>>>>> `call' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/middleware/chain.rb:127:in >>>>>>> `invoke' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/processor.rb:48:in >>>>>>> `block (2 levels) in process' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/processor.rb:105:in >>>>>>> `stats' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/processor.rb:47:in >>>>>>> `block in process' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/processor.rb:86:in >>>>>>> `do_defer' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/sidekiq-2.17.0/lib/sidekiq/processor.rb:37:in >>>>>>> `process' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/celluloid-0.15.2/lib/celluloid/calls.rb:25:in >>>>>>> `public_send' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/celluloid-0.15.2/lib/celluloid/calls.rb:25:in >>>>>>> `dispatch' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/celluloid-0.15.2/lib/celluloid/calls.rb:122:in >>>>>>> `dispatch' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/celluloid-0.15.2/lib/celluloid/actor.rb:322:in >>>>>>> `block in handle_message' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/celluloid-0.15.2/lib/celluloid/actor.rb:416:in >>>>>>> `block in task' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/celluloid-0.15.2/lib/celluloid/tasks.rb:55:in >>>>>>> `block in initialize' >>>>>>> /var/lib/mycorp/gitlab/gitlab/vendor/bundle/ruby/2.0.0/gems/celluloid-0.15.2/lib/celluloid/tasks/task_fiber.rb:13:in >>>>>>> `block in create' >>>>>>> >>>>>>> Is it related ? >>>>>>> >>>>>>> ssh access seems to works : >>>>>>> >>>>>>> ssh g...@swf-gitlab-preprod.lab.ancy.mycorp.int >>>>>>> PTY allocation request failed on channel 0 >>>>>>> Welcome to GitLab, Gomez Henri! >>>>>>> Connection to swf-gitlab-preprod.lab.ancy.mycorp.int closed. >>>>>>> >>>>>>> Any idea what could be wrong ? >>>>>>> >>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "GitLab" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>>>> an email to gitlabhq+unsubscr...@googlegroups.com. >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/gitlabhq/CALyUpY2DJ-6vBUkrrJWKazKV8%3D0hvFQSJZtY67DzgogFwuUE1g%40mail.gmail.com. >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "GitLab" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>>> an email to gitlabhq+unsubscr...@googlegroups.com. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/gitlabhq/CAJTzhG8JLEVjEc9fEhoPENFpq6BTMn_k_Kn_7iTrAsrWPvZhyg%40mail.gmail.com. >>>>>> For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/CALyUpY1hAmY8S3E7dcgVJpO7y-KRoW_%3DWO1L8w%2B7yc_fOcMHaQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
