[Spacewalk-list] Error occurred while processing python2-rhn-client-tools

[Raymond Setchfield]

Hi Everyone,

Can anyone help me with this error message? I cannot seem to get past this
error.

Reading package lists... Error!
W: The repository 'spacewalk://cent-mgmt channels: Release' does not have a
Release file.
N: Data from such a repository can't be authenticated and is therefore
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration
details.
E: Problem parsing dependency Depends
E: Error occurred while processing python2-rhn-client-tools (NewVersion2)
E: Problem with MergeList
/var/lib/apt/lists/cent-mgmt_dists_channels:_satellites-development-channel_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.

Thanks

Ray
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7

[William Hongach]

Hello,

The same holds true for SLES with respect to the 2.9 client as well.  The 2.8 
client made use of the rhnsd binary, whereas the 2.9 client uses systemd 
timers.  This is something that seems to have changed relatively quietly.

Have a good day.

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Gerald Vogt
Sent: Wednesday, January 8, 2020 10:59 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7

[EXTERNAL EMAIL]

As Nicole Beck wrote before: on CentOS 7 there is no daemon anymore.
It's a systemd service with a systemd timer which calls rhn_check directly.

See

# systemctl list-timers
# systemctl status rhnsd.timer

-Gerald

On 08.01.20 16:53, Len Ewen wrote:
> Ok, so if I start the daemon, it checks in, then instantly dies. I 
> look at the osad file and nothing has updated and I cannot seem to 
> find a log file for rhnsd to see if something is going on there so 
> what am I missing?  I've removed and reinstalled the rhnsd package and 
> still have no luck.
>
>
> ---
>
> Len Ewen
>
> Systems Administrator 1
>
> Information Technology
>
> University of Indianapolis
>
> (317) 788-3362
>
>
>
> UIndyIT.jpg
>
> Confidentiality Notice: This communication and/or its content are for 
> the sole use of the intended recipient, and may be privileged, 
> confidential, or otherwise protected from disclosure by law. If you 
> are not the intended recipient, please notify the sender and then 
> delete all copies of it. Unless you are the intended recipient, your 
> use or dissemination of the information contained in this 
> communication may be illegal.
>
>
>
> On Wed, Jan 8, 2020 at 9:28 AM Len Ewen  > wrote:
>
> Ok, so why wouldn't the daemon be running?  I forced a check in by
> installing and removing a package, which seemed to work fine, but if
> it requires the daemon to be running constantly, I am assuming it
> won't check in again unless I force it?  I didn't do anything
> special to this box, I literally did a fresh minimal install and
> installed the spacewalk server on one box and the client on another
> to see if I could get it to work.
>
> ---
>
> Len Ewen
>
> Systems Administrator 1
>
> Information Technology
>
> University of Indianapolis
>
> (317) 788-3362
>
>
>
> UIndyIT.jpg
>
> Confidentiality Notice: This communication and/or its content are
> for the sole use of the intended recipient, and may be privileged,
> confidential, or otherwise protected from disclosure by law. If you
> are not the intended recipient, please notify the sender and then
> delete all copies of it. Unless you are the intended recipient, your
> use or dissemination of the information contained in this
> communication may be illegal.
>
>
>
> On Wed, Jan 8, 2020 at 9:21 AM Robert Paschedag
> mailto:robert.pasche...@web.de>> wrote:
>
> The daemon should be running. It should then check every
> interval minutes if something has to be done. See also within
> /etc/sysconfig/rhn/ for the interval. (Just right now know the
> name of the config file). The minimum interval is 60 minutes.
>
> Robert
>
>
> ⁣sent from my mobile device​
>
>
>  Originale Nachricht 
> Von: Len Ewen mailto:ew...@uindy.edu>>
> Gesendet: Wed Jan 08 15:11:06 GMT+01:00 2020
> An: spacewalk-list@redhat.com 
> Betreff: Re: [Spacewalk-list] Spacewalk client not checking in
> on CentOS 7
>
> The rhnsd daemon isn't running, should it be constantly running
> or does it
> pause and then run again?  It is enabled, just not running.
>
> ---
>
> Len Ewen
>
> Systems Administrator 1
>
> Information Technology
>
> University of Indianapolis
>
> (317) 788-3362
>
> [image: UIndyIT.jpg]
>
> Confidentiality Notice: This communication and/or its content
> are for the
> sole use of the intended recipient, and may be privileged,
> confidential, or
> otherwise protected from disclosure by law. If you are not the
> intended
> recipient, please notify the sender and then delete all copies
> of it.
> Unless you are the intended recipient, your use or dissemination
> of the
> information contained in this communication may be illegal.
>
>
> On Wed, Jan 8, 2020 at 8:58 AM Michael Mraka
> mailto:michael.mr...@redhat.com>>
> wrote:
>
>  > Len Ewen:
>  > > I know this a stupid noob question but I have a problem.
> I've got a
>  > clean
>  > > built, fresh out of the box spacewalk 2.9 server and a 2.9
> client.  The
>  > > client checked in once, but hasn't check

