Re: [Spacewalk-list] Can spacewalk support Redhat Linux 8, or can not ?

It really depends on what you mean by supported. There is no support team and Spacewalk 2.10 is currently the final version. Spacewalk 2.10 runs on RHEL 8 as Client Spacewalk Nightly runs on RHEL 8 as Server. Overal RHEL8 functionality can certainly be improved in many areas. Best wishes,

Re: [Spacewalk-list] Spacewalk Server 2.10

Not 100% sure on that but it sounds like your certificate was renewed? Do you have the matching correct root certificate installed? Von: "Stephen Weaver" An: "spacewalk-list" Gesendet: Mittwoch, 3. Juni 2020 12:27:17 Betreff: [Spacewalk-list] Spacewalk Server 2.10 Hi All Big problem,

Re: [Spacewalk-list] Kickstart File - Increase Root Partition Size

Hello Sulove, as far as I am aware, by default on RHEL it is using the full HDD as root after a /boot and a swap default. This is how I do custom partition my servers: Go to Systems --> Kickstart --> Profiles --> --> System Details --> Partitioning --> Partition Details Enter part

Re: [Spacewalk-list] CentOS 8.1 Clone Channels didn't work

So the "package" clone/ channe clone option from Spacewalk seems to > miss something ... the only way seems to clone it via "repo sync". > > Strange ... in Total it looks all not very usable for CentOS 8. > > Regards Mario > > > Am 2020-04-14 12:14, s

Re: [Spacewalk-list] CentOS 8.1 Clone Channels didn't work

Hello Mario, I can only assume what the cause is. Maybe try using the "clonebychannel" tool? Best wishes, Stefan - Ursprüngliche Mail - Von: "Mario Heininger" An: "spacewalk-list" Gesendet: Dienstag, 14. April 2020 11:51:26 Betreff: [Spacewalk-list] CentOS 8.1 Clone Channels didn't

Re: [Spacewalk-list] Problem Kickstarting CentOS 8.1 with Spacewalk 2.10

Hello Mario again, I noticed that I noted down the background for myself. Check out the reasoning here and let me know if you still have questions: https://www.bluhm-de.com/content/os-tools/en/applications/spacewalk/fixing-spacewalk-issues.html (section: Kickstart fails, last sentence) "Edit

Re: [Spacewalk-list] Problem Kickstarting CentOS 8.1 with Spacewalk 2.10

Hi Mario, I also worked on this. The solution is to edit the .treeinfo file in the kickstart folder and remove the unmentioned modules. I will look later on more details. Best wishes, Stefan - Ursprüngliche Mail - Von: "Mario Heininger" An: "spacewalk-list" Gesendet: Donnerstag, 9.

Re: [Spacewalk-list] Permanently remove package from subscribed channel

tion, is there a way to make a/one package not get pushed/synced to one particular system within a Spacewalk channel environment? If so, how? Regards, Sulove On 4/8/20, 11:15 AM, "Stefan Bluhm" wrote: Hello Sulove, check out the filters in the repository settings:

Re: [Spacewalk-list] Permanently remove package from subscribed channel

Hello Sulove, check out the filters in the repository settings: Channels --> Manage Software Channels --> Manage Repositories --> --> Filters (last field on the screen). - excludes + includes Best wishes, Stefan - Ursprüngliche Mail - Von: "Sulove Khanal" An: "spacewalk-list"

Re: [Spacewalk-list] spacewalk - GUI console login issue

r Gupta Professional 2 System Administrator (Linux) DXC Technology A 44/45, Galaxy Business Park Sector-62 Noida- 201301 India Mob: +91 – 9971101172 Advance Leave Notification : From: spacewalk-list-boun...@redhat.com On Behalf Of Stefan Bluhm Sent: Tuesday, March 31, 2020 7:09 PM

Re: [Spacewalk-list] spacewalk - GUI console login issue

