ruby-on-rails - Bitnami GitLab 5.2.0 : gitlab_sidekiq not running and could not be started

Question

我们正在使用 Bitnami GitLab 5.2.0 .
我们偶然发现我们无法推送到新的存储库中，比如
git@192.168.133.10:sandbox/testgit2.git ,

但我们可以和旧的一起工作。更仔细的调查显示 gitlab_sidekiq 没有运行。
/opt/bitnami/ctlscript.sh restart gitlab_sidekiq
gitlab_sidekiq 无法启动

去哪里看？我应该update第一的？

更新:Bitnami GitLab 5.2 服务器出现故障:无法将代码推送到新的存储库中。
(虽然旧的存储库不受影响)

TestProject4>git remote add origin git
@192.168.133.10:sandbox/testproject4.git

TestProject4>git push -u origin master

fatal: '/opt/bitnami/apps/gitlab/repositories/sandbox/testproject4.git' does not  appear to be a git repository
fatal: The remote end hung up unexpectedly

更新答案:

我在我的 PC 上的 VirtualBox 中使用虚拟机(在 1 个团队中作为试点将 VM 移动到某个 VM 主机)
是的，我修改了 gitlab.yml

/opt/bitnami/apps/gitlab/htdocs/log/sidekiq.log 有这行重复，所以他们应该提供线索(读取某些文件时看起来有些错误)

DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released. (called from <top (required)> at /opt/bitnami/apps/gitlab/htdocs/config/environment.rb:5)
/opt/bitnami/ruby/lib/ruby/1.9.1/psych.rb:203:in `parse': (<unknown>): found character that cannot start any token while scanning for the next token at line 73 column 1 (Psych::SyntaxError)
    from /opt/bitnami/ruby/lib/ruby/1.9.1/psych.rb:203:in `parse_stream'
    from /opt/bitnami/ruby/lib/ruby/1.9.1/psych.rb:151:in `parse'
    from /opt/bitnami/ruby/lib/ruby/1.9.1/psych.rb:127:in `load'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/settingslogic-2.0.8/lib/settingslogic.rb:113:in `initialize'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/settingslogic-2.0.8/lib/settingslogic.rb:71:in `new'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/settingslogic-2.0.8/lib/settingslogic.rb:71:in `instance'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/settingslogic-2.0.8/lib/settingslogic.rb:48:in `[]'
    from /opt/bitnami/apps/gitlab/htdocs/config/initializers/1_settings.rb:38:in `<top (required)>'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/activesupport-3.2.13/lib/active_support/dependencies.rb:245:in `load'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/activesupport-3.2.13/lib/active_support/dependencies.rb:245:in `block in load'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/activesupport-3.2.13/lib/active_support/dependencies.rb:236:in `load_dependency'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/activesupport-3.2.13/lib/active_support/dependencies.rb:245:in `load'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/railties-3.2.13/lib/rails/engine.rb:588:in `block (2 levels) in <class:Engine>'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/railties-3.2.13/lib/rails/engine.rb:587:in `each'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/railties-3.2.13/lib/rails/engine.rb:587:in `block in <class:Engine>'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/railties-3.2.13/lib/rails/initializable.rb:30:in `instance_exec'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/railties-3.2.13/lib/rails/initializable.rb:30:in `run'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/railties-3.2.13/lib/rails/initializable.rb:55:in `block in run_initializers'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/railties-3.2.13/lib/rails/initializable.rb:54:in `each'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/railties-3.2.13/lib/rails/initializable.rb:54:in `run_initializers'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/railties-3.2.13/lib/rails/application.rb:136:in `initialize!'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/railties-3.2.13/lib/rails/railtie/configurable.rb:30:in `method_missing'
    from /opt/bitnami/apps/gitlab/htdocs/config/environment.rb:5:in `<top (required)>'
    from /opt/bitnami/ruby/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:55:in `require'
    from /opt/bitnami/ruby/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:55:in `require'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/sidekiq-2.8.0/lib/sidekiq/cli.rb:199:in `boot_system'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/sidekiq-2.8.0/lib/sidekiq/cli.rb:47:in `parse'
    from /opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/sidekiq-2.8.0/bin/sidekiq:7:in `<top (required)>'
    from /opt/bitnami/ruby/bin/sidekiq:23:in `load'
    from /opt/bitnami/ruby/bin/sidekiq:23:in `<main>'

GitLab says it requires ruby 1.9.3 ，但在这里我看到 1.9.1。那会是问题吗？

Answer 1

它很奇怪。你用的是什么，安装程序、虚拟机还是云镜像？如果 sidekiq 服务器未运行，则可能未正确创建存储库。你能检查一下sidekiq日志文件中是否有任何错误吗？

/opt/bitnami/apps/gitlab/htdocs/logs/sidekiq.log

您是否修改了 GitLab 的任何配置文件？

编辑:

问题似乎是 gitlab.yml 中的错误配置。空白也很重要。你能检查你在那个文件中的变化吗？

/opt/bitnami/ruby/lib/ruby/1.9.1/psych.rb:203:in `parse': (): 在第 73 行第 1 列扫描下一个标记时发现无法启动任何标记的字符(心理: :语法错误)

GitLab CI 发布了 Ruby 1.9.3 最新的稳定版本。文件夹名称使用 1.9.1 以实现 backguard 兼容性 Why is my gem "INSTALLATION DIRECTORY:" ...1.9.1 when the "RUBY VERSION:" is 1.9.3

如果您没有找到确切的错误，请发布 gitlab.yml 文件。