Katello 2.4 install on CentOS 7.2 with selinux enabled qpidd service fails to start

Support
1

I appear to be having an issue getting katello/theforeman/puppet installed
on my CentOS 7.2 server. I recently performed a fresh/clean install of
CentOS on this server and have followed the steps on this page to setup
katello for installation.

http://www.katello.org/docs/2.4/installation/index.html

When I run the following katello-installer command I get errors.

katello-installer --capsule-bmc="true" --capsule-dhcp="true"

–capsule-dhcp-gateway="10.4.15.1" --capsule-dhcp-interface="enp4s0"
–capsule-dhcp-range="10.4.15.240 10.4.15.254"
–capsule-dns-interface="enp5s0" --foreman-selinux="true"

Could not start Service[qpidd]: Execution of
'/usr/share/katello-installer/modules/service_wait/bin/service-wait start
qpidd' returned 6: Redirecting to /bin/systemctl start qpidd.service
/Stage[main]/Qpid::Service/Service[qpidd]/ensure: change from stopped to
running failed: Could not start Service[qpidd]: Execution of
'/usr/share/katello-installer/modules/service_wait/bin/service-wait start
qpidd' returned 6: Redirecting to /bin/systemctl start qpidd.service
/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]
Installing Done
[100%] […]
Something went wrong! Check the log for ERROR-level output

systemctl status qpidd

● qpidd.service - An AMQP message broker daemon.
Loaded: loaded (/usr/lib/systemd/system/qpidd.service; disabled; vendor
preset: disabled)
Active: failed (Result: exit-code) since Fri 2016-04-29 14:22:52 MDT;
1min 59s ago
Docs: man:qpidd(1)
http://qpid.apache.org/
Process: 13929 ExecStart=/usr/sbin/qpidd --config /etc/qpid/qpidd.conf
(code=exited, status=1/FAILURE)
Main PID: 13929 (code=exited, status=1/FAILURE)

Apr 29 14:22:51 il-foreman1.slc.westdc.net systemd[1]: Started An AMQP
message broker daemon…
Apr 29 14:22:51 il-foreman1.slc.westdc.net systemd[1]: Starting An AMQP
message broker daemon…
Apr 29 14:22:52 il-foreman1.slc.westdc.net qpidd[13929]: 2016-04-29
14:22:52 [Broker] critical Unexpected error: Queue katello_event_queue:
reco…
Apr 29 14:22:52 il-foreman1.slc.westdc.net qpidd[13929]: 2016-04-29
14:22:52 [Broker] critical Unexpected error: Queue katello_event_queue:
reco…
Apr 29 14:22:52 il-foreman1.slc.westdc.net systemd[1]: qpidd.service: main
process exited, code=exited, status=1/FAILURE
Apr 29 14:22:52 il-foreman1.slc.westdc.net systemd[1]: Unit qpidd.service
entered failed state.
Apr 29 14:22:52 il-foreman1.slc.westdc.net systemd[1]: qpidd.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

How can I get past this and get Katello/TheForeman installed on my server?

2

I should of included this, the full status output.

systemctl -l status qpidd

● qpidd.service - An AMQP message broker daemon.
Loaded: loaded (/usr/lib/systemd/system/qpidd.service; disabled; vendor
preset: disabled)
Active: failed (Result: exit-code) since Fri 2016-04-29 14:28:03 MDT;
6min ago
Docs: man:qpidd(1)
http://qpid.apache.org/
Process: 13973 ExecStart=/usr/sbin/qpidd --config /etc/qpid/qpidd.conf
(code=exited, status=1/FAILURE)
Main PID: 13973 (code=exited, status=1/FAILURE)

