[katello 2.2] Fedora 20 content hosts not getting errata

I have just updated to Katello 2.2 and downloaded the newest katello-agent
and subscription managers for a new Fedora 20 client.

The client is subscribed to a product and that product has been promoted to
the correct environment and has a repository available that has 5475 errata
available for Fedora 20.

According to this post here :
https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/m-Fe8yLQKNI/to20XW7x36cJ
installing the updated katello-agent should have solved this issue, causing
the client to correctly report and then the errata should become available
to this client.

This is not happening though, even after a client restart and check-in it
still shows no errata available.

[root@fedora20client1 ~]# yum list installed katello-agent
Loaded plugins: package_upload, product-id, subscription-manager
Installed Packages
katello-agent.noarch
2.2.0-3.fc20 @katello-client
[root@fedora20client1 ~]# yum list installed subscription-manager
Loaded plugins: package_upload, product-id, subscription-manager
Installed Packages
subscription-manager.x86_64
1.14.3-1.fc20
@My_Custom_Repo_Fedora_20_-x86_64-_Updates

Linked wrong post. Correct post :
https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/HHnt_5iE42Q/m4JilW9W7CkJ

··· On Friday, May 29, 2015 at 11:28:41 AM UTC-7, Nathan Peters wrote: > > I have just updated to Katello 2.2 and downloaded the newest katello-agent > and subscription managers for a new Fedora 20 client. > > The client is subscribed to a product and that product has been promoted > to the correct environment and has a repository available that has 5475 > errata available for Fedora 20. > > According to this post here : > https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/m-Fe8yLQKNI/to20XW7x36cJ > installing the updated katello-agent should have solved this issue, causing > the client to correctly report and then the errata should become available > to this client. > > This is not happening though, even after a client restart and check-in it > still shows no errata available. > > [root@fedora20client1 ~]# yum list installed katello-agent > Loaded plugins: package_upload, product-id, subscription-manager > Installed Packages > katello-agent.noarch > 2.2.0-3.fc20 @katello-client > [root@fedora20client1 ~]# yum list installed subscription-manager > Loaded plugins: package_upload, product-id, subscription-manager > Installed Packages > subscription-manager.x86_64 > 1.14.3-1.fc20 > @My_Custom_Repo_Fedora_20_-_x86_64_-_Updates >

Can you check if any errors are printed in /var/log/messages on the
client after restarting goferd?

-Justin

··· On 05/29/2015 02:29 PM, Nathan Peters wrote: > Linked wrong post. Correct post : > https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/HHnt_5iE42Q/m4JilW9W7CkJ > > On Friday, May 29, 2015 at 11:28:41 AM UTC-7, Nathan Peters wrote: > > I have just updated to Katello 2.2 and downloaded the newest > katello-agent and subscription managers for a new Fedora 20 client. > > The client is subscribed to a product and that product has been > promoted to the correct environment and has a repository available > that has 5475 errata available for Fedora 20. > > According to this post here : > https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/m-Fe8yLQKNI/to20XW7x36cJ > > installing the updated katello-agent should have solved this > issue, causing the client to correctly report and then the errata > should become available to this client. > > This is not happening though, even after a client restart and > check-in it still shows no errata available. > > [root@fedora20client1 ~]# yum list installed katello-agent > Loaded plugins: package_upload, product-id, subscription-manager > Installed Packages > katello-agent.noarch 2.2.0-3.fc20 @katello-client > [root@fedora20client1 ~]# yum list installed subscription-manager > Loaded plugins: package_upload, product-id, subscription-manager > Installed Packages > subscription-manager.x86_64 1.14.3-1.fc20 > @My_Custom_Repo_Fedora_20_-_x86_64_-_Updates > > -- > 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.

I noticed that if I went directly to the errata list in Katello, it showed
as applicable but not installable. Yet it is definitely in the hosts
content view and lifecycle environment. If I clicked on an errata, it
would actually show the content host, but still only as applicable, not
installable.

Here are the errors I get after restarting goferd on the client

May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
amqps://katello.dev-mydomain.net:5647
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
Traceback (most recent call last):
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib/python2.7/site-packages/gofer/messaging/adapt…102, in open
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
self._impl = BlockingConnection(url, ssl_domain=domain)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", l… in init
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
msg="Opening connection")
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", l…231, in wait
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
self.container.process()
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/init.py"… in dispatch
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
ev.dispatch(self.handler)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/init.py"… in dispatch
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
result = dispatch(handler, type.method, self)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/init.py"… in dispatch
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
return m(*args)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", l…_tail_closed
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
self.on_transport_closed(event)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", l…sport_closed
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
raise ConnectionException("Connection %s disconnected" % self.url);
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
ConnectionException: Connection
amqps://katello-sandbox-atdev-…disconnected

··· On Friday, May 29, 2015 at 1:03:37 PM UTC-7, jsherril wrote: > > On 05/29/2015 02:29 PM, Nathan Peters wrote: > > Linked wrong post. Correct post : > https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/HHnt_5iE42Q/m4JilW9W7CkJ > > On Friday, May 29, 2015 at 11:28:41 AM UTC-7, Nathan Peters wrote: >> >> I have just updated to Katello 2.2 and downloaded the newest >> katello-agent and subscription managers for a new Fedora 20 client. >> >> The client is subscribed to a product and that product has been promoted >> to the correct environment and has a repository available that has 5475 >> errata available for Fedora 20. >> >> According to this post here : >> https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/m-Fe8yLQKNI/to20XW7x36cJ >> installing the updated katello-agent should have solved this issue, causing >> the client to correctly report and then the errata should become available >> to this client. >> >> This is not happening though, even after a client restart and check-in it >> still shows no errata available. >> >> [root@fedora20client1 ~]# yum list installed katello-agent >> Loaded plugins: package_upload, product-id, subscription-manager >> Installed Packages >> katello-agent.noarch >> 2.2.0-3.fc20 @katello-client >> [root@fedora20client1 ~]# yum list installed subscription-manager >> Loaded plugins: package_upload, product-id, subscription-manager >> Installed Packages >> subscription-manager.x86_64 >> 1.14.3-1.fc20 >> @My_Custom_Repo_Fedora_20_-_x86_64_-_Updates >> > -- > 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. > > Can you check if any errors are printed in /var/log/messages on the client > after restarting goferd? > > -Justin >

This is kind of interesting. I found another log entry on the client :

May 29 21:20:13 fedora20client1.test.mydomain.net goferd[1192]:
[INFO][MainThread] root:481 - connecting to katello.dev-mydomain.net:5647
May 29 21:20:13 fedora20client1.test.mydomain.net goferd[1192]:
[INFO][MainThread] root:521 - Disconnected