Re: [Spacewalk-list] Error: Cannot retrieve repository metadata (repomd.xml) for

[Jody McIvor]

t-Type: text/plain; charset="UTF-8"

Considering Spacewalk 2.9 was released in January 2019, what is the
plan for 2.10?  Has Red Hat-sponsored Spacewalk development diminished
since Red Hat Satellite 6.x is based on TheForeman and Red Hat
Satellite 5.x is EOL in May 2020?

https://access.redhat.com/support/policy/updates/satellite

/Brian/

On Wed, Jan 8, 2020 at 3:30 AM Michael Mraka  wrote:
>
> Neal Gompa:
> > Hey all,
> >
> > It seems we don't have client repositories for Fedora 31 for Spacewalk
> > 2.9. Can someone please build the client packages for Fedora 31 and
> > make them available?
>
> Fedora 31 had not been around when Spacewalk 2.9 was released therefore there
> are no client repositories.
> You can use Fedora 31 client from nightly repos.
> https://copr.fedorainfracloud.org/coprs/g/spacewalkproject/nightly-client/
>
> Regards,
>
> --
> Michael Mr?ka
> System Management Engineering, Red Hat
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list




--

Message: 5
Date: Wed, 8 Jan 2020 07:54:06 -0500
From: Len Ewen 
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Spacewalk client not checking in on CentOS 7
Message-ID:

Content-Type: text/plain; charset="utf-8"

I know this a stupid noob question but I have a problem.  I've got a clean
built, fresh out of the box spacewalk 2.9 server and a 2.9 client.  The
client checked in once, but hasn't checked again for the last 16 hours.  16
hours seems like a long time for a check in to happen, but I am not sure
what is going on.  What am I missing?  Do I need to set up a cron job to
update or something?

---

Len Ewen

Systems Administrator 1

Information Technology

University of Indianapolis

(317) 788-3362

[image: UIndyIT.jpg]

Confidentiality Notice: This communication and/or its content are for the
sole use of the intended recipient, and may be privileged, confidential, or
otherwise protected from disclosure by law. If you are not the intended
recipient, please notify the sender and then delete all copies of it.
Unless you are the intended recipient, your use or dissemination of the
information contained in this communication may be illegal.
-- next part --
An HTML attachment was scrubbed...
URL: 
<https://www.redhat.com/archives/spacewalk-list/attachments/20200108/0f3100d1/attachment.html>

--

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

End of Spacewalk-list Digest, Vol 140, Issue 4
**


This email is intended only for the addressee. It may contain confidential or 
proprietary information that cannot be disclosed without BCLC's permission. If 
you have received this email in error, please notify the sender immediately and 
delete the email.


___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7

[Len Ewen]

I didn't have a reply from Nicole Beck in my email, but looking at the
listserv I found it.  I have enabled the rhnsd.timer and we'll see if this
makes it talk properly.  Thank you everyone for your help.  Sorry for
bothering you with something so trivial.

---

Len Ewen

Systems Administrator 1

Information Technology

University of Indianapolis

(317) 788-3362

[image: UIndyIT.jpg]

