Hi @wolf,
Thanks for the info. I checked our OpenProject asset and I think I have discovered what's happening. I tried to manually run the db:seed
command to populate the database with the sample data, and it fails with the next error message
bundle exec rake db:seed
[DEPRECATED] Bundler.environment has been removed in favor of Bundler.load (called at /opt/bitnami/apps/openproject/htdocs/lib/open_project/plugins/acts_as_op_engine.rb:178)
*** Seeding for locale: 'en'
*** Seeding basic data for standard edition
↳ BuiltinRolesSeeder
↳ RoleSeeder
↳ ActivitySeeder
↳ ColorSeeder
↳ ColorSchemeSeeder
↳ WorkflowSeeder
↳ Types
↳ Statuses
↳ PrioritySeeder
↳ SettingSeeder
Loading discovered seeders:
↳ SettingSeeder
↳ EnumerationsSeeder
*** Seeding admin user
*** No need to seed an admin as there already is one.
*** Seeding demo data
↳ GroupSeeder
↳ Creating groups
↳ AttributeHelpTextSeeder
↳ Creating attribute help texts
↳ GlobalQuerySeeder
↳ Creating global queries
↳ ProjectSeeder
↳ Creating demo-project project...
-Creating/Resetting project
-Setting project status.
-Setting members.
-Creating news.
-Assigning types.
-Creating categories
-Creating versions.
-Creating queries.
-WikiSeeder
↳ Creating wikis...
-CustomFieldSeeder
↳ Creating custom fields...
-WorkPackageSeeder
↳ Creating work_packages.rake aborted!
SocketError: getaddrinfo: Name or service not known
/opt/bitnami/apps/openproject/htdocs/vendor/bundle/ruby/2.6.0/gems/mail-2.7.1/lib/mail/network/delivery_methods/smtp.rb:109:in `start_smtp_session'
/opt/bitnami/apps/openproject/htdocs/vendor/bundle/ruby/2.6.0/gems/mail-2.7.1/lib/mail/network/delivery_methods/smtp.rb:100:in `deliver!'
/opt/bitnami/apps/openproject/htdocs/vendor/bundle/ruby/2.6.0/gems/mail-2.7.1/lib/mail/message.rb:2159:in `do_delivery'
/opt/bitnami/apps/openproject/htdocs/vendor/bundle/ruby/2.6.0/gems/mail-2.7.1/lib/mail/message.rb:260:in `block in deliver'
/opt/bitnami/apps/openproject/htdocs/vendor/bundle/ruby/2.6.0/gems/actionmailer-6.0.1/lib/action_mailer/base.rb:589:in `block in deliver_mail'
/opt/bitnami/apps/openproject/htdocs/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.1/lib/active_support/notifications.rb:180:in `block in instrument'
/opt/bitnami/apps/openproject/htdocs/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.1/lib/active_support/notifications/instrumenter.rb:24:in `instrument'
/opt/bitnami/apps/openproject/htdocs/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.1/lib/active_support/notifications.rb:180:in `instrument'
/opt/bitnami/apps/openproject/htdocs/vendor/bundle/ruby/2.6.0/gems/actionmailer-6.0.1/lib/action_mailer/base.rb:587:in `deliver_mail'
/opt/bitnami/apps/openproject/htdocs/vendor/bundle/ruby/2.6.0/gems/mail-2.7.1/lib/mail/message.rb:260:in `deliver'
/opt/bitnami/apps/openproject/htdocs/vendor/bundle/ruby/2.6.0/gems/actionmailer-6.0.1/lib/action_mailer/message_delivery.rb:114:in `block in deliver_now'
As you can see, it tries to do something related to SMTP and it fails because SMTP isn't configured by default. If you configure it in the admin panel with valid credentials and then you run the rake db:seed
command again, it will work fine. You only need to run the command below before configuring SMTP. There are some missing permissions we will fix on our side in a future release.
sudo chmod 664 /opt/bitnami/apps/openproject/htdocs/config/configuration.yml
I also recommend you to run the rake assets:precompile
task after the db:seed
success just in case. Apart from that, note you will need to restart Apache after running the rake command for changes to take effect.
sudo /opt/bitnami/ctlscript.sh restart apache
I can see now the work types populated on my side