Apr 29 14:28:03 il-foreman1.slc.westdc.net systemd[1]: Started An AMQP
message broker daemon…
Apr 29 14:28:03 il-foreman1.slc.westdc.net systemd[1]: Starting An AMQP
message broker daemon…
Apr 29 14:28:03 il-foreman1.slc.westdc.net qpidd[13973]: 2016-04-29
14:28:03 [Broker] critical Unexpected error: Queue katello_event_queue:
recoverQueues() failed: jexception 0x0308 jdir::is_dir() threw
JERR_JDIR_STAT: File stat failed.
(file="/var/lib/qpidd/.qpidd/qls/jrnl/katello_event_queue" errno=2 (No such
file or directory))
(/builddir/build/BUILD/qpid-cpp-0.30/src/qpid/linearstore/MessageStoreImpl.cpp:771)
Apr 29 14:28:03 il-foreman1.slc.westdc.net qpidd[13973]: 2016-04-29
14:28:03 [Broker] critical Unexpected error: Queue katello_event_queue:
recoverQueues() failed: jexception 0x0308 jdir::is_dir() threw
JERR_JDIR_STAT: File stat failed.
(file="/var/lib/qpidd/.qpidd/qls/jrnl/katello_event_queue" errno=2 (No such
file or directory))
(/builddir/build/BUILD/qpid-cpp-0.30/src/qpid/linearstore/MessageStoreImpl.cpp:771)
Apr 29 14:28:03 il-foreman1.slc.westdc.net systemd[1]: qpidd.service: main
process exited, code=exited, status=1/FAILURE
Apr 29 14:28:03 il-foreman1.slc.westdc.net systemd[1]: Unit qpidd.service
entered failed state.
Apr 29 14:28:03 il-foreman1.slc.westdc.net systemd[1]: qpidd.service failed.

ll /var/lib/qpidd/.qpidd/qls/jrnl/

total 0
drwxr-xr-x. 2 qpidd qpidd 54 Apr 29 11:30 celery
drwxr-xr-x. 2 qpidd qpidd 54 Apr 29 11:39 pulp.task
drwxr-xr-x. 2 qpidd qpidd 54 Apr 29 11:30 resource_manager

This path doesn't exist.

··· On Friday, 29 April 2016 14:33:01 UTC-6, Edward Clay wrote: > > I appear to be having an issue getting katello/theforeman/puppet installed > on my CentOS 7.2 server. I recently performed a fresh/clean install of > CentOS on this server and have followed the steps on this page to setup > katello for installation. > > http://www.katello.org/docs/2.4/installation/index.html > > When I run the following katello-installer command I get errors. > > # katello-installer --capsule-bmc="true" --capsule-dhcp="true" > --capsule-dhcp-gateway="10.4.15.1" --capsule-dhcp-interface="enp4s0" > --capsule-dhcp-range="10.4.15.240 10.4.15.254" > --capsule-dns-interface="enp5s0" --foreman-selinux="true" > > Could not start Service[qpidd]: Execution of > '/usr/share/katello-installer/modules/service_wait/bin/service-wait start > qpidd' returned 6: Redirecting to /bin/systemctl start qpidd.service > /Stage[main]/Qpid::Service/Service[qpidd]/ensure: change from stopped to > running failed: Could not start Service[qpidd]: Execution of > '/usr/share/katello-installer/modules/service_wait/bin/service-wait start > qpidd' returned 6: Redirecting to /bin/systemctl start qpidd.service > /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] > Installing Done > [100%] [...............................................................] > Something went wrong! Check the log for ERROR-level output > > # systemctl status qpidd > ● qpidd.service - An AMQP message broker daemon. > Loaded: loaded (/usr/lib/systemd/system/qpidd.service; disabled; vendor > preset: disabled) > Active: failed (Result: exit-code) since Fri 2016-04-29 14:22:52 MDT; > 1min 59s ago > Docs: man:qpidd(1) > http://qpid.apache.org/ > Process: 13929 ExecStart=/usr/sbin/qpidd --config /etc/qpid/qpidd.conf > (code=exited, status=1/FAILURE) > Main PID: 13929 (code=exited, status=1/FAILURE) > > Apr 29 14:22:51 il-foreman1.slc.westdc.net systemd[1]: Started An AMQP > message broker daemon.. > Apr 29 14:22:51 il-foreman1.slc.westdc.net systemd[1]: Starting An AMQP > message broker daemon.... > Apr 29 14:22:52 il-foreman1.slc.westdc.net qpidd[13929]: 2016-04-29 > 14:22:52 [Broker] critical Unexpected error: Queue katello_event_queue: > reco... > Apr 29 14:22:52 il-foreman1.slc.westdc.net qpidd[13929]: 2016-04-29 > 14:22:52 [Broker] critical Unexpected error: Queue katello_event_queue: > reco... > Apr 29 14:22:52 il-foreman1.slc.westdc.net systemd[1]: qpidd.service: > main process exited, code=exited, status=1/FAILURE > Apr 29 14:22:52 il-foreman1.slc.westdc.net systemd[1]: Unit qpidd.service > entered failed state. > Apr 29 14:22:52 il-foreman1.slc.westdc.net systemd[1]: qpidd.service > failed. > Hint: Some lines were ellipsized, use -l to show in full. > > > How can I get past this and get Katello/TheForeman installed on my server? >
3