Confidentiality Notice: This communication and/or its content are for the
sole use of the intended recipient, and may be privileged, confidential, or
otherwise protected from disclosure by law. If you are not the intended
recipient, please notify the sender and then delete all copies of it.
Unless you are the intended recipient, your use or dissemination of the
information contained in this communication may be illegal.


On Wed, Jan 8, 2020 at 10:58 AM Gerald Vogt  wrote:

> As Nicole Beck wrote before: on CentOS 7 there is no daemon anymore.
> It's a systemd service with a systemd timer which calls rhn_check directly.
>
> See
>
> # systemctl list-timers
> # systemctl status rhnsd.timer
>
> -Gerald
>
> On 08.01.20 16:53, Len Ewen wrote:
> > Ok, so if I start the daemon, it checks in, then instantly dies. I look
> > at the osad file and nothing has updated and I cannot seem to find a log
> > file for rhnsd to see if something is going on there so what am I
> > missing?  I've removed and reinstalled the rhnsd package and still have
> > no luck.
> >
> >
> > ---
> >
> > Len Ewen
> >
> > Systems Administrator 1
> >
> > Information Technology
> >
> > University of Indianapolis
> >
> > (317) 788-3362
> >
> >
> >
> > UIndyIT.jpg
> >
> > Confidentiality Notice: This communication and/or its content are for
> > the sole use of the intended recipient, and may be privileged,
> > confidential, or otherwise protected from disclosure by law. If you are
> > not the intended recipient, please notify the sender and then delete all
> > copies of it. Unless you are the intended recipient, your use or
> > dissemination of the information contained in this communication may be
> > illegal.
> >
> >
> >
> > On Wed, Jan 8, 2020 at 9:28 AM Len Ewen  > > wrote:
> >
> > Ok, so why wouldn't the daemon be running?  I forced a check in by
> > installing and removing a package, which seemed to work fine, but if
> > it requires the daemon to be running constantly, I am assuming it
> > won't check in again unless I force it?  I didn't do anything
> > special to this box, I literally did a fresh minimal install and
> > installed the spacewalk server on one box and the client on another
> > to see if I could get it to work.
> >
> > ---
> >
> > Len Ewen
> >
> > Systems Administrator 1
> >
> > Information Technology
> >
> > University of Indianapolis
> >
> > (317) 788-3362
> >
> >
> >
> > UIndyIT.jpg
> >
> > Confidentiality Notice: This communication and/or its content are
> > for the sole use of the intended recipient, and may be privileged,
> > confidential, or otherwise protected from disclosure by law. If you
> > are not the intended recipient, please notify the sender and then
> > delete all copies of it. Unless you are the intended recipient, your
> > use or dissemination of the information contained in this
> > communication may be illegal.
> >
> >
> >
> > On Wed, Jan 8, 2020 at 9:21 AM Robert Paschedag
> > mailto:robert.pasche...@web.de>> wrote:
> >
> > The daemon should be running. It should then check every
> > interval minutes if something has to be done. See also within
> > /etc/sysconfig/rhn/ for the interval. (Just right now know the
> > name of the config file). The minimum interval is 60 minutes.
> >
> > Robert
> >
> >
> > ⁣sent from my mobile device​
> >
> >
> >  Originale Nachricht 
> > Von: Len Ewen mailto:ew...@uindy.edu>>
> > Gesendet: Wed Jan 08 15:11:06 GMT+01:00 2020
> > An: spacewalk-list@redhat.com 
> > Betreff: Re: [Spacewalk-list] Spacewalk client not checking in
> > on CentOS 7
> >
> > The rhnsd daemon isn't running, should it be constantly running
> > or does it
> > pause and then run again?  It is enabled, just not running.
> >
> > ---
> >
> > Len Ewen
> >
> > Systems Administrator 1
> >
> > Information Technology
> >
> > University of Indianapolis
> >
> > (317) 788-3362
> >
> > [image: UIndyIT.jpg]
> >
> > Confidentiality Notice: This communication and/or its content
> > are for the
> > sole use of the intended recipient, and may be privileged,
> > confidential, or
> > otherwise protected from disclosure by law. If you are not the
> > intended
> > recipient, please notify the sender and then d

Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7

[Gerald Vogt]

