Content
Error after migrating to 10.1
Added by Kelsen Cristiano over 5 years ago
Ubuntu 14.04
Postgresql 11
I followed https://www.openproject.org/operations/migration-guides/migrating-packaged-openproject-database-postgresql/
and all went well untill openproject reconfigure
step.
Launching installer for openproject...
Selected addons: legacy-installer postgres apache2 repositories smtp memcached openproject
[legacy-installer] ./bin/configure
[postgres] ./bin/configure
Installation is already using MySQL, skipping postgres addon.
DONE
[apache2] ./bin/configure
DONE
[repositories] ./bin/configure
No server installed. Skipping.
DONE
[smtp] ./bin/configure
DONE
[memcached] ./bin/configure
DONE
[openproject] ./bin/configure
DONE
[legacy-installer] ./bin/preinstall
[postgres] ./bin/preinstall
INFO: autoinstall=skip. Skipping to next step.
[apache2] ./bin/preinstall
[repositories] ./bin/preinstall
[smtp] ./bin/preinstall
[memcached] ./bin/preinstall
No memcached server to install. Skipping.
[openproject] ./bin/preinstall
[legacy-installer] ./bin/postinstall
[postgres] ./bin/postinstall
[apache2] ./bin/postinstall
[repositories] ./bin/postinstall
[smtp] ./bin/postinstall
[memcached] ./bin/postinstall
[openproject] ./bin/postinstall
rake aborted!
Psych::SyntaxError: (<unknown>): did not find expected whitespace or line break while scanning a tag at line 38 column 18
/opt/openproject/lib/open_project/configuration.rb:420:in `load_config_from_file'
/opt/openproject/lib/open_project/configuration.rb:176:in `load'
/opt/openproject/lib/open_project/configuration.rb:245:in `[]'
/opt/openproject/config/application.rb:199:in `<class:Application>'
/opt/openproject/config/application.rb:100:in `<module:OpenProject>'
/opt/openproject/config/application.rb:99:in `<top (required)>'
/opt/openproject/Rakefile:33:in `require'
/opt/openproject/Rakefile:33:in `<top (required)>'
/opt/openproject/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/exe/rake:27:in `<top (required)>'
/opt/openproject/vendor/bundle/ruby/2.6.0/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:74:in `load'
/opt/openproject/vendor/bundle/ruby/2.6.0/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:74:in `kernel_load'
/opt/openproject/vendor/bundle/ruby/2.6.0/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:28:in `run'
/opt/openproject/vendor/bundle/ruby/2.6.0/gems/bundler-2.0.2/lib/bundler/cli.rb:465:in `exec'
/opt/openproject/vendor/bundle/ruby/2.6.0/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/opt/openproject/vendor/bundle/ruby/2.6.0/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/opt/openproject/vendor/bundle/ruby/2.6.0/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
/opt/openproject/vendor/bundle/ruby/2.6.0/gems/bundler-2.0.2/lib/bundler/cli.rb:27:in `dispatch'
/opt/openproject/vendor/bundle/ruby/2.6.0/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
/opt/openproject/vendor/bundle/ruby/2.6.0/gems/bundler-2.0.2/lib/bundler/cli.rb:18:in `start'
/opt/openproject/vendor/bundle/ruby/2.6.0/gems/bundler-2.0.2/exe/bundle:30:in `block in <top (required)>'
/opt/openproject/vendor/bundle/ruby/2.6.0/gems/bundler-2.0.2/lib/bundler/friendly_errors.rb:124:in `with_friendly_errors'
/opt/openproject/vendor/bundle/ruby/2.6.0/gems/bundler-2.0.2/exe/bundle:22:in `<top (required)>'
/opt/openproject/bin/bundle:3:in `load'
/opt/openproject/bin/bundle:3:in `<main>'
(See full trace by running task with --trace)
Replies (3)
You seem to have an invalid YAML entry in your
/opt/openproject/config/configuration.yml
Could you check its line 38 ?
Best,
Oliver
Line 38 reads:
smtp_password: <%= ENV['SMTP_PASSWORD'] %>
From what I can tell
openproject reconfigure
couldn't handle special characters like "!" and "#".I had to type a random password and configure through admin painel.
Hi Kelsen,
thanks for getting back. This is indeed a bug in the escaping of the configuration parsing. I couldn't reproduce the error for now, but can confirm that the value is not correctly escaped (and thus may lead to invalid paswords being used).
I created bug #31583 to track this.
Best,
Oliver