Why is the client trying to connect on port 5647? The only port near that
listed in the manual as needing to be opened is 5671.

··· On Friday, May 29, 2015 at 1:19:07 PM UTC-7, Nathan Peters wrote: > > On Friday, May 29, 2015 at 1:03:37 PM UTC-7, jsherril wrote: >> >> On 05/29/2015 02:29 PM, Nathan Peters wrote: >> >> Linked wrong post. Correct post : >> https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/HHnt_5iE42Q/m4JilW9W7CkJ >> >> On Friday, May 29, 2015 at 11:28:41 AM UTC-7, Nathan Peters wrote: >>> >>> I have just updated to Katello 2.2 and downloaded the newest >>> katello-agent and subscription managers for a new Fedora 20 client. >>> >>> The client is subscribed to a product and that product has been promoted >>> to the correct environment and has a repository available that has 5475 >>> errata available for Fedora 20. >>> >>> According to this post here : >>> https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/m-Fe8yLQKNI/to20XW7x36cJ >>> installing the updated katello-agent should have solved this issue, causing >>> the client to correctly report and then the errata should become available >>> to this client. >>> >>> This is not happening though, even after a client restart and check-in >>> it still shows no errata available. >>> >>> [root@fedora20client1 ~]# yum list installed katello-agent >>> Loaded plugins: package_upload, product-id, subscription-manager >>> Installed Packages >>> katello-agent.noarch >>> 2.2.0-3.fc20 @katello-client >>> [root@fedora20client1 ~]# yum list installed subscription-manager >>> Loaded plugins: package_upload, product-id, subscription-manager >>> Installed Packages >>> subscription-manager.x86_64 >>> 1.14.3-1.fc20 >>> @My_Custom_Repo_Fedora_20_-_x86_64_-_Updates >>> >> -- >> 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. >> >> Can you check if any errors are printed in /var/log/messages on the >> client after restarting goferd? >> >> -Justin >> > > I noticed that if I went directly to the errata list in Katello, it showed > as applicable but not installable. Yet it is definitely in the hosts > content view and lifecycle environment. If I clicked on an errata, it > would actually show the content host, but still only as applicable, not > installable. > > Here are the errors I get after restarting goferd on the client > > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - amqps:// > katello.dev-mydomain.net:5647 > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - > Traceback (most recent call last): > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File > "/usr/lib/python2.7/site-packages/gofer/messaging/adapt...102, in open > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - > self._impl = BlockingConnection(url, ssl_domain=domain) > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File > "/usr/lib64/python2.7/site-packages/proton/utils.py", l... in __init__ > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - > msg="Opening connection") > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File > "/usr/lib64/python2.7/site-packages/proton/utils.py", l...231, in wait > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - > self.container.process() > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File > "/usr/lib64/python2.7/site-packages/proton/__init__.py"... in dispatch > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - > ev.dispatch(self.handler) > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File > "/usr/lib64/python2.7/site-packages/proton/__init__.py"... in dispatch > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - > result = dispatch(handler, type.method, self) > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File > "/usr/lib64/python2.7/site-packages/proton/__init__.py"... in dispatch > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - > return m(*args) > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File > "/usr/lib64/python2.7/site-packages/proton/utils.py", l..._tail_closed > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - > self.on_transport_closed(event) > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File > "/usr/lib64/python2.7/site-packages/proton/utils.py", l...sport_closed > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - > raise ConnectionException("Connection %s disconnected" % self.url); > May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: > [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - > ConnectionException: Connection > amqps://katello-sandbox-atdev-...disconnected >

I fixed it!

The content view that I had produced was made in Katello 2.2RC and there
were bugs in that version that would make parts of the process freeze or
fail.

Once I deleted the content view and created a new one, the errata now show
up for that host.

··· On Friday, May 29, 2015 at 2:28:24 PM UTC-7, Nathan Peters wrote: > > This is kind of interesting. I found another log entry on the client : > > May 29 21:20:13 fedora20client1.test.mydomain.net goferd[1192]: > [INFO][MainThread] root:481 - connecting to katello.dev-mydomain.net:5647... > May 29 21:20:13 fedora20client1.test.mydomain.net goferd[1192]: > [INFO][MainThread] root:521 - Disconnected > > Why is the client trying to connect on port 5647? The only port near that > listed in the manual as needing to be opened is 5671. > > > On Friday, May 29, 2015 at 1:19:07 PM UTC-7, Nathan Peters wrote: >> >> On Friday, May 29, 2015 at 1:03:37 PM UTC-7, jsherril wrote: >>> >>> On 05/29/2015 02:29 PM, Nathan Peters wrote: >>> >>> Linked wrong post. Correct post : >>> https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/HHnt_5iE42Q/m4JilW9W7CkJ >>> >>> On Friday, May 29, 2015 at 11:28:41 AM UTC-7, Nathan Peters wrote: >>>> >>>> I have just updated to Katello 2.2 and downloaded the newest >>>> katello-agent and subscription managers for a new Fedora 20 client. >>>> >>>> The client is subscribed to a product and that product has been >>>> promoted to the correct environment and has a repository available that has >>>> 5475 errata available for Fedora 20. >>>> >>>> According to this post here : >>>> https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/m-Fe8yLQKNI/to20XW7x36cJ >>>> installing the updated katello-agent should have solved this issue, causing >>>> the client to correctly report and then the errata should become available >>>> to this client. >>>> >>>> This is not happening though, even after a client restart and check-in >>>> it still shows no errata available. >>>> >>>> [root@fedora20client1 ~]# yum list installed katello-agent >>>> Loaded plugins: package_upload, product-id, subscription-manager >>>> Installed Packages >>>> katello-agent.noarch >>>> 2.2.0-3.fc20 @katello-client >>>> [root@fedora20client1 ~]# yum list installed subscription-manager >>>> Loaded plugins: package_upload, product-id, subscription-manager >>>> Installed Packages >>>> subscription-manager.x86_64 >>>> 1.14.3-1.fc20 >>>> @My_Custom_Repo_Fedora_20_-_x86_64_-_Updates >>>> >>> -- >>> 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. >>> >>> Can you check if any errors are printed in /var/log/messages on the >>> client after restarting goferd? >>> >>> -Justin >>> >> >> I noticed that if I went directly to the errata list in Katello, it >> showed as applicable but not installable. Yet it is definitely in the >> hosts content view and lifecycle environment. If I clicked on an errata, >> it would actually show the content host, but still only as applicable, not >> installable. >> >> Here are the errors I get after restarting goferd on the client >> >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - amqps:// >> katello.dev-mydomain.net:5647 >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >> Traceback (most recent call last): >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >> "/usr/lib/python2.7/site-packages/gofer/messaging/adapt...102, in open >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >> self._impl = BlockingConnection(url, ssl_domain=domain) >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >> "/usr/lib64/python2.7/site-packages/proton/utils.py", l... in __init__ >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >> msg="Opening connection") >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >> "/usr/lib64/python2.7/site-packages/proton/utils.py", l...231, in wait >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >> self.container.process() >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >> "/usr/lib64/python2.7/site-packages/proton/__init__.py"... in dispatch >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >> ev.dispatch(self.handler) >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >> "/usr/lib64/python2.7/site-packages/proton/__init__.py"... in dispatch >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >> result = dispatch(handler, type.method, self) >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >> "/usr/lib64/python2.7/site-packages/proton/__init__.py"... in dispatch >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >> return m(*args) >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >> "/usr/lib64/python2.7/site-packages/proton/utils.py", l..._tail_closed >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >> self.on_transport_closed(event) >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >> "/usr/lib64/python2.7/site-packages/proton/utils.py", l...sport_closed >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >> raise ConnectionException("Connection %s disconnected" % self.url); >> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >> ConnectionException: Connection >> amqps://katello-sandbox-atdev-...disconnected >> >

