[Spacewalk-list] System not checking in with Spacewalk

Thu Oct 11 12:57:43 UTC 2018

Hi Ananda,
That is correct.  You just need to run that command on each RHEL 7 client that has the Spacewalk 2.8 client installed and it will be able to check in with Spacewalk again.  If Red Hat pushes out a new SELinux policy, you may need to run that command again after installing the policy package.

Good luck!

--
Jason Lewis
Senior Systems Engineer @ Micro Electronics, Inc.
P: (614) 777-2728 | E: jwlewis at microcenter.com<mailto:jwlewis at microcenter.com>

From: <spacewalk-list-bounces at redhat.com> on behalf of Ananda Arifianto <ananda.arifianto at danamon.co.id>
Reply-To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Date: Thursday, October 11, 2018 at 6:45 AM
To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Subject: Re: [Spacewalk-list] System not checking in with Spacewalk

**Attention**
The following message was received from outside the Micro Electronics network. Carefully examine it before you open any links or attachments.

--------------------------
Hi Jason,

All of our clients are RHEL.
So, when I register new client to spacewalk, I must add 1 more step as below?
chcon system_u:object_r:rpm_exec_t:s0 /sbin/rhn_check-2.7

So that our clients will synchron with spacewalk server.

Best Regards,

Ananda Arifianto

From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Jason W. Lewis
Sent: Wednesday, October 10, 2018 2:13 AM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] System not checking in with Spacewalk

Ananda,
That sounds just like what I ran into after the 2.8 upgrade: yum commands worked, but the client systems never checked in with Spacewalk, and therefore never picked up their scheduled tasks.  So, I suspect you’re running into the same thing I did – SELinux on the client systems doesn’t have a rule for the new file in /sbin (rhn-check-2.7), and isn’t allowing the program to run.

Are the client systems where you’re running into this CentOS 7 or RHEL 7?  (Or the corresponding version of Fedora?) If so, this command will add a rule for rhn_check-2.7 and will allow it to run.  Run it on every CentOS/RHEL 7 system that has the new Spacewalk 2.8 client on it:

chcon system_u:object_r:rpm_exec_t:s0 /sbin/rhn_check-2.7

That will tell SELinux that the program is allowed to execute.  Once that’s done, your client systems should begin checking into Spacewalk again.

For more info, see https://bugzilla.redhat.com/show_bug.cgi?id=1584255

--
Jason Lewis
Senior Systems Engineer @ Micro Electronics, Inc.
P: (614) 777-2728 | E: jwlewis at microcenter.com<mailto:jwlewis at microcenter.com>

From: <spacewalk-list-bounces at redhat.com> on behalf of Ananda Arifianto <ananda.arifianto at danamon.co.id>
Reply-To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Date: Sunday, October 7, 2018 at 11:50 PM
To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Subject: Re: [Spacewalk-list] System not checking in with Spacewalk

**Attention**
The following message was received from outside the Micro Electronics network. Carefully examine it before you open any links or attachments.

--------------------------
Hi Jason,

For the ‘yum update’, our clients can receive the updates.
Today some clients show the same error again, System not checking in with Spacewalk.
The only workaround that can be resolved this issue is running rhn_check

Best Regards,

Ananda Arifianto

From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Jason W. Lewis
Sent: Thursday, October 04, 2018 7:50 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] System not checking in with Spacewalk

Ananda,
If you run ‘yum update’ on the server, does that update it?

--
Jason Lewis
Senior Systems Engineer @ Micro Electronics, Inc.
P: (614) 777-2728 | E: jwlewis at microcenter.com<mailto:jwlewis at microcenter.com>

From: <spacewalk-list-bounces at redhat.com> on behalf of Ananda Arifianto <ananda.arifianto at danamon.co.id>
Reply-To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Date: Thursday, October 4, 2018 at 4:40 AM
To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Subject: Re: [Spacewalk-list] System not checking in with Spacewalk

**Attention**
The following message was received from outside the Micro Electronics network. Carefully examine it before you open any links or attachments.

--------------------------
Hi Team,

I also found our SW clients that have issue with check-in problem, all are in virtual environment.
For the physical server, we didn’t find check-in problem. Even I don’t need to create the cronjob for running rhn_check.

Best Regards,

Ananda Arifianto

From: Ananda Arifianto
Sent: Thursday, October 04, 2018 1:39 PM
To: spacewalk-list at redhat.com
Subject: RE: [Spacewalk-list] System not checking in with Spacewalk

Hi Jason,

