Problems installing Katello 2.0 using Manual Method in RHEL6.5, Centos 6.5, Centos 7

Hi all,

I've built and rebuilt Centos 6.5, Centos 7, and Redhat 6 systems using a
base install kickstart that I've been using successfully for quite some
time. I then configure all the repositories and run yum -y install
katello. All the packages install just fine.

Next, I run the katello-installer script. However, this runs for hours and
always fails with timeouts, usually on foreman-rake db:seed and
apipie:cache. The system is configured as follows:

VMware virtual machine.
1 vCPU with 4 cores. (Also tried with 2 vCPUs but didn't make a difference)
12 GB Memory
4 GB Swap
40 GB OS PV.
Large DB and Pulp PV.

After the install fails, it's only a matter of time before the VM's
resources are all used up and I can't even type without a 10 second or
longer delay.

Troubleshooting/random-button-pushing I've done:

1.) check directory permissions
2.) Check /etc/hosts for proper lookup of localhost and hostname -s and
hostname -f
3.) Check free space…not an issue.
4.) rerun installer
5.) Add installer options like --foreman-admin-password
6.) use katello-installer --reset
7.) remove katello and try again.
8.) Rebuild system to various OS's as described above.
9.) Ensure ntp is working and only using local authentication (no ldap, etc)
10.) Log file review for something useful. It just times out!

Here's the two relevant snippets of the latest katello-installer.log:

[ INFO 2014-10-14 15:56:44 main] RESOURCE Service[httpd]
[DEBUG 2014-10-14 15:56:54 main]
/Stage[main]/Apache::Service/Service[httpd]: The container
Class[Apache::Service] will propagate my refresh event
[ INFO 2014-10-14 15:56:56 main]
/Stage[main]/Apache::Service/Service[httpd]: Unscheduling refresh on
Service[httpd]
[DEBUG 2014-10-14 15:56:56 main] Class[Apache::Service]: The container
Stage[main] will propagate my refresh event
[ INFO 2014-10-14 15:56:58 main] RESOURCE Exec[foreman-rake-db:seed]
[DEBUG 2014-10-14 15:56:58 main]
Execforeman-rake-db:seed: Executing
'/usr/sbin/foreman-rake db:seed'
[DEBUG 2014-10-14 15:56:58 main] Executing '/usr/sbin/foreman-rake db:seed'
[ERROR 2014-10-14 16:01:52 main]
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]:
Failed to call refresh: Command exceeded timeout
[ERROR 2014-10-14 16:01:59 main]
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]:
Command exceeded timeout
[ INFO 2014-10-14 16:02:00 main] /usr/lib/ruby/1.8/timeout.rb:64:in
execute' [ INFO 2014-10-14 16:02:01 main] /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:63:inrun'
[ INFO 2014-10-14 16:02:02 main]
/usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:59:in run' [ INFO 2014-10-14 16:02:03 main] /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:29:inchdir'
[ INFO 2014-10-14 16:02:05 main]
/usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:29:in run' [ INFO 2014-10-14 16:02:05 main] /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec/posix.rb:45:inrun'
[ INFO 2014-10-14 16:02:06 main]
/usr/lib/ruby/site_ruby/1.8/puppet/type/exec.rb:130:in `sync'

INFO 2014-10-14 16:03:14 main]
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:384:in run' [ INFO 2014-10-14 16:03:14 main] /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:146:inrun'
[ INFO 2014-10-14 16:03:14 main]
/usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:92:in execute' [ INFO 2014-10-14 16:03:15 main] /usr/bin/puppet:8 [ INFO 2014-10-14 16:03:15 main] RESOURCE Foreman::Rake[db:seed] [ INFO 2014-10-14 16:03:15 main] RESOURCE Foreman::Rake[apipie:cache] [ INFO 2014-10-14 16:03:15 main] Foreman::Rake[apipie:cache]: Scheduling refresh of Exec[foreman-rake-apipie:cache] [ INFO 2014-10-14 16:03:15 main] RESOURCE Exec[foreman-rake-apipie:cache] [DEBUG 2014-10-14 16:03:15 main] Exec[foreman-rake-apipie:cache](provider=posix): Executing '/usr/sbin/foreman-rake apipie:cache' [DEBUG 2014-10-14 16:03:15 main] Executing '/usr/sbin/foreman-rake apipie:cache' [ERROR 2014-10-14 16:07:13 main] /Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache]/Exec[foreman-rake-apipie:cache]: Failed to call refresh: Command exceeded timeout [ERROR 2014-10-14 16:12:30 main] /Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache]/Exec[foreman-rake-apipie:cache]: Command exceeded timeout [ INFO 2014-10-14 16:12:42 main] /usr/lib/ruby/1.8/timeout.rb:64:inexecute'
[ INFO 2014-10-14 16:12:44 main]
/usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:63:in run' [ INFO 2014-10-14 16:12:46 main] /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:59:inrun'
[ INFO 2014-10-14 16:12:48 main]
/usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:29:in chdir' [ INFO 2014-10-14 16:12:48 main] /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:29:inrun'
[ INFO 2014-10-14 16:12:49 main]
/usr/lib/ruby/site_ruby/1.8/puppet/provider/exec/posix.rb:45:in `run'

