I've just done several katello installs from scratch, but am getting stuck
at the same point.
Kickstart contains:
install of CentOS 7.1.1503
yum -y update
installation of Katello repos as per documentation
yum -y install katello
Once booted I SSH onto the new system and run katello-installer without
any options. I'm getting:
[root@foreman ~]# katello-installer
Command exceeded timeout
/Stage[main]/Candlepin::Service/Exec[cpinit]/returns: change from notrun
to 0 failed: Command exceeded timeout
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]:
Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1 instead
of one of [0]
/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]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.rhel7.local]:
Failed to call refresh: Proxy foreman.rhel7.local cannot be registered
(Could not load data from https://foreman.rhel7.local
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.rhel7.local]:
Proxy foreman.rhel7.local cannot be registered (Could not load data from
https://foreman.rhel7.local
Installing Done
[100%]
[…]
Something went wrong! Check the log for ERROR-level output
The full log is at /var/log/katello-installer/katello-installer.log
[root@foreman ~]#
The full katello-installer.log is at - http://pastebin.com/g5E76Uih
Am I too early to be trying RC2?
Duncan
> I've just done several katello installs from scratch, but am getting stuck
> at the same point.
>
> Kickstart contains:
> install of CentOS 7.1.1503
> yum -y update
> installation of Katello repos as per documentation
> yum -y install katello
>
> Once booted I SSH onto the new system and run katello-installer without
> any options. I'm getting:
Can you supply a foreman-debug tarball? You can do foreman-debug -u to
uplaod it, and reply with the filename.
···
On Wed, Aug 12, 2015 at 08:47:29AM -0700, Duncan Innes wrote:
[root@foreman ~]# katello-installer
Command exceeded timeout
/Stage[main]/Candlepin::Service/Exec[cpinit]/returns: change from notrun
to 0 failed: Command exceeded timeout
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]:
Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1 instead
of one of [0]
/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]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.rhel7.local]:
Failed to call refresh: Proxy foreman.rhel7.local cannot be registered
(Could not load data from https://foreman.rhel7.local
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.rhel7.local]:
Proxy foreman.rhel7.local cannot be registered (Could not load data from
https://foreman.rhel7.local
Installing Done
[100%]
[…]
Something went wrong! Check the log for ERROR-level output
The full log is at /var/log/katello-installer/katello-installer.log
[root@foreman ~]#
The full katello-installer.log is at - http://pastebin.com/g5E76Uih
Am I too early to be trying RC2?
Duncan
–
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.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
>
> > I've just done several katello installs from scratch, but am getting
> stuck
> > at the same point.
> >
> > Kickstart contains:
> > install of CentOS 7.1.1503
> > yum -y update
> > installation of Katello repos as per documentation
> > yum -y install katello
> >
> > Once booted I SSH onto the new system and run katello-installer
> without
> > any options. I'm getting:
>
> Can you supply a foreman-debug tarball? You can do foreman-debug -u to
> uplaod it, and reply with the filename.
>
http://debugs.theforeman.org/foreman-debug-WaBjx.tar.xz
···
On Wednesday, 12 August 2015 17:06:29 UTC+1, stephen wrote:
> On Wed, Aug 12, 2015 at 08:47:29AM -0700, Duncan Innes wrote:
[root@foreman ~]# katello-installer
Command exceeded timeout
/Stage[main]/Candlepin::Service/Exec[cpinit]/returns: change from
notrun
to 0 failed: Command exceeded timeout
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]:
Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1
instead
of one of [0]
/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]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.rhel7.local]:
Failed to call refresh: Proxy foreman.rhel7.local cannot be registered
(Could not load data from https://foreman.rhel7.local
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.rhel7.local]:
Proxy foreman.rhel7.local cannot be registered (Could not load data from
https://foreman.rhel7.local
Installing Done
[100%]
[…]
Something went wrong! Check the log for ERROR-level output
The full log is at /var/log/katello-installer/katello-installer.log
[root@foreman ~]#
The full katello-installer.log is at - http://pastebin.com/g5E76Uih
Am I too early to be trying RC2?
Duncan
–
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 <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
>
>
> >
> > > I've just done several katello installs from scratch, but am getting
> > stuck
> > > at the same point.
> > >
> > > Kickstart contains:
> > > install of CentOS 7.1.1503
> > > yum -y update
> > > installation of Katello repos as per documentation
> > > yum -y install katello
> > >
> > > Once booted I SSH onto the new system and run katello-installer
> > without
> > > any options. I'm getting:
> >
> > Can you supply a foreman-debug tarball? You can do foreman-debug -u to
> > uplaod it, and reply with the filename.
> >
>
> http://debugs.theforeman.org/foreman-debug-WaBjx.tar.xz
Hi,
I'd bet your Katello VM is not running with hardware acceleration, which
is usually the reason we'd see so many timeouts. I don't think you can
tell from the guest itself if it's QEMU emulation or KVM, other than
performance issues, so I can't tell based on the foreman-debug.
But maybe have a look @ the steps here and check from the hypervisor:
https://fedoraproject.org/wiki/How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F
···
On Wed, Aug 12, 2015 at 10:17:24AM -0700, Duncan Innes wrote:
> On Wednesday, 12 August 2015 17:06:29 UTC+1, stephen wrote:
> > On Wed, Aug 12, 2015 at 08:47:29AM -0700, Duncan Innes wrote:
[root@foreman ~]# katello-installer
Command exceeded timeout
/Stage[main]/Candlepin::Service/Exec[cpinit]/returns: change from
notrun
to 0 failed: Command exceeded timeout
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]:
Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1
instead
of one of [0]
/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]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.rhel7.local]:
Failed to call refresh: Proxy foreman.rhel7.local cannot be registered
(Could not load data from https://foreman.rhel7.local
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.rhel7.local]:
Proxy foreman.rhel7.local cannot be registered (Could not load data from
https://foreman.rhel7.local
Installing Done
[100%]
[…]
Something went wrong! Check the log for ERROR-level output
The full log is at /var/log/katello-installer/katello-installer.log
[root@foreman ~]#
The full katello-installer.log is at - http://pastebin.com/g5E76Uih
Am I too early to be trying RC2?
Duncan
–
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 <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
–
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.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
>
> >
> >
> > >
> > > > I've just done several katello installs from scratch, but am getting
> > > stuck
> > > > at the same point.
> > > >
> > > > Kickstart contains:
> > > > install of CentOS 7.1.1503
> > > > yum -y update
> > > > installation of Katello repos as per documentation
> > > > yum -y install katello
> > > >
> > > > Once booted I SSH onto the new system and run katello-installer
> > > without
> > > > any options. I'm getting:
> > >
> > > Can you supply a foreman-debug tarball? You can do foreman-debug -u to
> > > uplaod it, and reply with the filename.
> > >
> >
> > http://debugs.theforeman.org/foreman-debug-WaBjx.tar.xz
>
> Hi,
>
> I'd bet your Katello VM is not running with hardware acceleration, which
> is usually the reason we'd see so many timeouts. I don't think you can
> tell from the guest itself if it's QEMU emulation or KVM, other than
> performance issues, so I can't tell based on the foreman-debug.
>
> But maybe have a look @ the steps here and check from the hypervisor:
>
> https://fedoraproject.org/wiki/How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F
>
>
Hmm - odd, but I'll investigate properly tomorrow morning.
For now though, this is an Intel Core i7 laptop with 16Gb RAM. The guest
is running on KVM which shows as having hardware virtualization. There's
8Gb RAM given to the guest.
Everything on the host OS side seems to show KVM running with hardware
accel. I'll check thoroughly in the morning though.
This is the same laptop, hypervisor, guest etc. that I've used for testing
Foreman/Katello/Satellite 6.0 for quite a while now.
D
···
On Wednesday, 12 August 2015 19:12:47 UTC+1, stephen wrote:
> On Wed, Aug 12, 2015 at 10:17:24AM -0700, Duncan Innes wrote:
> > On Wednesday, 12 August 2015 17:06:29 UTC+1, stephen wrote:
> > > On Wed, Aug 12, 2015 at 08:47:29AM -0700, Duncan Innes wrote:
[root@foreman ~]# katello-installer
Command exceeded timeout
/Stage[main]/Candlepin::Service/Exec[cpinit]/returns: change from
notrun
to 0 failed: Command exceeded timeout
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]:
Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1
instead
of one of [0]
/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]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.rhel7.local]:
Failed to call refresh: Proxy foreman.rhel7.local cannot be
registered
(Could not load data from https://foreman.rhel7.local
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.rhel7.local]:
Proxy foreman.rhel7.local cannot be registered (Could not load data
from
https://foreman.rhel7.local
Installing Done
[100%]
[…]
Something went wrong! Check the log for ERROR-level output
The full log is at
/var/log/katello-installer/katello-installer.log
[root@foreman ~]#
The full katello-installer.log is at - http://pastebin.com/g5E76Uih
Am I too early to be trying RC2?
Duncan
–
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 <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
–
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 <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
>
>
> >
> > >
> > >
> > > >
> > > > > I've just done several katello installs from scratch, but am getting
> > > > stuck
> > > > > at the same point.
> > > > >
> > > > > Kickstart contains:
> > > > > install of CentOS 7.1.1503
> > > > > yum -y update
> > > > > installation of Katello repos as per documentation
> > > > > yum -y install katello
> > > > >
> > > > > Once booted I SSH onto the new system and run katello-installer
> > > > without
> > > > > any options. I'm getting:
> > > >
> > > > Can you supply a foreman-debug tarball? You can do foreman-debug -u to
> > > > uplaod it, and reply with the filename.
> > > >
> > >
> > > http://debugs.theforeman.org/foreman-debug-WaBjx.tar.xz
> >
> > Hi,
> >
> > I'd bet your Katello VM is not running with hardware acceleration, which
> > is usually the reason we'd see so many timeouts. I don't think you can
> > tell from the guest itself if it's QEMU emulation or KVM, other than
> > performance issues, so I can't tell based on the foreman-debug.
> >
> > But maybe have a look @ the steps here and check from the hypervisor:
> >
> > https://fedoraproject.org/wiki/How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F
> >
> >
> Hmm - odd, but I'll investigate properly tomorrow morning.
>
> For now though, this is an Intel Core i7 laptop with 16Gb RAM. The guest
> is running on KVM which shows as having hardware virtualization. There's
> 8Gb RAM given to the guest.
>
> Everything on the host OS side seems to show KVM running with hardware
> accel. I'll check thoroughly in the morning though.
>
> This is the same laptop, hypervisor, guest etc. that I've used for testing
> Foreman/Katello/Satellite 6.0 for quite a while now.
>
> D
Ok, it was a long shot. I don't see anything in your logs that indicate
a particular problem, just that commands are timing out in the
installation. Would you mind doign katello-service restart, and
trying katello-installer again, and provide another debug after that?
It does look like Candlepin is in a weird state where tomcat is up but
never actually replying to any requests, but I don't know why.
···
On Wed, Aug 12, 2015 at 02:18:55PM -0700, Duncan Innes wrote:
> On Wednesday, 12 August 2015 19:12:47 UTC+1, stephen wrote:
> > On Wed, Aug 12, 2015 at 10:17:24AM -0700, Duncan Innes wrote:
> > > On Wednesday, 12 August 2015 17:06:29 UTC+1, stephen wrote:
> > > > On Wed, Aug 12, 2015 at 08:47:29AM -0700, Duncan Innes wrote:
[root@foreman ~]# katello-installer
Command exceeded timeout
/Stage[main]/Candlepin::Service/Exec[cpinit]/returns: change from
notrun
to 0 failed: Command exceeded timeout
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]:
Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1
instead
of one of [0]
/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]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.rhel7.local]:
Failed to call refresh: Proxy foreman.rhel7.local cannot be
registered
(Could not load data from https://foreman.rhel7.local
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.rhel7.local]:
Proxy foreman.rhel7.local cannot be registered (Could not load data
from
https://foreman.rhel7.local
Installing Done
[100%]
[…]
Something went wrong! Check the log for ERROR-level output
The full log is at
/var/log/katello-installer/katello-installer.log
[root@foreman ~]#
The full katello-installer.log is at - http://pastebin.com/g5E76Uih
Am I too early to be trying RC2?
Duncan
–
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 <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
–
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 <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
–
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.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
Stephen,
I've reinstalled a couple times this morning and hit the same issue each
time. My latest install, however, has managed to be coaxed into life by
running a
katello-installer --reset
following the initial failure. I can't rule out hypervisor issues as I'm
noticing odd pauses happening during the kickstart and occasional failures
to run the yum -y update and yum -y install katello commands in the
%post section. I've not narrowed these down yet, but the kickstart is
managing to install the katello repositories between these 2 yum commands.
I plan to wipe this laptop and install from scratch some point soon.
For now, I've got a running instance of Katello 2.3 RC2, so I'd like to
push on with some more functional tests. I'll update this thread once I
get a fresh host system on which to run further installation tests.
Thanks
Duncan