As Nicole Beck wrote before: on CentOS 7 there is no daemon anymore. 
It's a systemd service with a systemd timer which calls rhn_check directly.


See

# systemctl list-timers
# systemctl status rhnsd.timer

-Gerald

On 08.01.20 16:53, Len Ewen wrote:
Ok, so if I start the daemon, it checks in, then instantly dies. I look 
at the osad file and nothing has updated and I cannot seem to find a log 
file for rhnsd to see if something is going on there so what am I 
missing?  I've removed and reinstalled the rhnsd package and still have 
no luck.



---

Len Ewen

Systems Administrator 1

Information Technology

University of Indianapolis

(317) 788-3362



UIndyIT.jpg

Confidentiality Notice: This communication and/or its content are for 
the sole use of the intended recipient, and may be privileged, 
confidential, or otherwise protected from disclosure by law. If you are 
not the intended recipient, please notify the sender and then delete all 
copies of it. Unless you are the intended recipient, your use or 
dissemination of the information contained in this communication may be 
illegal.




On Wed, Jan 8, 2020 at 9:28 AM Len Ewen > wrote:


Ok, so why wouldn't the daemon be running?  I forced a check in by
installing and removing a package, which seemed to work fine, but if
it requires the daemon to be running constantly, I am assuming it
won't check in again unless I force it?  I didn't do anything
special to this box, I literally did a fresh minimal install and
installed the spacewalk server on one box and the client on another
to see if I could get it to work.

---

Len Ewen

Systems Administrator 1

Information Technology

University of Indianapolis

(317) 788-3362



UIndyIT.jpg

Confidentiality Notice: This communication and/or its content are
for the sole use of the intended recipient, and may be privileged,
confidential, or otherwise protected from disclosure by law. If you
are not the intended recipient, please notify the sender and then
delete all copies of it. Unless you are the intended recipient, your
use or dissemination of the information contained in this
communication may be illegal.



On Wed, Jan 8, 2020 at 9:21 AM Robert Paschedag
mailto:robert.pasche...@web.de>> wrote:

The daemon should be running. It should then check every
interval minutes if something has to be done. See also within
/etc/sysconfig/rhn/ for the interval. (Just right now know the
name of the config file). The minimum interval is 60 minutes.

Robert


⁣sent from my mobile device​


 Originale Nachricht 
Von: Len Ewen mailto:ew...@uindy.edu>>
Gesendet: Wed Jan 08 15:11:06 GMT+01:00 2020
An: spacewalk-list@redhat.com 
Betreff: Re: [Spacewalk-list] Spacewalk client not checking in
on CentOS 7

The rhnsd daemon isn't running, should it be constantly running
or does it
pause and then run again?  It is enabled, just not running.

---

Len Ewen

Systems Administrator 1

Information Technology

University of Indianapolis

(317) 788-3362

[image: UIndyIT.jpg]

Confidentiality Notice: This communication and/or its content
are for the
sole use of the intended recipient, and may be privileged,
confidential, or
otherwise protected from disclosure by law. If you are not the
intended
recipient, please notify the sender and then delete all copies
of it.
Unless you are the intended recipient, your use or dissemination
of the
information contained in this communication may be illegal.


On Wed, Jan 8, 2020 at 8:58 AM Michael Mraka
mailto:michael.mr...@redhat.com>>
wrote:

 > Len Ewen:
 > > I know this a stupid noob question but I have a problem. 
I've got a

 > clean
 > > built, fresh out of the box spacewalk 2.9 server and a 2.9
client.  The
 > > client checked in once, but hasn't checked again for the
last 16 hours.
 > 16
 > > hours seems like a long time for a check in to happen, but
I am not sure
 > > what is going on.  What am I missing?  Do I need to set up
a cron job to
 > > update or something?
 >
 > Hello,
 >
 > Check that rhnsd service is enabled and daemon is running.
 > You can also check manually if the client is able to connect
to the
 > spacewalk server:
 >   rhn_check -vv
 >
 >
 > Regards,
 >
 > --
 > Michael Mráka
 > System Management Engineering, Red Hat
 >
 > _

Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7

[Len Ewen]