> I fixed it!
>
> The content view that I had produced was made in Katello 2.2RC and
> there were bugs in that version that would make parts of the process
> freeze or fail.
>
> Once I deleted the content view and created a new one, the errata now
> show up for that host.
Ah! Nice find!

The gofer "Disconnected' is still a problem. I bet you are hitting:
http://projects.theforeman.org/issues/10350

Can you verify on the katello server that the files listed by: 'ls -l
/etc/pki/katello/qpid*' are owned by the 'qdrouterd' user? if they
are not, then I would:

chown qdrouterd /etc/pki/katello/qpid*
service qdrouterd restart

After that you should no longer see those 'Disconnected' messages on the
clients. (The only functionality you would see not working is remote
actions, package install/uninstall, errata apply).

-justin

··· On 05/29/2015 06:47 PM, Nathan Peters wrote:

On Friday, May 29, 2015 at 2:28:24 PM UTC-7, Nathan Peters wrote:

This is kind of interesting.  I found another log entry on the
client :

May 29 21:20:13 fedora20client1.test.mydomain.net
<http://fedora20client1.test.mydomain.net> goferd[1192]:
[INFO][MainThread] root:481 - connecting to
katello.dev-mydomain.net:5647...
May 29 21:20:13 fedora20client1.test.mydomain.net
<http://fedora20client1.test.mydomain.net> goferd[1192]:
[INFO][MainThread] root:521 - Disconnected

Why is the client trying to connect on port 5647?  The only port
near that listed in the manual as needing to be opened is 5671.


On Friday, May 29, 2015 at 1:19:07 PM UTC-7, Nathan Peters wrote:

    On Friday, May 29, 2015 at 1:03:37 PM UTC-7, jsherril wrote:

        On 05/29/2015 02:29 PM, Nathan Peters wrote:
        Linked wrong post.  Correct post :
        https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/HHnt_5iE42Q/m4JilW9W7CkJ
        <https://groups.google.com/forum/#%21searchin/foreman-users/fedora$2020$20errata/foreman-users/HHnt_5iE42Q/m4JilW9W7CkJ>

        On Friday, May 29, 2015 at 11:28:41 AM UTC-7, Nathan >>             Peters wrote:

            I have just updated to Katello 2.2 and downloaded the
            newest katello-agent and subscription managers for a
            new Fedora 20 client.

            The client is subscribed to a product and that
            product has been promoted to the correct environment
            and has a repository available that has 5475 errata
            available for Fedora 20.

            According to this post here :
            https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/m-Fe8yLQKNI/to20XW7x36cJ
            <https://groups.google.com/forum/#%21searchin/foreman-users/fedora$2020$20errata/foreman-users/m-Fe8yLQKNI/to20XW7x36cJ>
            installing the updated katello-agent should have
            solved this issue, causing the client to correctly
            report and then the errata should become available to
            this client.

            This is not happening though, even after a client
            restart and check-in it still shows no errata available.

            [root@fedora20client1 ~]# yum list installed
            katello-agent
            Loaded plugins: package_upload, product-id,
            subscription-manager
            Installed Packages
            katello-agent.noarch 2.2.0-3.fc20 @katello-client
            [root@fedora20client1 ~]# yum list installed
            subscription-manager
            Loaded plugins: package_upload, product-id,
            subscription-manager
            Installed Packages
            subscription-manager.x86_64 1.14.3-1.fc20
            @My_Custom_Repo_Fedora_20_-_x86_64_-_Updates

        -- 
        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
        <http://groups.google.com/group/foreman-users>.
        For more options, visit
        https://groups.google.com/d/optout
        <https://groups.google.com/d/optout>.
        Can you check if any errors are printed in
        /var/log/messages on the client after restarting goferd?

        -Justin


    I noticed that if I went directly to the errata list in
    Katello, it showed as applicable but not installable.  Yet it
    is definitely in the hosts content view and lifecycle
    environment.  If I clicked on an errata, it would actually
    show the content host, but still only as applicable, not
    installable.

    Here are the errors I get after restarting goferd on the client

    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 -
    amqps://katello.dev-mydomain.net:5647
    <http://katello.dev-mydomain.net:5647>
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 - Traceback
    (most recent call last):
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 - File
    "/usr/lib/python2.7/site-packages/gofer/messaging/adapt...102,
    in open
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 -     self._impl
    = BlockingConnection(url, ssl_domain=domain)
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 - File
    "/usr/lib64/python2.7/site-packages/proton/utils.py", l... in
    __init__
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 -    
    msg="Opening connection")
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 - File
    "/usr/lib64/python2.7/site-packages/proton/utils.py", l...231,
    in wait
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 -    
    self.container.process()
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 - File
    "/usr/lib64/python2.7/site-packages/proton/__init__.py"... in
    dispatch
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 -    
    ev.dispatch(self.handler)
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 - File
    "/usr/lib64/python2.7/site-packages/proton/__init__.py"... in
    dispatch
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 -     result =
    dispatch(handler, type.method, self)
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 - File
    "/usr/lib64/python2.7/site-packages/proton/__init__.py"... in
    dispatch
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 -     return
    m(*args)
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 - File
    "/usr/lib64/python2.7/site-packages/proton/utils.py",
    l..._tail_closed
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 -    
    self.on_transport_closed(event)
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 - File
    "/usr/lib64/python2.7/site-packages/proton/utils.py",
    l...sport_closed
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 -     raise
    ConnectionException("Connection %s disconnected" % self.url);
    May 29 20:15:15 fedora20client1.test.mydomain.net
    <http://fedora20client1.test.mydomain.net> goferd[1192]:
    [ERROR][MainThread]
    gofer.messaging.adapter.proton.connection:106 -
    ConnectionException: Connection
    amqps://katello-sandbox-atdev-...disconnected


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
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto: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.

