Bitnami GitLab 5.2.0: gitlab_sidekiq未运行且无法启动

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无法启动

去哪找？我应该先更新吗？

更新: 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中的虚拟机(在一个团队中作为飞行员将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说它需要红宝石1.9.3，但这里我看到了1.9.1。这会有问题吗？

Answer 1

这很奇怪。您在使用什么，安装程序，虚拟机还是云映像？如果sidekiq服务器没有运行，则可能没有正确创建存储库。您能检查一下侧方日志文件中是否有错误吗？

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

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

编辑：

这个问题在gitlab.yml中似乎是一个错误的配置。这也是很重要的空白。你能在那份文件里查一下你的零钱吗？

/opt/bitnami/ruby/lib/ruby/1.9.1/psych.rb:203:in“解析”：()：在第73列第1行扫描下一个令牌时无法启动任何令牌的发现字符(精神病学：：SyntaxError)

GitLab CI发布了Ruby1.9.3最新的稳定版本。文件夹名使用1.9.1作为后防兼容性为什么我的gem“安装目录：”...1.9.1时"RUBY：“是1.9.3

如果没有找到确切的错误，请张贴gitlab.yml文件。

Answer 2

在我的例子中，我的yml文件中有<tab>。

这是相当奇怪的错误，尽管！