Has anyone else experienced this? Any ideas on why this becomes such a
resource hog and, most importantly, any ideas on how to fix this?

Thanks,

I forgot to mention that selinux and firewall are disabled and clear.

··· On Wednesday, October 15, 2014 8:19:51 AM UTC-4, Garrett DeMarco wrote: > > Hi all, > > I've built and rebuilt Centos 6.5, Centos 7, and Redhat 6 systems using a > base install kickstart that I've been using successfully for quite some > time. I then configure all the repositories and run yum -y install > katello. All the packages install just fine. > > Next, I run the katello-installer script. However, this runs for hours and > always fails with timeouts, usually on foreman-rake db:seed and > apipie:cache. The system is configured as follows: > > VMware virtual machine. > 1 vCPU with 4 cores. (Also tried with 2 vCPUs but didn't make a difference) > 12 GB Memory > 4 GB Swap > 40 GB OS PV. > Large DB and Pulp PV. > > After the install fails, it's only a matter of time before the VM's > resources are all used up and I can't even type without a 10 second or > longer delay. > > Troubleshooting/random-button-pushing I've done: > > 1.) check directory permissions > 2.) Check /etc/hosts for proper lookup of localhost and `hostname -s` and > `hostname -f` > 3.) Check free space...not an issue. > 4.) rerun installer > 5.) Add installer options like --foreman-admin-password > 6.) use katello-installer --reset > 7.) remove katello and try again. > 8.) Rebuild system to various OS's as described above. > 9.) Ensure ntp is working and only using local authentication (no ldap, > etc) > 10.) Log file review for something useful. It just times out! > > Here's the two relevant snippets of the latest katello-installer.log: > > [ INFO 2014-10-14 15:56:44 main] RESOURCE Service[httpd] > [DEBUG 2014-10-14 15:56:54 main] > /Stage[main]/Apache::Service/Service[httpd]: The container > Class[Apache::Service] will propagate my refresh event > [ INFO 2014-10-14 15:56:56 main] > /Stage[main]/Apache::Service/Service[httpd]: Unscheduling refresh on > Service[httpd] > [DEBUG 2014-10-14 15:56:56 main] Class[Apache::Service]: The container > Stage[main] will propagate my refresh event > [ INFO 2014-10-14 15:56:58 main] RESOURCE Exec[foreman-rake-db:seed] > [DEBUG 2014-10-14 15:56:58 main] > Exec[foreman-rake-db:seed](provider=posix): Executing > '/usr/sbin/foreman-rake db:seed' > [DEBUG 2014-10-14 15:56:58 main] Executing '/usr/sbin/foreman-rake > db:seed' > [ERROR 2014-10-14 16:01:52 main] > /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: > Failed to call refresh: Command exceeded timeout > [ERROR 2014-10-14 16:01:59 main] > /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: > Command exceeded timeout > [ INFO 2014-10-14 16:02:00 main] /usr/lib/ruby/1.8/timeout.rb:64:in > `execute' > [ INFO 2014-10-14 16:02:01 main] > /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:63:in `run' > [ INFO 2014-10-14 16:02:02 main] > /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:59:in `run' > [ INFO 2014-10-14 16:02:03 main] > /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:29:in `chdir' > [ INFO 2014-10-14 16:02:05 main] > /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:29:in `run' > [ INFO 2014-10-14 16:02:05 main] > /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec/posix.rb:45:in `run' > [ INFO 2014-10-14 16:02:06 main] > /usr/lib/ruby/site_ruby/1.8/puppet/type/exec.rb:130:in `sync' > > > > INFO 2014-10-14 16:03:14 main] > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:384:in `run' > [ INFO 2014-10-14 16:03:14 main] > /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:146:in `run' > [ INFO 2014-10-14 16:03:14 main] > /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:92:in `execute' > [ INFO 2014-10-14 16:03:15 main] /usr/bin/puppet:8 > [ INFO 2014-10-14 16:03:15 main] RESOURCE Foreman::Rake[db:seed] > [ INFO 2014-10-14 16:03:15 main] RESOURCE Foreman::Rake[apipie:cache] > [ INFO 2014-10-14 16:03:15 main] Foreman::Rake[apipie:cache]: Scheduling > refresh of Exec[foreman-rake-apipie:cache] > [ INFO 2014-10-14 16:03:15 main] RESOURCE Exec[foreman-rake-apipie:cache] > [DEBUG 2014-10-14 16:03:15 main] > Exec[foreman-rake-apipie:cache](provider=posix): Executing > '/usr/sbin/foreman-rake apipie:cache' > [DEBUG 2014-10-14 16:03:15 main] Executing '/usr/sbin/foreman-rake > apipie:cache' > [ERROR 2014-10-14 16:07:13 main] > /Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache]/Exec[foreman-rake-apipie:cache]: > Failed to call refresh: Command exceeded timeout > [ERROR 2014-10-14 16:12:30 main] > /Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache]/Exec[foreman-rake-apipie:cache]: > Command exceeded timeout > [ INFO 2014-10-14 16:12:42 main] /usr/lib/ruby/1.8/timeout.rb:64:in > `execute' > [ INFO 2014-10-14 16:12:44 main] > /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:63:in `run' > [ INFO 2014-10-14 16:12:46 main] > /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:59:in `run' > [ INFO 2014-10-14 16:12:48 main] > /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:29:in `chdir' > [ INFO 2014-10-14 16:12:48 main] > /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:29:in `run' > [ INFO 2014-10-14 16:12:49 main] > /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec/posix.rb:45:in `run' > > Has anyone else experienced this? Any ideas on why this becomes such a > resource hog and, most importantly, any ideas on how to fix this? > > Thanks, > > >

