Bitnami GitLab 5.2.0: gitlab_sidekiq does not work and cannot be started

Question

We are using Bitnami GitLab 5.2.0 .
We stumbled upon the fact that we cannot go into a new repository, for example

git@192.168.133.10 :sandbox/testgit2.git ,

but we can work with the old ones. More thorough research has shown that gitlab_sidekiq is not working.

/opt/bitnami/ctlscript.sh restart gitlab_sidekiq

gitlab_sidekiq could not be started

Where to look? Should I update first?

UPDATE: Bitnami GitLab 5.2 server is broken: it is not possible to move the code to new repositories. (Although the old vaults are not affected)

 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 WITH ANSWERS:

I use a virtual machine in VirtualBox on my PC (in 1 command as a pilot moving the virtual machine to some kind of VM host) Yes, I changed gitlab.yml

/opt/bitnami/apps/gitlab/htdocs/log/sidekiq.log has these lines in repetition, so they should give a hint (as if something was wrong while reading some file)

 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 , but here I see 1.9.1. Could this be a problem?

Answer 1

This is strange. What do you use, installer, virtual machine or cloud? If the sidekiq server is not running, it is possible that the repository was not created properly. Could you check if there is an error in the sidekiq log file?

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

Have you changed any configuration file for GitLab?

Edition:

The problem seems to be the wrong configuration in gitlab.yml. It is also important for white spaces. Could you check your change in this file?

/opt/bitnami/ruby/lib/ruby/1.9.1/psych.rb:203:in `parse ':(): a found character that cannot run any token when scanning the next token in row 73, column 1 (Psych :: SyntaxError)

GitLab CI ships the latest stable version of Ruby 1.9.3. The folder name uses 1.9.1 to support the backguard. Why is my gem "INSTALLATION DIRECTORY:" ... 1.9.1 when "VERSION RUBY": is 1.9.3

Please write the gitlab.yml file if you did not find the exact error.

Answer 2

In my case, I had a <tab> in my yml file.

This is a rather strange mistake though!