Katello 2.2. install on clean RHEL 6.6 machine error

qpid-config --ssl-certificate /etc/pki/katello/certs/java-client.crt
–ssl-key /etc/pki/katello/private/java-client.key -b
'amqps://llin417.xhl.test.net:5671' add exchange topic event --durable
returned 1 instead of one of [0]
/Stage[main]/Certs::Candlepin/Exec[create candlepin qpid
exchange]/returns: change from notrun to 0 failed: qpid-config
–ssl-certificate /etc/pki/katello/certs/java-client.crt --ssl-key
/etc/pki/katello/private/java-client.key -b
'amqps://llin417.xhl.test.net:5671' add exchange topic event --durable
returned 1 instead of one of [0]
/Stage[main]/Certs::Candlepin/Exec[create candlepin qpid exchange]: Failed
to call refresh: qpid-config --ssl-certificate
/etc/pki/katello/certs/java-client.crt --ssl-key
/etc/pki/katello/private/java-client.key -b
'amqps://llin417.xhl.test.net:5671' add exchange topic event --durable
returned 1 instead of one of [0]
/Stage[main]/Certs::Candlepin/Exec[create candlepin qpid exchange]:
qpid-config --ssl-certificate /etc/pki/katello/certs/java-client.crt
–ssl-key /etc/pki/katello/private/java-client.key -b
'amqps://llin417.xhl.test.net:5671' add exchange topic event --durable
returned 1 instead of one of [0]

Peter - I had a plethora of confusing errors installing on CentOS6, but all
were resolved when I disabled selinux, made sure root's umask was suitable
(e.g. 0022), configured NTP and confirmed hostname -f was resolvable.
These may have no relevance to you, but you might want to double
check…(I also disabled iptables/ip6tables for the install).

··· On Thursday, 19 March 2015 06:27:01 UTC, Peter Santiago wrote: > > qpid-config --ssl-certificate /etc/pki/katello/certs/java-client.crt > --ssl-key /etc/pki/katello/private/java-client.key -b 'amqps:// > llin417.xhl.test.net:5671' add exchange topic event --durable returned 1 > instead of one of [0] > /Stage[main]/Certs::Candlepin/Exec[create candlepin qpid > exchange]/returns: change from notrun to 0 failed: qpid-config > --ssl-certificate /etc/pki/katello/certs/java-client.crt --ssl-key > /etc/pki/katello/private/java-client.key -b 'amqps:// > llin417.xhl.test.net:5671' add exchange topic event --durable returned 1 > instead of one of [0] > /Stage[main]/Certs::Candlepin/Exec[create candlepin qpid exchange]: > Failed to call refresh: qpid-config --ssl-certificate > /etc/pki/katello/certs/java-client.crt --ssl-key > /etc/pki/katello/private/java-client.key -b 'amqps:// > llin417.xhl.test.net:5671' add exchange topic event --durable returned 1 > instead of one of [0] > /Stage[main]/Certs::Candlepin/Exec[create candlepin qpid exchange]: > qpid-config --ssl-certificate /etc/pki/katello/certs/java-client.crt > --ssl-key /etc/pki/katello/private/java-client.key -b 'amqps:// > llin417.xhl.test.net:5671' add exchange topic event --durable returned 1 > instead of one of [0] > >

still no go…

Installed fine this time… but production log… <sigh>