This is how I install katello (and worked in the past)

On a clean OS install perform the following tasks:

yum -y update
yum install -y git ruby rubygems
git clone https://github.com/Katello/katello-deploy.git
cd katello-deploy
./setup.rb centos6 --skip-installer --version 2.0
katello-installer --foreman-admin-password="changeme"
–foreman-authentication=true --capsule-tftp=true
–capsule-tftp-servername="10.10.10.10" --capsule-dhcp=true
–capsule-dhcp-gateway="10.10.10.10" --capsule-dhcp-interface="eth1"
–capsule-dhcp-range="10.10.10.20 10.10.10.200" --capsule-dns=true
–capsule-dns-forwarders "10.10.10.10" --capsule-dns-interface="eth1"
–capsule-dns-reverse="10.10.10.in-addr.arpa" --capsule-dns-zone
"mydomain.local"

Enjoy.

··· On Wednesday, October 15, 2014 8:23:30 AM UTC-4, Garrett DeMarco wrote: > > I forgot to mention that selinux and firewall are disabled and clear. > > > > On Wednesday, October 15, 2014 8:19:51 AM UTC-4, Garrett DeMarco wrote: >> >> Hi all, >> >> I've built and rebuilt Centos 6.5, Centos 7, and Redhat 6 systems using a >> base install kickstart that I've been using successfully for quite some >> time. I then configure all the repositories and run yum -y install >> katello. All the packages install just fine. >> >> Next, I run the katello-installer script. However, this runs for hours >> and always fails with timeouts, usually on foreman-rake db:seed and >> apipie:cache. The system is configured as follows: >> >> VMware virtual machine. >> 1 vCPU with 4 cores. (Also tried with 2 vCPUs but didn't make a >> difference) >> 12 GB Memory >> 4 GB Swap >> 40 GB OS PV. >> Large DB and Pulp PV. >> >> After the install fails, it's only a matter of time before the VM's >> resources are all used up and I can't even type without a 10 second or >> longer delay. >> >> Troubleshooting/random-button-pushing I've done: >> >> 1.) check directory permissions >> 2.) Check /etc/hosts for proper lookup of localhost and `hostname -s` and >> `hostname -f` >> 3.) Check free space...not an issue. >> 4.) rerun installer >> 5.) Add installer options like --foreman-admin-password >> 6.) use katello-installer --reset >> 7.) remove katello and try again. >> 8.) Rebuild system to various OS's as described above. >> 9.) Ensure ntp is working and only using local authentication (no ldap, >> etc) >> 10.) Log file review for something useful. It just times out! >> >> Here's the two relevant snippets of the latest katello-installer.log: >> >> [ INFO 2014-10-14 15:56:44 main] RESOURCE Service[httpd] >> [DEBUG 2014-10-14 15:56:54 main] >> /Stage[main]/Apache::Service/Service[httpd]: The container >> Class[Apache::Service] will propagate my refresh event >> [ INFO 2014-10-14 15:56:56 main] >> /Stage[main]/Apache::Service/Service[httpd]: Unscheduling refresh on >> Service[httpd] >> [DEBUG 2014-10-14 15:56:56 main] Class[Apache::Service]: The container >> Stage[main] will propagate my refresh event >> [ INFO 2014-10-14 15:56:58 main] RESOURCE Exec[foreman-rake-db:seed] >> [DEBUG 2014-10-14 15:56:58 main] >> Exec[foreman-rake-db:seed](provider=posix): Executing >> '/usr/sbin/foreman-rake db:seed' >> [DEBUG 2014-10-14 15:56:58 main] Executing '/usr/sbin/foreman-rake >> db:seed' >> [ERROR 2014-10-14 16:01:52 main] >> /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: >> Failed to call refresh: Command exceeded timeout >> [ERROR 2014-10-14 16:01:59 main] >> /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: >> Command exceeded timeout >> [ INFO 2014-10-14 16:02:00 main] /usr/lib/ruby/1.8/timeout.rb:64:in >> `execute' >> [ INFO 2014-10-14 16:02:01 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:63:in `run' >> [ INFO 2014-10-14 16:02:02 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:59:in `run' >> [ INFO 2014-10-14 16:02:03 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:29:in `chdir' >> [ INFO 2014-10-14 16:02:05 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:29:in `run' >> [ INFO 2014-10-14 16:02:05 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec/posix.rb:45:in `run' >> [ INFO 2014-10-14 16:02:06 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/type/exec.rb:130:in `sync' >> >> >> >> INFO 2014-10-14 16:03:14 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:384:in `run' >> [ INFO 2014-10-14 16:03:14 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:146:in `run' >> [ INFO 2014-10-14 16:03:14 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:92:in `execute' >> [ INFO 2014-10-14 16:03:15 main] /usr/bin/puppet:8 >> [ INFO 2014-10-14 16:03:15 main] RESOURCE Foreman::Rake[db:seed] >> [ INFO 2014-10-14 16:03:15 main] RESOURCE Foreman::Rake[apipie:cache] >> [ INFO 2014-10-14 16:03:15 main] Foreman::Rake[apipie:cache]: Scheduling >> refresh of Exec[foreman-rake-apipie:cache] >> [ INFO 2014-10-14 16:03:15 main] RESOURCE Exec[foreman-rake-apipie:cache] >> [DEBUG 2014-10-14 16:03:15 main] >> Exec[foreman-rake-apipie:cache](provider=posix): Executing >> '/usr/sbin/foreman-rake apipie:cache' >> [DEBUG 2014-10-14 16:03:15 main] Executing '/usr/sbin/foreman-rake >> apipie:cache' >> [ERROR 2014-10-14 16:07:13 main] >> /Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache]/Exec[foreman-rake-apipie:cache]: >> Failed to call refresh: Command exceeded timeout >> [ERROR 2014-10-14 16:12:30 main] >> /Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache]/Exec[foreman-rake-apipie:cache]: >> Command exceeded timeout >> [ INFO 2014-10-14 16:12:42 main] /usr/lib/ruby/1.8/timeout.rb:64:in >> `execute' >> [ INFO 2014-10-14 16:12:44 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:63:in `run' >> [ INFO 2014-10-14 16:12:46 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:59:in `run' >> [ INFO 2014-10-14 16:12:48 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:29:in `chdir' >> [ INFO 2014-10-14 16:12:48 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:29:in `run' >> [ INFO 2014-10-14 16:12:49 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec/posix.rb:45:in `run' >> >> Has anyone else experienced this? Any ideas on why this becomes such a >> resource hog and, most importantly, any ideas on how to fix this? >> >> Thanks, >> >> >>

Thanks Ignacio, however after rebuilding, I'm still getting the following:

.
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]:
Failed to call refresh: Command exceeded timeout
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]:
Command exceeded timeout
/Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache]/Exec[foreman-rake-apipie:cache]:
Failed to call refresh: Command exceeded timeout
/Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache]/Exec[foreman-rake-apipie:cache]:
Command exceeded timeout

