[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 <robert.paschedag at 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 <ewenf at uindy.edu>
> Gesendet: Wed Jan 08 15:11:06 GMT+01:00 2020
> An: spacewalk-list at 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 <michael.mraka at 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
> >
> > _______________________________________________
> > Spacewalk-list mailing list
> > Spacewalk-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20200108/2f06188f/attachment.htm>