Ok, so if I start the daemon, it checks in, then instantly dies. I look at
the osad file and nothing has updated and I cannot seem to find a log file
for rhnsd to see if something is going on there so what am I missing?  I've
removed and reinstalled the rhnsd package and still have no luck.


---

Len Ewen

Systems Administrator 1

Information Technology

University of Indianapolis

(317) 788-3362

[image: UIndyIT.jpg]

Confidentiality Notice: This communication and/or its content are for the
sole use of the intended recipient, and may be privileged, confidential, or
otherwise protected from disclosure by law. If you are not the intended
recipient, please notify the sender and then delete all copies of it.
Unless you are the intended recipient, your use or dissemination of the
information contained in this communication may be illegal.


On Wed, Jan 8, 2020 at 9:28 AM Len Ewen  wrote:

> Ok, so why wouldn't the daemon be running?  I forced a check in by
> installing and removing a package, which seemed to work fine, but if it
> requires the daemon to be running constantly, I am assuming it won't check
> in again unless I force it?  I didn't do anything special to this box, I
> literally did a fresh minimal install and installed the spacewalk server on
> one box and the client on another to see if I could get it to work.
>
> ---
>
> Len Ewen
>
> Systems Administrator 1
>
> Information Technology
>
> University of Indianapolis
>
> (317) 788-3362
>
> [image: UIndyIT.jpg]
>
> Confidentiality Notice: This communication and/or its content are for the
> sole use of the intended recipient, and may be privileged, confidential, or
> otherwise protected from disclosure by law. If you are not the intended
> recipient, please notify the sender and then delete all copies of it.
> Unless you are the intended recipient, your use or dissemination of the
> information contained in this communication may be illegal.
>
>
> On Wed, Jan 8, 2020 at 9:21 AM Robert Paschedag 
> wrote:
>
>> The daemon should be running. It should then check every interval minutes
>> if something has to be done. See also within /etc/sysconfig/rhn/ for the
>> interval. (Just right now know the name of the config file). The minimum
>> interval is 60 minutes.
>>
>> Robert
>>
>>
>> ⁣sent from my mobile device​
>>
>>
>>  Originale Nachricht 
>> Von: Len Ewen 
>> Gesendet: Wed Jan 08 15:11:06 GMT+01:00 2020
>> An: spacewalk-list@redhat.com
>> Betreff: Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7
>>
>> The rhnsd daemon isn't running, should it be constantly running or does it
>> pause and then run again?  It is enabled, just not running.
>>
>> ---
>>
>> Len Ewen
>>
>> Systems Administrator 1
>>
>> Information Technology
>>
>> University of Indianapolis
>>
>> (317) 788-3362
>>
>> [image: UIndyIT.jpg]
>>
>> Confidentiality Notice: This communication and/or its content are for the
>> sole use of the intended recipient, and may be privileged, confidential,
>> or
>> otherwise protected from disclosure by law. If you are not the intended
>> recipient, please notify the sender and then delete all copies of it.
>> Unless you are the intended recipient, your use or dissemination of the
>> information contained in this communication may be illegal.
>>
>>
>> On Wed, Jan 8, 2020 at 8:58 AM Michael Mraka 
>> wrote:
>>
>> > Len Ewen:
>> > > I know this a stupid noob question but I have a problem.  I've got a
>> > clean
>> > > built, fresh out of the box spacewalk 2.9 server and a 2.9 client.
>> The
>> > > client checked in once, but hasn't checked again for the last 16
>> hours.
>> > 16
>> > > hours seems like a long time for a check in to happen, but I am not
>> sure
>> > > what is going on.  What am I missing?  Do I need to set up a cron job
>> to
>> > > update or something?
>> >
>> > Hello,
>> >
>> > Check that rhnsd service is enabled and daemon is running.
>> > You can also check manually if the client is able to connect to the
>> > spacewalk server:
>> >   rhn_check -vv
>> >
>> >
>> > Regards,
>> >
>> > --
>> > Michael Mráka
>> > System Management Engineering, Red Hat
>> >
>> > ___
>> > Spacewalk-list mailing list
>> > Spacewalk-list@redhat.com
>> > https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>>
>> 
>>
>> ___
>> Spacewalk-list mailing list
>> Spacewalk-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>>
>> ___
>> Spacewalk-list mailing list
>> Spacewalk-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7