Note, I set dhcp to false, but that's the only real difference.

Thanks.

Garret,

Can you look at the full installer log to see if there is a traceback?

Eric

··· On Thu, Oct 16, 2014 at 10:24 AM, Garrett DeMarco wrote: > Thanks Ignacio, however after rebuilding, I'm still getting the following: > > . > /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: > Failed to call refresh: Command exceeded timeout > > /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: > Command exceeded timeout > > /Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache]/Exec[foreman-rake-apipie:cache]: > Failed to call refresh: Command exceeded timeout > > /Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache]/Exec[foreman-rake-apipie:cache]: > Command exceeded timeout > > Note, I set dhcp to false, but that's the only real difference. > > Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-users+unsubscribe@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout.

Hi Eric,

It looks like the same timeout message as before. Here's the db:migrate
error:

> [ INFO 2014-10-16 10:09:55 main] Class[Pulp::Service]: Scheduling refresh
>> of Service[httpd]
>
> [DEBUG 2014-10-16 10:09:55 main] Executing
>> '/usr/share/katello-installer/modules/service_wait/bin/service-wait httpd
>> status'
>
> [DEBUG 2014-10-16 10:09:56 main] Executing '/sbin/chkconfig httpd'
>
> [DEBUG 2014-10-16 10:09:56 main] Executing
>> '/usr/share/katello-installer/modules/service_wait/bin/service-wait httpd
>> start'
>
> [DEBUG 2014-10-16 10:10:04 main] Executing '/sbin/chkconfig httpd'
>
> [DEBUG 2014-10-16 10:10:05 main] Executing '/sbin/chkconfig httpd on'
>
> [ WARN 2014-10-16 10:10:16 main]
>> /Stage[main]/Apache::Service/Service[httpd]/ensure: ensure changed
>> 'stopped' to 'running'
>
> [ INFO 2014-10-16 10:10:17 main] RESOURCE Service[httpd]
>
> [DEBUG 2014-10-16 10:10:17 main]
>> /Stage[main]/Apache::Service/Service[httpd]: The container
>> Class[Apache::Service] will propagate my refresh event
>
> [ INFO 2014-10-16 10:10:17 main]
>> /Stage[main]/Apache::Service/Service[httpd]: Unscheduling refresh on
>> Service[httpd]
>
> [DEBUG 2014-10-16 10:10:19 main] Class[Apache::Service]: The container
>> Stage[main] will propagate my refresh event
>
> [ INFO 2014-10-16 10:10:21 main] RESOURCE Exec[foreman-rake-db:seed]
>
> [DEBUG 2014-10-16 10:10:21 main]
>> Execforeman-rake-db:seed: Executing
>> '/usr/sbin/foreman-rake db:seed'
>
> [DEBUG 2014-10-16 10:10:21 main] Executing '/usr/sbin/foreman-rake
>> db:seed'
>
> [ERROR 2014-10-16 10:15:27 main]
>> /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]:
>> Failed to call refresh: Command exceeded timeout
>
> [ERROR 2014-10-16 10:15:30 main]
>> /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]:
>> Command exceeded timeout
>
> [ INFO 2014-10-16 10:15:31 main] /usr/lib/ruby/1.8/timeout.rb:64:in
>> execute' > > [ INFO 2014-10-16 10:15:31 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:63:inrun'
>
> [ INFO 2014-10-16 10:15:32 main]
>> /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:59:in run' > > [ INFO 2014-10-16 10:15:32 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:29:inchdir'
>
> [ INFO 2014-10-16 10:15:33 main]
>> /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:29:in run' > > [ INFO 2014-10-16 10:15:34 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec/posix.rb:45:inrun'
>
> [ INFO 2014-10-16 10:15:34 main]
>> /usr/lib/ruby/site_ruby/1.8/puppet/type/exec.rb:130:in sync' > > [ INFO 2014-10-16 10:15:34 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/type/exec.rb:127:intimes'
>
> [ INFO 2014-10-16 10:15:34 main]
>> /usr/lib/ruby/site_ruby/1.8/puppet/type/exec.rb:127:in sync' > > [ INFO 2014-10-16 10:15:34 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/type/exec.rb:583:inrefresh'
>
> [ INFO 2014-10-16 10:15:35 main]
>> /usr/lib/ruby/site_ruby/1.8/puppet/transaction/event_manager.rb:101:in
>> send' > > [ INFO 2014-10-16 10:15:35 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/transaction/event_manager.rb:101:in >>process_callback'
>
> [ INFO 2014-10-16 10:15:36 main]
>> /usr/lib/ruby/site_ruby/1.8/puppet/transaction/event_manager.rb:20:in
>> process_events' > > [ INFO 2014-10-16 10:15:36 main] >> /usr/lib/ruby/site_ruby/1.8/puppet/transaction/event_manager.rb:93:in >>queued_event
>
>

