Problem:
I am getting this error when I go to:
foreman web UI --> Hosts
Error: Could not calculate errata status, ensure host is registered and katello-agent is installed
Expected outcome:
Host should check in properly.
Foreman and Proxy versions:
foreman-1.16
Foreman and Proxy plugin versions:
Katello-3.5.1
Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]
Hi,
Any help? katello-agent package is installed:
# rpm -qa | grep katello
katello-host-tools-fact-plugin-3.0.2-1.el6.noarch
katello-host-tools-3.0.2-1.el6.noarch
katello-client-repos-3.4.0-3.el6.noarch
katello-agent-3.0.2-1.el6.noarch
katello-ca-consumer-katelloservername.domain.com-1.0-1.noarch
goferd daemon is running.
Thanks,
In which state is the rhsmcertd daemon ? If I m not wrong, it should be running.
It was stopped. I started it just now. Let’s see what happens.
After starting rhsmcertd daemon and restarting goferd it still is in the same condition. Any thought on what to try next?
I think that report is sent by yum plugin, run “yum update” or some yum install command to trigger the report push.
Well, I ran yum update and yum repolist and all other yum related commands but I still don’t see any change.
The qpid daemon can talk with server and client properly and I don’t see any disconnect.
I re-registered the client with the server, however it didn’t make any improvement.
# netstat -tunapl | grep ip-of-not-working-client
tcp 0 0 katello-server-ip:5647 ip-of-not-working-client:36327 ESTABLISHED 27436/qdrouterd
I have another client registered and it doesn’t have any problem.
# netstat -tunapl | grep ip-of-working-client
tcp 0 0 katello-server-ip:5647 ip-of-working-client:20792 ESTABLISHED 27436/qdrouterd
In the logs of katello server, I have these:
# tailf /var/log/qdrouterd/qdrouterd.log
2018-07-27 14:06:28.916897 -0400 SERVER (info) Accepted connection to 0.0.0.0:5647 from ip-of-not-working-client:56673
2018-07-27 14:06:29.907689 -0400 SERVER (info) Accepted connection to 0.0.0.0:5647 from ip-of-not-working-client:56674
2018-07-30 03:24:05.943387 -0400 SERVER (info) Accepted connection to 0.0.0.0:5647 from ip-of-not-working-client:36202
2018-07-30 03:24:09.30462 -0400 SERVER (info) Accepted connection to 0.0.0.0:5647 from ip-of-not-working-client:36203
2018-07-30 03:24:38.575770 -0400 SERVER (info) Accepted connection to 0.0.0.0:5647 from ip-of-not-working-client:36216
2018-07-30 03:24:39.300247 -0400 SERVER (info) Accepted connection to 0.0.0.0:5647 from ip-of-not-working-client:36217
2018-07-30 03:31:38.560875 -0400 SERVER (info) Accepted connection to 0.0.0.0:5647 from ip-of-not-working-client:36316
2018-07-30 03:31:41.633409 -0400 SERVER (info) Accepted connection to 0.0.0.0:5647 from ip-of-not-working-client:36318
2018-07-30 03:31:50.846762 -0400 SERVER (info) Accepted connection to 0.0.0.0:5647 from ip-of-not-working-client:36325
2018-07-30 03:31:51.568320 -0400 SERVER (info) Accepted connection to 0.0.0.0:5647 from ip-of-not-working-client:36327
All the while the other client can talk fine. This is very odd :\
is goferd service running ?
(just a suggestion, I m not sure it s required for centos 6 clients)
Yes, it is running. In both clients, non working and working. Which is what is making it even more surprising to me.
I dont have other idea…
My setup is a little different (foreman 1.17, centos 7clients, no selinux) but what I can say is that to register content host, the only things I do are :
just like that, what are the selinux states of these hosts ?
