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
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:
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/attachme
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
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,
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.
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
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
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
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
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,
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
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
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
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
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.
16 matches
Mail list logo