2015-03-20 05:33:02 [W] Connection refused -
"/usr/share/foreman/tmp/sockets/dynflow_socket" (Errno::ECONNREFUSED)
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/executors/remote_via_socket/core.rb:142:in
initialize&#39; /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/executors/remote_via_socket/core.rb:142:innew'
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/executors/remote_via_socket/core.rb:142:in
connect&#39; /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/executors/remote_via_socket/core.rb:91:inblock in on_message'
/opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:859:in
block in assigns&#39; /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:intap'
/opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in
assigns&#39; /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:138:inmatch_value'
/opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:116:in
block in match&#39; /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:ineach'
/opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in
match&#39; /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/executors/remote_via_socket/core.rb:79:inon_message'
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:80:in
block in on_envelope&#39; /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/future.rb:75:incall'
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/future.rb:75:in
evaluate_to&#39; /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:80:inon_envelope'
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:72:in
receive&#39; /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:99:inblock (2 levels) in run'
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:99:in
loop&#39; /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:99:inblock in run'
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:99:in
catch&#39; /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:99:inrun'
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:13:in
block in initialize&#39; /opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:incall'
/opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in
`block in create_with_logging_context'

··· On Thursday, March 19, 2015 at 6:19:16 PM UTC+8, JC wrote: > > Peter - I had a plethora of confusing errors installing on CentOS6, but > all were resolved when I disabled selinux, made sure root's umask was > suitable (e.g. 0022), configured NTP and confirmed hostname -f was > resolvable. These may have no relevance to you, but you might want to > double check...(I also disabled iptables/ip6tables for the install). > > On Thursday, 19 March 2015 06:27:01 UTC, Peter Santiago wrote: >> >> qpid-config --ssl-certificate /etc/pki/katello/certs/java-client.crt >> --ssl-key /etc/pki/katello/private/java-client.key -b 'amqps:// >> llin417.xhl.test.net:5671' add exchange topic event --durable returned 1 >> instead of one of [0] >> /Stage[main]/Certs::Candlepin/Exec[create candlepin qpid >> exchange]/returns: change from notrun to 0 failed: qpid-config >> --ssl-certificate /etc/pki/katello/certs/java-client.crt --ssl-key >> /etc/pki/katello/private/java-client.key -b 'amqps:// >> llin417.xhl.test.net:5671' add exchange topic event --durable returned 1 >> instead of one of [0] >> /Stage[main]/Certs::Candlepin/Exec[create candlepin qpid exchange]: >> Failed to call refresh: qpid-config --ssl-certificate >> /etc/pki/katello/certs/java-client.crt --ssl-key >> /etc/pki/katello/private/java-client.key -b 'amqps:// >> llin417.xhl.test.net:5671' add exchange topic event --durable returned 1 >> instead of one of [0] >> /Stage[main]/Certs::Candlepin/Exec[create candlepin qpid exchange]: >> qpid-config --ssl-certificate /etc/pki/katello/certs/java-client.crt >> --ssl-key /etc/pki/katello/private/java-client.key -b 'amqps:// >> llin417.xhl.test.net:5671' add exchange topic event --durable returned 1 >> instead of one of [0] >> >>

Are you iptables and ip6tables firewalls back on? What services do you
have listening?

$ netstat -pntl
$ katello-service status

··· On Friday, 20 March 2015 10:35:19 UTC, Peter Santiago wrote: > > still no go... > > Installed fine this time... but production log... > > 2015-03-20 05:33:02 [W] Connection refused - > "/usr/share/foreman/tmp/sockets/dynflow_socket" (Errno::ECONNREFUSED) > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/executors/remote_via_socket/core.rb:142:in > `initialize' > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/executors/remote_via_socket/core.rb:142:in > `new' > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/executors/remote_via_socket/core.rb:142:in > `connect' > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/executors/remote_via_socket/core.rb:91:in > `block in on_message' > /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:859:in > `block in assigns' > /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in > `tap' > /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in > `assigns' > /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:138:in > `match_value' > /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:116:in > `block in match' > /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in > `each' > /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in > `match' > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/executors/remote_via_socket/core.rb:79:in > `on_message' > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:80:in > `block in on_envelope' > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/future.rb:75:in > `call' > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/future.rb:75:in > `evaluate_to' > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:80:in > `on_envelope' > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:72:in > `receive' > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:99:in > `block (2 levels) in run' > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:99:in > `loop' > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:99:in > `block in run' > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:99:in > `catch' > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:99:in > `run' > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:13:in > `block in initialize' > /opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in > `call' > /opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in > `block in create_with_logging_context' > > > On Thursday, March 19, 2015 at 6:19:16 PM UTC+8, JC wrote: >> >> Peter - I had a plethora of confusing errors installing on CentOS6, but >> all were resolved when I disabled selinux, made sure root's umask was >> suitable (e.g. 0022), configured NTP and confirmed hostname -f was >> resolvable. These may have no relevance to you, but you might want to >> double check...(I also disabled iptables/ip6tables for the install). >> >> On Thursday, 19 March 2015 06:27:01 UTC, Peter Santiago wrote: >>> >>> qpid-config --ssl-certificate /etc/pki/katello/certs/java-client.crt >>> --ssl-key /etc/pki/katello/private/java-client.key -b 'amqps:// >>> llin417.xhl.test.net:5671' add exchange topic event --durable returned >>> 1 instead of one of [0] >>> /Stage[main]/Certs::Candlepin/Exec[create candlepin qpid >>> exchange]/returns: change from notrun to 0 failed: qpid-config >>> --ssl-certificate /etc/pki/katello/certs/java-client.crt --ssl-key >>> /etc/pki/katello/private/java-client.key -b 'amqps:// >>> llin417.xhl.test.net:5671' add exchange topic event --durable returned >>> 1 instead of one of [0] >>> /Stage[main]/Certs::Candlepin/Exec[create candlepin qpid exchange]: >>> Failed to call refresh: qpid-config --ssl-certificate >>> /etc/pki/katello/certs/java-client.crt --ssl-key >>> /etc/pki/katello/private/java-client.key -b 'amqps:// >>> llin417.xhl.test.net:5671' add exchange topic event --durable returned >>> 1 instead of one of [0] >>> /Stage[main]/Certs::Candlepin/Exec[create candlepin qpid exchange]: >>> qpid-config --ssl-certificate /etc/pki/katello/certs/java-client.crt >>> --ssl-key /etc/pki/katello/private/java-client.key -b 'amqps:// >>> llin417.xhl.test.net:5671' add exchange topic event --durable returned >>> 1 instead of one of [0] >>> >>>

