If /etc/sysconfig/rhn/rhnsd is not there, then need to investigate the
package rhnsd. I would try and reinstall the rpm, and check to see if the
file is there.
If the file is not there:
What version of rhnsd is installed on the clients?
What files are being provided by the rpm? rpm -ql rhnsd
If the file is there:
Wait..... If it is no longer there after some time.
A mis-configured chef/puppet/automated action could be deleting
the file vs creating or updating the file.
If it is still there, some other items to look at:
Someone could have accidentally deleted the file (oops).
There could a custom RPM that is being installed on the impacted
systems that has a script which is deleting the file.
Thanks
From: Wachauer Harald <harald.wacha...@akm.at>
To: "spacewalk-list@redhat.com" <spacewalk-list@redhat.com>
Date: 02/19/2019 02:33 AM
Subject: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
Sent by: spacewalk-list-boun...@redhat.com
This email originated from outside of the company. Please use discretion
if opening attachments or clicking on links.
Phil,
Still a problem with the offline clients.
It looks like that the rhn daemon stops working after some time.
Redirecting to /bin/systemctl status rhnsd.service
● rhnsd.service - Spacewalk Server daemon
Loaded: loaded (/usr/lib/systemd/system/rhnsd.service; static; vendor
preset: disabled)
Active: inactive (dead)
And some more:
I have no /etc/sysconfig/rhn/rhnsd
[root@vie-srv-XXX log]# cd /etc/sysconfig/rhn/
[root@vie-srv-XXX rhn]# ls -la
total 24
drwxr-xr-x. 4 root root 4096 Feb 19 09:18 .
drwxr-xr-x. 7 root root 4096 Jan 23 16:48 ..
drwxr-xr-x. 4 root root 37 Jan 23 16:48 allowed-actions
drwxr-xr-x. 2 root root 37 Feb 14 12:19 clientCaps.d
-rw-------. 1 root root 129 Jan 29 16:48 osad-auth.conf.rpmsave
-rw-r--r--. 1 root root 1446 Nov 26 21:50 rhncfg-client.conf
-rw-------. 1 root root 1321 Jan 23 16:51 systemid
-rw-r--r--. 1 root root 1948 Jan 23 16:51 up2date
In the rhncfg-client.conf I can find a log directory: script_log_file =
/var/log/rhn/rhncfg-action-output.log
But even this log file does not exist……
Warm regards,
Harald
Von: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com>
Im Auftrag von p.cook...@bham.ac.uk
Gesendet: Donnerstag, 14. Februar 2019 14:46
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
No problem Harald. If you want to continue using rhnsd you can still
reduce the check-in time in /etc/sysconfig/rhn/rhnsd if you want though
(default is 240 mins):
# cat /etc/sysconfig/rhn/rhnsd
INTERVAL=240
#
Regards
Phil
From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com
> On Behalf Of harald.wacha...@akm.at
Sent: 14 February 2019 11:18
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
Hi Phil,
Thanks for your reply.
It looks like it was a rookie mistake.
I am new at Spacewalk and I followed the instructions here to register a
client.
https://github.com/spacewalkproject/spacewalk/wiki/RegisteringClients
Unfortunately there was no hint that you have to start the rhnsd service.
So I have started the service now and configured it to start
automatically.
And I need no osad at the moment. Every 4 hours check in is fine for me.
Thanks again,
Warm regards,
Harald
Von: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com>
Im Auftrag von p.cook...@bham.ac.uk
Gesendet: Donnerstag, 14. Februar 2019 10:01
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
Hi Harald
Were they ok originally, and stopped working properly, or are you just
trying to setup OSAD for the first time? Either way if you work through my
personal notes (for OSAD), below, it may help to identify your problem. If
everything has been done correctly it may be an infrastructure problem
though ie un-reliable network connection or NTP?
By default, the rhnsd daemon on a client system connects to the Spacewalk
server every four hours (see /etc/sysconfig/rhn/rhnsd) and performs any
updates or actions that have been scheduled. If you install the OSA
daemon, you can apply updates and actions to client systems immediately
from the Spacewalk server.
osa-dispatcher
Server-side service that determines when an osad client instance needs to
be pinged or run rhn_check and sends a message telling them to do so. This
is installed when Spacewalk is installed.
Open Source Architecture Daemon (OSAD)
Client-side service that responds to pings and runs rhn_check when told to
by osa-dispatcher.
See official documentation, at the following link, for more details:
https://github.com/spacewalkproject/spacewalk/wiki/OSADSetup
Install OSAD and related RHN/Spacewalk packages
# yum -y install osad rhncfg rhncfg-actions rhncfg-client
Spacewalk Actions Control - Enable Scheduled Actions
# rhn-actions-control --enable-all
Spacewalk Actions Control - Show Status
# rhn-actions-control --report
Start OSAD
# systemctl start osad.service OR service osad start
Enable OSAD
# systemctl enable osad.service OR chkconfig osad on
OSAD Log File
/var/log/osad
Hope this is of help
Phil
From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com
> On Behalf Of harald.wacha...@akm.at
Sent: 14 February 2019 08:22
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
Hi, Jonathan,
Looks good:
[root@vie-srv-log02 ~]# netstat -tn|grep 5222
tcp 0 0 172.21.0.181:46018 172.21.0.166:5222 ESTABLISHED
Nerveless the client is offline in spacewalk.
Warm regards,
Harald
Von: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com>
Im Auftrag von Jonathan Horne
Gesendet: Mittwoch, 13. Februar 2019 21:48
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
all your clients should have established traffic to the spacewalk server
on port 5222. it should stay in an established state.
[jhorne@dlp-log01 ~]$ netstat -tn|grep 5222
tcp 0 0 10.12.59.52:38718 10.12.59.64:5222 ESTABLISHED
From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com
> on behalf of Wachauer Harald <harald.wacha...@akm.at>
Sent: Wednesday, February 13, 2019 10:17:45 AM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
Hi all,
I have the problem that most of my systems (CentOS 6 & 7) are going
offline after approximately one day.
Only if I run rhn_check the systems come online again, but only for short
time.
I have tried to install osad service, the service is running but nerveless
the client is going offline.
Any help would be very appreciated.
Best regards,
Harald
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
**
This email and any attachments may contain information that is confidential
and/or privileged for the sole use of the intended recipient. Any use, review,
disclosure, copying, distribution or reliance by others, and any forwarding of
this email or its contents, without the express permission of the sender is
strictly prohibited by law. If you are not the intended recipient, please
contact the sender immediately, delete the e-mail and destroy all copies.
**
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
