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 https://myhostname.example.com
      Initial credentials are admin / vkscvVxFJHnrrAdH
  * Foreman Proxy is running at https://myhostname.example.com:8443
  * 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





Comments

  1. Kamal8 April 2020 at 20:58

    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'
    /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/

    ReplyDelete

Post a Comment

Popular posts from this blog

Rebuild your new Yum repository after changing the packages

-
If you have done any  changes  to your local  repository  packages, adding new ones or deleting some, you can just simply update your yum sqlite metadata database for your changes to take effect, rather than creating the whole repository again which takes time if you have  thousands  of packages in your repository.  Here is how we rebuild our yum repository. 1. After you are done with adding/removing packages to your local repo, then: # createrepo --update /path/to/repo_dir 2. On the  client  side, you need to clean up the cached yum meta data in order to see the changes after repo rebuild: # yum clean all 3. Now update the  client  yum cache  # yum update
Read more

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

-
I have recently built the whole Development Environment of Java Enterprise Edition (J2EE) project on multiple Docker containers. It has saved the hassle of setting up a dev env for new developers. All it takes to setup the environment is to clone our github repositories and run the Docker images. I will explain the setup in a future post. Build Wildfly Docker Image with Debugging Enabled So basically in order to run the Wildfly in debug mode, we need to add --debug  flag to the Wildfly standalone.sh  startup script. Also we need to expose port 8787  in our image as it's the default port for Wildfly JVM debug mode. 1. Create or change your Wildfly Dockerfile as follows: $ cat Dockerfile FROM jboss/wildfly: 10.0 . 0 .Final EXPOSE 8787 CMD [ "/opt/jboss/wildfly/bin/standalone.sh" , "-b" , "0.0.0.0" , "-bmanagement" , "0.0.0.0" , "--debug" ] 2. Build and tag the image: $ docker build -t wildfly-debug . 3.
Read more

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

-
In Linux, if you want to set the password for an account to never expire, here is the command: # chage -I -1 -m 0 -M 99999 -E -1 username  And to force a user to change his password upon first login: # chage -d0 username Current status of the account can be checked via chage command : # chage -l username  Last password change                                    : Jun 18, 2013 Password expires                                        : never Password inactive                                       : never Account expires                                         : never Minimum number of days between password change          : 0 Maximum number of days between password change          : 99999 Number of days of warning before password expires       : 7 For AIX, to set the password to non expiry and force the user to change his password upon first login: # chuser expires=0 maxage=0 username  To check the username status in AIX: # lsuser -f username
Read more