Common Redmine Installation & Update troubles

During application update an error message containing "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ..." appears in the log.

Cause
It means your database is outdated and it can't work with the request our application sends to it. It just doesn't understand it.

Solution
You need to update your database.

How to update the database?
Detailed description in the Knowledge base.

You have installed or updated Easy Redmine under user with insufficient permissions, not following our strong recommendation in the instructions (at least once in the past).

1. Correct permissions by commands chgrp and chown according to server settings (eg. chgrp -R www-data public_html)
2. Run installation again bundle exec rake easyproject:install RAILS_ENV=production which will clear cache (if you run it by root, it will not be succesful)
3. Restart server

If you are using virtual machine provided by Easy Software, run under user easy:

sudo chown -R easy /home/easy/current
(in older machines - sudo chown -R easy /srv/easyredmine/public_html)

sudo chgrp -R easy /home/easy/current
(in older machines - sudo chgrp -R easy /srv/easyredmine/public_html)

cd /home/easy/current
(in older machines - cd /srv/easyredmine/public_html)

bundle exec rake easyproject:install RAILS_ENV=production

sudo service unicorn restart

Remember to set the permissions for all necessary folders.

Here are some hints what you can do if you run into 500 error.

• run Easy server requirements check and try to repair failed validations
• back-up your database
• download the latest package from the Client Zone
• make sure that webserver has Full access public, files, log, tmp folders
• run bundle install --without development test
• run bundle exec rake easyproject:install RAILS_ENV=production
• restart application server
• delete any 3rd parties' Redmine plugins (also from database)
• write us on support@easyredmine.com and attach log/production.log

There are many possible causes of this error. Here are a few tips:

• browser cache problem - try deleting cache from the browser
• dns problem
• server setting problem

First check your connection and network (verify that server is reachable by using a ping command or traceroute command). Firewall server side.

If all above seems fine, try to get some information from nginx error.logs. Check nginx error.log at the server side - /var/log/nginx/error.log

Double check that your nginx configuration matches the standard. Standard nginx configuration can be found here:
https://www.redmine.org/projects/redmine/wiki/HowTo_configure_Nginx_to_run_Redmine

Example of an nginx configuration (as is used by Easy Software). It's quite similar to official one only few variables are optimized:

user www-data;
worker_processes  8;

worker_rlimit_nofile 60000;

error_log  /var/log/nginx/error.log;
pid        /var/run/nginx.pid;

events {
    worker_connections  10240;
    # multi_accept on;
}

