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
    • Upgrade to Enterprise edition
    • 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

Support Installation & Updates
  1. OpenProject
  2. Forums
  3. Support Installation & Updates
  4. Internal Error nach Update von 4.0.8 (Community Edition) auf 5.0.5

Internal Error nach Update von 4.0.8 (Community Edition) auf 5.0.5

Added by Ronald Mitterer over 9 years ago

Nach einem Update von 4.0.8 (Community Editon) auf 5.0.5 bekomme ich beim Aufruf von /admin folgende Fehlermeldung:

Internal error

An error occurred on the page you were trying to access.
If you continue to experience problems please contact your OpenProject administrator for assistance.

If you are the OpenProject administrator, check your log files for details about the error.

Im LogFile finde ich folgenden MySQL Fehler:

@
E, [2015-12-05T19:26:51.258154 #10903] ERROR — : Mysql2::Error: Unknown column ‘repos.required_storage_bytes’ in ‘field list’: SELECT SUM (required_disk_space) FROM (SELECT projects.*, wiki.filesize AS wiki_required_space, wp.filesize AS work_package_required_space, repos.required_storage_bytes AS repositories_required_space, (COALESCE (wiki.filesize, 0) +
COALESCE (wp.filesize, 0) +
COALESCE (repos.required_storage_bytes, 0)) AS required_disk_space FROM projects projects LEFT JOIN ( SELECT wiki.project_id, SUM (wiki_attached.filesize) AS filesize
FROM wikis wiki
LEFT JOIN wiki_pages pages
ON pages.wiki_id = wiki.id
LEFT JOIN attachments wiki_attached
ON (wiki_attached.container_id = pages.id AND wiki_attached.container_type = ‘WikiPage’)
GROUP BY wiki.project_id
) wiki ON projects.id = wiki.project_id LEFT JOIN ( SELECT wp.project_id, SUM (wp_attached.filesize) AS filesize
FROM work_packages wp
LEFT JOIN attachments wp_attached
ON (wp_attached.container_id = wp.id AND wp_attached.container_type = ‘WorkPackage’)
GROUP BY wp.project_id
) wp ON projects.id = wp.project_id LEFT JOIN repositories repos ON repos.project_id = projects.id) sub
@

Ich gehe mal stark davon aus, dass das Update von 4.0.8 auf 5.0.5 Probleme in der Datenbank verursacht hat. Gibt es vielleicht eine möglichkeit die Datenbank nachträglich 5.0.5 “tauglich” zu machen??

Danke


Replies (3)

RE: Internal Error nach Update von 4.0.8 (Community Edition) auf 5.0.5 - Added by René Juan Rico Mendoza over 9 years ago

I have the same problem, after upgrade from 4.2.8 to 5.0.6.

RE: Internal Error nach Update von 4.0.8 (Community Edition) auf 5.0.5 - Added by Oliver Günther over 9 years ago

Hi guys,

judging by the output, it looks like the database migration wasn’t successful in the upgrade process.

You can ensure that all migrations are being run by executing:

(Manual installation in OpenProject application root)
RAILS_ENV=production ./bin/rake db:migrate

(Packaged installation)
openproject run bundle exec rake db:migrate

If that does not solve the error, please give me some more details on your installation, i.e., previous installed version (Core, Community Edition) and installation type (Packaged, Bitnami, Manual)?

Best,
Oliver

RE: Internal Error nach Update von 4.0.8 (Community Edition) auf 5.0.5 - Added by René Juan Rico Mendoza over 9 years ago

You are right, the problem was in the repository table.
In my case there was three columns missing, after adding this 3 columns I could fix the problem.

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