Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • 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
    • Professional 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?
      Create a new account

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
  • Roadmap
  • Work packages
  • Calendars
  • Team planners
  • Boards
  • Forums
  • Wiki
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showDeveloper
        • Hierarchy leafAccessibility Checklist
        • Hierarchy leafCode Review Guidelines
        • Expanded. Click to collapseCollapsed. Click to showContribution
          • Hierarchy leafGit Workflow
          • Hierarchy leafTranslations
        • Expanded. Click to collapseCollapsed. Click to showDeveloping Plugins
          • Hierarchy leafDeveloping an OmniAuth Authentication Plugin
        • Hierarchy leafRelease Process
        • Hierarchy leafReport a bug
        • Hierarchy leafSecurity
        • Hierarchy leafSetting up an OpenLDAP server for testing
        • Hierarchy leafTheme Features
      • Hierarchy leafDownload
      • Expanded. Click to collapseCollapsed. Click to showFeature tour
        • Hierarchy leafRelease Notes OpenProject 30
        • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 30 - Overview
          • Hierarchy leafGlossary
          • Hierarchy leafRelease Notes - Accessibility
          • Hierarchy leafRelease Notes - Accessibility changes
          • Hierarchy leafRelease Notes - Add work package queries as menu items to sidebar
          • Hierarchy leafRelease Notes - Copy projects based on Templates
          • Hierarchy leafRelease Notes - Design changes
          • Hierarchy leafRelease Notes - Fixed Bugs
          • Hierarchy leafRelease Notes - Keyboard Shortcuts
          • Hierarchy leafRelease Notes - Project settings
          • Hierarchy leafRelease Notes - Ruby&Rails Update
          • Hierarchy leafRelease Notes - Security
          • Hierarchy leafRelease Notes - Timelines
          • Hierarchy leafRelease Notes - Work packages
      • Hierarchy leafHowto create animated gifs
      • Hierarchy leafMigration Squashing
      • Hierarchy leafMod security
      • Hierarchy leafNew work package page
      • Hierarchy leafOP3 to OP4 Debian upgrade
      • Hierarchy leafOP4 Ubuntu1404 Stable with MySQL in production
      • Hierarchy leafOpenProject 40 Development Setup
      • Expanded. Click to collapseCollapsed. Click to showOpenProject Foundation
        • Hierarchy leafBoards
        • Hierarchy leafMembers
        • Hierarchy leafOPF-Meetings
        • Hierarchy leafStatutes
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes
        • Hierarchy leafOpenProject released on Bitnami
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 40 - Overview
        • Hierarchy leafRelease Notes OpenProject 40 - Accessibility improvements
        • Hierarchy leafRelease Notes OpenProject 40 - Column header functions in work package table
        • Hierarchy leafRelease Notes OpenProject 40 - Improved Design
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated query title on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated toolbar on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - OmniAuth integration for OpenProject
        • Hierarchy leafRelease Notes OpenProject 40 - Work package details pane
      • Expanded. Click to collapseCollapsed. Click to showSecurity and privacy
        • Hierarchy leafFAQ
      • Expanded. Click to collapseCollapsed. Click to showSupport
        • Expanded. Click to collapseCollapsed. Click to showDownload and Installation
          • Hierarchy leafInstallation MacOS
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 3 0
            • Hierarchy leafDebian Stable with MySQL in production
            • Hierarchy leafInstallation Ubuntu
            • Hierarchy leafInstallation Windows
            • Hierarchy leafInstallation on Centos 65 x64 with Apache and PostgreSQL 93
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 40
            • Hierarchy leafOP4 Debian Stable with MySQL in production
          • Expanded. Click to collapseCollapsed. Click to showMigration paths
            • Hierarchy leafFrom Chilliproject to OpenProject
            • Hierarchy leafMigration 15 to 30
            • Hierarchy leafMigration 24 to 30
            • Hierarchy leafMigration Redmine 2x › OpenProject 30
            • Hierarchy leafOpenProject 3 Migration
          • Hierarchy leafOpenProject 40
        • Expanded. Click to collapseCollapsed. Click to showNews
          • Hierarchy leafNew OpenProject Translations Plugin
          • Hierarchy leafNew Plugin on OpenProjectorg Local Avatars
          • Hierarchy leafNew design for OpenProject
          • Hierarchy leafNews Accessibility workshop for OpenProject
          • Hierarchy leafNews Glossary for OpenProject
          • Hierarchy leafNews Heartbleed fixed
          • Hierarchy leafNews Icon Fonts
          • Hierarchy leafNews OpenProject 30 Release
          • Hierarchy leafNews Release GitHub Integration Plugin
          • Hierarchy leafNews Success Story Deutsche Telekom
          • Hierarchy leafNews Timelines
          • Hierarchy leafOpenProject 3013 released
          • Hierarchy leafOpenProject 3017 released
          • Hierarchy leafOpenProject 40 released
          • Hierarchy leafOpenProject 40 will be coming soon
          • Hierarchy leafOpenProject 405 released
          • Hierarchy leafOpenProject and pkgrio
          • Hierarchy leafOpenProject news moved to a new blog
          • Hierarchy leafOpenProjectBitnami
          • Hierarchy leafPackager version with plugins released ("Community edition")
          • Hierarchy leafRegistration OpenProject-Foundation
          • Hierarchy leafRelease OpenProject AuthPlugins
          • Hierarchy leafUpdates on OpenProject
          • Hierarchy leafWe need your feedback for the the new fullscreen view for work packages
        • Hierarchy leafOpenProject Plug-Ins
      • Expanded. Click to collapseCollapsed. Click to showWiki
        • Hierarchy leaf2nd Level Support
