Hi Gerald,
Thank you for the clarification. I see it being controlled by the system timer
now. Does this mean that /etc/sysconfig/rhn/rhnsd is no longer used i.e. rhnsd
ignores this file now?
-----Original Message-----
From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> On
Behalf Of Gerald Vogt
Sent: Thursday, April 25, 2019 12:12 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] FW: Spacewalk 2.9 clients
2.9 is using a systemd timer which runs the rhnsd.service, i.e. rhn_check:
$ systemctl status rhnsd.timer
● rhnsd.timer - Spacewalk periodic check timer
Loaded: loaded (/usr/lib/systemd/system/rhnsd.timer; enabled; vendor
preset: disabled)
Active: active (waiting) since Tue 2019-04-16 09:17:42 CEST; 1 weeks
2 days ago
$ systemctl status rhnsd
● rhnsd.service - Spacewalk Server daemon
Loaded: loaded (/usr/lib/systemd/system/rhnsd.service; static; vendor
preset: disabled)
Active: inactive (dead) since Thu 2019-04-25 16:23:01 CEST; 1h 47min ago
Process: 113537 ExecStart=/usr/sbin/rhn_check (code=exited,
status=0/SUCCESS)
Main PID: 113537 (code=exited, status=0/SUCCESS)
$ cat /usr/lib/systemd/system/rhnsd.timer
[Unit]
Description=Spacewalk periodic check timer
[Timer]
OnCalendar=00/4:00
RandomizedDelaySec=30min
[Install]
WantedBy=timers.target
-Gerald
On 25.04.19 18:05, William Hongach wrote:
> Hello again,
>
> Following up on yesterday's inquiry regarding compatibility, I installed the
> 2.9 client on a test SLES 12 SP4 machine. This is my first experience with
> 2.9 and I noticed something interesting. Following the online Spacewalk
> documentation, I installed all necessary packages for SLES successfully,
> including rhnsd yet there is no rhnsd binary installed on the system. Did
> something go wrong with the install?
>
> The 2.8 client package installed a binary /usr/sbin/rhnsd that started as
> rhnsd.service under systemd. This obviously called rhn_check at the
> frequency detailed in /etc/sysconfig/rhn/rhnsd. Our 2.9 installation of the
> rhnsd package on SLES 12 SP4 did not install the binary nor is rhnsd.service
> running. The system is checking in at the expected frequency according to
> the Spacewalk server, yet no scheduled tasks queued on the server are being
> picked up by this client. Running rhn_check manually picks up queued tasks.
>
> I am looking for some feedback with someone familiar with the 2.9 client
> install on SLES 12 SP4. Is this a bug with the rhnsd package, problem with
> installation, or perhaps things work differently now? Thanks in advance.
>
>
> -----Original Message-----
> From: spacewalk-list-boun...@redhat.com
> <spacewalk-list-boun...@redhat.com> On Behalf Of William Hongach
> Sent: Wednesday, April 24, 2019 9:53 AM
> To: spacewalk-list@redhat.com
> Subject: [Spacewalk-list] Spacewalk 2.9 clients
>
> Hello,
>
> Can anyone confirm if Spacewalk 2.9 clients can communicate with a Spacewalk
> 2.8 server? I ask because we currently have a 2.8 environment, but we are
> ready to deploy some SLES 12 SP4 servers. The client available at
> download.opensuse.org for SLES 12 SP4 is version 2.9.
>
> The majority of our SLES environment remains SLES 12 SP3 at this time so we
> would prefer to keep our Spacewalk server at 2.8 until we plan for a future
> migration. Any insight into the 2.9 client backwards compatibility would be
> appreciated. Thanks.
>
> _______________________________________________
> 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
