Content
Package Installation/configuration fails in Ubuntu 14
Added by Mito Tranin over 9 years ago
I’m trying to install into a brand new Ubuntu Server 14 (trusty) server. The only thing installed on this server is the LAMP stack from installation, and OpenProject.
The installation itself via the package was successful, but when trying to configure the installation, I keep running into the following error:
[memcached] ./bin/postinstall [openproject] ./bin/postinstall rake aborted! Psych::SyntaxError: (<unknown>): control characters are not allowed at line 1 column 1 /opt/openproject/lib/open_project/configuration.rb:224:in `load_config_from_file' /opt/openproject/lib/open_project/configuration.rb:98:in `load' /opt/openproject/lib/open_project/configuration.rb:171:in `[]' /opt/openproject/config/application.rb:155:in `<class:Application>' /opt/openproject/config/application.rb:72:in `<module:OpenProject>' /opt/openproject/config/application.rb:71:in `<top (required)>' /opt/openproject/Rakefile:33:in `require' /opt/openproject/Rakefile:33:in `<top (required)>' (See full trace by running task with --trace) rootopenproject:~#
@
I have been looking everywhere for a solution, but I can’t seem to find one? Things seem to point to a corrupted .bashrc file, but I can’t find any corruption or bad syntax in my root/.bashrc file?
Any help would be appreciated,
Thanks!
Replies (2)
Hi Mito,
thanks for your report.
The YAML parser is unable to parse the configuration file at
/opt/openproject/config/configuration.yml. I could not reproduce it on a fresh 14.04 VM.Could you attach that configuration, leaving out any sensible information?
Best,
Oliver
At first glance, nothing seems to be odd to me…. but it does reference a lot of variables… and I noticed that it referenced the email variables! I had originally set the email options to use SMTP, and thus provided the necessary information for it to send via that, one of which was the account password, which included special characters. Due to the error, I had attempted to remove that possibility by telling it to skip email configuration. Since I kept receiving that error, I assumed that wasn’t the case, though continued to skip the configuration.
When you mentioned that you did not run into the error, I was confused, and thought through myself what of the other variables that it was using in that file would have a special character in the variable… and I couldn’t come up with any? So I tried to configure using sendmail instead of skipping the mail config… and now it worked! The configuration script just completed successfully!
Thank you again for your help in pointing me to which file to look at! I’m not sure if it was something in my email configuration, or if it was something in the smtp portion of the script, or what… but the issue persisted when skipped, but it worked using sendmail.
Thanks again for your help!
Mito