You are here:
  • Forums
  • General discussion

Content

[solved]After update to OP 4 I cannot display uploaded png

Added by Bernd Müller over 7 years ago

Hi!

I cannot not display any images after updating OP to the latest version.

Maybe this log gives someone an idea what is going wrong. Any help is appreciated.

Cheers

ActionController::RoutingError (No route matches [GET] "/install1.PNG"):
  actionpack (3.2.21) lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'
  actionpack (3.2.21) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call'
  railties (3.2.21) lib/rails/rack/logger.rb:32:in `call_app'
  railties (3.2.21) lib/rails/rack/logger.rb:16:in `block in call'
  activesupport (3.2.21) lib/active_support/tagged_logging.rb:22:in `tagged'
  railties (3.2.21) lib/rails/rack/logger.rb:16:in `call'
  request_store (1.1.0) lib/request_store/middleware.rb:8:in `call'
  actionpack (3.2.21) lib/action_dispatch/middleware/request_id.rb:22:in `call'
  rack (1.4.5) lib/rack/methodoverride.rb:21:in `call'
  rack (1.4.5) lib/rack/runtime.rb:17:in `call'
  activesupport (3.2.21) lib/active_support/cache/strategy/local_cache.rb:72:in `call'
  rack (1.4.5) lib/rack/lock.rb:15:in `call'
  rack-cache (1.2) lib/rack/cache/context.rb:136:in `forward'
  rack-cache (1.2) lib/rack/cache/context.rb:245:in `fetch'
  rack-cache (1.2) lib/rack/cache/context.rb:185:in `lookup'
  rack-cache (1.2) lib/rack/cache/context.rb:66:in `call!'
  rack-cache (1.2) lib/rack/cache/context.rb:51:in `call'
  airbrake (4.1.0) lib/airbrake/user_informer.rb:16:in `_call'
  airbrake (4.1.0) lib/airbrake/user_informer.rb:12:in `call'
  railties (3.2.21) lib/rails/engine.rb:484:in `call'
  railties (3.2.21) lib/rails/application.rb:231:in `call'
  railties (3.2.21) lib/rails/railtie/configurable.rb:30:in `method_missing'

Processing by WorkPackagesController#preview as */*
  Parameters: {"..I delete this here.."}
  Rendered common/preview.html.erb (24.4ms)
Completed 500 Internal Server Error in 173.9ms

Replies (20)

RE: After update to OP 4 I cannot display uploaded png - Added by Bernd Müller over 7 years ago