I think this still has something to do with the candlepin stuff and qpidd…

[root@llin417 ~]# iptables -v -L
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination

[root@llin417 ~]# netstat -pntl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address
State PID/Program name
tcp 0 0 127.0.0.1:28017 0.0.0.0:*
LISTEN 19616/mongod
tcp 0 0 0.0.0.0:47221 0.0.0.0:*
LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:*
LISTEN 1947/sshd
tcp 0 0 127.0.0.1:631 0.0.0.0:*
LISTEN 1769/cupsd
tcp 0 0 127.0.0.1:5432 0.0.0.0:*
LISTEN 7101/postmaster
tcp 0 0 127.0.0.1:3128 0.0.0.0:*
LISTEN 2538/cntlm
tcp 0 0 127.0.0.1:6010 0.0.0.0:*
LISTEN 41525/sshd
tcp 0 0 127.0.0.1:35771 0.0.0.0:*
LISTEN 23639/Passenger Rac
tcp 0 0 0.0.0.0:8000 0.0.0.0:*
LISTEN 9388/ruby
tcp 0 0 0.0.0.0:9090 0.0.0.0:*
LISTEN 9388/ruby
tcp 0 0 127.0.0.1:57124 0.0.0.0:*
LISTEN 22953/Passenger Rac
tcp 0 0 0.0.0.0:5671 0.0.0.0:*
LISTEN 10050/qpidd
tcp 0 0 0.0.0.0:5672 0.0.0.0:*
LISTEN 10050/qpidd
tcp 0 0 127.0.0.1:27017 0.0.0.0:*
LISTEN 19616/mongod
tcp 0 0 0.0.0.0:651 0.0.0.0:*
LISTEN 1742/ypbind
tcp 0 0 0.0.0.0:49100 0.0.0.0:*
LISTEN 1588/rpc.statd
tcp 0 0 0.0.0.0:111 0.0.0.0:*
LISTEN 1568/rpcbind
tcp 0 0 :::54483 :::*
LISTEN 1588/rpc.statd
tcp 0 0 ::ffff:127.0.0.1:9300 :::*
LISTEN 20984/java
tcp 0 0 :::40052 :::*
LISTEN -
tcp 0 0 :::22 :::*
LISTEN 1947/sshd
tcp 0 0 :::23 :::*
LISTEN 1957/xinetd
tcp 0 0 ::1:631 :::*
LISTEN 1769/cupsd
tcp 0 0 ::1:5432 :::*
LISTEN 7101/postmaster
tcp 0 0 ::1:6010 :::*
LISTEN 41525/sshd
tcp 0 0 :::443 :::*
LISTEN 22313/httpd
tcp 0 0 :::8443 :::*
LISTEN 21839/java
tcp 0 0 :::513 :::*
LISTEN 1957/xinetd
tcp 0 0 :::514 :::*
LISTEN 1957/xinetd
tcp 0 0 ::ffff:127.0.0.1:8005 :::*
LISTEN 21839/java
tcp 0 0 :::5671 :::*
LISTEN 10050/qpidd
tcp 0 0 :::5000 :::*
LISTEN 22313/httpd
tcp 0 0 :::5672 :::*
LISTEN 10050/qpidd
tcp 0 0 :::8009 :::*
LISTEN 21839/java
tcp 0 0 :::8140 :::*
LISTEN 22313/httpd
tcp 0 0 :::111 :::*
LISTEN 1568/rpcbind
tcp 0 0 :::80 :::*
LISTEN 22313/httpd
tcp 0 0 :::8080 :::*
LISTEN 21839/java
tcp 0 0 ::ffff:127.0.0.1:9200 :::*
LISTEN 20984/java

[root@llin417 ~]# katello-service status
qpidd (pid 10050) is running…
tomcat6 (pid 21839) is running… [ OK ]
mongod (pid 19616) is running…
elasticsearch (pid 20984) is running…
celery init v10.0.
Using config script: /etc/default/pulp_resource_manager
node resource_manager (pid 22091) is running…
celery init v10.0.
Using config script: /etc/default/pulp_workers
node reserved_resource_worker-0 (pid 22211) is running…
node reserved_resource_worker-1 (pid 22254) is running…
celery init v10.0.
Using configuration: /etc/default/pulp_workers, /etc/default/pulp_celerybeat
pulp_celerybeat (pid 21974) is running.
httpd (pid 22313) is running…
dynflow_executor is running.
dynflow_executor_monitor is running.