And before posting the last comment I should of tried to start
qpidd.service. It's now running after doing the following.

mkdir /var/lib/qpidd/.qpidd/qls/jrnl/katello_event_queue
chown -R qpidd. /var/log/katello-installer/katello-installer.log
restorecon -R /var/log/katello-installer/katello-installer.log

systemctl start qpidd.service

systemctl -l status qpidd.service

● qpidd.service - An AMQP message broker daemon.
Loaded: loaded (/usr/lib/systemd/system/qpidd.service; disabled; vendor
preset: disabled)
Active: active (running) since Fri 2016-04-29 14:37:13 MDT; 9s ago
Docs: man:qpidd(1)
http://qpid.apache.org/
Main PID: 14142 (qpidd)
CGroup: /system.slice/qpidd.service
└─14142 /usr/sbin/qpidd --config /etc/qpid/qpidd.conf

Apr 29 14:37:13 il-foreman1.slc.westdc.net systemd[1]: Started An AMQP
message broker daemon…
Apr 29 14:37:13 il-foreman1.slc.westdc.net systemd[1]: Starting An AMQP
message broker daemon…

Now when I re-run the katello-installer I end up with these errors.

Could not start Service[httpd]: Execution of
'/usr/share/katello-installer/modules/service_wait/bin/service-wait start
httpd' returned 1: Redirecting to /bin/systemctl start httpd.service
/Stage[main]/Apache::Service/Service[httpd]/ensure: change from stopped to
running failed: Could not start Service[httpd]: Execution of
'/usr/share/katello-installer/modules/service_wait/bin/service-wait start
httpd' returned 1: Redirecting to /bin/systemctl start httpd.service

Which appears to be related to httpd trying to bind to port 5000. When I
check for apache ports allowed via selinux I get the following.

semanage port -l | grep 5000

commplex_main_port_t tcp 5000
commplex_main_port_t udp 5000

When I attempt to enable this port for apache I get the following error.

semanage port -a -t http_port_t -p tcp 5000

ValueError: Port tcp/5000 already defined

How do I make this work?