I guess that somehow the way that attachments get handled, seems to be changed.
I found the the folder “files” in it I got all the files I have uploaded previously, now it seems like all new uploaded files go to /files/attachement/file/. This is a new structure. But still the folder is accessible ->as OP was able to upload the files that I cannot display.

Any suggestion would be appreciated.

RE: RE: After update to OP 4 I cannot display uploaded png - Added by Bernd Müller over 7 years ago

Oh…it is even worse than I thought. No image is displayed at all, meaning if I open old WPs the pages will always get this 500 error.
->This is really annoying!

RE: After update to OP 4 I cannot display uploaded png - Added by Karsten Gallinowski over 7 years ago

Hi Bernd,

as far as I can tell you missed the execution of migrations, right? If so please run the migrations and everything should be fine. If you do not know how to do that please let me know how you installed your openproject.

Cheers,
Karsten

RE: After update to OP 4 I cannot display uploaded png - Added by Bernd Müller over 7 years ago

Hi!

Thanks for the feedback, this is really appreciated!
Well…ehmm…
you missed the execution of migrations, right?
Could be. Honestly I got no clue. I have manually installed OP on a debian system, is that the info you need to know?

Cheerio!

RE: After update to OP 4 I cannot display uploaded png - Added by Karsten Gallinowski over 7 years ago

Ok, that is the info I need. So you can try to cd into the root of your openproject installation. Please try to run the following command.

RAILS_ENV=production bundle exec rake db:migrate --trace

Cheers,
Karsten

RE: After update to OP 4 I cannot display uploaded png - Added by Bernd Müller over 7 years ago

Hmm…I entered the command, but I still have the same error.

RE: After update to OP 4 I cannot display uploaded png - Added by Karsten Gallinowski over 7 years ago

What about the output of the command. Does it say something about migrations? Did it change something?

RE: After update to OP 4 I cannot display uploaded png - Added by Bernd Müller over 7 years ago

Maybe this gives you a hint:

openproject@moserver:~/openproject$ RAILS_ENV=production bundle exec rake db:migrate --trace
require 'rails/all'... 1.320s
Bundler.require... 4.860s
** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
Application.initialize!... [deprecated] I18n.enforce_available_locales will default to true in the future. If you really want to skip validation of your locale you can set I18n.enforce_available_locales = false to avoid this message.
4.720s
** Invoke db:load_config (first_time)
** Execute db:load_config
** Execute db:migrate
==  AddSessionsTable: migrating ===============================================
-- create_table(:sessions)
rake aborted!
StandardError: An error has occurred, all later migrations canceled:

Mysql2::Error: Table 'sessions' already exists: CREATE TABLE `sessions` (`id` int(11) DEFAULT NULL auto_increment PRIMARY KEY, `session_id` varchar(255) NOT NULL, `data` text, `created_at` datetime NOT NULL, `updated_at` datetime NOT NULL) ENGINE=InnoDB/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:245:in `query'

RE: After update to OP 4 I cannot display uploaded png - Added by Karsten Gallinowski over 7 years ago

Ok that explains a lot. First of all I do not know why your migration ends up with an error but I can see where. The important migration for your particular problem is executed after the AddSessionsTable migration.

As you can see in the error log:

StandardError: An error has occurred, all later migrations canceled:

The migration important for you gets not executed. So now we know what is causing the problem. Now we have to find out why. Can you please paste more log info of the actual error, please?

Cheers,
Karsten

RE: After update to OP 4 I cannot display uploaded png - Added by Karsten Gallinowski over 7 years ago

Ok I missed the last line about the session table already existing. Let us do something fancy here and try to fix this by doing the following:

please open a mysql connection to your mysql database end execute the following statement:

INSERT INTO schema_migrations VALUES('20140429152018')

After that please run the migrations again.

Cheers,
Karsten

RE: After update to OP 4 I cannot display uploaded png - Added by Bernd Müller over 7 years ago

Hej!

I did as you told me , now it get this, after having inserted the sql command:

openproject@moserver:~/openproject$ RAILS_ENV=production bundle exec rake db:migrate --trace
require 'rails/all'... 1.320s
Bundler.require... 4.770s
** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
Application.initialize!... [deprecated] I18n.enforce_available_locales will default to true in the future. If you really want to skip validation of your locale you can set I18n.enforce_available_locales = false to avoid this message.
4.610s
** Invoke db:load_config (first_time)
** Execute db:load_config
** Execute db:migrate
==  ResetContentTypes: migrating ==============================================
rake aborted!
StandardError: An error has occurred, all later migrations canceled:

undefined method `to_file' for nil:NilClass/home/openproject/openproject/app/uploaders/file_uploader.rb:35:in `local_file'
/home/openproject/openproject/app/models/attachment.rb:138:in `diskfile'
/home/openproject/openproject/db/migrate/20140430125956_reset_content_types.rb:32:in `block in up'
/home/openproject/openproject/db/migrate/20140430125956_reset_content_types.rb:31:in `each'
/home/openproject/openproject/db/migrate/20140430125956_reset_content_types.rb:31:in `up'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:410:in `block (2 levels) in migrate'
/home/openproject/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/benchmark.rb:279:in `measure'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:410:in `block in migrate'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/connection_adapters/abstract/connection_pool.rb:129:in `with_connection'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:389:in `migrate'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:528:in `migrate'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:720:in `block (2 levels) in migrate'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:777:in `call'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:777:in `ddl_transaction'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:719:in `block in migrate'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:700:in `each'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:700:in `migrate'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:570:in `up'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:551:in `migrate'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/railties/databases.rake:193:in `block (2 levels) in <top (required)>'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/task.rb:240:in `call'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/task.rb:240:in `block in execute'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/task.rb:235:in `each'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/task.rb:235:in `execute'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/task.rb:179:in `block in invoke_with_call_chain'
/home/openproject/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/monitor.rb:211:in `mon_synchronize'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/task.rb:172:in `invoke_with_call_chain'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/task.rb:165:in `invoke'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:150:in `invoke_task'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:106:in `block (2 levels) in top_level'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:106:in `each'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:106:in `block in top_level'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:115:in `run_with_threads'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:100:in `top_level'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:78:in `block in run'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:176:in `standard_exception_handling'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:75:in `run'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/bin/rake:33:in `<top (required)>'
/home/openproject/.rvm/gems/ruby-2.1.5/bin/rake:23:in `load'
/home/openproject/.rvm/gems/ruby-2.1.5/bin/rake:23:in `<main>'
/home/openproject/.rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:15:in `eval'
/home/openproject/.rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:15:in `<main>'
NoMethodError: undefined method `to_file' for nil:NilClass
/home/openproject/openproject/app/uploaders/file_uploader.rb:35:in `local_file'
/home/openproject/openproject/app/models/attachment.rb:138:in `diskfile'
/home/openproject/openproject/db/migrate/20140430125956_reset_content_types.rb:32:in `block in up'
/home/openproject/openproject/db/migrate/20140430125956_reset_content_types.rb:31:in `each'
/home/openproject/openproject/db/migrate/20140430125956_reset_content_types.rb:31:in `up'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:410:in `block (2 levels) in migrate'
/home/openproject/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/benchmark.rb:279:in `measure'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:410:in `block in migrate'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/connection_adapters/abstract/connection_pool.rb:129:in `with_connection'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:389:in `migrate'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:528:in `migrate'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:720:in `block (2 levels) in migrate'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:777:in `call'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:777:in `ddl_transaction'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:719:in `block in migrate'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:700:in `each'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:700:in `migrate'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:570:in `up'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/migration.rb:551:in `migrate'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/activerecord-3.2.21/lib/active_record/railties/databases.rake:193:in `block (2 levels) in <top (required)>'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/task.rb:240:in `call'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/task.rb:240:in `block in execute'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/task.rb:235:in `each'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/task.rb:235:in `execute'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/task.rb:179:in `block in invoke_with_call_chain'
/home/openproject/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/monitor.rb:211:in `mon_synchronize'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/task.rb:172:in `invoke_with_call_chain'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/task.rb:165:in `invoke'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:150:in `invoke_task'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:106:in `block (2 levels) in top_level'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:106:in `each'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:106:in `block in top_level'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:115:in `run_with_threads'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:100:in `top_level'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:78:in `block in run'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:176:in `standard_exception_handling'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/lib/rake/application.rb:75:in `run'
/home/openproject/.rvm/gems/ruby-2.1.5/gems/rake-10.4.2/bin/rake:33:in `<top (required)>'
/home/openproject/.rvm/gems/ruby-2.1.5/bin/rake:23:in `load'
/home/openproject/.rvm/gems/ruby-2.1.5/bin/rake:23:in `<main>'
/home/openproject/.rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:15:in `eval'
/home/openproject/.rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:15:in `<main>'
Tasks: TOP => db:migrate