[root@llin417 ~]# hammer -u admin ping
/usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.4/lib/hammer_cli/./apipie/…/abstract.rb:68:
warning: already initialized constant DEFAULT_LABEL_INDENT
[Foreman] Password for admin:
candlepin:
Status: ok
Server Response: Duration: 34ms
candlepin_auth:
Status: ok
Server Response: Duration: 21ms
pulp:
Status: ok
Server Response: Duration: 13ms
pulp_auth:
Status: ok
Server Response: Duration: 16ms
elasticsearch:
Status: ok
Server Response: Duration: 35ms
foreman_tasks:
Status: FAIL
Server Response: Message: foreman-tasks service not running

··· On Friday, March 20, 2015 at 7:21:29 PM UTC+8, JC wrote: > > Are you iptables and ip6tables firewalls back on? What services do you > have listening? > > $ netstat -pntl > $ katello-service status > > > On Friday, 20 March 2015 10:35:19 UTC, Peter Santiago wrote: >> >> still no go... >> >> Installed fine this time... but production log... >> >> 2015-03-20 05:33:02 [W] Connection refused - >> "/usr/share/foreman/tmp/sockets/dynflow_socket" (Errno::ECONNREFUSED) >> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/executors/remote_via_socket/core.rb:142:in >> `initialize' >> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/executors/remote_via_socket/core.rb:142:in >> `new' >> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/executors/remote_via_socket/core.rb:142:in >> `connect' >> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/executors/remote_via_socket/core.rb:91:in >> `block in on_message' >> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:859:in >> `block in assigns' >> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in >> `tap' >> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in >> `assigns' >> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:138:in >> `match_value' >> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:116:in >> `block in match' >> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in >> `each' >> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in >> `match' >> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/executors/remote_via_socket/core.rb:79:in >> `on_message' >> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:80:in >> `block in on_envelope' >> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/future.rb:75:in >> `call' >> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/future.rb:75:in >> `evaluate_to' >> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:80:in >> `on_envelope' >> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:72:in >> `receive' >> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:99:in >> `block (2 levels) in run' >> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:99:in >> `loop' >> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:99:in >> `block in run' >> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:99:in >> `catch' >> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:99:in >> `run' >> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/micro_actor.rb:13:in >> `block in initialize' >> /opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in >> `call' >> /opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in >> `block in create_with_logging_context' >> >> >> On Thursday, March 19, 2015 at 6:19:16 PM UTC+8, JC wrote: >>> >>> Peter - I had a plethora of confusing errors installing on CentOS6, but >>> all were resolved when I disabled selinux, made sure root's umask was >>> suitable (e.g. 0022), configured NTP and confirmed hostname -f was >>> resolvable. These may have no relevance to you, but you might want to >>> double check...(I also disabled iptables/ip6tables for the install). >>> >>> On Thursday, 19 March 2015 06:27:01 UTC, Peter Santiago wrote: >>>> >>>> qpid-config --ssl-certificate /etc/pki/katello/certs/java-client.crt >>>> --ssl-key /etc/pki/katello/private/java-client.key -b 'amqps:// >>>> llin417.xhl.test.net:5671' add exchange topic event --durable returned >>>> 1 instead of one of [0] >>>> /Stage[main]/Certs::Candlepin/Exec[create candlepin qpid >>>> exchange]/returns: change from notrun to 0 failed: qpid-config >>>> --ssl-certificate /etc/pki/katello/certs/java-client.crt --ssl-key >>>> /etc/pki/katello/private/java-client.key -b 'amqps:// >>>> llin417.xhl.test.net:5671' add exchange topic event --durable returned >>>> 1 instead of one of [0] >>>> /Stage[main]/Certs::Candlepin/Exec[create candlepin qpid exchange]: >>>> Failed to call refresh: qpid-config --ssl-certificate >>>> /etc/pki/katello/certs/java-client.crt --ssl-key >>>> /etc/pki/katello/private/java-client.key -b 'amqps:// >>>> llin417.xhl.test.net:5671' add exchange topic event --durable returned >>>> 1 instead of one of [0] >>>> /Stage[main]/Certs::Candlepin/Exec[create candlepin qpid exchange]: >>>> qpid-config --ssl-certificate /etc/pki/katello/certs/java-client.crt >>>> --ssl-key /etc/pki/katello/private/java-client.key -b 'amqps:// >>>> llin417.xhl.test.net:5671' add exchange topic event --durable returned >>>> 1 instead of one of [0] >>>> >>>>

Hmmm. If you stop and start the services using katello-service do the
foreman-tasks report OK with hammer? My 2.2 install is from a 2.1
upgrade… I don't think I'm helping much here.

··· On 20 March 2015 at 13:43, Peter Santiago wrote:

I think this still has something to do with the candlepin stuff and
qpidd…

[root@llin417 ~]# iptables -v -L
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination

[root@llin417 ~]# netstat -pntl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign
Address State PID/Program name
tcp 0 0 127.0.0.1:28017 0.0.0.0:*
LISTEN 19616/mongod
tcp 0 0 0.0.0.0:47221 0.0.0.0:*
LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:*
LISTEN 1947/sshd
tcp 0 0 127.0.0.1:631 0.0.0.0:*
LISTEN 1769/cupsd
tcp 0 0 127.0.0.1:5432 0.0.0.0:*
LISTEN 7101/postmaster
tcp 0 0 127.0.0.1:3128 0.0.0.0:*
LISTEN 2538/cntlm
tcp 0 0 127.0.0.1:6010 0.0.0.0:*
LISTEN 41525/sshd
tcp 0 0 127.0.0.1:35771 0.0.0.0:*
LISTEN 23639/Passenger Rac
tcp 0 0 0.0.0.0:8000 0.0.0.0:*
LISTEN 9388/ruby
tcp 0 0 0.0.0.0:9090 0.0.0.0:*
LISTEN 9388/ruby
tcp 0 0 127.0.0.1:57124 0.0.0.0:*
LISTEN 22953/Passenger Rac
tcp 0 0 0.0.0.0:5671 0.0.0.0:*
LISTEN 10050/qpidd
tcp 0 0 0.0.0.0:5672 0.0.0.0:*
LISTEN 10050/qpidd
tcp 0 0 127.0.0.1:27017 0.0.0.0:*
LISTEN 19616/mongod
tcp 0 0 0.0.0.0:651 0.0.0.0:*
LISTEN 1742/ypbind
tcp 0 0 0.0.0.0:49100 0.0.0.0:*
LISTEN 1588/rpc.statd
tcp 0 0 0.0.0.0:111 0.0.0.0:*
LISTEN 1568/rpcbind
tcp 0 0 :::54483
:::* LISTEN 1588/rpc.statd
tcp 0 0 ::ffff:127.0.0.1:9300
:::* LISTEN 20984/java
tcp 0 0 :::40052
:::* LISTEN -
tcp 0 0 :::22
:::* LISTEN 1947/sshd
tcp 0 0 :::23
:::* LISTEN 1957/xinetd
tcp 0 0 ::1:631
:::* LISTEN 1769/cupsd
tcp 0 0 ::1:5432
:::* LISTEN 7101/postmaster
tcp 0 0 ::1:6010
:::* LISTEN 41525/sshd
tcp 0 0 :::443
:::* LISTEN 22313/httpd
tcp 0 0 :::8443
:::* LISTEN 21839/java
tcp 0 0 :::513
:::* LISTEN 1957/xinetd
tcp 0 0 :::514
:::* LISTEN 1957/xinetd
tcp 0 0 ::ffff:127.0.0.1:8005
:::* LISTEN 21839/java
tcp 0 0 :::5671
:::* LISTEN 10050/qpidd
tcp 0 0 :::5000
:::* LISTEN 22313/httpd
tcp 0 0 :::5672
:::* LISTEN 10050/qpidd
tcp 0 0 :::8009
:::* LISTEN 21839/java
tcp 0 0 :::8140
:::* LISTEN 22313/httpd
tcp 0 0 :::111
:::* LISTEN 1568/rpcbind
tcp 0 0 :::80
:::* LISTEN 22313/httpd
tcp 0 0 :::8080
:::* LISTEN 21839/java
tcp 0 0 ::ffff:127.0.0.1:9200
:::* LISTEN 20984/java

[root@llin417 ~]# katello-service status
qpidd (pid 10050) is running…
tomcat6 (pid 21839) is running… [ OK ]
mongod (pid 19616) is running…
elasticsearch (pid 20984) is running…
celery init v10.0.
Using config script: /etc/default/pulp_resource_manager
node resource_manager (pid 22091) is running…
celery init v10.0.
Using config script: /etc/default/pulp_workers
node reserved_resource_worker-0 (pid 22211) is running…
node reserved_resource_worker-1 (pid 22254) is running…
celery init v10.0.
Using configuration: /etc/default/pulp_workers,
/etc/default/pulp_celerybeat
pulp_celerybeat (pid 21974) is running.
httpd (pid 22313) is running…
dynflow_executor is running.
dynflow_executor_monitor is running.

[root@llin417 ~]# hammer -u admin ping
/usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.4/lib/hammer_cli/./apipie/…/abstract.rb:68:
warning: already initialized constant DEFAULT_LABEL_INDENT
[Foreman] Password for admin:
candlepin:
Status: ok
Server Response: Duration: 34ms
candlepin_auth:
Status: ok
Server Response: Duration: 21ms
pulp:
Status: ok
Server Response: Duration: 13ms
pulp_auth:
Status: ok
Server Response: Duration: 16ms
elasticsearch:
Status: ok
Server Response: Duration: 35ms
foreman_tasks:
Status: FAIL
Server Response: Message: foreman-tasks service not running

On Friday, March 20, 2015 at 7:21:29 PM UTC+8, JC wrote:

Are you iptables and ip6tables firewalls back on? What services do you
have listening?

$ netstat -pntl
$ katello-service status

On Friday, 20 March 2015 10:35:19 UTC, Peter Santiago wrote:

still no go…

Installed fine this time… but production log…

2015-03-20 05:33:02 [W] Connection refused - “/usr/share/foreman/tmp/sockets/dynflow_socket”
(Errno::ECONNREFUSED)
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/
lib/dynflow/executors/remote_via_socket/core.rb:142:in initialize' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/ lib/dynflow/executors/remote_via_socket/core.rb:142:innew’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/
lib/dynflow/executors/remote_via_socket/core.rb:142:in connect' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/ lib/dynflow/executors/remote_via_socket/core.rb:91:inblock in
on_message’
/opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:859:in
block in assigns' /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:intap’
/opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in
assigns' /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:138:inmatch_value’
/opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:116:in
block in match' /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:ineach’
/opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in
match' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/ lib/dynflow/executors/remote_via_socket/core.rb:79:inon_message’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/
lib/dynflow/micro_actor.rb:80:in block in on_envelope' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/future.rb:75:incall’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/future.rb:75:in
evaluate_to' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/ lib/dynflow/micro_actor.rb:80:inon_envelope’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/
lib/dynflow/micro_actor.rb:72:in receive' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/ lib/dynflow/micro_actor.rb:99:inblock (2 levels) in run’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/
lib/dynflow/micro_actor.rb:99:in loop' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/ lib/dynflow/micro_actor.rb:99:inblock in run’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/
lib/dynflow/micro_actor.rb:99:in catch' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/ lib/dynflow/micro_actor.rb:99:inrun’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/
lib/dynflow/micro_actor.rb:13:in block in initialize' /opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/ lib/logging/diagnostic_context.rb:323:incall’
/opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/
lib/logging/diagnostic_context.rb:323:in `block in
create_with_logging_context’

