Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
If /etc/sysconfig/rhn/rhnsd isn’t there then either rhnsd hasn’t installed correctly or, like you say, someone or something has removed it afterwards. If that’s the case may be other related files could be missing too? Either way if you verify the package (rpm -V rhnsd) it should give you some indication of this. If it does find errors then yes, initially, just try re-installing it. Might be wise to check the other packages, that were installed for client registration, too: rhn-client-tools rhn-check rhn-setup m2crypto yum-rhn-plugin Regards Phil From: spacewalk-list-boun...@redhat.com On Behalf Of whten...@up.com Sent: 21 February 2019 00:22 To: spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients 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 mailto:harald.wacha...@akm.at>> To:"spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>" mailto: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<mailto: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<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> Im Auftrag von p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk> Gesendet: Donnerstag, 14. Februar 2019 14:46 An: spacewalk-list@redhat.com<mailto: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<mailto:spacewalk-list-boun...@redhat.com>mailto:spacewalk-list-boun...@redhat.com>> On Behalf Of harald.wacha...@akm.at<mailto:harald.wacha...@akm.at> Sent: 14 February 2019 11:18 To: spacewalk-list@redhat.com<mailto: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<mailto:spacewalk-list-boun...@redhat.com>mailto:spacewalk-list-boun...@redhat.com>> Im Auftrag von p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk> Gesendet: Donnerstag, 14. Februar 2019 10:01 An: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com> Betreff: Re: [Spacewalk-list] Spa
Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
Hi Harald I have Spacewalk 2.8 installed on a RHEL 7 server. I only need to register RHEL 6/7 and Oracle Linux 6/7 systems, rather than Centos, so this may possibly be why I’m not seeing your issue? However, if rhnsd has been installed, correctly, it should start automatically and /etc/sysconfig/rhn/rhnsd should be present too - /etc/sysconfig/rhn/rhnsd comes from the rhnsd package: # rpm -qf /etc/sysconfig/rhn/rhnsd rhnsd-5.0.37-1.el7.centos.x86_64 # Therefore, it may be wise to check the steps you took to register the client systems and/or verify the package: [root@its-n-swcli-01 ~]# rpm -V rhnsd [root@its-n-swcli-01 ~]# Regards Phil From: spacewalk-list-boun...@redhat.com On Behalf Of harald.wacha...@akm.at Sent: 19 February 2019 08:32 To: spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients 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<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> Im Auftrag von p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk> Gesendet: Donnerstag, 14. Februar 2019 14:46 An: spacewalk-list@redhat.com<mailto: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<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> On Behalf Of harald.wacha...@akm.at<mailto:harald.wacha...@akm.at> Sent: 14 February 2019 11:18 To: spacewalk-list@redhat.com<mailto: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<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> Im Auftrag von p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk> Gesendet: Donnerstag, 14. Februar 2019 10:01 An: spacewalk-list@redhat.com<mailto: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/Spac
Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
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 To: "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 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 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 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-contro
Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
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 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<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> On Behalf Of harald.wacha...@akm.at<mailto:harald.wacha...@akm.at> Sent: 14 February 2019 11:18 To: spacewalk-list@redhat.com<mailto: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<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> Im Auftrag von p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk> Gesendet: Donnerstag, 14. Februar 2019 10:01 An: spacewalk-list@redhat.com<mailto: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<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> On Behalf Of harald.wacha...@akm.at<mailto:harald.wacha...@akm.at> Sent: 14 February 2019 08:22 To: spacewalk-list@redhat.com<mailto: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 tcp0 0 172.21.0.181:46018 172.21.0.166:5222 ESTABLISHED Nerveless the client is offline in spacewalk. Warm regards, Harald Von: sp
Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
You can also cron the check-in. Also, if the hardware/profile sync is not put in cron, the hostname or IP changes are never updated. #!/bin/bash PATH=/usr/sbin:/sbin:/bin:/usr/bin # Implemented on the RedHat Linux based systems supported by the five spacewalk environments. ### #Hardware / profile sync 3rd Sunday of every month # With the # of systems each app server supports, cannot have all the systems running this in < 1 hour (oops). It will degrade the app server. # The load on the app server was 30+. Each app server specs. PROC: 2 Socket, 6 Core, hyper threaded RAM: 32 or 64 G DB: Off host. # minute=1 # hour=0 # date range = 14 - 22 # month all # day of week= Sunday 1 0 14-22 * 0 root [ -f /etc/redhat-release ] && [ `grep "release 4" /etc/redhat-release` ] && perl -le 'sleep rand 14400' && up2date --hardware >& /dev/null 1 0 14-22 * 0 root [ -f /etc/redhat-release ] && [[ `grep "release [567]" /etc/redhat-release` ]] && perl -le 'sleep rand 14400' && rhn-profile-sync >& /dev/null #rhn_check 1 0 * * * root [ -f /etc/redhat-release ] && [[ `grep "release [4567]" /etc/redhat-release` ]] && perl -le 'sleep rand 14400' && rhn_check >& /dev/null @reboot root [ -f /etc/redhat-release ] && [[ `grep "release [4567]" /etc/redhat-release` ]] && perl -le 'sleep rand 14400' && rhn_check >& /dev/null Thanks and good luck From: David Rock To: spacewalk-list@redhat.com Date: 02/14/2019 04:26 PM 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. IIRC, the lowest you can set it for is 60 minutes. — David Rock da...@graniteweb.com > On Feb 14, 2019, at 07:45, p.cook...@bham.ac.uk wrote: > > 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 > # ___ 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
Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
IIRC, the lowest you can set it for is 60 minutes. — David Rock da...@graniteweb.com > On Feb 14, 2019, at 07:45, p.cook...@bham.ac.uk wrote: > > 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 > # ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
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 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<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> Im Auftrag von p.cook...@bham.ac.uk<mailto:p.cook...@bham.ac.uk> Gesendet: Donnerstag, 14. Februar 2019 10:01 An: spacewalk-list@redhat.com<mailto: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<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> On Behalf Of harald.wacha...@akm.at<mailto:harald.wacha...@akm.at> Sent: 14 February 2019 08:22 To: spacewalk-list@redhat.com<mailto: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 tcp0 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<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> Im Auftrag von Jonathan Horne Gesendet: Mittwoch, 13. Februar 2019 21:48 An: spacewalk-list@redhat.com<mailto: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 tcp0 0 10.12.59.52:38718 10.12.59.64:5222 ESTABLISHED From: spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> on behalf of Wachauer Harald mailto:harald.wacha...@akm.at>> Sent: Wednesday, February 13, 2019 10:17:45 AM To: spacewalk-list@redhat.com<mailto: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
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 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<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> On Behalf Of harald.wacha...@akm.at<mailto:harald.wacha...@akm.at> Sent: 14 February 2019 08:22 To: spacewalk-list@redhat.com<mailto: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 tcp0 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<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> Im Auftrag von Jonathan Horne Gesendet: Mittwoch, 13. Februar 2019 21:48 An: spacewalk-list@redhat.com<mailto: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 tcp0 0 10.12.59.52:38718 10.12.59.64:5222 ESTABLISHED From: spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> on behalf of Wachauer Harald mailto:harald.wacha...@akm.at>> Sent: Wednesday, February 13, 2019 10:17:45 AM To: spacewalk-list@redhat.com<mailto: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
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 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 tcp0 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<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> Im Auftrag von Jonathan Horne Gesendet: Mittwoch, 13. Februar 2019 21:48 An: spacewalk-list@redhat.com<mailto: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 tcp0 0 10.12.59.52:38718 10.12.59.64:5222 ESTABLISHED From: spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> on behalf of Wachauer Harald mailto:harald.wacha...@akm.at>> Sent: Wednesday, February 13, 2019 10:17:45 AM To: spacewalk-list@redhat.com<mailto: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
Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
Hi, Jonathan, Looks good: [root@vie-srv-log02 ~]# netstat -tn|grep 5222 tcp0 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 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 tcp0 0 10.12.59.52:38718 10.12.59.64:5222 ESTABLISHED From: spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> mailto:spacewalk-list-boun...@redhat.com>> on behalf of Wachauer Harald mailto:harald.wacha...@akm.at>> Sent: Wednesday, February 13, 2019 10:17:45 AM To: spacewalk-list@redhat.com<mailto: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
Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
Am 13. Februar 2019 21:48:07 MEZ schrieb Jonathan Horne : >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 >tcp0 0 10.12.59.52:38718 10.12.59.64:5222 >ESTABLISHED > > > >From: spacewalk-list-boun...@redhat.com > on behalf of Wachauer Harald > >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. Don't you have "rhnsd" running? It should get in contact with your server at least every 4 hours (by default). Robert > > >Best regards, > >Harald -- sent from my mobile device ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
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 tcp0 0 10.12.59.52:38718 10.12.59.64:5222 ESTABLISHED From: spacewalk-list-boun...@redhat.com on behalf of Wachauer Harald 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
Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
Hi Harald, Do you have SELinux enabled on these systems? If so, have you verified that rhn_check has the correct context and it is allowed to run? Check the audit.log on these systems for details. From: spacewalk-list-boun...@redhat.com On Behalf Of Wachauer Harald Sent: Wednesday, February 13, 2019 11:18 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
[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