And down to the apipie:cache…(I assume this fails because of the
db:migrate):

[ INFO 2014-10-16 10:15:49 main]
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:131:in run' [ INFO 2014-10-16 10:15:49 main] /usr/lib/ruby/site_ruby/1.8/puppet/application/apply.rb:297:inapply_catalog'
[ INFO 2014-10-16 10:15:49 main]
/usr/lib/ruby/site_ruby/1.8/puppet/application/apply.rb:231:in main' [ INFO 2014-10-16 10:15:49 main] /usr/lib/ruby/site_ruby/1.8/puppet/context.rb:64:inoverride'
[ INFO 2014-10-16 10:15:49 main]
/usr/lib/ruby/site_ruby/1.8/puppet.rb:244:in override' [ INFO 2014-10-16 10:15:49 main] /usr/lib/ruby/site_ruby/1.8/puppet/application/apply.rb:193:inmain'
[ INFO 2014-10-16 10:15:49 main]
/usr/lib/ruby/site_ruby/1.8/puppet/application/apply.rb:154:in run_command' [ INFO 2014-10-16 10:15:49 main] /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:384:inrun'
[ INFO 2014-10-16 10:15:49 main]
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:510:in plugin_hook' [ INFO 2014-10-16 10:15:49 main] /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:384:inrun'
[ INFO 2014-10-16 10:15:49 main]
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:488:in exit_on_fail' [ INFO 2014-10-16 10:15:49 main] /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:384:inrun'
[ INFO 2014-10-16 10:15:49 main]
/usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:146:in run' [ INFO 2014-10-16 10:15:49 main] /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:92:inexecute'
[ INFO 2014-10-16 10:15:50 main] /usr/bin/puppet:8
[ INFO 2014-10-16 10:15:50 main] RESOURCE Foreman::Rake[db:seed]
[ INFO 2014-10-16 10:15:50 main] RESOURCE Foreman::Rake[apipie:cache]
[ INFO 2014-10-16 10:15:50 main] Foreman::Rake[apipie:cache]: Scheduling
refresh of Exec[foreman-rake-apipie:cache]
[ INFO 2014-10-16 10:15:50 main] RESOURCE Exec[foreman-rake-apipie:cache]
[DEBUG 2014-10-16 10:15:50 main]
Execforeman-rake-apipie:cache: Executing
'/usr/sbin/foreman-rake apipie:cache'
[DEBUG 2014-10-16 10:15:51 main] Executing '/usr/sbin/foreman-rake
apipie:cache'
[ERROR 2014-10-16 10:20:51 main]
/Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache]/Exec[foreman-rake-apipie:cache]:
Failed to call refresh: Command exceeded timeout
[ERROR 2014-10-16 10:20:56 main]
/Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache]/Exec[foreman-rake-apipie:cache]:
Command exceeded timeout
[ INFO 2014-10-16 10:20:56 main] /usr/lib/ruby/1.8/timeout.rb:64:in
execute' [ INFO 2014-10-16 10:20:56 main] /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:63:inrun'
[ INFO 2014-10-16 10:20:57 main]
/usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:59:in run' [ INFO 2014-10-16 10:20:57 main] /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:29:inchdir'
[ INFO 2014-10-16 10:20:57 main]
/usr/lib/ruby/site_ruby/1.8/puppet/provider/exec.rb:29:in run' [ INFO 2014-10-16 10:20:57 main] /usr/lib/ruby/site_ruby/1.8/puppet/provider/exec/posix.rb:45:inrun'
[ INFO 2014-10-16 10:20:58 main]
/usr/lib/ruby/site_ruby/1.8/puppet/type/exec.rb:130:in sync' [ INFO 2014-10-16 10:20:58 main] /usr/lib/ruby/site_ruby/1.8/puppet/type/exec.rb:127:intimes'
[ INFO 2014-10-16 10:20:58 main]
/usr/lib/ruby/site_ruby/1.8/puppet/type/exec.rb:127:in sync' [ INFO 2014-10-16 10:20:59 main] /usr/lib/ruby/site_ruby/1.8/puppet/type/exec.rb:583:inrefresh'
[ INFO 2014-10-16 10:20:59 main]
/usr/lib/ruby/site_ruby/1.8/puppet/transaction/event_manager.rb:101:in
send' [ INFO 2014-10-16 10:20:59 main] /usr/lib/ruby/site_ruby/1.8/puppet/transaction/event_manager.rb:101:inprocess_callback'
[ INFO 2014-10-16 10:20:59 main]
/usr/lib/ruby/site_ruby/1.8/puppet/transaction/event_manager.rb:20:in
process_events' [ INFO 2014-10-16 10:20:59 main] /usr/lib/ruby/site_ruby/1.8/puppet/transaction/event_manager.rb:93:inqueued_events'
[ INFO 2014-10-16 10:21:00 main]
/usr/lib/ruby/site_ruby/1.8/puppet/transaction/event_manager.rb:92:in each' [ INFO 2014-10-16 10:21:00 main] /usr/lib/ruby/site_ruby/1.8/puppet/transaction/event_manager.rb:92:inqueued_events'
[ INFO 2014-10-16 10:21:00 main]
/usr/lib/ruby/site_ruby/1.8/puppet/transaction/event_manager.rb:19:in
process_events' [ INFO 2014-10-16 10:21:00 main] /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:221:ineval_resource'