On Thursday, March 19, 2015 at 6:19:16 PM UTC+8, JC wrote:

Peter - I had a plethora of confusing errors installing on CentOS6, but
all were resolved when I disabled selinux, made sure root’s umask was
suitable (e.g. 0022), configured NTP and confirmed hostname -f was
resolvable. These may have no relevance to you, but you might want to
double check…(I also disabled iptables/ip6tables for the install).

On Thursday, 19 March 2015 06:27:01 UTC, Peter Santiago wrote:

qpid-config --ssl-certificate /etc/pki/katello/certs/java-client.crt
–ssl-key /etc/pki/katello/private/java-client.key -b ‘amqps://
llin417.xhl.test.net:5671’ add exchange topic event --durable
returned 1 instead of one of [0]
/Stage[main]/Certs::Candlepin/Exec[create candlepin qpid
exchange]/returns: change from notrun to 0 failed: qpid-config
–ssl-certificate /etc/pki/katello/certs/java-client.crt --ssl-key
/etc/pki/katello/private/java-client.key -b ‘amqps://
llin417.xhl.test.net:5671’ add exchange topic event --durable
returned 1 instead of one of [0]
/Stage[main]/Certs::Candlepin/Exec[create candlepin qpid exchange]:
Failed to call refresh: qpid-config --ssl-certificate
/etc/pki/katello/certs/java-client.crt --ssl-key
/etc/pki/katello/private/java-client.key -b ‘amqps://
llin417.xhl.test.net:5671’ add exchange topic event --durable
returned 1 instead of one of [0]
/Stage[main]/Certs::Candlepin/Exec[create candlepin qpid exchange]:
qpid-config --ssl-certificate /etc/pki/katello/certs/java-client.crt
–ssl-key /etc/pki/katello/private/java-client.key -b ‘amqps://
llin417.xhl.test.net:5671’ add exchange topic event --durable
returned 1 instead of one of [0]


