Good Afternoon,
From the background you have listed, Spacewalk on Oracle Linux or Uyuni on
openSUSE / SLES could be viable alternatives for you to consider. Hope this
helps.
From: spacewalk-list-boun...@redhat.com On
Behalf Of Emmett Hogan
Sent: Wednesday, December 16, 2020 2:18 PM
To:
CEST schrieb William Hongach:
> Hi Robert,
>
> There is no error on the command line when using rhnpush and the
> packages do not make it into the channel. There is, however, the
> issue of certain packages (some not all) which will not upload and
> timeout after three trie
when running the rhnpush or do the packages just don't
make it into the channel?
You should take a look into the PostgreSQL logs in /var/lib/pgsql/data/log and
look for errors.
Robert
sent from my mobile device
Originale Nachricht
Von: William Hongach
Gesendet: Wed
Good Morning,
Is anyone experiencing issues with pushing SLES 12 SP5 packages to Spacewalk
via rhnpush? We stage our updates in a Spacewalk 2.8 server and this is our
first attempt to push SP5 updates but it does not appear to work. We are
successfully pushing SLES 12 SP3, SP4, SLES 15 SP1
Hello,
Not directly. The method I use for SLES 12 and 15 is to sync the target repos
to a local SMT server using smt-mirror, then use a scripted cron job to push
these package updates to custom Spacewalk channels via rhnpush. It's not
elegant but it works as a staging process with granular
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:
Hello,
I can confirm that my 2.9 clients are checking in with the 2.8 server
successfully. I did notice a change in the frequency of rhn_check, however.
It now uses rhnsd.timer which may account for the change in behavior that
you're seeing.
-Original Message-
From:
Hello,
I experience the same issue with the 2.8 web interface. It would appear to be
a bug as the column is labeled "Updates" but only tracks Errata. I would
welcome a fix in 2.8 and 2.9 repositories.
From: spacewalk-list-boun...@redhat.com On
Behalf Of Jay McCanta
Sent: Tuesday, June 25,
Hello,
I am curious to learn what specific benefits you are seeking to run in a
container versus a traditional virtual machine given the usual Spacewalk model.
It seems like an interesting endeavor and perhaps a worthwhile discussion.
From: spacewalk-list-boun...@redhat.com On
Behalf Of
, Jun 11, 2019 at 5:00 PM William Hongach
mailto:william.hong...@marist.edu>> wrote:
Hello,
Add all of the target systems to the SSM as Robert suggested, then run the
following from the server:
spacecmd system_addchildchannels ssm
This should subscribe all of the systems currently in t
?
On Thu, Jun 13, 2019 at 1:02 PM William Hongach
mailto:william.hong...@marist.edu>> wrote:
Hello,
I suppose you could run rhn_check out of cron if you did not want rhnsd to
schedule it.
From:
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>
mailto:sp
Hello,
I suppose you could run rhn_check out of cron if you did not want rhnsd to
schedule it.
From: spacewalk-list-boun...@redhat.com On
Behalf Of Paul Greene
Sent: Thursday, June 13, 2019 12:31 PM
To: Spacewalk-list@redhat.com
Subject: [Spacewalk-list] Is the rhnsd service required to be
] Best Practice for adding a child Channel?
Hey! Thanks for the reply! I'm asking about the scenario in which a system is
already registered and a new child channel is added . . .
On Tue, Jun 11, 2019 at 4:36 PM William Hongach
mailto:william.hong...@marist.edu>> wrote:
Hello,
If the
Hello,
If the child channel is already associated with the activation key at the time
of client registration, the client should subscribe to the base and child
channels simultaneously if things are working correctly. If you want to
retroactively associate previously registered clients with a
periodic check timer
[Timer]
OnCalendar=00/4:00
RandomizedDelaySec=30min
[Install]
WantedBy=timers.target
-Gerald
On 25.04.19 18:05, William Hongach wrote:
> Hello again,
>
> Following up on yesterday's inquiry regarding compatibility, I installed the
> 2.9 client on a test SLES 12
Hello,
Can anyone confirm if Spacewalk 2.9 clients can communicate with a Spacewalk
2.8 server? I ask because we currently have a 2.8 environment, but we are
ready to deploy some SLES 12 SP4 servers. The client available at
download.opensuse.org for SLES 12 SP4 is version 2.9.
The majority
Hi,
You can back up the database using:
db-control online-backup $filename
And this Perl script should pull in the credentials that Robert referenced in
your /etc/rhn/rhn.conf file. There should be no need to log into the postgres
database manually.
From: spacewalk-list-boun...@redhat.com
An alternative that I prefer would be to modify spacewalk.css on each server to
place an image or name value relating to the specific server in the header
class. This way that change would propagate to every page within the Spacewalk
portal as feedback to the user regarding which server they
Welcome,
I cannot answer any specifics regarding Oracle Linux as I do not have that
distribution in our Spacewalk environment, but here is a link to the Spacewalk
user documentation which you may find useful regarding its features:
https://spacewalkproject.github.io/documentation.html
From:
Good Morning All,
I noticed something interesting in the web gui of our Spacewalk 2.8 server.
I'm actually surprised that I did not notice it sooner. If I change the IP
address of a client, this change is not reflected in Systems > Details >
Overview > System Info. This same outdated
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,
want the new client to subscribe automatically (I use
the name "1-ubuntu18" here for example)
- Install the needed packages (read mentioned archive message above)
- Register the system with "rhnreg_ks --activationkey=1-ubuntu18
--serverUrl=https:///XMLRPC"
That should be it.
Robert
Hi James,
I posted a similar inquiry a few weeks ago. I have difficulty getting Debian
clients to play nicely with Spacewalk and I haven’t found an over abundance of
related documentation online for managing Debian/Ubuntu. From previous list
traffic, I know we have some active users out
Good Afternoon,
I am currently managing RHEL and SLES within Spacewalk, but I would like to
expand this to Debian clients as well. I did some initial research and I have
discovered documentation that is either out of date or expired/broken links.
Can someone direct me to useful, reasonably
Hello,
To clarify, are you referring to packages that have been downloaded locally and
pushed to Spacewalk? If so, an unwanted package that is no longer part of a
software channel can be listed and removed as follows:
spacecmd package_listorphans
spacecmd package_removeorphans
This will
Hello,
Have you checked to see if this is an selinux issue? If you have selinux set
to enforcing, you can look for messages relating to rhnsd and rhn_check in
/var/log/audit/audit.log.
The context for rhnsd should be rhnsd_exec_t and rhn_check should be rpm_exec_t.
From:
5, 2018 9:25 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Metadata backups
William Hongach:
> Good Morning,
>
> I am looking to back up the pgsql database that stores Spacewalk metadata. I
> used most (if not all) of the default options upon installation, and I wan
to
satellite? Is that right?
Jeff
From:
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>
mailto:spacewalk-list-boun...@redhat.com>>
on behalf of William Hongach
mailto:william.hong...@marist.edu>>
Sent: Tuesday, Nove
Hi Phil,
I use Spacewalk to centrally manage multiple distributions and different major
releases within each distribution, as you are seeking to accomplish.
Understanding that the Linux server running Spacewalk would not have access to
all of the different proprietary subscriptions, this was
Kaempf:
> * William Hongach [Sep 11. 2018 14:21]:
> > Hi Klaus,
> >
> > Any progress on the python3-usix libraries? If I can assist with
> > testing, let me know.
> The Uyuni team is working on it and should be finished by end of this
> week.
>
> Kla
Klaus,
Sounds good. Thanks for the update!
-Original Message-
From: spacewalk-list-boun...@redhat.com On
Behalf Of Klaus Kaempf
Sent: Wednesday, September 12, 2018 3:27 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Missing RPMs for SLE_15
* William Hongach [Sep 11
Hi Klaus,
Any progress on the python3-usix libraries? If I can assist with testing, let
me know.
-Original Message-
From: spacewalk-list-boun...@redhat.com On
Behalf Of Klaus Kaempf
Sent: Friday, August 31, 2018 2:33 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list]
Subject: Re: [Spacewalk-list] Missing RPMs for SLE_15
* William Hongach [Aug 30. 2018 15:20]:
>
> Will these fixes be uploaded to the Spacewalk 2.8 repo at
> download.opensuse.org, or will they be slated for the future release of
> Spacewalk 2.9? Let me know if I can assist with test
RPMs for SLE_15
* William Hongach [Aug 28. 2018 20:36]:
> Problem: nothing provides python3-spacewalk-usix needed by
> python3-rhncfg-5.10.122-4.2.noarch
That's another packaging bug since there's no python3-variant being build.
Sorry for the mess.
Klaus
--
SUSE Linux GmbH, GF: Felix Imend
be
needed for spacewalk functionality I don't use.
Regards,
Javier
Von:
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von William Hongach
Gesendet: Dienstag, 28. August 2018 22:35
An: spacewalk-list@redh
Hello,
This may depend on what distribution you are using. For example, I can confirm
that the spacewalk-client 2.8 repo has the rhncfg-actions package for RHEL 6,
RHEL 7 and SLES 12 (noarch), but not sure about other distros.
From: spacewalk-list-boun...@redhat.com On
Behalf Of Guy Matz
Hi Jason,
The check-in interval is controlled by the INTERVAL variable in
/etc/sysconfig/rhn/rhnsd. By default, I believe it is set to INTERVAL=240 (4
hrs). Have you checked this value on the affected clients to determine if it
is behaving as configured?
I believe rhnsd will -not- check in
Hi All,
I ran into a snag getting OpenSCAP scanning to work for our SLES 12SP3 clients.
I ran "zypper install spacewalk-oscap" and receive the following error:
"Problem: nothing provides openscap-scanner needed by
spacewalk-oscap-2.8.8-4.1.noarch"
Our architecture is s390x so it is using the
boun...@redhat.com] Im Auftrag von William Hongach
Gesendet: Donnerstag, 28. Juni 2018 15:15
An: 'spacewalk-list@redhat.com'
mailto:spacewalk-list@redhat.com>>
Betreff: Re: [Spacewalk-list] Adding SLE_SP3 client
Hi Javier,
I am pointed to that repository as per the doc for registering
use.org/repositories/systemsmanagement:/spacewalk:/
Regards,
Javier
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von William Hongach
Gesendet: Mittwoch, 27. Juni 2018 21:17
An: spacewalk-list@redhat.com
Betreff: [Spacewalk-list] Adding SLE_SP3 clien
Hello all,
I have a working Spacewalk server that is able to serve packages to RHEL
clients. I am now attempting to get some SLES clients registered with the
server. Following the documentation for registering clients, I pointed our
SLE_SP3 host to the correct zypper repo at opensuse.org,
41 matches
Mail list logo