[Len Ewen]

Ok, so why wouldn't the daemon be running?  I forced a check in by
installing and removing a package, which seemed to work fine, but if it
requires the daemon to be running constantly, I am assuming it won't check
in again unless I force it?  I didn't do anything special to this box, I
literally did a fresh minimal install and installed the spacewalk server on
one box and the client on another to see if I could get it to work.

---

Len Ewen

Systems Administrator 1

Information Technology

University of Indianapolis

(317) 788-3362

[image: UIndyIT.jpg]

Confidentiality Notice: This communication and/or its content are for the
sole use of the intended recipient, and may be privileged, confidential, or
otherwise protected from disclosure by law. If you are not the intended
recipient, please notify the sender and then delete all copies of it.
Unless you are the intended recipient, your use or dissemination of the
information contained in this communication may be illegal.


On Wed, Jan 8, 2020 at 9:21 AM Robert Paschedag 
wrote:

> The daemon should be running. It should then check every interval minutes
> if something has to be done. See also within /etc/sysconfig/rhn/ for the
> interval. (Just right now know the name of the config file). The minimum
> interval is 60 minutes.
>
> Robert
>
>
> ⁣sent from my mobile device​
>
>
>  Originale Nachricht 
> Von: Len Ewen 
> Gesendet: Wed Jan 08 15:11:06 GMT+01:00 2020
> An: spacewalk-list@redhat.com
> Betreff: Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7
>
> The rhnsd daemon isn't running, should it be constantly running or does it
> pause and then run again?  It is enabled, just not running.
>
> ---
>
> Len Ewen
>
> Systems Administrator 1
>
> Information Technology
>
> University of Indianapolis
>
> (317) 788-3362
>
> [image: UIndyIT.jpg]
>
> Confidentiality Notice: This communication and/or its content are for the
> sole use of the intended recipient, and may be privileged, confidential, or
> otherwise protected from disclosure by law. If you are not the intended
> recipient, please notify the sender and then delete all copies of it.
> Unless you are the intended recipient, your use or dissemination of the
> information contained in this communication may be illegal.
>
>
> On Wed, Jan 8, 2020 at 8:58 AM Michael Mraka 
> wrote:
>
> > Len Ewen:
> > > I know this a stupid noob question but I have a problem.  I've got a
> > clean
> > > built, fresh out of the box spacewalk 2.9 server and a 2.9 client.  The
> > > client checked in once, but hasn't checked again for the last 16 hours.
> > 16
> > > hours seems like a long time for a check in to happen, but I am not
> sure
> > > what is going on.  What am I missing?  Do I need to set up a cron job
> to
> > > update or something?
> >
> > Hello,
> >
> > Check that rhnsd service is enabled and daemon is running.
> > You can also check manually if the client is able to connect to the
> > spacewalk server:
> >   rhn_check -vv
> >
> >
> > Regards,
> >
> > --
> > Michael Mráka
> > System Management Engineering, Red Hat
> >
> > ___
> > Spacewalk-list mailing list
> > Spacewalk-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
> 
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7

[Robert Paschedag]

The daemon should be running. It should then check every interval minutes if 
something has to be done. See also within /etc/sysconfig/rhn/ for the interval. 
(Just right now know the name of the config file). The minimum interval is 60 
minutes.

Robert


⁣sent from my mobile device​


 Originale Nachricht 
Von: Len Ewen 
Gesendet: Wed Jan 08 15:11:06 GMT+01:00 2020
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7

The rhnsd daemon isn't running, should it be constantly running or does it
pause and then run again?  It is enabled, just not running.

---

Len Ewen

Systems Administrator 1

Information Technology

University of Indianapolis

(317) 788-3362

[image: UIndyIT.jpg]

Confidentiality Notice: This communication and/or its content are for the
sole use of the intended recipient, and may be privileged, confidential, or
otherwise protected from disclosure by law. If you are not the intended
recipient, please notify the sender and then delete all copies of it.
Unless you are the intended recipient, your use or dissemination of the
information contained in this communication may be illegal.