You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/QoyV7fmyQPs/unsubscribe.
To unsubscribe from this group and all its topics, 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.


Jamie.

There have been a number of issues fixed since the first RC including
updating the version of qpid that we are providing. I hope to have a second
RC out later today or early next week.

Eric

··· On Fri, Mar 20, 2015 at 10:22 AM, Jamie Caldwell < mr.jamie.caldwell@gmail.com> wrote:

Hmmm. If you stop and start the services using katello-service do the
foreman-tasks report OK with hammer? My 2.2 install is from a 2.1
upgrade… I don’t think I’m helping much here.

On 20 March 2015 at 13:43, Peter Santiago vanyell2001@gmail.com wrote:

I think this still has something to do with the candlepin stuff and
qpidd…

[root@llin417 ~]# iptables -v -L
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination

[root@llin417 ~]# netstat -pntl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign
Address State PID/Program name
tcp 0 0 127.0.0.1:28017 0.0.0.0:*
LISTEN 19616/mongod
tcp 0 0 0.0.0.0:47221 0.0.0.0:*
LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:*
LISTEN 1947/sshd
tcp 0 0 127.0.0.1:631 0.0.0.0:*
LISTEN 1769/cupsd
tcp 0 0 127.0.0.1:5432 0.0.0.0:*
LISTEN 7101/postmaster
tcp 0 0 127.0.0.1:3128 0.0.0.0:*
LISTEN 2538/cntlm
tcp 0 0 127.0.0.1:6010 0.0.0.0:*
LISTEN 41525/sshd
tcp 0 0 127.0.0.1:35771 0.0.0.0:*
LISTEN 23639/Passenger Rac
tcp 0 0 0.0.0.0:8000 0.0.0.0:*
LISTEN 9388/ruby
tcp 0 0 0.0.0.0:9090 0.0.0.0:*
LISTEN 9388/ruby
tcp 0 0 127.0.0.1:57124 0.0.0.0:*
LISTEN 22953/Passenger Rac
tcp 0 0 0.0.0.0:5671 0.0.0.0:*
LISTEN 10050/qpidd
tcp 0 0 0.0.0.0:5672 0.0.0.0:*
LISTEN 10050/qpidd
tcp 0 0 127.0.0.1:27017 0.0.0.0:*
LISTEN 19616/mongod
tcp 0 0 0.0.0.0:651 0.0.0.0:*
LISTEN 1742/ypbind
tcp 0 0 0.0.0.0:49100 0.0.0.0:*
LISTEN 1588/rpc.statd
tcp 0 0 0.0.0.0:111 0.0.0.0:*
LISTEN 1568/rpcbind
tcp 0 0 :::54483
:::* LISTEN 1588/rpc.statd
tcp 0 0 ::ffff:127.0.0.1:9300
:::* LISTEN 20984/java
tcp 0 0 :::40052
:::* LISTEN -
tcp 0 0 :::22
:::* LISTEN 1947/sshd
tcp 0 0 :::23
:::* LISTEN 1957/xinetd
tcp 0 0 ::1:631
:::* LISTEN 1769/cupsd
tcp 0 0 ::1:5432
:::* LISTEN 7101/postmaster
tcp 0 0 ::1:6010
:::* LISTEN 41525/sshd
tcp 0 0 :::443
:::* LISTEN 22313/httpd
tcp 0 0 :::8443
:::* LISTEN 21839/java
tcp 0 0 :::513
:::* LISTEN 1957/xinetd
tcp 0 0 :::514
:::* LISTEN 1957/xinetd
tcp 0 0 ::ffff:127.0.0.1:8005
:::* LISTEN 21839/java
tcp 0 0 :::5671
:::* LISTEN 10050/qpidd
tcp 0 0 :::5000
:::* LISTEN 22313/httpd
tcp 0 0 :::5672
:::* LISTEN 10050/qpidd
tcp 0 0 :::8009
:::* LISTEN 21839/java
tcp 0 0 :::8140
:::* LISTEN 22313/httpd
tcp 0 0 :::111
:::* LISTEN 1568/rpcbind
tcp 0 0 :::80
:::* LISTEN 22313/httpd
tcp 0 0 :::8080
:::* LISTEN 21839/java
tcp 0 0 ::ffff:127.0.0.1:9200
:::* LISTEN 20984/java