··· On Friday, 29 April 2016 14:36:19 UTC-6, Edward Clay wrote: > > I should of included this, the full status output. > > # systemctl -l status qpidd > ● qpidd.service - An AMQP message broker daemon. > Loaded: loaded (/usr/lib/systemd/system/qpidd.service; disabled; vendor > preset: disabled) > Active: failed (Result: exit-code) since Fri 2016-04-29 14:28:03 MDT; > 6min ago > Docs: man:qpidd(1) > http://qpid.apache.org/ > Process: 13973 ExecStart=/usr/sbin/qpidd --config /etc/qpid/qpidd.conf > (code=exited, status=1/FAILURE) > Main PID: 13973 (code=exited, status=1/FAILURE) > > Apr 29 14:28:03 il-foreman1.slc.westdc.net systemd[1]: Started An AMQP > message broker daemon.. > Apr 29 14:28:03 il-foreman1.slc.westdc.net systemd[1]: Starting An AMQP > message broker daemon.... > Apr 29 14:28:03 il-foreman1.slc.westdc.net qpidd[13973]: 2016-04-29 > 14:28:03 [Broker] critical Unexpected error: Queue katello_event_queue: > recoverQueues() failed: jexception 0x0308 jdir::is_dir() threw > JERR_JDIR_STAT: File stat failed. > (file="/var/lib/qpidd/.qpidd/qls/jrnl/katello_event_queue" errno=2 (No such > file or directory)) > (/builddir/build/BUILD/qpid-cpp-0.30/src/qpid/linearstore/MessageStoreImpl.cpp:771) > Apr 29 14:28:03 il-foreman1.slc.westdc.net qpidd[13973]: 2016-04-29 > 14:28:03 [Broker] critical Unexpected error: Queue katello_event_queue: > recoverQueues() failed: jexception 0x0308 jdir::is_dir() threw > JERR_JDIR_STAT: File stat failed. > (file="/var/lib/qpidd/.qpidd/qls/jrnl/katello_event_queue" errno=2 (No such > file or directory)) > (/builddir/build/BUILD/qpid-cpp-0.30/src/qpid/linearstore/MessageStoreImpl.cpp:771) > Apr 29 14:28:03 il-foreman1.slc.westdc.net systemd[1]: qpidd.service: > main process exited, code=exited, status=1/FAILURE > Apr 29 14:28:03 il-foreman1.slc.westdc.net systemd[1]: Unit qpidd.service > entered failed state. > Apr 29 14:28:03 il-foreman1.slc.westdc.net systemd[1]: qpidd.service > failed. > > > # ll /var/lib/qpidd/.qpidd/qls/jrnl/ > total 0 > drwxr-xr-x. 2 qpidd qpidd 54 Apr 29 11:30 celery > drwxr-xr-x. 2 qpidd qpidd 54 Apr 29 11:39 pulp.task > drwxr-xr-x. 2 qpidd qpidd 54 Apr 29 11:30 resource_manager > > This path doesn't exist. > > On Friday, 29 April 2016 14:33:01 UTC-6, Edward Clay wrote: >> >> I appear to be having an issue getting katello/theforeman/puppet >> installed on my CentOS 7.2 server. I recently performed a fresh/clean >> install of CentOS on this server and have followed the steps on this page >> to setup katello for installation. >> >> http://www.katello.org/docs/2.4/installation/index.html >> >> When I run the following katello-installer command I get errors. >> >> # katello-installer --capsule-bmc="true" --capsule-dhcp="true" >> --capsule-dhcp-gateway="10.4.15.1" --capsule-dhcp-interface="enp4s0" >> --capsule-dhcp-range="10.4.15.240 10.4.15.254" >> --capsule-dns-interface="enp5s0" --foreman-selinux="true" >> >> Could not start Service[qpidd]: Execution of >> '/usr/share/katello-installer/modules/service_wait/bin/service-wait start >> qpidd' returned 6: Redirecting to /bin/systemctl start qpidd.service >> /Stage[main]/Qpid::Service/Service[qpidd]/ensure: change from stopped to >> running failed: Could not start Service[qpidd]: Execution of >> '/usr/share/katello-installer/modules/service_wait/bin/service-wait start >> qpidd' returned 6: Redirecting to /bin/systemctl start qpidd.service >> /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] >> Installing Done >> [100%] [...............................................................] >> Something went wrong! Check the log for ERROR-level output >> >> # systemctl status qpidd >> ● qpidd.service - An AMQP message broker daemon. >> Loaded: loaded (/usr/lib/systemd/system/qpidd.service; disabled; >> vendor preset: disabled) >> Active: failed (Result: exit-code) since Fri 2016-04-29 14:22:52 MDT; >> 1min 59s ago >> Docs: man:qpidd(1) >> http://qpid.apache.org/ >> Process: 13929 ExecStart=/usr/sbin/qpidd --config /etc/qpid/qpidd.conf >> (code=exited, status=1/FAILURE) >> Main PID: 13929 (code=exited, status=1/FAILURE) >> >> Apr 29 14:22:51 il-foreman1.slc.westdc.net systemd[1]: Started An AMQP >> message broker daemon.. >> Apr 29 14:22:51 il-foreman1.slc.westdc.net systemd[1]: Starting An AMQP >> message broker daemon.... >> Apr 29 14:22:52 il-foreman1.slc.westdc.net qpidd[13929]: 2016-04-29 >> 14:22:52 [Broker] critical Unexpected error: Queue katello_event_queue: >> reco... >> Apr 29 14:22:52 il-foreman1.slc.westdc.net qpidd[13929]: 2016-04-29 >> 14:22:52 [Broker] critical Unexpected error: Queue katello_event_queue: >> reco... >> Apr 29 14:22:52 il-foreman1.slc.westdc.net systemd[1]: qpidd.service: >> main process exited, code=exited, status=1/FAILURE >> Apr 29 14:22:52 il-foreman1.slc.westdc.net systemd[1]: Unit >> qpidd.service entered failed state. >> Apr 29 14:22:52 il-foreman1.slc.westdc.net systemd[1]: qpidd.service >> failed. >> Hint: Some lines were ellipsized, use -l to show in full. >> >> >> How can I get past this and get Katello/TheForeman installed on my server? >> >
4