Thanks,

Ok, this is interesting…just checked teh /var/log/foreman/db_migrate.log
and apipie_cache.log and both have this:

rake aborted!
Please install the sqlite3 adapter: gem install activerecord-sqlite3-adapter (Could not find sqlite3 (~> 1.3.5) amongst
[actionmailer-3.2.8, actionpack-3.2.8, activemodel-3.2.8,
activerecord-3.2.8, activeresource-3.2.8, activesupport-3.2.8,
addressable-2.3.5, algebrick-0.4.0, ancestry-2.0.0, anemone-0.7.2,
angular-rails-templates-0.0.4, ansi-1.4.3, apipie-params-0.0.3,
apipie-rails-0.2.5, arel-3.0.2, audited-3.0.0, audited-activerecord-3.0.0,
autoparse-0.3.3, bigdecimal-1.1.0, bootstrap-sass-3.0.3.0, builder-3.0.0,
bundler-1.3.5, bundler_ext-0.3.0, chunky_png-1.2.0, commonjs-0.2.6,
compass-0.12.2, compass-960-plugin-0.10.4, compass-rails-1.0.3,
daemons-1.1.4, deep_cloneable-2.0.0, deface-0.7.2, diff-lcs-1.1.3,
dynflow-0.7.3, erubis-2.7.0, excon-0.38.0, extlib-0.9.16, faraday-0.8.8,
fast_gettext-0.8.0, fog-1.23.0, fog-brightbox-0.0.1, fog-core-1.23.0,
fog-json-1.0.0, fog-softlayer-0.3.9, foreigner-1.4.2, foreman-tasks-0.6.10,
foreman_bootdisk-3.2.0, foreman_discovery-1.4.0.rc4, foreman_hooks-0.3.7,
formatador-0.2.1, fssm-0.2.7, ftools-0.0.0, gettext_i18n_rails-0.10.0,
gettext_i18n_rails_js-0.0.8, google-api-client-0.6.4, haml-3.1.6,
haml-rails-0.3.4, hashr-0.0.22, hike-1.2.1, hooks-0.2.2, hpricot-0.8.6,
i18n-0.6.0, i18n_data-0.2.7, io-console-0.3, ipaddress-0.8.0,
journey-1.0.4, jquery-rails-2.0.2, jquery-ui-rails-4.0.2, json-1.5.5,
justified-0.0.4, jwt-0.1.8, katello-2.0.0, launchy-2.3.0, ldap_fluff-0.3.1,
less-2.3.1, less-rails-2.3.2, little-plugger-1.1.3, logging-1.8.1,
mail-2.4.4, maruku-0.6.1, mime-types-1.19, minitest-2.5.1,
multi_json-1.8.2, multipart-post-1.2.0, net-http-persistent-2.7,
net-ldap-0.3.1, net-scp-1.1.0, net-ssh-2.6.7, netrc-0.7.7, nokogiri-1.5.11,
oauth-0.4.7, open4-1.3.0, po_to_json-0.0.7, polyglot-0.3.3, rabl-0.9.0,
rack-1.4.1, rack-cache-1.2, rack-protection-1.2.0, rack-ssl-1.3.2,
rack-test-0.6.1, rails-3.2.8, railties-3.2.8, rake-0.9.2.2, rbovirt-0.0.29,
rbvmomi-1.6.0, rdoc-3.9.5, ref-1.0.0, rest-client-1.6.7, robotex-1.0.0,
ruby-libvirt-0.5.1, ruby2ruby-2.0.1, ruby_parser-3.1.1, runcible-1.1.0,
safemode-1.2.1, sass-3.2.13, sass-rails-3.2.5, scoped_search-2.7.1,
sequel-3.45.0, sexp_processor-4.1.3, signet-0.4.5, sinatra-1.3.2,
sprockets-2.10.1, sprockets-rails-2.0.1, sshkey-1.6.0,
strong_parameters-0.2.1, syntax-1.0.0, therubyracer-0.11.0beta5,
thor-0.18.1, tilt-1.3.3, tire-0.6.2, treetop-1.4.10, trollop-2.0,
tzinfo-0.3.33, ui_alchemy-rails-1.0.12, unf-0.1.3, unf_ext-0.0.6,
uuidtools-2.1.3, validates_lengths_from_database-0.2.0,
will_paginate-3.0.2])