[root@llin417 ~]# katello-service status
qpidd (pid 10050) is running…
tomcat6 (pid 21839) is running… [ OK ]
mongod (pid 19616) is running…
elasticsearch (pid 20984) is running…
celery init v10.0.
Using config script: /etc/default/pulp_resource_manager
node resource_manager (pid 22091) is running…
celery init v10.0.
Using config script: /etc/default/pulp_workers
node reserved_resource_worker-0 (pid 22211) is running…
node reserved_resource_worker-1 (pid 22254) is running…
celery init v10.0.
Using configuration: /etc/default/pulp_workers,
/etc/default/pulp_celerybeat
pulp_celerybeat (pid 21974) is running.
httpd (pid 22313) is running…
dynflow_executor is running.
dynflow_executor_monitor is running.

[root@llin417 ~]# hammer -u admin ping
/usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.4/lib/hammer_cli/./apipie/…/abstract.rb:68:
warning: already initialized constant DEFAULT_LABEL_INDENT
[Foreman] Password for admin:
candlepin:
Status: ok
Server Response: Duration: 34ms
candlepin_auth:
Status: ok
Server Response: Duration: 21ms
pulp:
Status: ok
Server Response: Duration: 13ms
pulp_auth:
Status: ok
Server Response: Duration: 16ms
elasticsearch:
Status: ok
Server Response: Duration: 35ms
foreman_tasks:
Status: FAIL
Server Response: Message: foreman-tasks service not running