One of them is owned by apache. I should take ownership of that one ?

[root@katello ~]# ls -l /etc/pki/katello/qpid*
-rw-r----- 1 apache apache 7264 Apr 9 16:03
/etc/pki/katello/qpid_client_striped.crt
-rw-r----- 1 qdrouterd root 5724 Apr 16 17:00
/etc/pki/katello/qpid_router_client.crt
-rw-r----- 1 qdrouterd root 1675 Apr 16 17:00
/etc/pki/katello/qpid_router_client.key
-rw-r----- 1 qdrouterd root 5724 Apr 16 17:00
/etc/pki/katello/qpid_router_server.crt
-rw-r----- 1 qdrouterd root 1679 Apr 16 17:00
/etc/pki/katello/qpid_router_server.key

··· On Friday, May 29, 2015 at 4:22:51 PM UTC-7, jsherril wrote: > > On 05/29/2015 06:47 PM, Nathan Peters wrote: > > I fixed it! > > The content view that I had produced was made in Katello 2.2RC and there > were bugs in that version that would make parts of the process freeze or > fail. > > Once I deleted the content view and created a new one, the errata now show > up for that host. > > Ah! Nice find! > > The gofer "Disconnected' is still a problem. I bet you are hitting: > http://projects.theforeman.org/issues/10350 > > Can you verify on the katello server that the files listed by: 'ls -l > /etc/pki/katello/qpid*' are owned by the 'qdrouterd' user? if they are > not, then I would: > > chown qdrouterd /etc/pki/katello/qpid* > service qdrouterd restart > > After that you should no longer see those 'Disconnected' messages on the > clients. (The only functionality you would see not working is remote > actions, package install/uninstall, errata apply). > > -justin > > > On Friday, May 29, 2015 at 2:28:24 PM UTC-7, Nathan Peters wrote: >> >> This is kind of interesting. I found another log entry on the client : >> >> May 29 21:20:13 fedora20client1.test.mydomain.net goferd[1192]: >> [INFO][MainThread] root:481 - connecting to katello.dev-mydomain.net:5647... >> May 29 21:20:13 fedora20client1.test.mydomain.net goferd[1192]: >> [INFO][MainThread] root:521 - Disconnected >> >> Why is the client trying to connect on port 5647? The only port near >> that listed in the manual as needing to be opened is 5671. >> >> >> On Friday, May 29, 2015 at 1:19:07 PM UTC-7, Nathan Peters wrote: >>> >>> On Friday, May 29, 2015 at 1:03:37 PM UTC-7, jsherril wrote: >>>> >>>> On 05/29/2015 02:29 PM, Nathan Peters wrote: >>>> >>>> Linked wrong post. Correct post : >>>> https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/HHnt_5iE42Q/m4JilW9W7CkJ >>>> >>>> On Friday, May 29, 2015 at 11:28:41 AM UTC-7, Nathan Peters wrote: >>>>> >>>>> I have just updated to Katello 2.2 and downloaded the newest >>>>> katello-agent and subscription managers for a new Fedora 20 client. >>>>> >>>>> The client is subscribed to a product and that product has been >>>>> promoted to the correct environment and has a repository available that has >>>>> 5475 errata available for Fedora 20. >>>>> >>>>> According to this post here : >>>>> https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/m-Fe8yLQKNI/to20XW7x36cJ >>>>> installing the updated katello-agent should have solved this issue, causing >>>>> the client to correctly report and then the errata should become available >>>>> to this client. >>>>> >>>>> This is not happening though, even after a client restart and check-in >>>>> it still shows no errata available. >>>>> >>>>> [root@fedora20client1 ~]# yum list installed katello-agent >>>>> Loaded plugins: package_upload, product-id, subscription-manager >>>>> Installed Packages >>>>> katello-agent.noarch >>>>> 2.2.0-3.fc20 @katello-client >>>>> [root@fedora20client1 ~]# yum list installed subscription-manager >>>>> Loaded plugins: package_upload, product-id, subscription-manager >>>>> Installed Packages >>>>> subscription-manager.x86_64 >>>>> 1.14.3-1.fc20 >>>>> @My_Custom_Repo_Fedora_20_-_x86_64_-_Updates >>>>> >>>> -- >>>> 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. >>>> >>>> Can you check if any errors are printed in /var/log/messages on the >>>> client after restarting goferd? >>>> >>>> -Justin >>>> >>> >>> I noticed that if I went directly to the errata list in Katello, it >>> showed as applicable but not installable. Yet it is definitely in the >>> hosts content view and lifecycle environment. If I clicked on an errata, >>> it would actually show the content host, but still only as applicable, not >>> installable. >>> >>> Here are the errors I get after restarting goferd on the client >>> >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - amqps:// >>> katello.dev-mydomain.net:5647 >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>> Traceback (most recent call last): >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >>> "/usr/lib/python2.7/site-packages/gofer/messaging/adapt...102, in open >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>> self._impl = BlockingConnection(url, ssl_domain=domain) >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >>> "/usr/lib64/python2.7/site-packages/proton/utils.py", l... in __init__ >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>> msg="Opening connection") >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >>> "/usr/lib64/python2.7/site-packages/proton/utils.py", l...231, in wait >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>> self.container.process() >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >>> "/usr/lib64/python2.7/site-packages/proton/__init__.py"... in dispatch >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>> ev.dispatch(self.handler) >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >>> "/usr/lib64/python2.7/site-packages/proton/__init__.py"... in dispatch >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>> result = dispatch(handler, type.method, self) >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >>> "/usr/lib64/python2.7/site-packages/proton/__init__.py"... in dispatch >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>> return m(*args) >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >>> "/usr/lib64/python2.7/site-packages/proton/utils.py", l..._tail_closed >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>> self.on_transport_closed(event) >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >>> "/usr/lib64/python2.7/site-packages/proton/utils.py", l...sport_closed >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>> raise ConnectionException("Connection %s disconnected" % self.url); >>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>> ConnectionException: Connection >>> amqps://katello-sandbox-atdev-...disconnected >>> >> -- > 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. > > >