I'm going to try installing this gem and run again. I'll post any
successes…

Garret,

Unfortunately that log is misleading and shows up on every
installation. Trying runnning 'foreman-rake db:seed' from the command
line post install and see if that times out as well. If you'd like to
debug this more real time, you can find me on #theforeman at 'ehelms'

Eric

··· On Thu, Oct 16, 2014 at 11:55 AM, Garrett DeMarco wrote: > Ok, this is interesting...just checked teh /var/log/foreman/db_migrate.log > and apipie_cache.log and both have this: > > rake aborted! > Please install the sqlite3 adapter: `gem install > activerecord-sqlite3-adapter` (Could not find sqlite3 (~> 1.3.5) amongst > [actionmailer-3.2.8, actionpack-3.2.8, activemodel-3.2.8, > activerecord-3.2.8, activeresource-3.2.8, activesupport-3.2.8, > addressable-2.3.5, algebrick-0.4.0, ancestry-2.0.0, anemone-0.7.2, > angular-rails-templates-0.0.4, ansi-1.4.3, apipie-params-0.0.3, > apipie-rails-0.2.5, arel-3.0.2, audited-3.0.0, audited-activerecord-3.0.0, > autoparse-0.3.3, bigdecimal-1.1.0, bootstrap-sass-3.0.3.0, builder-3.0.0, > bundler-1.3.5, bundler_ext-0.3.0, chunky_png-1.2.0, commonjs-0.2.6, > compass-0.12.2, compass-960-plugin-0.10.4, compass-rails-1.0.3, > daemons-1.1.4, deep_cloneable-2.0.0, deface-0.7.2, diff-lcs-1.1.3, > dynflow-0.7.3, erubis-2.7.0, excon-0.38.0, extlib-0.9.16, faraday-0.8.8, > fast_gettext-0.8.0, fog-1.23.0, fog-brightbox-0.0.1, fog-core-1.23.0, > fog-json-1.0.0, fog-softlayer-0.3.9, foreigner-1.4.2, foreman-tasks-0.6.10, > foreman_bootdisk-3.2.0, foreman_discovery-1.4.0.rc4, foreman_hooks-0.3.7, > formatador-0.2.1, fssm-0.2.7, ftools-0.0.0, gettext_i18n_rails-0.10.0, > gettext_i18n_rails_js-0.0.8, google-api-client-0.6.4, haml-3.1.6, > haml-rails-0.3.4, hashr-0.0.22, hike-1.2.1, hooks-0.2.2, hpricot-0.8.6, > i18n-0.6.0, i18n_data-0.2.7, io-console-0.3, ipaddress-0.8.0, journey-1.0.4, > jquery-rails-2.0.2, jquery-ui-rails-4.0.2, json-1.5.5, justified-0.0.4, > jwt-0.1.8, katello-2.0.0, launchy-2.3.0, ldap_fluff-0.3.1, less-2.3.1, > less-rails-2.3.2, little-plugger-1.1.3, logging-1.8.1, mail-2.4.4, > maruku-0.6.1, mime-types-1.19, minitest-2.5.1, multi_json-1.8.2, > multipart-post-1.2.0, net-http-persistent-2.7, net-ldap-0.3.1, > net-scp-1.1.0, net-ssh-2.6.7, netrc-0.7.7, nokogiri-1.5.11, oauth-0.4.7, > open4-1.3.0, po_to_json-0.0.7, polyglot-0.3.3, rabl-0.9.0, rack-1.4.1, > rack-cache-1.2, rack-protection-1.2.0, rack-ssl-1.3.2, rack-test-0.6.1, > rails-3.2.8, railties-3.2.8, rake-0.9.2.2, rbovirt-0.0.29, rbvmomi-1.6.0, > rdoc-3.9.5, ref-1.0.0, rest-client-1.6.7, robotex-1.0.0, ruby-libvirt-0.5.1, > ruby2ruby-2.0.1, ruby_parser-3.1.1, runcible-1.1.0, safemode-1.2.1, > sass-3.2.13, sass-rails-3.2.5, scoped_search-2.7.1, sequel-3.45.0, > sexp_processor-4.1.3, signet-0.4.5, sinatra-1.3.2, sprockets-2.10.1, > sprockets-rails-2.0.1, sshkey-1.6.0, strong_parameters-0.2.1, syntax-1.0.0, > therubyracer-0.11.0beta5, thor-0.18.1, tilt-1.3.3, tire-0.6.2, > treetop-1.4.10, trollop-2.0, tzinfo-0.3.33, ui_alchemy-rails-1.0.12, > unf-0.1.3, unf_ext-0.0.6, uuidtools-2.1.3, > validates_lengths_from_database-0.2.0, will_paginate-3.0.2]) > > > I'm going to try installing this gem and run again. I'll post any > successes... > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-users+unsubscribe@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout.