RE: After update to OP 4 I cannot display uploaded png - Added by Karsten Gallinowski over 7 years ago

Ok something is really odd with your installation. Unfortunately the migration failing is the next in line so we haven’t accomplish that much. Your data seem to be broken so we have to fix this somehow.

There are some things we can try. We could skip this migration too which might be a bad idea. Or we are lucky and by skipping it we get what we want. I suggest not to skip the migration. So we have to figure out which attachment is producing the error.

See the code for more information.

To move on with this I have to asked how experienced are you in regard to programming ruby? Can you debug this by your own when I point you in the correct direction or do you need additional help?

Cheers,
Karsten

RE: After update to OP 4 I cannot display uploaded png - Added by Karsten Gallinowski over 7 years ago

A general advice: Please backup the data of your database now before we move on. So we are able to roll back all our changes. Better safe than sorry ;-)

Karsten

RE: After update to OP 4 I cannot display uploaded png - Added by Bernd Müller over 7 years ago

Hi!

Thanks for your support!

Hmm my Ruby skills? They are pretty much as good as my islandic skills, meaning: 0 ;-) I can only try to understand what I see, when I see a log in “Ruby”.
But: Wouldn´t it be better to skip this zombie installation, delete it and use the packaged version of OP instead? And then reimport the settings and db?

What do you think?

Bernd

RE: After update to OP 4 I cannot display uploaded png - Added by Karsten Gallinowski over 7 years ago

Hi,

yeah that is in general a good idea but your data is broken and will also produce problems with the packager installation. So you should somehow fix this issue. If you did a backup already we could try to skip the last migration error.

What do you think?

To skip the migration you can do the following:

Insert this in the db INSERT INTO schema_migrations VALUES('20140430125956') and do the migration again.

What do you think?

Regards,
Karsten

RE: After update to OP 4 I cannot display uploaded png - Added by Bernd Müller over 7 years ago

Oh…so this is not related to the openproject program itself, but the data is corrupt…oh…. :-(

Anyways, as I am brave and courageous I entered the commands “und siehe” I can see the old images again that are in the wiki and older WP. Great!

But it seems like all new WP do not accept to display images I still got this error 500. Still the folder/file was created and i can see the file…strange?!

RE: After update to OP 4 I cannot display uploaded png - Added by Karsten Gallinowski over 7 years ago

Ok that is strange. Can you provide some log information on that. Without that I will not be able to help.

RE: After update to OP 4 I cannot display uploaded png - Added by Bernd Müller over 7 years ago

Hi!

Did you have a chance to take a look at the logs. Are they useful?

Cheers!

RE: After update to OP 4 I cannot display uploaded png - Added by Karsten Gallinowski over 7 years ago

Hi,

yes I looked at it but could not find any useful information. The problem is the log is too long and there are a lot of error messages not related to our problem. Could you please just send me the log with the error in it. For example you could stop the server, clean the log and do whatever is necessary to produce the error and stop the server again.

After that the log will be small and will only include our error.

What do you think?

Cheers,
Karsten

RE: After update to OP 4 I cannot display uploaded png - Added by Bernd Müller over 7 years ago

Hi!

Yes of course you are, I didn´t think of reducing the logs, sorry that was stupid.

Anyway: When I create a new WP the upload/display of attachment seems to work perfectly now.

Thank you very much, I would have never ever found out what the problem could have been.

Best regards!

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