On Wed, Jan 8, 2020 at 8:58 AM Michael Mraka 
wrote:

> Len Ewen:
> > I know this a stupid noob question but I have a problem.  I've got a
> clean
> > built, fresh out of the box spacewalk 2.9 server and a 2.9 client.  The
> > client checked in once, but hasn't checked again for the last 16 hours.
> 16
> > hours seems like a long time for a check in to happen, but I am not sure
> > what is going on.  What am I missing?  Do I need to set up a cron job to
> > update or something?
>
> Hello,
>
> Check that rhnsd service is enabled and daemon is running.
> You can also check manually if the client is able to connect to the
> spacewalk server:
>   rhn_check -vv
>
>
> Regards,
>
> --
> Michael Mráka
> System Management Engineering, Red Hat
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list




___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list


___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7

[Nicole Beck]

Hi Len,
I had the same problem with centos 7.  I think I had to enable and start the 
rhnsd.timer as well as rhnsd.service in order for the client to check in.

This is what I have in my notes.

systemctl enable rhnsd.service
systemctl start rhnsd.service

systemctl enable rhnsd.timer
systemctl start rhnsd.timer

[root@gonzo ~]# systemctl is-active rhnsd.timer
active
[root@gonzo ~]#
[root@gonzo ~]# systemctl is-enabled rhnsd.timer
enabled

[root@gonzo ~]# systemctl list-timers
NEXT LEFT  LAST PASSED UNIT
Wed 2019-05-29 13:50:43 EDT  5s left   n/a  n/asystemd-tmpfiles-clean.ti
Wed 2019-05-29 16:10:13 EDT  2h 19min left n/a  n/arhnsd.timer

Hope this helps.
Nicole



From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Brian Long
Sent: Wednesday, January 8, 2020 8:03 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7

On Wed, Jan 8, 2020 at 7:54 AM Len Ewen 
mailto:ew...@uindy.edu>> wrote:
I know this a stupid noob question but I have a problem.  I've got a clean 
built, fresh out of the box spacewalk 2.9 server and a 2.9 client.  The client 
checked in once, but hasn't checked again for the last 16 hours.  16 hours 
seems like a long time for a check in to happen, but I am not sure what is 
going on.  What am I missing?  Do I need to set up a cron job to update or 
something?

Look into setting up the optional osad.  
https://github.com/spacewalkproject/spacewalk/wiki/OsadHowTo

/Brian/

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7

[Len Ewen]

The rhnsd daemon isn't running, should it be constantly running or does it
pause and then run again?  It is enabled, just not running.

---

Len Ewen

Systems Administrator 1

Information Technology

University of Indianapolis

(317) 788-3362

[image: UIndyIT.jpg]

Confidentiality Notice: This communication and/or its content are for the
sole use of the intended recipient, and may be privileged, confidential, or
otherwise protected from disclosure by law. If you are not the intended
recipient, please notify the sender and then delete all copies of it.
Unless you are the intended recipient, your use or dissemination of the
information contained in this communication may be illegal.


On Wed, Jan 8, 2020 at 8:58 AM Michael Mraka 
wrote:

> Len Ewen:
> > I know this a stupid noob question but I have a problem.  I've got a
> clean
> > built, fresh out of the box spacewalk 2.9 server and a 2.9 client.  The
> > client checked in once, but hasn't checked again for the last 16 hours.
> 16
> > hours seems like a long time for a check in to happen, but I am not sure
> > what is going on.  What am I missing?  Do I need to set up a cron job to
> > update or something?
>
> Hello,
>
> Check that rhnsd service is enabled and daemon is running.
> You can also check manually if the client is able to connect to the
> spacewalk server:
>   rhn_check -vv
>
>
> Regards,
>
> --
> Michael Mráka
> System Management Engineering, Red Hat
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7

[Michael Mraka]