I'm getting this issue as well (centos7 is the client this time)

have tried the following as per the bug report and also chowned the one by
apache

[root@katello-test log]# ls -l /etc/pki/katello/qpid*
-rw-r-----. 1 apache apache 7250 Jun 2 11:23
/etc/pki/katello/qpid_client_striped.crt
-rw-r-----. 1 qdrouterd qdrouterd 5696 Jun 2 11:14
/etc/pki/katello/qpid_router_client.crt
-rw-r-----. 1 qdrouterd qdrouterd 1679 Jun 2 11:13
/etc/pki/katello/qpid_router_client.key
-rw-r-----. 1 qdrouterd qdrouterd 5696 Jun 2 11:14
/etc/pki/katello/qpid_router_server.crt
-rw-r-----. 1 qdrouterd qdrouterd 1679 Jun 2 11:14
/etc/pki/katello/qpid_router_server.key
[root@katello-test log]# ls -l /etc/pki/katello/qpid*
-rw-r-----. 1 apache apache 7250 Jun 2 11:23
/etc/pki/katello/qpid_client_striped.crt
-rw-r-----. 1 qdrouterd qdrouterd 5696 Jun 2 11:14
/etc/pki/katello/qpid_router_client.crt
-rw-r-----. 1 qdrouterd qdrouterd 1679 Jun 2 11:13
/etc/pki/katello/qpid_router_client.key
-rw-r-----. 1 qdrouterd qdrouterd 5696 Jun 2 11:14
/etc/pki/katello/qpid_router_server.crt
-rw-r-----. 1 qdrouterd qdrouterd 1679 Jun 2 11:14
/etc/pki/katello/qpid_router_server.key
[root@katello-test log]# chown qdrouterd:qdrouterd
/etc/pki/katello/qpid_client_striped.crt
[root@katello-test log]# chown qdrouterd /etc/pki/katello/qpid*
[root@katello-test log]# service qdrouterd restart
Shutting down qdrouterd services: [ OK ]
Starting qdrouterd services: [ OK ]

selinux is disabled, as are the firewalls just incase.

error on the client is the same (i think)
Jun 3 14:00:20 centos7 goferd: [INFO][MainThread]
gofer.messaging.adapter.proton.connection:100 - connecting: URL:
amqps://katello-test:5647|SSL: ca: /etc/rhsm/ca/katello-server-ca.pem|key:
None>certificate: /etc/pki/consumer/bundle.pem|host-validation: None
Jun 3 14:00:20 centos7 goferd: [INFO][MainThread] root:481 - connecting to
katello-test:5647…
Jun 3 14:00:20 centos7 goferd: [INFO][MainThread] root:521 - Disconnected
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - amqps://katello-test:5647
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - Traceback (most recent call
last):
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib/python2.7/site-packages/gofer/messaging/adapter/proton/connection.py",
line 102, in open
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - self._impl =
BlockingConnection(url, ssl_domain=domain)
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", line 200, in init
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - msg="Opening
connection")
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", line 231, in wait
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - self.container.process()
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/init.py", line 3729, in
dispatch
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 -
ev.dispatch(self.handler)
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/init.py", line 3654, in
dispatch
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - result =
dispatch(handler, type.method, self)
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/init.py", line 3543, in
dispatch
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - return m(*args)
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", line 257, in
on_transport_tail_closed
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 -
self.on_transport_closed(event)
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", line 261, in
on_transport_closed
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - raise
ConnectionException("Connection %s disconnected" % self.url);
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - ConnectionException:
Connection amqps://katello-test:5647 disconnected
Jun 3 14:00:20 centos7 goferd: [INFO][MainThread]
gofer.messaging.adapter.proton.connection:108 - retry in 106 seconds

