Content
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)
I have the same problem, after upgrade from 4.2.8 to 5.0.6.
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
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.