Len Ewen:
> I know this a stupid noob question but I have a problem.  I've got a clean
> built, fresh out of the box spacewalk 2.9 server and a 2.9 client.  The
> client checked in once, but hasn't checked again for the last 16 hours.  16
> hours seems like a long time for a check in to happen, but I am not sure
> what is going on.  What am I missing?  Do I need to set up a cron job to
> update or something?

Hello,

Check that rhnsd service is enabled and daemon is running.
You can also check manually if the client is able to connect to the spacewalk 
server:
  rhn_check -vv


Regards,

--
Michael Mráka
System Management Engineering, Red Hat

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Missing Fedora 31 client repositories for Spacewalk 2.9

[Michael Mraka]

Brian Long:
> Considering Spacewalk 2.9 was released in January 2019, what is the
> plan for 2.10?  Has Red Hat-sponsored Spacewalk development diminished
> since Red Hat Satellite 6.x is based on TheForeman and Red Hat
> Satellite 5.x is EOL in May 2020?

Hello,

We would like to release Spacewalk 2.10 with RHEL8 support (both client
and server). Unfortunately we have very limited resources to work on it
and I expect it will take some time.

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk client not checking in on CentOS 7

[Brian Long]

On Wed, Jan 8, 2020 at 7:54 AM Len Ewen  wrote:

> I know this a stupid noob question but I have a problem.  I've got a clean
> built, fresh out of the box spacewalk 2.9 server and a 2.9 client.  The
> client checked in once, but hasn't checked again for the last 16 hours.  16
> hours seems like a long time for a check in to happen, but I am not sure
> what is going on.  What am I missing?  Do I need to set up a cron job to
> update or something?
>

Look into setting up the optional osad.
https://github.com/spacewalkproject/spacewalk/wiki/OsadHowTo

/Brian/
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] Spacewalk client not checking in on CentOS 7

[Len Ewen]

I know this a stupid noob question but I have a problem.  I've got a clean
built, fresh out of the box spacewalk 2.9 server and a 2.9 client.  The
client checked in once, but hasn't checked again for the last 16 hours.  16
hours seems like a long time for a check in to happen, but I am not sure
what is going on.  What am I missing?  Do I need to set up a cron job to
update or something?

---

Len Ewen

Systems Administrator 1

Information Technology

University of Indianapolis

(317) 788-3362

[image: UIndyIT.jpg]

Confidentiality Notice: This communication and/or its content are for the
sole use of the intended recipient, and may be privileged, confidential, or
otherwise protected from disclosure by law. If you are not the intended
recipient, please notify the sender and then delete all copies of it.
Unless you are the intended recipient, your use or dissemination of the
information contained in this communication may be illegal.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Missing Fedora 31 client repositories for Spacewalk 2.9

[Brian Long]

Considering Spacewalk 2.9 was released in January 2019, what is the
plan for 2.10?  Has Red Hat-sponsored Spacewalk development diminished
since Red Hat Satellite 6.x is based on TheForeman and Red Hat
Satellite 5.x is EOL in May 2020?

https://access.redhat.com/support/policy/updates/satellite

/Brian/

On Wed, Jan 8, 2020 at 3:30 AM Michael Mraka  wrote:
>
> Neal Gompa:
> > Hey all,
> >
> > It seems we don't have client repositories for Fedora 31 for Spacewalk
> > 2.9. Can someone please build the client packages for Fedora 31 and
> > make them available?
>
> Fedora 31 had not been around when Spacewalk 2.9 was released therefore there
> are no client repositories.
> You can use Fedora 31 client from nightly repos.
> https://copr.fedorainfracloud.org/coprs/g/spacewalkproject/nightly-client/
>
> Regards,
>
> --
> Michael Mráka
> System Management Engineering, Red Hat
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list


___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Missing Fedora 31 client repositories for Spacewalk 2.9

[Michael Mraka]

Neal Gompa:
> Hey all,
> 
> It seems we don't have client repositories for Fedora 31 for Spacewalk
> 2.9. Can someone please build the client packages for Fedora 31 and
> make them available?

Fedora 31 had not been around when Spacewalk 2.9 was released therefore there
are no client repositories.
You can use Fedora 31 client from nightly repos.
https://copr.fedorainfracloud.org/coprs/g/spacewalkproject/nightly-client/

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list