··· On Saturday, 30 May 2015 09:43:58 UTC+9:30, Nathan Peters wrote: > > One of them is owned by apache. I should take ownership of that one ? > > [root@katello ~]# ls -l /etc/pki/katello/qpid* > -rw-r----- 1 apache apache 7264 Apr 9 16:03 > /etc/pki/katello/qpid_client_striped.crt > -rw-r----- 1 qdrouterd root 5724 Apr 16 17:00 > /etc/pki/katello/qpid_router_client.crt > -rw-r----- 1 qdrouterd root 1675 Apr 16 17:00 > /etc/pki/katello/qpid_router_client.key > -rw-r----- 1 qdrouterd root 5724 Apr 16 17:00 > /etc/pki/katello/qpid_router_server.crt > -rw-r----- 1 qdrouterd root 1679 Apr 16 17:00 > /etc/pki/katello/qpid_router_server.key > > > On Friday, May 29, 2015 at 4:22:51 PM UTC-7, jsherril wrote: >> >> On 05/29/2015 06:47 PM, Nathan Peters wrote: >> >> I fixed it! >> >> The content view that I had produced was made in Katello 2.2RC and there >> were bugs in that version that would make parts of the process freeze or >> fail. >> >> Once I deleted the content view and created a new one, the errata now >> show up for that host. >> >> Ah! Nice find! >> >> The gofer "Disconnected' is still a problem. I bet you are hitting: >> http://projects.theforeman.org/issues/10350 >> >> Can you verify on the katello server that the files listed by: 'ls -l >> /etc/pki/katello/qpid*' are owned by the 'qdrouterd' user? if they are >> not, then I would: >> >> chown qdrouterd /etc/pki/katello/qpid* >> service qdrouterd restart >> >> After that you should no longer see those 'Disconnected' messages on the >> clients. (The only functionality you would see not working is remote >> actions, package install/uninstall, errata apply). >> >> -justin >> >> >> On Friday, May 29, 2015 at 2:28:24 PM UTC-7, Nathan Peters wrote: >>> >>> This is kind of interesting. I found another log entry on the client : >>> >>> May 29 21:20:13 fedora20client1.test.mydomain.net goferd[1192]: >>> [INFO][MainThread] root:481 - connecting to katello.dev-mydomain.net:5647... >>> May 29 21:20:13 fedora20client1.test.mydomain.net goferd[1192]: >>> [INFO][MainThread] root:521 - Disconnected >>> >>> Why is the client trying to connect on port 5647? The only port near >>> that listed in the manual as needing to be opened is 5671. >>> >>> >>> On Friday, May 29, 2015 at 1:19:07 PM UTC-7, Nathan Peters wrote: >>>> >>>> On Friday, May 29, 2015 at 1:03:37 PM UTC-7, jsherril wrote: >>>>> >>>>> On 05/29/2015 02:29 PM, Nathan Peters wrote: >>>>> >>>>> Linked wrong post. Correct post : >>>>> https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/HHnt_5iE42Q/m4JilW9W7CkJ >>>>> >>>>> On Friday, May 29, 2015 at 11:28:41 AM UTC-7, Nathan Peters wrote: >>>>>> >>>>>> I have just updated to Katello 2.2 and downloaded the newest >>>>>> katello-agent and subscription managers for a new Fedora 20 client. >>>>>> >>>>>> The client is subscribed to a product and that product has been >>>>>> promoted to the correct environment and has a repository available that has >>>>>> 5475 errata available for Fedora 20. >>>>>> >>>>>> According to this post here : >>>>>> https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/m-Fe8yLQKNI/to20XW7x36cJ >>>>>> installing the updated katello-agent should have solved this issue, causing >>>>>> the client to correctly report and then the errata should become available >>>>>> to this client. >>>>>> >>>>>> This is not happening though, even after a client restart and >>>>>> check-in it still shows no errata available. >>>>>> >>>>>> [root@fedora20client1 ~]# yum list installed katello-agent >>>>>> Loaded plugins: package_upload, product-id, subscription-manager >>>>>> Installed Packages >>>>>> katello-agent.noarch >>>>>> 2.2.0-3.fc20 @katello-client >>>>>> [root@fedora20client1 ~]# yum list installed subscription-manager >>>>>> Loaded plugins: package_upload, product-id, subscription-manager >>>>>> Installed Packages >>>>>> subscription-manager.x86_64 >>>>>> 1.14.3-1.fc20 >>>>>> @My_Custom_Repo_Fedora_20_-_x86_64_-_Updates >>>>>> >>>>> -- >>>>> 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. >>>>> >>>>> Can you check if any errors are printed in /var/log/messages on the >>>>> client after restarting goferd? >>>>> >>>>> -Justin >>>>> >>>> >>>> I noticed that if I went directly to the errata list in Katello, it >>>> showed as applicable but not installable. Yet it is definitely in the >>>> hosts content view and lifecycle environment. If I clicked on an errata, >>>> it would actually show the content host, but still only as applicable, not >>>> installable. >>>> >>>> Here are the errors I get after restarting goferd on the client >>>> >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - amqps:// >>>> katello.dev-mydomain.net:5647 >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>>> Traceback (most recent call last): >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >>>> "/usr/lib/python2.7/site-packages/gofer/messaging/adapt...102, in open >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>>> self._impl = BlockingConnection(url, ssl_domain=domain) >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >>>> "/usr/lib64/python2.7/site-packages/proton/utils.py", l... in __init__ >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>>> msg="Opening connection") >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >>>> "/usr/lib64/python2.7/site-packages/proton/utils.py", l...231, in wait >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>>> self.container.process() >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >>>> "/usr/lib64/python2.7/site-packages/proton/__init__.py"... in dispatch >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>>> ev.dispatch(self.handler) >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >>>> "/usr/lib64/python2.7/site-packages/proton/__init__.py"... in dispatch >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>>> result = dispatch(handler, type.method, self) >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >>>> "/usr/lib64/python2.7/site-packages/proton/__init__.py"... in dispatch >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>>> return m(*args) >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >>>> "/usr/lib64/python2.7/site-packages/proton/utils.py", l..._tail_closed >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>>> self.on_transport_closed(event) >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File >>>> "/usr/lib64/python2.7/site-packages/proton/utils.py", l...sport_closed >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>>> raise ConnectionException("Connection %s disconnected" % self.url); >>>> May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]: >>>> [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - >>>> ConnectionException: Connection >>>> amqps://katello-sandbox-atdev-...disconnected >>>> >>> -- >> 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. >> >> >>

No, I did and got this error, so changed ownership back to apache:apache

Jun 3 14:29:06 katello-test pulp:
pulp.server.webservices.middleware.exception:ERROR: (1714-37856)
ModelError: "/etc/pki/katello/qpid_client_striped.crt" insufficient
permissions

So leave that file with apache:apache ownership.

so it really should be

··· > # chown qdrouterd:qdrouterd /etc/pki/katello/qpid_router* > # service qdrouterd restart OR systemtl restart qdrouterd

On Saturday, 30 May 2015 09:43:58 UTC+9:30, Nathan Peters wrote:

One of them is owned by apache. I should take ownership of that one ?

[root@katello ~]# ls -l /etc/pki/katello/qpid*
-rw-r----- 1 apache apache 7264 Apr 9 16:03
/etc/pki/katello/qpid_client_striped.crt
-rw-r----- 1 qdrouterd root 5724 Apr 16 17:00
/etc/pki/katello/qpid_router_client.crt
-rw-r----- 1 qdrouterd root 1675 Apr 16 17:00
/etc/pki/katello/qpid_router_client.key
-rw-r----- 1 qdrouterd root 5724 Apr 16 17:00
/etc/pki/katello/qpid_router_server.crt
-rw-r----- 1 qdrouterd root 1679 Apr 16 17:00
/etc/pki/katello/qpid_router_server.key

On Friday, May 29, 2015 at 4:22:51 PM UTC-7, jsherril wrote:

On 05/29/2015 06:47 PM, Nathan Peters wrote:

I fixed it!

The content view that I had produced was made in Katello 2.2RC and there
were bugs in that version that would make parts of the process freeze or
fail.

Once I deleted the content view and created a new one, the errata now
show up for that host.

Ah! Nice find!

The gofer "Disconnected’ is still a problem. I bet you are hitting:
Bug #10350: qpid-dispatch-0.4-4 runs under non-root account and has no access to PKI files - Katello - Foreman

Can you verify on the katello server that the files listed by: ‘ls -l
/etc/pki/katello/qpid*’ are owned by the ‘qdrouterd’ user? if they are
not, then I would:

chown qdrouterd /etc/pki/katello/qpid*
service qdrouterd restart

After that you should no longer see those ‘Disconnected’ messages on the
clients. (The only functionality you would see not working is remote
actions, package install/uninstall, errata apply).

-justin

On Friday, May 29, 2015 at 2:28:24 PM UTC-7, Nathan Peters wrote:

This is kind of interesting. I found another log entry on the client :

May 29 21:20:13 fedora20client1.test.mydomain.net goferd[1192]:
[INFO][MainThread] root:481 - connecting to katello.dev-mydomain.net:5647
May 29 21:20:13 fedora20client1.test.mydomain.net goferd[1192]:
[INFO][MainThread] root:521 - Disconnected

