Any tool available to check
        On Mon, 18 Feb 2019 18:17:45,  Thomas Schweikle
<> wrote:


>Is there any tool available to check spacewalk database for consistency
and for being complete (all >tables having all columns spacewalk awaits)?


Well, if you're wondering about schema completeness, as long as you're
using Postgres, there's a number of free DB design tools that do round
trip engineering that you could try.
Just build and initialize a fresh database for your version, then reverse
engineer it into a model, and compare that with your existing database.


Message: 2
Date: Tue, 19 Feb 2019 08:31:46 +0000
From: Wachauer Harald <>
To: "" <>
Subject: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients
Message-ID: <>
Content-Type: text/plain; charset="iso-2022-jp"


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 =

But even this log file does not exist??

Warm regards,


Von: <>
Im Auftrag von
Gesendet: Donnerstag, 14. Februar 2019 14:46
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


m>> On Behalf Of<>
Sent: 14 February 2019 11:18
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

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
And I need no osad at the moment. Every 4 hours check in is fine for me.

Thanks again,

Warm regards,


m>> Im Auftrag von<>
Gesendet: Donnerstag, 14. Februar 2019 10:01
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.

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:

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

Hope this is of help

m>> On Behalf Of<>
Sent: 14 February 2019 08:22
Subject: Re: [Spacewalk-list] Spacewalk 2.8 | Offline Clients

Hi, Jonathan,

Looks good:

[root@vie-srv-log02 ~]# netstat -tn|grep 5222
tcp        0      0

Nerveless the client is offline in spacewalk.

Warm regards,


m>> Im Auftrag von Jonathan Horne
Gesendet: Mittwoch, 13. Februar 2019 21:48
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

m>> on behalf of Wachauer Harald
Sent: Wednesday, February 13, 2019 10:17:45 AM
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

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,


-------------- next part --------------
An HTML attachment was scrubbed...


Spacewalk-list mailing list

End of Spacewalk-list Digest, Vol 129, Issue 31

Spacewalk-list mailing list

Reply via email to