On Friday, March 20, 2015 at 7:21:29 PM UTC+8, JC wrote:

Are you iptables and ip6tables firewalls back on? What services do you
have listening?

$ netstat -pntl
$ katello-service status

On Friday, 20 March 2015 10:35:19 UTC, Peter Santiago wrote:

still no go…

Installed fine this time… but production log…

2015-03-20 05:33:02 [W] Connection refused - “/usr/share/foreman/tmp/sockets/dynflow_socket”
(Errno::ECONNREFUSED)
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/
lib/dynflow/executors/remote_via_socket/core.rb:142:in initialize' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/ lib/dynflow/executors/remote_via_socket/core.rb:142:innew’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/
lib/dynflow/executors/remote_via_socket/core.rb:142:in connect' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/ lib/dynflow/executors/remote_via_socket/core.rb:91:inblock in
on_message’
/opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:859:in
block in assigns' /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:intap’
/opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in
assigns' /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:138:inmatch_value’
/opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:116:in
block in match' /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:ineach’
/opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in
match' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/ lib/dynflow/executors/remote_via_socket/core.rb:79:inon_message’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/
lib/dynflow/micro_actor.rb:80:in block in on_envelope' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/future.rb:75:incall’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/lib/dynflow/future.rb:75:in
evaluate_to' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/ lib/dynflow/micro_actor.rb:80:inon_envelope’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/
lib/dynflow/micro_actor.rb:72:in receive' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/ lib/dynflow/micro_actor.rb:99:inblock (2 levels) in run’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/
lib/dynflow/micro_actor.rb:99:in loop' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/ lib/dynflow/micro_actor.rb:99:inblock in run’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/
lib/dynflow/micro_actor.rb:99:in catch' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/ lib/dynflow/micro_actor.rb:99:inrun’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.6/
lib/dynflow/micro_actor.rb:13:in block in initialize' /opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/ lib/logging/diagnostic_context.rb:323:incall’
/opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/
lib/logging/diagnostic_context.rb:323:in `block in
create_with_logging_context’

On Thursday, March 19, 2015 at 6:19:16 PM UTC+8, JC wrote:

Peter - I had a plethora of confusing errors installing on CentOS6,
but all were resolved when I disabled selinux, made sure root’s umask was
suitable (e.g. 0022), configured NTP and confirmed hostname -f was
resolvable. These may have no relevance to you, but you might want to
double check…(I also disabled iptables/ip6tables for the install).

On Thursday, 19 March 2015 06:27:01 UTC, Peter Santiago wrote:

qpid-config --ssl-certificate /etc/pki/katello/certs/java-client.crt
–ssl-key /etc/pki/katello/private/java-client.key -b ‘amqps://
llin417.xhl.test.net:5671’ add exchange topic event --durable
returned 1 instead of one of [0]
/Stage[main]/Certs::Candlepin/Exec[create candlepin qpid
exchange]/returns: change from notrun to 0 failed: qpid-config
–ssl-certificate /etc/pki/katello/certs/java-client.crt --ssl-key
/etc/pki/katello/private/java-client.key -b ‘amqps://
llin417.xhl.test.net:5671’ add exchange topic event --durable
returned 1 instead of one of [0]
/Stage[main]/Certs::Candlepin/Exec[create candlepin qpid exchange]:
Failed to call refresh: qpid-config --ssl-certificate
/etc/pki/katello/certs/java-client.crt --ssl-key
/etc/pki/katello/private/java-client.key -b ‘amqps://
llin417.xhl.test.net:5671’ add exchange topic event --durable
returned 1 instead of one of [0]
/Stage[main]/Certs::Candlepin/Exec[create candlepin qpid exchange]:
qpid-config --ssl-certificate /etc/pki/katello/certs/java-client.crt
–ssl-key /etc/pki/katello/private/java-client.key -b ‘amqps://
llin417.xhl.test.net:5671’ add exchange topic event --durable
returned 1 instead of one of [0]


You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/QoyV7fmyQPs/unsubscribe.
To unsubscribe from this group and all its topics, 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.


Jamie.


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.