Why is the client trying to connect on port 5647? The only port near
that listed in the manual as needing to be opened is 5671.

On Friday, May 29, 2015 at 1:19:07 PM UTC-7, Nathan Peters wrote:

On Friday, May 29, 2015 at 1:03:37 PM UTC-7, jsherril wrote:

On 05/29/2015 02:29 PM, Nathan Peters wrote:

Linked wrong post. Correct post :
https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/HHnt_5iE42Q/m4JilW9W7CkJ

On Friday, May 29, 2015 at 11:28:41 AM UTC-7, Nathan Peters wrote:

I have just updated to Katello 2.2 and downloaded the newest
katello-agent and subscription managers for a new Fedora 20 client.

The client is subscribed to a product and that product has been
promoted to the correct environment and has a repository available that has
5475 errata available for Fedora 20.

According to this post here :
https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/m-Fe8yLQKNI/to20XW7x36cJ
installing the updated katello-agent should have solved this issue, causing
the client to correctly report and then the errata should become available
to this client.

This is not happening though, even after a client restart and
check-in it still shows no errata available.

[root@fedora20client1 ~]# yum list installed katello-agent
Loaded plugins: package_upload, product-id, subscription-manager
Installed Packages
katello-agent.noarch
2.2.0-3.fc20 @katello-client
[root@fedora20client1 ~]# yum list installed subscription-manager
Loaded plugins: package_upload, product-id, subscription-manager
Installed Packages
subscription-manager.x86_64
1.14.3-1.fc20
@My_Custom_Repo_Fedora_20_-x86_64-_Updates


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.

Can you check if any errors are printed in /var/log/messages on the
client after restarting goferd?

-Justin

I noticed that if I went directly to the errata list in Katello, it
showed as applicable but not installable. Yet it is definitely in the
hosts content view and lifecycle environment. If I clicked on an errata,
it would actually show the content host, but still only as applicable, not
installable.

Here are the errors I get after restarting goferd on the client

May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - amqps://
katello.dev-mydomain.net:5647
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
Traceback (most recent call last):
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib/python2.7/site-packages/gofer/messaging/adapt…102, in open
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
self._impl = BlockingConnection(url, ssl_domain=domain)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", l… in init
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
msg=“Opening connection”)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", l…231, in wait
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
self.container.process()
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/init.py"… in dispatch
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
ev.dispatch(self.handler)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/init.py"… in dispatch
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
result = dispatch(handler, type.method, self)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/init.py"… in dispatch
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
return m(*args)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", l…_tail_closed
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
self.on_transport_closed(event)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", l…sport_closed
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
raise ConnectionException(“Connection %s disconnected” % self.url);
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
ConnectionException: Connection
amqps://katello-sandbox-atdev-…disconnected


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.

So I looked into mine a little more… and tried a telnet on the port 5647
and the issue on my end was IPv6

netstat -anp | grep 5647

showed me it was only listening on 0.0.0.0:5647

I edited /etc/qpid-dispatch/qdrouterd.conf and added in the following
listen params

the first 2 starting with 0.0.0.0 already existed, i just added in the IPv6
ones…

The config wouldn't let me specific :: as the listen address so I had to
bind it to the actual IP of the machine.

listener {

··· > addr: 0.0.0.0 > port: 5647 > sasl-mechanisms: ANONYMOUS > ssl-profile: server > } > listener { > addr: 0.0.0.0 > port: 5646 > sasl-mechanisms: ANONYMOUS > role: inter-router > ssl-profile: server > } > listener { > addr: 2400:xxxxx > port: 5646 > sasl-mechanisms: ANONYMOUS > role: inter-router > ssl-profile: server > } > listener { > addr: 2400:xxxxx > port: 5647 > sasl-mechanisms: ANONYMOUS > ssl-profile: server > }

On Wednesday, 3 June 2015 14:03:24 UTC+9:30, David LeVene wrote:

I’m getting this issue as well (centos7 is the client this time)

have tried the following as per the bug report and also chowned the one by
apache

[root@katello-test log]# ls -l /etc/pki/katello/qpid*
-rw-r-----. 1 apache apache 7250 Jun 2 11:23
/etc/pki/katello/qpid_client_striped.crt
-rw-r-----. 1 qdrouterd qdrouterd 5696 Jun 2 11:14
/etc/pki/katello/qpid_router_client.crt
-rw-r-----. 1 qdrouterd qdrouterd 1679 Jun 2 11:13
/etc/pki/katello/qpid_router_client.key
-rw-r-----. 1 qdrouterd qdrouterd 5696 Jun 2 11:14
/etc/pki/katello/qpid_router_server.crt
-rw-r-----. 1 qdrouterd qdrouterd 1679 Jun 2 11:14
/etc/pki/katello/qpid_router_server.key
[root@katello-test log]# ls -l /etc/pki/katello/qpid*
-rw-r-----. 1 apache apache 7250 Jun 2 11:23
/etc/pki/katello/qpid_client_striped.crt
-rw-r-----. 1 qdrouterd qdrouterd 5696 Jun 2 11:14
/etc/pki/katello/qpid_router_client.crt
-rw-r-----. 1 qdrouterd qdrouterd 1679 Jun 2 11:13
/etc/pki/katello/qpid_router_client.key
-rw-r-----. 1 qdrouterd qdrouterd 5696 Jun 2 11:14
/etc/pki/katello/qpid_router_server.crt
-rw-r-----. 1 qdrouterd qdrouterd 1679 Jun 2 11:14
/etc/pki/katello/qpid_router_server.key
[root@katello-test log]# chown qdrouterd:qdrouterd
/etc/pki/katello/qpid_client_striped.crt
[root@katello-test log]# chown qdrouterd /etc/pki/katello/qpid*
[root@katello-test log]# service qdrouterd restart
Shutting down qdrouterd services: [ OK ]
Starting qdrouterd services: [ OK ]

selinux is disabled, as are the firewalls just incase.