Eric,

Well, I've rebuilt twice (an @base install) and tried this again…still no
luck. I was able to get past the db:seed by running it from the command
line. Now it is stuck at foreman-tasks start… I turn the machine off
(because resources are so used up at this point (I've upped it to 8 cores
and it still is slow to respond after this stage of installation). There's
several foreman processes running at between 60-90+ percent of cpu
(according to top). After rebooting the machine, foreman-tasks starts
automatically. After they start, I try to rerun the katello-installer
command but it just hangs. No output at all…No useful logs…

Thanks for the help.

Would you be able to send to either me or eric a foreman-debug?

I think that might enlighten the situation a bit.

-Justin

··· On 10/16/2014 04:09 PM, Garrett DeMarco wrote: > Eric, > > Well, I've rebuilt twice (an @base install) and tried this > again...still no luck. I was able to get past the db:seed by running > it from the command line. Now it is stuck at foreman-tasks start... I > turn the machine off (because resources are so used up at this point > (I've upped it to 8 cores and it still is slow to respond after this > stage of installation). There's several foreman processes running at > between 60-90+ percent of cpu (according to top). After rebooting the > machine, foreman-tasks starts automatically. After they start, I try > to rerun the katello-installer command but it just hangs. No output > at all...No useful logs... > > Thanks for the help. > -- > You received this message because you are subscribed to the Google > Groups "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to foreman-users+unsubscribe@googlegroups.com > . > To post to this group, send email to foreman-users@googlegroups.com > . > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout.

By way of update…this issue seems to be related to the VM config file,
NOT to the OS.

··· On Thursday, October 16, 2014 4:17:14 PM UTC-4, jsherril wrote: > > On 10/16/2014 04:09 PM, Garrett DeMarco wrote: > > Eric, > > Well, I've rebuilt twice (an @base install) and tried this again...still > no luck. I was able to get past the db:seed by running it from the command > line. Now it is stuck at foreman-tasks start... I turn the machine off > (because resources are so used up at this point (I've upped it to 8 cores > and it still is slow to respond after this stage of installation). There's > several foreman processes running at between 60-90+ percent of cpu > (according to top). After rebooting the machine, foreman-tasks starts > automatically. After they start, I try to rerun the katello-installer > command but it just hangs. No output at all...No useful logs... > > Thanks for the help. > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-user...@googlegroups.com . > To post to this group, send email to forema...@googlegroups.com > . > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > > Would you be able to send to either me or eric a foreman-debug? > > I think that might enlighten the situation a bit. > > -Justin >