I have seen a similar looking issue before where the system needed to have
up to date packages. Given the error output, we may need to post this to
the qpidd maintainers to give us some insight into what might have failed
or be missing.

Was your installation on latest Centos 7.2 fully up to date? Anything
customized to the system prior to installation?

··· On Fri, Apr 29, 2016 at 4:44 PM, Edward Clay wrote:

And before posting the last comment I should of tried to start
qpidd.service. It’s now running after doing the following.

mkdir /var/lib/qpidd/.qpidd/qls/jrnl/katello_event_queue
chown -R qpidd. /var/log/katello-installer/katello-installer.log
restorecon -R /var/log/katello-installer/katello-installer.log

systemctl start qpidd.service

systemctl -l status qpidd.service

● qpidd.service - An AMQP message broker daemon.
Loaded: loaded (/usr/lib/systemd/system/qpidd.service; disabled; vendor
preset: disabled)
Active: active (running) since Fri 2016-04-29 14:37:13 MDT; 9s ago
Docs: man:qpidd(1)
http://qpid.apache.org/
Main PID: 14142 (qpidd)
CGroup: /system.slice/qpidd.service
└─14142 /usr/sbin/qpidd --config /etc/qpid/qpidd.conf

Apr 29 14:37:13 il-foreman1.slc.westdc.net systemd[1]: Started An AMQP
message broker daemon…
Apr 29 14:37:13 il-foreman1.slc.westdc.net systemd[1]: Starting An AMQP
message broker daemon…

Now when I re-run the katello-installer I end up with these errors.

Could not start Service[httpd]: Execution of
’/usr/share/katello-installer/modules/service_wait/bin/service-wait start
httpd’ returned 1: Redirecting to /bin/systemctl start httpd.service
/Stage[main]/Apache::Service/Service[httpd]/ensure: change from stopped
to running failed: Could not start Service[httpd]: Execution of
’/usr/share/katello-installer/modules/service_wait/bin/service-wait start
httpd’ returned 1: Redirecting to /bin/systemctl start httpd.service

Which appears to be related to httpd trying to bind to port 5000. When I
check for apache ports allowed via selinux I get the following.

semanage port -l | grep 5000

commplex_main_port_t tcp 5000
commplex_main_port_t udp 5000

When I attempt to enable this port for apache I get the following error.

semanage port -a -t http_port_t -p tcp 5000

ValueError: Port tcp/5000 already defined

How do I make this work?

On Friday, 29 April 2016 14:36:19 UTC-6, Edward Clay wrote:

I should of included this, the full status output.

systemctl -l status qpidd

