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

1

我们正在使用Bitnami GitLab 5.2.0。
我们偶然发现，我们不能推到新的仓库，像Bitnami GitLab 5.2.0：gitlab_sidekiq未运行且无法启动

[email protected]: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

的答案UPDATE：

我使用虚拟机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。这可能是问题吗？

来源

2013-07-17 Paul Verest

+0

嗨保罗，你最终发现了问题？ – Beltran

+0

gitlab。yml应该是原因，因为它是我在最近几周改变的唯一文件（试图使LDAP工作）。我看不出有什么问题http://stackoverflow.com/questions/17825404/how-to-check-yml-grammar-is-correct-gitlab-yml，现在我找不到GitLab有什么问题了检查安装是否正常。（我跑了一次，但它给了我唯一的错误） –

2

这很奇怪。你在使用什么，安装程序，虚拟机或云图像？如果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（Psych :: SyntaxError）

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文件。

来源

2013-07-19 09:11:38 Beltran

0

在我的情况下，我在我的yml文件中有<tab>。

虽然这是很奇怪的错误！

来源

2015-12-06 04:15:37 slashmili

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

回答

相关问题