error on the client is the same (i think)
Jun 3 14:00:20 centos7 goferd: [INFO][MainThread]
gofer.messaging.adapter.proton.connection:100 - connecting: URL:
amqps://katello-test:5647|SSL: ca: /etc/rhsm/ca/katello-server-ca.pem|key:
None>certificate: /etc/pki/consumer/bundle.pem|host-validation: None
Jun 3 14:00:20 centos7 goferd: [INFO][MainThread] root:481 - connecting
to katello-test:5647…
Jun 3 14:00:20 centos7 goferd: [INFO][MainThread] root:521 - Disconnected
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - amqps://katello-test:5647
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - Traceback (most recent call
last):
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib/python2.7/site-packages/gofer/messaging/adapter/proton/connection.py",
line 102, in open
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - self._impl =
BlockingConnection(url, ssl_domain=domain)
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", line 200, in init
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - msg=“Opening
connection”)
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", line 231, in wait
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - self.container.process()
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/init.py", line 3729, in
dispatch
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 -
ev.dispatch(self.handler)
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/init.py", line 3654, in
dispatch
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - result =
dispatch(handler, type.method, self)
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/init.py", line 3543, in
dispatch
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - return m(*args)
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", line 257, in
on_transport_tail_closed
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 -
self.on_transport_closed(event)
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", line 261, in
on_transport_closed
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - raise
ConnectionException(“Connection %s disconnected” % self.url);
Jun 3 14:00:20 centos7 goferd: [ERROR][MainThread]
gofer.messaging.adapter.proton.connection:106 - ConnectionException:
Connection amqps://katello-test:5647 disconnected
Jun 3 14:00:20 centos7 goferd: [INFO][MainThread]
gofer.messaging.adapter.proton.connection:108 - retry in 106 seconds

On Saturday, 30 May 2015 09:43:58 UTC+9:30, Nathan Peters wrote:

One of them is owned by apache. I should take ownership of that one ?

[root@katello ~]# ls -l /etc/pki/katello/qpid*
-rw-r----- 1 apache apache 7264 Apr 9 16:03
/etc/pki/katello/qpid_client_striped.crt
-rw-r----- 1 qdrouterd root 5724 Apr 16 17:00
/etc/pki/katello/qpid_router_client.crt
-rw-r----- 1 qdrouterd root 1675 Apr 16 17:00
/etc/pki/katello/qpid_router_client.key
-rw-r----- 1 qdrouterd root 5724 Apr 16 17:00
/etc/pki/katello/qpid_router_server.crt
-rw-r----- 1 qdrouterd root 1679 Apr 16 17:00
/etc/pki/katello/qpid_router_server.key

On Friday, May 29, 2015 at 4:22:51 PM UTC-7, jsherril wrote:

On 05/29/2015 06:47 PM, Nathan Peters wrote:

I fixed it!

The content view that I had produced was made in Katello 2.2RC and there
were bugs in that version that would make parts of the process freeze or
fail.

Once I deleted the content view and created a new one, the errata now
show up for that host.

Ah! Nice find!

The gofer "Disconnected’ is still a problem. I bet you are hitting:
Bug #10350: qpid-dispatch-0.4-4 runs under non-root account and has no access to PKI files - Katello - Foreman

Can you verify on the katello server that the files listed by: ‘ls -l
/etc/pki/katello/qpid*’ are owned by the ‘qdrouterd’ user? if they are
not, then I would:

chown qdrouterd /etc/pki/katello/qpid*
service qdrouterd restart

After that you should no longer see those ‘Disconnected’ messages on the
clients. (The only functionality you would see not working is remote
actions, package install/uninstall, errata apply).

-justin

On Friday, May 29, 2015 at 2:28:24 PM UTC-7, Nathan Peters wrote:

This is kind of interesting. I found another log entry on the client :

May 29 21:20:13 fedora20client1.test.mydomain.net goferd[1192]:
[INFO][MainThread] root:481 - connecting to katello.dev-mydomain.net:5647
May 29 21:20:13 fedora20client1.test.mydomain.net goferd[1192]:
[INFO][MainThread] root:521 - Disconnected

Why is the client trying to connect on port 5647? The only port near
that listed in the manual as needing to be opened is 5671.

On Friday, May 29, 2015 at 1:19:07 PM UTC-7, Nathan Peters wrote:

On Friday, May 29, 2015 at 1:03:37 PM UTC-7, jsherril wrote:

On 05/29/2015 02:29 PM, Nathan Peters wrote:

Linked wrong post. Correct post :
https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/HHnt_5iE42Q/m4JilW9W7CkJ

On Friday, May 29, 2015 at 11:28:41 AM UTC-7, Nathan Peters wrote:

I have just updated to Katello 2.2 and downloaded the newest
katello-agent and subscription managers for a new Fedora 20 client.

The client is subscribed to a product and that product has been
promoted to the correct environment and has a repository available that has
5475 errata available for Fedora 20.

According to this post here :
https://groups.google.com/forum/#!searchin/foreman-users/fedora$2020$20errata/foreman-users/m-Fe8yLQKNI/to20XW7x36cJ
installing the updated katello-agent should have solved this issue, causing
the client to correctly report and then the errata should become available
to this client.

This is not happening though, even after a client restart and
check-in it still shows no errata available.

[root@fedora20client1 ~]# yum list installed katello-agent
Loaded plugins: package_upload, product-id, subscription-manager
Installed Packages
katello-agent.noarch
2.2.0-3.fc20 @katello-client
[root@fedora20client1 ~]# yum list installed subscription-manager
Loaded plugins: package_upload, product-id, subscription-manager
Installed Packages
subscription-manager.x86_64
1.14.3-1.fc20
@My_Custom_Repo_Fedora_20_-x86_64-_Updates


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.

Can you check if any errors are printed in /var/log/messages on the
client after restarting goferd?

-Justin

I noticed that if I went directly to the errata list in Katello, it
showed as applicable but not installable. Yet it is definitely in the
hosts content view and lifecycle environment. If I clicked on an errata,
it would actually show the content host, but still only as applicable, not
installable.

Here are the errors I get after restarting goferd on the client

May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - amqps://
katello.dev-mydomain.net:5647
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
Traceback (most recent call last):
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib/python2.7/site-packages/gofer/messaging/adapt…102, in open
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
self._impl = BlockingConnection(url, ssl_domain=domain)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", l… in init
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
msg=“Opening connection”)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", l…231, in wait
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
self.container.process()
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/init.py"… in dispatch
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
ev.dispatch(self.handler)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/init.py"… in dispatch
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
result = dispatch(handler, type.method, self)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/init.py"… in dispatch
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
return m(*args)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", l…_tail_closed
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
self.on_transport_closed(event)
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File
"/usr/lib64/python2.7/site-packages/proton/utils.py", l…sport_closed
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
raise ConnectionException(“Connection %s disconnected” % self.url);
May 29 20:15:15 fedora20client1.test.mydomain.net goferd[1192]:
[ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 -
ConnectionException: Connection
amqps://katello-sandbox-atdev-…disconnected


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.