http {
    ssl_protocols  TLSv1 TLSv1.1 TLSv1.2;  # dont use SSLv3 ref: POODLE
    include       /etc/nginx/mime.types;
                default_type  application/octet-stream;
                server_names_hash_bucket_size 2048;

    access_log  /var/log/nginx/access.log;

    sendfile        on;
    #tcp_nopush     on;

    #keepalive_timeout  0;
    keepalive_timeout  65;
    tcp_nodelay        on;

    send_timeout 1800;
    client_body_timeout  1800;
    client_header_timeout 1800;
    proxy_read_timeout 1800;
    client_max_body_size 220m;
    fastcgi_buffer_size 64K;
    fastcgi_buffers 128 16k;
    proxy_max_temp_file_size 0;
    types_hash_max_size 4096;
    types_hash_bucket_size 128;

    proxy_busy_buffers_size   256k;
    proxy_buffers 8 256k;
    proxy_buffer_size 256k;

    gzip  on;
    gzip_disable "MSIE [1-6]\.(?!.*SV1)";

    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;
    include /etc/nginx/sites-auto/*;
}

Other possible causes of 502 error include...

Unicorn is not running at all, due to

• Insufficient permissions
• Wrong version of passenger
• Wrong Ruby version
• Missing gems
• Broken filesystem

To find out the exact problem, you need to check error logs in unicorn or apache + application log from Easy Redmine (log/production.log)

Timeout

If low timeout is configured, this error will appear on:

• large exports
• overload of server
• rake tasks run from the GUI

Limit of MySQL connections

Make sure you have a sufficient number of connections allowed to MySQL. It depends on the number of users, but you should have at least a 100 allowed.

This error occurs from version 2018 1.2 (platform 04.00 and higher)

Error during upgrade installation containg some of the following.

[!] There was an error parsing `Gemfile`:

[!] There was an error parsing `Gemfile`: cannot load such file --

#  plugin 'rys-bundler', github: 'easysoftware/rys-bundler', branch: 'master'
 >  Plugin.hook('rys-gemfile', self)

Bundler cannot continue.

It is caused by outdated version of redmine installer.

Solution:

Before installing the upgrade

$ gem install redmine-installer

This problems occurs when you use a suffix on your Easy Redmine URL, for example: https://company.com/easyredmine/

In this case, you need to make sure that you have the variable RAILS_RELATIVE_URL_ROOT configured to your correct suffix /easyredmine

Bitnami:

1. Create an additional configuration file config/additional_environment.rb
2. config.action_controller.relative_url_root = "/easyredmine"
3. then precompile assets (rake easyproject:install RAILS_ENV=production) and restart the server

Make sure wkhtmltopdf is installed and running ( wkhtmltopdf needs X server or other emulation)
Test it using: "wkhtmltopdf google.com google.pdf"

Add to your proxy configuration:

proxy_set_header X-Forwarded-Proto https

When you are updating Easy Redmine on Windows platform and hit on error message ExecJs ::RuntimeError

All you have to do is install NODEJS on your system for the proper update.

If the installation fails, run manually:

$ bundle update
$ rake db:migrate
$ rake redmine:plugins:migrate

Make sure your webserver supports actual size of URL address

Make sure you are NOT using Webrick webserver!

• make sure you have the latest version of the webserver and Ruby
• reconfigure the slow filter queries in order to show less fields
• reset you CRON not to launch so often
• refer to this case study - Rails speed up without touching Ruby code
• check your configuration - https://www.easyredmine.com/resources/installation/1885-recommended-optimal-configuration-of-easy-redmine-server

Copy files folder from your old Redmine.

Make sure your webserver has Full access public, files, log, tmp folders

New commits into your repository are not reflected in Easy Redmine unless they are fetched by the application. You need to set webhooks on your repository client (github, gitlab, TortoiseSVN,...) with information about your Easy Redmine instance.

1. Go to administration >> settings >> repositories
2. Enable WS for repository management
3. Generate an API key
   
4. Save
5. Go to your repository client
6. Add a webhook
   Let's say your site is easyredmine.company.com
   For git - https://easyredmine.company.com/sys/git_fetcher
   or https://easyredmine.company.com/sys/git_fetcher?key=[API key]
    - depending on client setting, it can require a single URL or the key into a different field
   For SVN - https://easyredmine.company.com/sys/fetch_changesets
   or https://easyredmine.company.com/sys/fetch_changesets?key=[API key]

From point 5, it is all up to the repository client and not related to Easy Redmine settings. It is something you must verify after clean installation or upgrade from Redmine.

When configuring the domain of your Easy Redmine, make sure to use at least first level domain, for example http://myeasyredmine.com instead of just http://myeasyredmine . Some browsers may have problem with reaching it.

Go to Administration >> Settings >> Email notifications
and verify that the FROM address is correct.

It should be the same (or at least from the same SMTP server) as in configuration file. Otherwise some email services (gmail, yahoo, etc.) may reject notifications.

Check your configuration according to this article in Knowledge base.

To verify that the configuration is correct, try to check if can connect to the mail server from your Easy Redmine server using telnet.

telnet your.domain.here port_number_here (For example: telnet gmail.com 465)

It will show you if you really can connect to your mailserver or there is a problem in your mailserver configuration.

When you try to fo a PDF export which results in an error (or acts as if nothing happens). The production log would list error similar to
Errno::EPIPE (Broken pipe) or wkhtmltopdf: cannot connect to X server

Caused by issues with exporting component wkhtmltopdf

Here are the proposed solutions.

Headless server

Get needed version of wkhtmltopdf from http://wkhtmltopdf.org/downloads.html

Example (you have to work with details of your own environment):

1. sudo apt-get install xvfb xauth
2. wget https://bitbucket.org/wkhtmltopdf/wkhtmltopdf/downloads/wkhtmltox-0.13.0-alpha-7b36694_linux-jessie-amd64.deb
3. sudo dpkg -i wkhtmltox-0.13.0-alpha-7b36694_linux-jessie-amd64.deb
4. sudo apt-get -f install
5. sudo mv /usr/local/bin/wkhtmltopdf /usr/local/bin/xwkhtmltopdf
6. echo 'exec xvfb-run -a -s "-screen 0 640x480x16" xwkhtmltopdf "$@"' | sudo tee /usr/local/bin/wkhtmltopdf >/dev/null
7. sudo chmod a+x /usr/local/bin/wkhtmltopdf

Non-headless server only

1. You need to have wkhtmltopdf installed on your server in PATH
   (apt-get install wkhtmltox, yum install wkhtmltox)
   It must be installed in bundler, otherwise it may not work after updating Easy Redmine
2. Make sure that program works correctly (run from the console for example wkhtmltopdf https://easyredmine.com homepage.pdf)
3. re-run rake easyproject:install RAILS_ENV=production
4. restart server