Hello Ajay, I was accidentally able to reproduce this issue. On the server, check if all services are running (# spacewalk-service). Also check your disk space. Mine was full so you see this behaviour. Maybe this helps. Best wishes, Stefan Von: "GUPTA, AJAY KUMAR" An:

Re: [Spacewalk-list] HTTP Status 403 - Validation of CSRF security token failed on Webui on POST request on spacewalk 2.10

ebui on POST request on spacewalk 2.10 Stefan Bluhm: > Thank you Benoit! That also fixed the last of my known issues on RHEL8. > >> After investigating this problem comes from selinux was activated. I hope you did not fix it by disabling selinux but fixing selinux policy. -- Michael Mrá

Re: [Spacewalk-list] HTTP Status 403 - Validation of CSRF security token failed on Webui on POST request on spacewalk 2.10

Thank you Benoit! That also fixed the last of my known issues on RHEL8. Von: "BARRIERE Benoit" An: "spacewalk-list" Gesendet: Dienstag, 24. März 2020 00:43:55 Betreff: Re: [Spacewalk-list] HTTP Status 403 - Validation of CSRF security token failed on Webui on POST request on spacewalk

Re: [Spacewalk-list] channels and gpg key fields

Hello Laurence, we actually had the question here a few days ago. The field GPG key on the channel setup is information for the package installer on the CLIENT. It tells the package installer on the client where to find the GPG key for these packages. You have to enter it from the client

Re: [Spacewalk-list] GPG keys for CentOS channels in Spacewalk

Hi Chen, to clarify a bit more: > does this mean that for each package downloaded from Spacewalk onto the > Client, it is being signed by CentOS The signing is not happening when you download the file from Spacewalk. The signing has happened before it was uploaded to the source repository

Re: [Spacewalk-list] GPG keys for CentOS channels in Spacewalk

ompany/ensign-infosecurity/ ] [ https://youtu.be/9J7FkhXpb-4 ] [ https://www.facebook.com/EnsignGlobal ] E: wenkai_c...@ensigninfosecurity.com A: 30A Kallang Place, Level 9 Right Wing, Singapore 339213 From: spacewalk-list-boun...@redhat.com On Behalf Of Stefan Bluhm

Re: [Spacewalk-list] GPG keys for CentOS channels in Spacewalk

Hello Chen, the field GPG key on the channel setup is information for the package installer on the CLIENT. It tells the package installer on the client where to find the GPG key for these packages. You have to enter it from the client point of view (in the same format the client would use

Re: [Spacewalk-list] [External Sender] Re: missing public key

5 4DDD 4E12 B8CA AD32 9E0D 6E54 54FA I have updated the channel with this ID and Fingerprint but that made no difference. I'm very confused at this point. The client does have a public key installed which matched the version I get from the gpg --with-fingerprint command. On Mon, Feb 24, 202

Re: [Spacewalk-list] missing public key

Hello Larry, how did you provision the client? When provisioning, you do need to push the key to the client first. This is not necessarily done automatically. Best wishes, Stefan Von: "Larry Clegg" An: "spacewalk-list" Gesendet: Montag, 24. Februar 2020 20:20:37 Betreff:

Re: [Spacewalk-list] Too many open files while syncing Red hat repository on Spacewalk server 2.9

Hello Wenkai, I never experienced this issue myself. Maybe a restart would help. If this issue is happening frequently, check the file system limit (ulimit) to see if this might be the root cause. Best wishes, Stefan Von: "Wenkai Chen" An: "spacewalk-list" Gesendet: Montag, 24.

Re: [Spacewalk-list] can Spacewalk 2.9 be installed on RHEL 8

Hello Paul, depends on what you mean by "issues". You can maintain CentOS 8 clients (provisioning, configuration management). When it comes to package management, modules are not fully supported so you will not be able to properly manage packages. Best wishes, Stefan - Ursprüngliche

Re: [Spacewalk-list] Packages listed as available to update, but no update done (Appstream/module issue for redhat8?)

Hello Kent, this seems to be indeed related to the modules. You could either disable the modules on the machine and then the updates should install. Or try to enhance Spacewalk to act like that (the community would be grateful!). I can't think of any other options. Maybe others can? Best

Re: [Spacewalk-list] "Invalid function call attempted (code 6)"

Hello Paul, please check that your up2date config file contains the FQDN. Also make sure it is the same FQDN that the Spacewalk server is configured fore. Best wishes, Stefan Von: "Paul Greene" An: spacewalk-list@redhat.com Gesendet: Freitag, 14. Februar 2020 18:15:17 Betreff: Re:

[Spacewalk-list] Spacewalk 1.0 and External Oracle DB

Hi, can anyone confirm that the issue in 0.8 with external Oracle DBs has been fixed (Spacewalk 0.8 did not work with a database on a different server) Feedback/experience would be great. Best wishes Stefan ___ Spacewalk-list mailing list

Re: [Spacewalk-list] Spacewalk only works with local DB

Hi Bruce, thank you for your reply. My hostname is fine and I spent all weekend to isolate this problem. I am more than happy to give you access to my server to have a look yourself and get it configured. having the DB installed locally works. Even without the FQDN in the hosts file.

Re: [Spacewalk-list] Spacewalk only works with local DB

seems to have a problem with this. On 22.02.2010 15:08, Travis Camechis wrote: Its not an issue where your DB is locked down to only accept connections from localhost is it? On Mon, Feb 22, 2010 at 9:02 AM, Stefan Bluhm stefanblu...@alice-dsl.net mailto:stefanblu...@alice-dsl.net wrote

[Spacewalk-list] Spacewalk only works with local DB install

Hello all, these are my set-ups: a) Fedora 12, minimum install, DB on a different server b) Fedora 12, minimum install, DB on the same server c) Fedora 12, minimum install, dummy/empty DB running on the same server, actual DB on a different server when I run a), I get the error message:

Re: [Spacewalk-list] osa-dispatcher problems. no system ever, reports

Hi Josh, I have just now done a very fresh clean install: 1 VMWare Fedora 12 2 yum update 3 installation of spacewalk nightly (using an existing Oracle DB server on a different machine) I still get Starting osa-dispatcher: /usr/lib/python2.6/site-packages/jabber/jabber.py:68:

Re: [Spacewalk-list] osa-dispatcher problems. no system ever, reports

Thanks Josh, this is osa-dispatcher on v errorconflict xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' //error and this is the strace socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 6 socket(PF_NETLINK, SOCK_RAW, 0) = 7 bind(7, {sa_family=AF_NETLINK, pid=0, groups=}, 12) = 0

Re: [Spacewalk-list] osa-dispatcher problems. no system ever, reports

Hi Bruce, that did the job!! I added my IP and FQDN to the hosts file and now it works (new entry 192.168.0.28spacewalk.domain.com) This is rather strange behavior though as I am able to connect from the same machine via telnet and use the FQDN from the command line. Also this was a very

[Spacewalk-list] osa-dispatcher problems. no system ever reports

Hello, I am running the following setup: Clean VMWARE Fedora 12 32bit Spacewalk nightly built (updated just now) My clients never seem to check in (although they register fine) or execute any of the activities. When I run /usr/sbin/rhn-satellite restart I get the following message on the

Re: [Spacewalk-list] FW: Spacewalk-list Digest, Vol 21, Issue 19

Bluhm) 2. Re: osa-dispatcher problems. no system ever reports (Joshua Roys) -- Message: 1 Date: Mon, 08 Feb 2010 13:13:51 +0100 From: Stefan Bluhm stefanblu...@alice-dsl.net To: spacewalk-list@redhat.com Subject: [Spacewalk

Re: [Spacewalk-list] osa-dispatcher problems. no system ever reports

: Contents of Spacewalk-list digest... Today's Topics: 1. osa-dispatcher problems. no system ever reports (Stefan Bluhm) 2. Re: osa-dispatcher problems. no system ever reports (Joshua Roys) -- Message: 1 Date: Mon, 08 Feb

Re: [Spacewalk-list] osa-dispatcher problems. no system ever reports

14565/java 14258/java 14281/httpd 888/sshd 740/cupsd 14281/httpd db_verify authreg.db sm.db ; echo $? this seems to hang and not do anything. I cannot even ctrl+c it. On 08.02.2010 16:05, not applicable wrote: On 02/08/2010 09:47 AM, Stefan Bluhm wrote: This is what the logs state after a /usr

[Spacewalk-list] nightly built - reposync broken

Hi, my system: VMWARE updated Fedora 12 - 32bit nightly builts I ran the nightly update (9 hrs ago) and since then I get the following error message: 13/2842 : schroot-1.2.3-3.fc12-0.i686 ERRORException reported from spacewalk.bluhm-de.com Time: Mon Feb 8 20:31:14 2010 Exception type class

Re: [Spacewalk-list] osa-dispatcher problems. no system ever reports

Hi Joshua, thanks for this. Unfortunately, this didn't quite help. I restarted a couple of times and now I get two new error messages on stop: Stopping sm: [FAILED] Stopping c2s: [FAILED] and still the