Yes, you’re right. I just upgraded to 2.8.
All clients are check in, but now the spacewalk server itself show that it’s not checked in.
When I try to run rhn_check, there is an error “ERROR: unable to read system id”
What can I do to resolve this?

Best Regards,

Ananda Arifianto

From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Jason W. Lewis
Sent: Tuesday, October 02, 2018 7:37 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] System not checking in with Spacewalk

I saw that, and I hope it works well for you.

That said, if you recently upgraded to 2.8, an SELinux context setting does keep rhn_check from running.  Changing the context for the new binary fixes it:

chcon system_u:object_r:rpm_exec_t:s0 /sbin/rhn_check-2.7

For more info, see https://bugzilla.redhat.com/show_bug.cgi?id=1584255

--
Jason Lewis
Senior Systems Engineer @ Micro Electronics, Inc.
P: (614) 777-2728 | E: jwlewis at microcenter.com<mailto:jwlewis at microcenter.com>

From: <spacewalk-list-bounces at redhat.com> on behalf of Ananda Arifianto <ananda.arifianto at danamon.co.id>
Reply-To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Date: Tuesday, October 2, 2018 at 6:51 AM
To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Subject: Re: [Spacewalk-list] System not checking in with Spacewalk

**Attention**
The following message was received from outside the Micro Electronics network. Carefully examine it before you open any links or attachments.

--------------------------
Hi Jason,

There is no change between that window.
But, I have created the cronjob to regularly execute rhn_check, so that I can pull the package from spacewalk server.

Thanks..

Best Regards,

Ananda Arifianto

From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Jason W. Lewis
Sent: Tuesday, October 02, 2018 5:23 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] System not checking in with Spacewalk

Ananda,
You’ll have to provide more info; that’s not a lot to go on.  What changed between Friday and today?

--
Jason Lewis
Senior Systems Engineer @ Micro Electronics, Inc.
P: (614) 777-2728 | E: jwlewis at microcenter.com<mailto:jwlewis at microcenter.com>

From: <spacewalk-list-bounces at redhat.com> on behalf of Ananda Arifianto <ananda.arifianto at danamon.co.id>
Reply-To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Date: Monday, October 1, 2018 at 11:06 PM
To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Subject: [Spacewalk-list] System not checking in with Spacewalk

**Attention**
The following message was received from outside the Micro Electronics network. Carefully examine it before you open any links or attachments.

--------------------------
Hi Guys,

Some of our clients show that system not checking in with Spacewalk, Last checked in was on Friday.
What is the solution for this problem?
Is it need to change the interval time in rhnsd.conf?
Thank you in advance..

Best Regards,
Ananda Arifianto
The information in this e-mail is confidential and is transmitted strictly for the addressee/s. If you receive this e-mail in error, please notify the sender and delete it immediately. Copying and/or disseminating the contents are prohibited. PT Bank Danamon Indonesia, Tbk. shall not be responsible for the accuracy or completeness of this email and any views expressed herein do not necessarily reflect the views of PT Bank Danamon Indonesia, Tbk.
The information in this e-mail is confidential and is transmitted strictly for the addressee/s. If you receive this e-mail in error, please notify the sender and delete it immediately. Copying and/or disseminating the contents are prohibited. PT Bank Danamon Indonesia, Tbk. shall not be responsible for the accuracy or completeness of this email and any views expressed herein do not necessarily reflect the views of PT Bank Danamon Indonesia, Tbk.
The information in this e-mail is confidential and is transmitted strictly for the addressee/s. If you receive this e-mail in error, please notify the sender and delete it immediately. Copying and/or disseminating the contents are prohibited. PT Bank Danamon Indonesia, Tbk. shall not be responsible for the accuracy or completeness of this email and any views expressed herein do not necessarily reflect the views of PT Bank Danamon Indonesia, Tbk.
The information in this e-mail is confidential and is transmitted strictly for the addressee/s. If you receive this e-mail in error, please notify the sender and delete it immediately. Copying and/or disseminating the contents are prohibited. PT Bank Danamon Indonesia, Tbk. shall not be responsible for the accuracy or completeness of this email and any views expressed herein do not necessarily reflect the views of PT Bank Danamon Indonesia, Tbk.
The information in this e-mail is confidential and is transmitted strictly for the addressee/s. If you receive this e-mail in error, please notify the sender and delete it immediately. Copying and/or disseminating the contents are prohibited. PT Bank Danamon Indonesia, Tbk. shall not be responsible for the accuracy or completeness of this email and any views expressed herein do not necessarily reflect the views of PT Bank Danamon Indonesia, Tbk.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20181011/f7506955/attachment.htm>