Issue with Foreman rake db during Foreman installation

During the Foreman installation on RHEL 6, I got the following error:

[root@puppesrv01-vlt ~]# foreman-installer
 /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]: Failed to call refresh: Command exceeded timeout
 /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]: Command exceeded timeout
 /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]
Preparing installation Done
  Something went wrong! Check the log for ERROR-level output
  * Foreman is running at
      Initial credentials are admin / vkscvVxFJHnrrAdH
  * Foreman Proxy is running at
  * Puppetmaster is running at port 8140
  The full log is at /var/log/foreman-installer/foreman-installer.log

It turns out that I need to issue the following commands manually and run the foreman-installer again:

# foreman-rake db:migrate

# foreman-rake db:seed

It should not return any error and then clear the cache:

# foreman-rake tmp:cache:clear

# foreman-rake tmp:sessions:clear


  1. Can you please guide me hre. Thank you

    [kamals@centmanager bin]$ sudo foreman-rake db:seed
    API controllers newer than Apipie cache! Run apipie:cache rake task to regenerate cache.
    rake aborted!
    Foreman::PermissionMissingException: ERF73-0602 [Foreman::PermissionMissingException]: some permissions were not found: [:create_lifecycle_environments, :create_content_views]
    /usr/share/foreman/app/models/role.rb:335:in `permission_records'
    /usr/share/foreman/app/models/role.rb:154:in `add_permissions'
    /usr/share/foreman/app/models/role.rb:207:in `add_permissions!'

    [kamals@centmanager bin]$ sudo foreman-installer
    '/usr/sbin/foreman-rake db:migrate' returned 1 instead of one of [0]
    /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/errors.rb:157:in `fail'
    /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/exec.rb:183:in `sync'
    /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:241:in `sync'


Post a Comment

Popular posts from this blog

Rebuild your new Yum repository after changing the packages

Running Docker Wildfly/JBoss Application Server in Debug mode via Eclipse

Linux and AIX user non expiry and force password change at first login