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 G

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 p

Re: [Spacewalk-list] remote command responses are really slow

Hi This MAY be due to a similar issue someone has reported with systems going offline. Are you using OSAD? If so, my personal notes, below, 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 NT

[Spacewalk-list] Sequences going wrong

Hi! We're having a lot of troubble with spacewalk loosing sequences, or better: loosing sync within sequences. As spacewalk runs all looks ok for some time. then you may get "Internal server error" at a variety of places. Mostly it starts showing up in "Schedule -> Actions" click on one of the num

Re: [Spacewalk-list] Sequences going wrong

Hi Thomas The "Internal Server Error" appears to be a really generic and un-helpful message that comes out of Spacewalk in all sorts of scenario's! I haven't experienced your particular problem but, in the past, I've been advised to look at " /var/log/tomcat/catalina.out" to try and get a bette

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.

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...@

[Spacewalk-list] Getting an error when trying to delete a machine or doing a cobbler-sync

Hello. When trying to delete a system from the GUI, I get an error message to my email address. It's long so I'll post it in a pastebin. https://pastebin.com/ftkWw4mw This is rhn_taskomatic_daemon.log from my last restart. https://pastebin.com/sHG7Csp6 I've looked at cobbler settings, cobbler

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 (def

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