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

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

Building RPM OpenSSH 7.1p1 on RHEL/CentOS 6.5

-
After I've implemented the OpenVAS vulnerability assessment system, I've made a complete vulnerability testing on the environment for both Linux and Wintel servers. The result for the all Linux servers were Red :) Severity 10.0(High). The reason was the OpenSSH version 5. Test result: High  (CVSS: 8.5) NVT: OpenSSH Multiple Vulnerabilities (OID: 1.3.6.1.4.1.25623.1.0.806052) Product detection result: cpe:/a:openbsd:openssh:5.3 by SSH Server type and version (OID: 1.3.6.1.4.1.25623.1.0.10267) Summary This host is running OpenSSH and is prone to multiple vulnerabilities. Vulnerability Detection Result Installed version: 5.3 Fixed version: 7.0 Impact Successful exploitation will allow an attacker to gain privileges, to conduct impersonation attacks, to conduct brute-force attacks or cause a denial of service. Impact Level: Application Solution Upgrade to OpenSSH 7.0 or later. For updates refer to http://www.openssh.com Affected Software/OS OpenSSH vers
Read more