Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums

Content

You are here:
  1. Messages
Support Installation & Updates
  1. OpenProject
  2. Forums
  3. Support Installation & Updates
  4. Cannot upgrade from OpenProject 7.0.2 to 7.1.0

Cannot upgrade from OpenProject 7.0.2 to 7.1.0

Added by Thomas Roder over 7 years ago

OpenProject 7.0.2 is running well on my Ubuntu Server 16:04.
I want to upgrade to the newest Version using sudo apt-get install --only-upgrade openproject, but I get this error:

Reading package lists... Done
(…)
Unpacking openproject (7.1.0-1499089014.b01cc3e.xenial) over (7.0.2-1497278524.7de7cda.xenial) ...
dpkg: error processing archive /var/cache/apt/archives/openproject_7.1.0-1499089014.b01cc3e.xenial_amd64.deb (--unpack):
@ unable to create ‘/opt/openproject/vendor/bundle/ruby/2.4.0/gems/newrelic_rpm-4.1.0.333/test/new_relic/agent/utilization_data_test.rb.dpkg-new’ (while processing ‘./opt/openproject/vendor/bundle/ruby/2.4.0/gems/newrelic_rpm-4.1.0.333/test/new_relic/agent/utilization_data_test.rb’): No space left on device@
(…)

The error implies that I don’t have enough space left, but that hardly makes sense. According to df, I have

  • 1.1G free in /opt/
  • 4.5G free in /
  • 3.4G free in /home

The full output of both commands can be found here: [[https://pastebin.com/i3jGaumk]]

Is this an OpenProject problem?


Replies (4)

RE: Cannot upgrade from OpenProject 7.0.2 to 7.1.0 - Added by Oliver Günther over 7 years ago

Hi Thomas,

the packaged installation bundle contains a full ruby and node environment. The latter, with its huge number of small dependencies is often a problem with your free inodes. Even though 1GB should be enough space to upgrade OpenProject, you may be running out of inodes.

Can you post the output of df -i ?

I’m still looking into alternatives to shipping with the entire node environment, but since we have to preprocess our assets when a user decides to install openproject in a subdirectory (due to the required URL rewriting of the assets), we currently depend on it.

Best,
Oliver

RE: Cannot upgrade from OpenProject 7.0.2 to 7.1.0 - Added by Thomas Roder over 7 years ago

Thanks for the quick reply.

Here’s the output of df -i: [[https://pastebin.com/6zzCVkkD]]

RE: Cannot upgrade from OpenProject 7.0.2 to 7.1.0 - Added by Oliver Günther over 7 years ago

Weird, that doesn’t look too bad. I still believe that the node_modules are causing this. You are able to safely delete /opt/openproject/frontend/node_modules and retry the installation. The package should extract the remainder now.

If your installation is running for some time, its also possible that older ruby versions are still installed in /opt/openproject/vendor/ruby-2.2.5/ or /opt/openproject/vendor/ruby-2.1.X/ , which you could also try to remove prior to installing the package.

RE: Cannot upgrade from OpenProject 7.0.2 to 7.1.0 - Added by Thomas Roder over 7 years ago

removing /opt/openproject/frontend/node_modules did the trick, thank you!

  • (1 - 4/4)
Loading...