These are chat archives for opf/openproject
vuser@openproject:/opt/openproject-ce$ sudo openproject-ce run bundle install You are trying to install in deployment mode after changing your Gemfile. Run `bundle install` elsewhere and add the updated Gemfile.lock to version control. If this is a development machine, remove the Gemfile freeze by running `bundle install --no-deployment`. You have added to the Gemfile: * newrelic_rpm
openproject-ce runto run
railsor whatever you can think of.
no-deploymentflag but you will have to install git first. After that you have to do a
service openproject-ce restartto apply the changes. This is always necessary even if you just change the settings. But you already know that, right?
Your bundle is complete! Gems in the groups development and test were not installed. Use `bundle show [gemname]` to see where a bundled gem is installed.
Installing newrelic_rpm 18.104.22.1689
new relic.ymlfile. This file has to be placed into your
Vladimir K wants you to check out an error collected by New Relic. Error raised by Api::V2::PlanningElementsController#create: ActiveRecord::StatementInvalid: Mysql2::Error: Deadlock found when trying to get lock; try restarting transaction: UPDATE `work_packages` SET root_id = 23864, `lft` = 1, `rgt` = 2 WHERE (id = 23864) URL: /api/v2/projects/4/planning_elements.json Time: 12:28 pm To see the error, click this link: https://rpm.newrelic.com/accounts/1072740/applications/8225066/traced_errors/7d8144-fe9c6d45-4b13-11e5-b82f-f8bc12425d4c
activerecord. Nor CPU nor disk IO was maxed during the tests
16% /opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/activerecord-3.2.22/lib/active_record/persistence.rb.update_attributes :215
UPDATEcalls, whether it should be just
UPDATE `work_packages` SET root_id = 23864, `lft` = 1, `rgt` = 2 WHERE (id = 23864)
rgtlook like attributes of a nested set...)
If you encounter them more than once (which appears to be the case): yes...
Still I can't see how the workload of adding work packages can create those deadlocks. Please also report relevant changes to your setup in the ticket (e.g. are you using TokuDB or still vanilla InnoDB?)