● qpidd.service - An AMQP message broker daemon.
Loaded: loaded (/usr/lib/systemd/system/qpidd.service; disabled;
vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2016-04-29 14:28:03 MDT;
6min ago
Docs: man:qpidd(1)
http://qpid.apache.org/
Process: 13973 ExecStart=/usr/sbin/qpidd --config /etc/qpid/qpidd.conf
(code=exited, status=1/FAILURE)
Main PID: 13973 (code=exited, status=1/FAILURE)

Apr 29 14:28:03 il-foreman1.slc.westdc.net systemd[1]: Started An AMQP
message broker daemon…
Apr 29 14:28:03 il-foreman1.slc.westdc.net systemd[1]: Starting An AMQP
message broker daemon…
Apr 29 14:28:03 il-foreman1.slc.westdc.net qpidd[13973]: 2016-04-29
14:28:03 [Broker] critical Unexpected error: Queue katello_event_queue:
recoverQueues() failed: jexception 0x0308 jdir::is_dir() threw
JERR_JDIR_STAT: File stat failed.
(file="/var/lib/qpidd/.qpidd/qls/jrnl/katello_event_queue" errno=2 (No such
file or directory))
(/builddir/build/BUILD/qpid-cpp-0.30/src/qpid/linearstore/MessageStoreImpl.cpp:771)
Apr 29 14:28:03 il-foreman1.slc.westdc.net qpidd[13973]: 2016-04-29
14:28:03 [Broker] critical Unexpected error: Queue katello_event_queue:
recoverQueues() failed: jexception 0x0308 jdir::is_dir() threw
JERR_JDIR_STAT: File stat failed.
(file="/var/lib/qpidd/.qpidd/qls/jrnl/katello_event_queue" errno=2 (No such
file or directory))
(/builddir/build/BUILD/qpid-cpp-0.30/src/qpid/linearstore/MessageStoreImpl.cpp:771)
Apr 29 14:28:03 il-foreman1.slc.westdc.net systemd[1]: qpidd.service:
main process exited, code=exited, status=1/FAILURE
Apr 29 14:28:03 il-foreman1.slc.westdc.net systemd[1]: Unit
qpidd.service entered failed state.
Apr 29 14:28:03 il-foreman1.slc.westdc.net systemd[1]: qpidd.service
failed.

ll /var/lib/qpidd/.qpidd/qls/jrnl/

total 0
drwxr-xr-x. 2 qpidd qpidd 54 Apr 29 11:30 celery
drwxr-xr-x. 2 qpidd qpidd 54 Apr 29 11:39 pulp.task
drwxr-xr-x. 2 qpidd qpidd 54 Apr 29 11:30 resource_manager

This path doesn’t exist.

On Friday, 29 April 2016 14:33:01 UTC-6, Edward Clay wrote:

I appear to be having an issue getting katello/theforeman/puppet
installed on my CentOS 7.2 server. I recently performed a fresh/clean
install of CentOS on this server and have followed the steps on this page
to setup katello for installation.

http://www.katello.org/docs/2.4/installation/index.html

When I run the following katello-installer command I get errors.

katello-installer --capsule-bmc=“true” --capsule-dhcp=“true”

–capsule-dhcp-gateway=“10.4.15.1” --capsule-dhcp-interface=“enp4s0”
–capsule-dhcp-range=“10.4.15.240 10.4.15.254”
–capsule-dns-interface=“enp5s0” --foreman-selinux=“true”

Could not start Service[qpidd]: Execution of
’/usr/share/katello-installer/modules/service_wait/bin/service-wait start
qpidd’ returned 6: Redirecting to /bin/systemctl start qpidd.service
/Stage[main]/Qpid::Service/Service[qpidd]/ensure: change from stopped
to running failed: Could not start Service[qpidd]: Execution of
’/usr/share/katello-installer/modules/service_wait/bin/service-wait start
qpidd’ returned 6: Redirecting to /bin/systemctl start qpidd.service
/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]
Installing
Done [100%]
[…]
Something went wrong! Check the log for ERROR-level output

systemctl status qpidd

● qpidd.service - An AMQP message broker daemon.
Loaded: loaded (/usr/lib/systemd/system/qpidd.service; disabled;
vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2016-04-29 14:22:52 MDT;
1min 59s ago
Docs: man:qpidd(1)
http://qpid.apache.org/
Process: 13929 ExecStart=/usr/sbin/qpidd --config /etc/qpid/qpidd.conf
(code=exited, status=1/FAILURE)
Main PID: 13929 (code=exited, status=1/FAILURE)

Apr 29 14:22:51 il-foreman1.slc.westdc.net systemd[1]: Started An AMQP
message broker daemon…
Apr 29 14:22:51 il-foreman1.slc.westdc.net systemd[1]: Starting An AMQP
message broker daemon…
Apr 29 14:22:52 il-foreman1.slc.westdc.net qpidd[13929]: 2016-04-29
14:22:52 [Broker] critical Unexpected error: Queue katello_event_queue:
reco…
Apr 29 14:22:52 il-foreman1.slc.westdc.net qpidd[13929]: 2016-04-29
14:22:52 [Broker] critical Unexpected error: Queue katello_event_queue:
reco…
Apr 29 14:22:52 il-foreman1.slc.westdc.net systemd[1]: qpidd.service:
main process exited, code=exited, status=1/FAILURE
Apr 29 14:22:52 il-foreman1.slc.westdc.net systemd[1]: Unit
qpidd.service entered failed state.
Apr 29 14:22:52 il-foreman1.slc.westdc.net systemd[1]: qpidd.service
failed.
Hint: Some lines were ellipsized, use -l to show in full.

How can I get past this and get Katello/TheForeman installed on my
server?

–
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 https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University