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, Stefan Von: "崔涛" An: "spacewalk-list" Gesendet: Sonntag, 21. Juni 2020 15:36:51 Betreff: [Spacewalk-list] Can spacewalk support Redhat Linux 8, or can not ? ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
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, just upgraded from 2.9 to 2.10 not I get a SSL privacy notice in my browser every time I click on any button? If any one can point me in the right direction. ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
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 /boot --fstype=ext4 --size=500 part pv.01 --grow --size=1 part swap --size=1000 --maxsize=2000 volgroup vg_main --pesize=4096 pv.01 logvol /var/log --fstype=ext4 --name=lv_log --vgname=vg_main --size=1000 logvol / --fstype=ext4 --name=lv_root --vgname=vg_main --size=1 --grow logvol swap --name=lv_swap --vgname=vg_main --size=2016 This creates: - /boot 500MB as ext4 - swap between 1GB to 2GB (I think this is autoscaled to memory 1:1) - /log 1GB as ext4 - / [root] for the rest I hope this helps. Best wishes, Stefan Von: "Sulove Khanal" An: "spacewalk-list" Gesendet: Donnerstag, 14. Mai 2020 15:22:29 Betreff: [Spacewalk-list] Kickstart File - Increase Root Partition Size Hello, I’m looking to increase the size of the root partition in my Spacewalk kickstart file to 20GB. It is currently defaulted to 8GB when I boot up a new VM based off the kickstart file. The kickstart is also set to autopart –type=lvm. I am using Centos 7. I haven’t found how to increase the size of the root partition while still using the autopart option in the kickstart from my research online. Is this possible? Thank you, Sulove ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] CentOS 8.1 Clone Channels didn't work
To me, this sounds like module "issues"/works as designed. Check out if modules are enabled/disabled for these packages and in which modules these are contained. If you have locally modules enabled, updates will show in Spacewalk but not on the client. So start digging in that direction. Here some fun commands to try out dnf module list dnf module info (try rhn-tools) dnf module disable dnf module enable dnf module install dnf module <(choose from 'list', 'update', 'install', 'reset', 'disable', 'enable', 'provides', 'info', 'remove')> Good Luck - Ursprüngliche Mail - Von: "Mario Heininger" An: "spacewalk-list" Gesendet: Dienstag, 14. April 2020 17:13:45 Betreff: Re: [Spacewalk-list] CentOS 8.1 Clone Channels didn't work I am facing more and more Problems. I see an osad-5.11.110 Package in the spacewalk-client repo ... CentOS 8 Server is connected also to that Channel. But the Server see only osad-5.10 from appstreams ... Also if i look with a dnf repo-packages test-centos-81-64-spacewalktools list i didn't see that osad Package which is in the channel. I checked the REPO Files on the Spacewalk ... there is the Package included. if i add directly the spacewalk-client repository from the Internet -> Client doesn't see that osad Package. Strange things going on with CentOS-8 ... Am 2020-04-14 12:49, schrieb Mario Heininger: > Hi Stefan, > > well clonebychannel Tool ? What did you mean ? > > I figured out that it is working if i avoid "channel_sync" on spacecmd > or GUI ! Instead setup a Repository pointing to to the Base CentOS 8.1 > then add the repository to the Clone Channel. > > Sync conntent with normal Repo Sync -> Still working. > > 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, schrieb Stefan Bluhm: >> 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 work >> >> Hello, >> >> i have a new Problem. i Synced the CentOS 8.1 to a Channel Structure: >> Base 8.1 - No packages >> --Server >> --Streams >> --Spacewalktools >> >> I install a Client via Kickstart from that -> Is working. >> >> I cloned the channels to a New Set of Channels: >> TEST - Base 8.1 - No Packages >> --Server >> --Streams >> --Spacewalktools >> >> Then i made a "spacecmd channel_sync base-server test-server" and the >> same with Streams and Spacewalk Tools. >> >> If i switch the System to the Cloned TEST Channels Package >> Installs/UPdate didn't work any mor. >> The Problem seems that the channel_sync is loosing the Steam/Group >> informations: >> >> TEST-CENTOS 8 - 64 Bit - All Releases >> 3.2 kB/s | >> 251 >> B 00:00 >> TEST-CENTOS 8.1 - 64 Bit - AppStream >>50 MB/s | >> 7.9 >> MB 00:00 >> TEST-CENTOS 8.1 - 64 Bit - EPEL >>47 MB/s | >> 8.1 >> MB 00:00 >> TEST-CENTOS 8.1 - 64 Bit - Server >>39 MB/s | >> 5.8 >> MB 00:00 >> TEST-CENTOS 8.1 - 64 Bit - Spacewalk Tools >> 347 kB/s | >> 25 >> kB 00:00 >> @modulefailsafe >> Name Stream >> Profiles Summary >> satellite-5-client 1.0 [e] >> common, gui Red Hat Satellite 5 client packages >> >> Hint: [d]efault, [e]nabled, [x]disabled, [i]nstalled >> >> That looks different to the output when it is connected to the >> orriginal >> Synced channels: >> CENTOS 8 - 64 Bit - All Releases >> 1.9 kB/s | >> 251 >> B 00:00 >> CENTOS 8.1 - 64 Bit - AppStream >> 6.7 MB/s | >> 8.7 >> MB 00:0
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 work Hello, i have a new Problem. i Synced the CentOS 8.1 to a Channel Structure: Base 8.1 - No packages --Server --Streams --Spacewalktools I install a Client via Kickstart from that -> Is working. I cloned the channels to a New Set of Channels: TEST - Base 8.1 - No Packages --Server --Streams --Spacewalktools Then i made a "spacecmd channel_sync base-server test-server" and the same with Streams and Spacewalk Tools. If i switch the System to the Cloned TEST Channels Package Installs/UPdate didn't work any mor. The Problem seems that the channel_sync is loosing the Steam/Group informations: TEST-CENTOS 8 - 64 Bit - All Releases 3.2 kB/s | 251 B 00:00 TEST-CENTOS 8.1 - 64 Bit - AppStream 50 MB/s | 7.9 MB 00:00 TEST-CENTOS 8.1 - 64 Bit - EPEL 47 MB/s | 8.1 MB 00:00 TEST-CENTOS 8.1 - 64 Bit - Server 39 MB/s | 5.8 MB 00:00 TEST-CENTOS 8.1 - 64 Bit - Spacewalk Tools 347 kB/s | 25 kB 00:00 @modulefailsafe Name Stream Profiles Summary satellite-5-client 1.0 [e] common, gui Red Hat Satellite 5 client packages Hint: [d]efault, [e]nabled, [x]disabled, [i]nstalled That looks different to the output when it is connected to the orriginal Synced channels: CENTOS 8 - 64 Bit - All Releases 1.9 kB/s | 251 B 00:00 CENTOS 8.1 - 64 Bit - AppStream 6.7 MB/s | 8.7 MB 00:01 CENTOS 8.1 - 64 Bit - EPEL 14 MB/s | 8.7 MB 00:00 CENTOS 8.1 - 64 Bit - Server 15 MB/s | 6.1 MB 00:00 CENTOS 8.1 - 64 Bit - Spacewalk Tools 207 kB/s | 25 kB 00:00 CENTOS 8.1 - 64 Bit - AppStream Name StreamProfiles Summary 389-ds 1.4 389 Directory Server (base) ant 1.10 [d] common [d] Java build tool container-tools rhel8 [d] common [d] Common tools and dependencies for container runtimes container-tools 1.0 common [d] Common tools and dependencies for container runtimes [...] Seems i miss something or channel cloning for staging isn't possible any more with CentOS 8 on the Spacewalk ? What i see is that on the orriginal CENTOS Channels the Repodata are bigger - seems the softwarechannel_sync didn't do the job correctly here. Regards Mario -- Mario Heininger e-Mail: ma...@mediatronix.de D - 14165 Berlin - GermanyInternet: maja-on-tour.de ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
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 .treeinfo in the kickstart folder and remove the variants references to other repositories (i.e. Appstream for CentOS 8)" Also make sure that the .treeinfo exists. Best wishes, Stefan - Ursprüngliche Mail - Von: "Mario Heininger" An: "spacewalk-list" Gesendet: Donnerstag, 9. April 2020 16:21:03 Betreff: [Spacewalk-list] Problem Kickstarting CentOS 8.1 with Spacewalk 2.10 Hello, i am trying Kickstarting a CentOS 8.1 System with Spacewalk 2.10 but the Installation stopped with "error setting up software source". From the Apache Log i see the following 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-spacewalktools/centos-81-64-server/repodata/repomd.xml HTTP/1.1" 200 871 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-spacewalktools/centos-81-64-server/repodata/filelists.xml.gz HTTP/1.1" 200 12738 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-spacewalktools/centos-81-64-server/repodata/primary.xml.gz HTTP/1.1" 200 12755 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-appstream/centos-81-64-server/repodata/repomd.xml HTTP/1.1" 200 1428 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-appstream/centos-81-64-server/repodata/comps.xml HTTP/1.1" 200 467367 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-appstream/centos-81-64-server/repodata/primary.xml.gz HTTP/1.1" 200 1606656 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-appstream/centos-81-64-server/repodata/modules.yaml HTTP/1.1" 200 306772 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-appstream/centos-81-64-server/repodata/filelists.xml.gz HTTP/1.1" 200 6719436 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-server/centos-81-64-server/repodata/repomd.xml HTTP/1.1" 200 1228 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-server/centos-81-64-server/repodata/comps.xml HTTP/1.1" 200 297154 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-server/centos-81-64-server/repodata/filelists.xml.gz HTTP/1.1" 200 3306395 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-server/centos-81-64-server/repodata/primary.xml.gz HTTP/1.1" 200 2756593 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:19 +0200] "GET /ks/dist/AppStream/x86_64/os/repodata/repomd.xml HTTP/1.1" 404 5051 "-" "libdnf" The last one with the 404 is the point where the Anaconda is stopping - and yes, this path is wrong - but i don't know from where it comes. The Pathes before are good and as we see there is allready appstream included. Any hint what's going on there or what's the Problem is ? Best regards Mario -- Mario Heininger e-Mail: ma...@mediatronix.de D - 14165 Berlin - GermanyInternet: maja-on-tour.de ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
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. April 2020 16:21:03 Betreff: [Spacewalk-list] Problem Kickstarting CentOS 8.1 with Spacewalk 2.10 Hello, i am trying Kickstarting a CentOS 8.1 System with Spacewalk 2.10 but the Installation stopped with "error setting up software source". From the Apache Log i see the following 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-spacewalktools/centos-81-64-server/repodata/repomd.xml HTTP/1.1" 200 871 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-spacewalktools/centos-81-64-server/repodata/filelists.xml.gz HTTP/1.1" 200 12738 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-spacewalktools/centos-81-64-server/repodata/primary.xml.gz HTTP/1.1" 200 12755 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-appstream/centos-81-64-server/repodata/repomd.xml HTTP/1.1" 200 1428 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-appstream/centos-81-64-server/repodata/comps.xml HTTP/1.1" 200 467367 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-appstream/centos-81-64-server/repodata/primary.xml.gz HTTP/1.1" 200 1606656 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-appstream/centos-81-64-server/repodata/modules.yaml HTTP/1.1" 200 306772 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-appstream/centos-81-64-server/repodata/filelists.xml.gz HTTP/1.1" 200 6719436 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-server/centos-81-64-server/repodata/repomd.xml HTTP/1.1" 200 1228 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-server/centos-81-64-server/repodata/comps.xml HTTP/1.1" 200 297154 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-server/centos-81-64-server/repodata/filelists.xml.gz HTTP/1.1" 200 3306395 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:18 +0200] "GET /ks/dist/child/centos-81-64-server/centos-81-64-server/repodata/primary.xml.gz HTTP/1.1" 200 2756593 "-" "libdnf" 192.168.41.231 - - [09/Apr/2020:14:48:19 +0200] "GET /ks/dist/AppStream/x86_64/os/repodata/repomd.xml HTTP/1.1" 404 5051 "-" "libdnf" The last one with the 404 is the point where the Anaconda is stopping - and yes, this path is wrong - but i don't know from where it comes. The Pathes before are good and as we see there is allready appstream included. Any hint what's going on there or what's the Problem is ? Best regards Mario -- Mario Heininger e-Mail: ma...@mediatronix.de D - 14165 Berlin - GermanyInternet: maja-on-tour.de ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Permanently remove package from subscribed channel
The way I do that is via the command line on the system: yum versionlock [1]. You might also want to create a channel copy and assign the system to that specific channel. You can also lock the complete system via Spacewalk, but I don't think you are looking for that. [] 1https://access.redhat.com/solutions/98873 - Ursprüngliche Mail - Von: "Sulove Khanal" An: "spacewalk-list" Gesendet: Mittwoch, 8. April 2020 20:11:50 Betreff: Re: [Spacewalk-list] Permanently remove package from subscribed channel That worked, thank you all for the help. One more question, 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: 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" Gesendet: Mittwoch, 8. April 2020 15:36:43 Betreff: Re: [Spacewalk-list] Permanently remove package from subscribed channel Where on the WebUI am I able to block these packages? The only thing I see is to delete a package within a channel, which will reappear the next time it syncs. (Manage software channels ---> click on # of packages in channel, search for package in question, click remove.) Regards, Sulove On 4/7/20, 4:21 PM, "Robert Paschedag" wrote: I would go via the WebUI and edit the channel sent from my mobile device Originale Nachricht Von: Sulove Khanal Gesendet: Tue Apr 07 21:12:57 GMT+02:00 2020 An: spacewalk-list@redhat.com Betreff: Re: [Spacewalk-list] Permanently remove package from subscribed channel Is the channel definition within the command line? How would I get to where I want to go? For example, if I want to block Firefox package updates from a channel called "centos7-x86-64," what commands would I run exactly? I am a beginner Spacewalk user. Regards, Sulove On 4/7/20, 2:54 PM, "Robert Paschedag" wrote: Within the channel definition, you can specify to block certain packages. Something like "-perl*" would not sync perl packages. Note that this might break dependencies. Robert sent from my mobile device Originale Nachricht Von: Sulove Khanal Gesendet: Tue Apr 07 15:54:21 GMT+02:00 2020 An: spacewalk-list@redhat.com Betreff: [Spacewalk-list] Permanently remove package from subscribed channel Hi, Is there a way to permanently remove packages from a Spacewalk channel? I am receiving Firefox package updates in a Centos7 channel that I don’t believe should be occurring; I’ve figured out a way to temporarily delete the Firefox package updates, but once the channel syncs (which is often), the Firefox updates pull again and I am left with the same issue. Thank you, Sulove ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list __
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" Gesendet: Mittwoch, 8. April 2020 15:36:43 Betreff: Re: [Spacewalk-list] Permanently remove package from subscribed channel Where on the WebUI am I able to block these packages? The only thing I see is to delete a package within a channel, which will reappear the next time it syncs. (Manage software channels ---> click on # of packages in channel, search for package in question, click remove.) Regards, Sulove On 4/7/20, 4:21 PM, "Robert Paschedag" wrote: I would go via the WebUI and edit the channel sent from my mobile device Originale Nachricht Von: Sulove Khanal Gesendet: Tue Apr 07 21:12:57 GMT+02:00 2020 An: spacewalk-list@redhat.com Betreff: Re: [Spacewalk-list] Permanently remove package from subscribed channel Is the channel definition within the command line? How would I get to where I want to go? For example, if I want to block Firefox package updates from a channel called "centos7-x86-64," what commands would I run exactly? I am a beginner Spacewalk user. Regards, Sulove On 4/7/20, 2:54 PM, "Robert Paschedag" wrote: Within the channel definition, you can specify to block certain packages. Something like "-perl*" would not sync perl packages. Note that this might break dependencies. Robert sent from my mobile device Originale Nachricht Von: Sulove Khanal Gesendet: Tue Apr 07 15:54:21 GMT+02:00 2020 An: spacewalk-list@redhat.com Betreff: [Spacewalk-list] Permanently remove package from subscribed channel Hi, Is there a way to permanently remove packages from a Spacewalk channel? I am receiving Firefox package updates in a Centos7 channel that I don’t believe should be occurring; I’ve figured out a way to temporarily delete the Firefox package updates, but once the channel syncs (which is often), the Firefox updates pull again and I am left with the same issue. Thank you, Sulove ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] spacewalk - GUI console login issue
ctor-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 To: spacewalk-list Subject: 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" < [ mailto:agupta...@dxc.com | agupta...@dxc.com ] > An: "spacewalk-list" < [ mailto:spacewalk-list@redhat.com | spacewalk-list@redhat.com ] > Gesendet: Sonntag, 29. März 2020 19:07:23 Betreff: Re: [Spacewalk-list] spacewalk - GUI console login issue Spacewalk server is working fine and we are able to patch client server. Only we have issue with GUI console , not getting login screen. Attaching here screenshot. Actually we need to add repository for CentOS 8 on my spacewalk server to patch client server and need GUI console access for same. We have no idea how to repo from command line. Can you help me for same please. Regards, Ajay Kumar 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: [ mailto:spacewalk-list-boun...@redhat.com | spacewalk-list-boun...@redhat.com ] < [ mailto:spacewalk-list-boun...@redhat.com | spacewalk-list-boun...@redhat.com ] > On Behalf Of Raymond Setchfield Sent: Sunday, March 29, 2020 10:30 PM To: [ mailto:spacewalk-list@redhat.com | spacewalk-list@redhat.com ] Subject: Re: [Spacewalk-list] spacewalk - GUI console login issue There is very little information to go on here. Is the spacewalk service running? What does the logs say? Are you receiving any error message when you go to the url? Ray On 29 Mar 2020, at 17:58, GUPTA, AJAY KUMAR < [ mailto:agupta...@dxc.com | agupta...@dxc.com ] > wrote: BQ_BEGIN Hi Team, I have spacewalk 2.8 server running on RHEL 7.7. I am not getting login screen to put my credential to get GUI console access. Please help me to fix the issue. Regards, Ajay Kumar 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 : DXC Technology India Private Limited - Unit 13, Block 2, SDF Buildings, MEPZ SEZ, Tambaram, Chennai 600 045, Tamil Nadu. Registered in India, CIN: U72900TN2015FTC102489. DXC Technology Company -- This message is transmitted to you by or on behalf of DXC Technology Company or one of its affiliates. It is intended exclusively for the addressee. The substance of this message, along with any attachments, may contain proprietary, confidential or privileged information or information that is otherwise legally exempt from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate any part of this message. If you have received this message in error, please destroy and delete all copies and notify the sender by return e-mail. Regardless of content, this e-mail shall not operate to bind DXC Technology Company or any of its affiliates to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. ___ Spacewalk-list mailing list [ mailto:Spacewalk-list@redhat.com | Spacewalk-list@redhat.com ] [ https://clicktime.symantec.com/3YP2ey18ykwLzawxk1QPbtf7Vc?u=https%3A%2F%2Fwww.redhat.com%2Fmailman%2Flistinfo%2Fspacewalk-list | https://clicktime.symantec.com/3YP2ey18ykwLzawxk1QPbtf7Vc?u=https%3A%2F%2Fwww.redhat.com%2Fmailman%2Flistinfo%2Fspacewalk-list ] BQ_END ___ Spacewalk-list mailing list [ mailto:Spacewalk-list@redhat.com | Spacewalk-list@redhat.com ] [ https://clicktime.symantec.com/3W8RrmfF36LtDsHwHBSFUKj7Vc?u=https%3A%2F%2Fwww.redhat.com%2Fmailman%2Flistinfo%2Fspacewalk-list | https://clicktime.symantec.com/3W8RrmfF36LtDsHwHBSFUKj7Vc?u=https%3A%2F%2Fwww.redhat.com%2Fmailman%2Flistinfo%2Fspacewalk-list ] ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
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: "spacewalk-list" Gesendet: Sonntag, 29. März 2020 19:07:23 Betreff: Re: [Spacewalk-list] spacewalk - GUI console login issue Spacewalk server is working fine and we are able to patch client server. Only we have issue with GUI console , not getting login screen. Attaching here screenshot. Actually we need to add repository for CentOS 8 on my spacewalk server to patch client server and need GUI console access for same. We have no idea how to repo from command line. Can you help me for same please. Regards, Ajay Kumar 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 Raymond Setchfield Sent: Sunday, March 29, 2020 10:30 PM To: spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] spacewalk - GUI console login issue There is very little information to go on here. Is the spacewalk service running? What does the logs say? Are you receiving any error message when you go to the url? Ray On 29 Mar 2020, at 17:58, GUPTA, AJAY KUMAR < [ mailto:agupta...@dxc.com | agupta...@dxc.com ] > wrote: BQ_BEGIN Hi Team, I have spacewalk 2.8 server running on RHEL 7.7. I am not getting login screen to put my credential to get GUI console access. Please help me to fix the issue. Regards, Ajay Kumar 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 : DXC Technology India Private Limited - Unit 13, Block 2, SDF Buildings, MEPZ SEZ, Tambaram, Chennai 600 045, Tamil Nadu. Registered in India, CIN: U72900TN2015FTC102489. DXC Technology Company -- This message is transmitted to you by or on behalf of DXC Technology Company or one of its affiliates. It is intended exclusively for the addressee. The substance of this message, along with any attachments, may contain proprietary, confidential or privileged information or information that is otherwise legally exempt from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate any part of this message. If you have received this message in error, please destroy and delete all copies and notify the sender by return e-mail. Regardless of content, this e-mail shall not operate to bind DXC Technology Company or any of its affiliates to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. ___ Spacewalk-list mailing list [ mailto:Spacewalk-list@redhat.com | Spacewalk-list@redhat.com ] [ https://clicktime.symantec.com/3YP2ey18ykwLzawxk1QPbtf7Vc?u=https%3A%2F%2Fwww.redhat.com%2Fmailman%2Flistinfo%2Fspacewalk-list | https://clicktime.symantec.com/3YP2ey18ykwLzawxk1QPbtf7Vc?u=https%3A%2F%2Fwww.redhat.com%2Fmailman%2Flistinfo%2Fspacewalk-list ] BQ_END ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] HTTP Status 403 - Validation of CSRF security token failed on Webui on POST request on spacewalk 2.10
:) Never! It is on my todo list. One after the other... - Ursprüngliche Mail - Von: "michael mraka" An: "spacewalk-list" Gesendet: Donnerstag, 26. März 2020 12:49:19 Betreff: Re: [Spacewalk-list] HTTP Status 403 - Validation of CSRF security token failed on Webui 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áka System Management Engineering, Red Hat ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
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 2.10 After investigating this problem comes from selinux was activated. Télécharger [ https://aka.ms/ghei36 | Outlook pour Android ] De : BARRIERE Benoit Envoyé : vendredi 20 mars 2020 à 18:00 À : spacewalk-list@redhat.com Objet : HTTP Status 403 - Validation of CSRF security token failed on Webui on POST request on spacewalk 2.10 Hello, After a fresh install of spacewalk 2.10 on an centos 7 we have this issue when we want to change for exemple language for the user admin I follow the install guide [ https://github.com/spacewalkproject/spacewalk/wiki/HowToInstall | https://github.com/spacewalkproject/spacewalk/wiki/HowToInstall ] Also i no information in the overview and no icons appears : It’s the same result on chrome, firefox and IE. Thanks for your help . ___ BARRIERE Benoit Monaco Telecom [ mailto:b.barri...@monaco-telecom.mc | b.barri...@monaco-telecom.mc ] Tel: (377) 99 66 66 03 Fax: (377) 99 66 96 07 _ Des informations nominatives sont exploitées par Monaco Telecom SAM dans le cadre de la fourniture de la messagerie professionnelle. Conformément à la Loi 1.165, modifiée, vous disposez d’un droit d’accès, de rectification et de suppression en écrivant à Monaco Telecom SAM, au 25 Bd de Suisse MC - 98008 Monaco Cedex. Personal data are processed for messaging services purpose by Monaco Telecom SAM. In compliance with the applicable legislation (Law n° 1.165, as amended) relating to the protection of personal information, you may access, update and remove your data, by writing to Monaco Telecom SAM - 25 Bd de Suisse MC - 98008 Monaco Cedex. Afin de préserver l’environnement, merci de n’imprimer ce courrier que si nécessaire. To preserve the environment, thank you to print this letter only if necessary. ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
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 point of view (in the same format the client would use it). So no URL. It must be a client local file location. 1. When you use Spacewalk to kickstart a server, you can configure the keys there and they get deployed on each new build. 2. When you provision otherwise, you have to place the non-default keys (i.e. not included in the OS) manually onto the server. How about adding the keys to a configuration channel and auto-deploy the channel contents on each new registration? You could then also use the channel to push new repos/keys to all clients, if required. Best wishes, Stefan Von: "Laurence Rosen" An: "spacewalk-list" Gesendet: Freitag, 6. März 2020 19:29:31 Betreff: [Spacewalk-list] channels and gpg key fields Is there any doc that describes these fields other than how to fill them out? What are they for, as they don't seem to do anything and aren't used by yum to automatically add them to a client? To register new clients, my script has to do a wget the keys from /pub/gpg on my server and save in /etc/pki/rpm-gpg, but it seems like the channel should beagle to be utilized somehow. I have searched quite a bit looking for the answers on my own and thought I had seen and old spacewalk-list mention but cannot find again. *** This e-mail and any of its attachments may contain Interactions LLC proprietary information, which is privileged, confidential, or subject to copyright belonging to the Interactions LLC. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You. *** ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
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 (i.e. Signing happens --> Uploaded to public repository --> Spacewalk syncs the public repository down --> package is pushed to client --> client verifies the signature. Best wishes, Stefan - Ursprüngliche Mail - Von: "Michael Mraka" An: "spacewalk-list" Gesendet: Mittwoch, 4. März 2020 10:39:28 Betreff: Re: [Spacewalk-list] GPG keys for CentOS channels in Spacewalk Wenkai Chen: > HI Stefan, > > If the GPG check is done on the client side for the Spacewalk channel, does > this mean that for each package downloaded from Spacewalk onto the Client, it > is being signed by CentOS and that the client will use the GPG public key on > its local file location to verify its integrity? Yes, unless you've explicitly disabled gpg checking in yum/dnf. -- Michael Mráka System Management Engineering, Red Hat ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] GPG keys for CentOS channels in Spacewalk
Hello Chen, > So this means that in order to do GPG check for the clients, I would need to > place the same GPG key on all registered clients on this channel at the same > location? (file:///etc/pki/rpm-gpg/) correct. Practically, this would only be necessary if the keys are not already imported into the rpm database (I import the keys on provisioning and never fill out the GPG key field). > How does Spacewalk verify its integrity when it syncs its repositories for > each channel? How does it ensure that the repo it syncs with have not been > compromised? It doesn't do it. And I don't think it needs to (or you don't want to when mixing packages from different sources). You will latest notice the compromise when installing the package as it would then fail. Best wishes, Stefan Von: "Wenkai Chen" An: "spacewalk-list" Gesendet: Mittwoch, 4. März 2020 09:50:03 Betreff: Re: [Spacewalk-list] GPG keys for CentOS channels in Spacewalk HI Stefan, Thanks. So this means that in order to do GPG check for the clients, I would need to place the same GPG key on all registered clients on this channel at the same location? (file:///etc/pki/rpm-gpg/) How does Spacewalk verify its integrity when it syncs its repositories for each channel? How does it ensure that the repo it syncs with have not been compromised? Chen Wenkai Infrastructure Security Engineer [ https://www.linkedin.com/company/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 Sent: Wednesday, 4 March 2020 2:43 PM To: spacewalk-list Subject: Re: [Spacewalk-list] GPG keys for CentOS channels in Spacewalk EXTERNAL: Caution this email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. 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 it). So no URL. It must be a client local file location. Best wishes, Stefan Von: "Wenkai Chen" < [ mailto:wenkai_c...@ensigninfosecurity.com | wenkai_c...@ensigninfosecurity.com ] > An: "spacewalk-list" < [ mailto:spacewalk-list@redhat.com | spacewalk-list@redhat.com ] > Gesendet: Mittwoch, 4. März 2020 04:19:56 Betreff: [Spacewalk-list] GPG keys for CentOS channels in Spacewalk HI Spacewalk users, Sorry just would like to confirm. When we enter GPG key into a channel on Spacewalk, does it mean that whenever we do a repo-sync, it does a gpg-check on all the packages downloaded and synced? If there is no GPG key entered for a channel in Spacewalk, will there be a gpg-check? If clients are registered to this channel on Spacewalk, will there be a gpg-check? Thank you. Chen Wenkai Infrastructure Security Engineer [ https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fensign-infosecurity%2F=02%7C01%7Cwenkai_chen%40ensigninfosecurity.com%7Cbec92e4d7f924ce0609a08d7c0077ac5%7Cd5cb08f4d38848b2bc028ecce3c63fce%7C1%7C0%7C637189010679631245=gwUYQPIcYMJ0jgab4J585p5TEBny9%2BwdY2eJeD4N3iY%3D=0 ] [ https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyoutu.be%2F9J7FkhXpb-4=02%7C01%7Cwenkai_chen%40ensigninfosecurity.com%7Cbec92e4d7f924ce0609a08d7c0077ac5%7Cd5cb08f4d38848b2bc028ecce3c63fce%7C1%7C0%7C637189010679641236=Z%2BRMDHv5ifakyKT2oJoatuw4btwFNg4GEvAJ%2BzBmA%2B8%3D=0 ] [ https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.facebook.com%2FEnsignGlobal=02%7C01%7Cwenkai_chen%40ensigninfosecurity.com%7Cbec92e4d7f924ce0609a08d7c0077ac5%7Cd5cb08f4d38848b2bc028ecce3c63fce%7C1%7C0%7C637189010679641236=ldesps5s%2F2ASMZBP5Esel2ZUuziRX%2FQm4iCYoST2tjk%3D=0 ] E: [ mailto:wenkai_c...@ensigninfosecurity.com | wenkai_c...@ensigninfosecurity.com ] A: 30A Kallang Place, Level 9 Right Wing, Singapore 339213 CONFIDENTIALITY NOTICE: “This email is confidential and may also be privileged. If this email has been sent to you in error, please delete it immediately and notify us. Please do not copy, distribute or disseminate part or whole of this email if you are not the intended recipient or if you have not been authorized to do so. We reserve the right, to the extent and under circumstances permitted by applicable laws, to monitor, retain, intercept and block email messages to and from our systems. Thank you.” ___ Spacewalk-
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 it). So no URL. It must be a client local file location. Best wishes, Stefan Von: "Wenkai Chen" An: "spacewalk-list" Gesendet: Mittwoch, 4. März 2020 04:19:56 Betreff: [Spacewalk-list] GPG keys for CentOS channels in Spacewalk HI Spacewalk users, Sorry just would like to confirm. When we enter GPG key into a channel on Spacewalk, does it mean that whenever we do a repo-sync, it does a gpg-check on all the packages downloaded and synced? If there is no GPG key entered for a channel in Spacewalk, will there be a gpg-check? If clients are registered to this channel on Spacewalk, will there be a gpg-check? Thank you. Chen Wenkai Infrastructure Security Engineer [ https://www.linkedin.com/company/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 CONFIDENTIALITY NOTICE: “This email is confidential and may also be privileged. If this email has been sent to you in error, please delete it immediately and notify us. Please do not copy, distribute or disseminate part or whole of this email if you are not the intended recipient or if you have not been authorized to do so. We reserve the right, to the extent and under circumstances permitted by applicable laws, to monitor, retain, intercept and block email messages to and from our systems. Thank you.” ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] [External Sender] Re: missing public key
Hello Larry, note that there is a client and server pubkey.gpg. Maybe you mixed them up? The key on the client is independent from the server. It is matched to the original package source. Only things I can think of is 1) that you installed the wrong key to the clients, 2) you pushed the keys to the client but you did not import them (rpm --import pubkey.gpg) 3) maybe place the key folder path into the corresponding channel field (this is local to the client, where the client would find the file on the HDD) Maybe somebody else has different ideas. Best wishes, Stefan Von: "Larry Clegg" An: "spacewalk-list" Gesendet: Montag, 24. Februar 2020 21:09:33 Betreff: Re: [Spacewalk-list] [External Sender] Re: missing public key The client was originally provisioned against a Centos6/Spacewalk 2.8 server. I did the standard client install of the rpms, etc as documented in the client installation guide. Since then the 2.8 Spacewalk Server was rebuilt from scratch using Centos 7 and Spacewalk 2.9 and all the clients re-registered. The SW channels are created on the server using the spacewalk-common-channels command like this: /usr/bin/spacewalk-common-channels - u -p -a x86_64 spacewalk29-client-centos6 I have noticed that the gpg key generated in the SW channel for the 2.9 client looks like this: GPG key URL: [ https://copr-be.cloud.fedoraproject.org/results/@spacewalkproject/spacewalk-2.9-client/pubkey.gpg | https://copr-be.cloud.fedoraproject.org/results/@spacewalkproject/spacewalk-2.9-client/pubkey.gpg ] GPG key ID: 9BD837BA GPG key Fingerprint: A353 22CF 3B3F 9C71 101E B74B 49FC 0FD8 9BD8 37BA Yet when I download that same pubkey.gpg and examine it I get different results for the id and fingerprint: [root@us3-inf-lu-s01 rpm-gpg]# gpg --with-fingerprint RPM-GPG-KEY-spacewalk-2.9 pub 2048R/6E5454FA 2018-11-26 @spacewalkproject_spacewalk-2.9 (None) <@spacewalkproject# [ mailto:spacewalk-...@copr.fedorahosted.org | spacewalk-...@copr.fedorahosted.org ] > Key fingerprint = E089 1A20 65C5 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, 2020 at 11:32 AM Stefan Bluhm < [ mailto:redhat@bluhm-de.com | redhat@bluhm-de.com ] > wrote: 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" < [ mailto:lcl...@kyriba.com | lcl...@kyriba.com ] > An: "spacewalk-list" < [ mailto:spacewalk-list@redhat.com | spacewalk-list@redhat.com ] > Gesendet: Montag, 24. Februar 2020 20:20:37 Betreff: [Spacewalk-list] missing public key Greetings Spacewalkers: I have gone over and over my configuration and I'm just not finding the problem. Server: Spacewalk 2.9 on Centos 6 - all fully patched Client: Centos6 download This issue is NOT happening on all clients...only a few. When I try to do a "yum upgrade" I get this message about rhncfg: warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature, key ID 9bd837ba: NOKEY Public key for rhncfg-5.10.129-1.el6.noarch.rpm is not installed -- It is trying to upgrade rhncfg from 5.10.122-1 to 5.10.129-1 No other package reports this issue. Using the --nogpg on the yum command line gets around this issue but I'd like to understand and fix root cause. Any hints are greatly appreciated. Larry E. Clegg Systems Administrator | Kyriba [Address] 4435 Eastgate Mall, Suite 200, San Diego, CA 92121 [ http://www.kyriba.com/ | www.kyriba.com ] | [ https://www.facebook.com/KyribaCorp | Facebook ] | [ https://twitter.com/kyribacorp | Twitter ] | [ http://www.linkedin.com/company/kyriba-corporation | LinkedIn ] | [ http://www.kyriba.com/blog | Blog ] ___ Spacewalk-list mailing list [ mailto:Spacewalk-list@redhat.com | Spacewalk-list@redhat.com ] [ https://www.redhat.com/mailman/listinfo/spacewalk-list | https://www.redhat.com/mailman/listinfo/spacewalk-list ] ___ Spacewalk-list mailing list [ mailto:Spacewalk-list@redhat.com | Spacewalk-list@redhat.com ] [ https://www.redhat.com/mailman/listinfo/spacewalk-list | https://www.redhat.com/mailman/listinfo/spacewalk-list ] -- Larry E. Clegg Systems Administrator | Kyriba [Address] 4435 Eastgate Mall, Suite 200, San Diego, CA 92121 [ http://www.kyriba.com/ | www.kyriba.com ] | [ https://www.facebook.com/KyribaCorp | Facebook ] | [ https://twitter.com/kyribacorp | Twitter ] | [ http://www.linkedin.com/company/kyriba-corporation | LinkedIn ] | [ http://www.kyriba.com/blog | Blog ] __
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: [Spacewalk-list] missing public key Greetings Spacewalkers: I have gone over and over my configuration and I'm just not finding the problem. Server: Spacewalk 2.9 on Centos 6 - all fully patched Client: Centos6 download This issue is NOT happening on all clients...only a few. When I try to do a "yum upgrade" I get this message about rhncfg: warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature, key ID 9bd837ba: NOKEY Public key for rhncfg-5.10.129-1.el6.noarch.rpm is not installed -- It is trying to upgrade rhncfg from 5.10.122-1 to 5.10.129-1 No other package reports this issue. Using the --nogpg on the yum command line gets around this issue but I'd like to understand and fix root cause. Any hints are greatly appreciated. Larry E. Clegg Systems Administrator | Kyriba [Address] 4435 Eastgate Mall, Suite 200, San Diego, CA 92121 [ http://www.kyriba.com/ | www.kyriba.com ] | [ https://www.facebook.com/KyribaCorp | Facebook ] | [ https://twitter.com/kyribacorp | Twitter ] | [ http://www.linkedin.com/company/kyriba-corporation | LinkedIn ] | [ http://www.kyriba.com/blog | Blog ] ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
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. Februar 2020 02:32:48 Betreff: [Spacewalk-list] Too many open files while syncing Red hat repository on Spacewalk server 2.9 HI Spacewalk users, I have an issue while running a repo sync on one of our red hat repositories in spacewalk. This was the error log. === 2020/02/21 19:47:45 +08:00 [Errno 24] Too many open files: '/var/satellite/redhat/1/stage/zziplib-0.13.62-9.el7.x86_64.rpm' 2020/02/21 19:47:45 +08:00 [Errno 24] Too many open files: '/var/satellite/redhat/1/stage/zziplib-0.13.62-11.el7.x86_64.rpm' 2020/02/21 19:47:45 +08:00 [Errno 24] Too many open files: '/var/satellite/redhat/1/stage/zziplib-0.13.62-5.el7.x86_64.rpm' 2020/02/21 19:47:45 +08:00 [Errno 24] Too many open files: '/var/satellite/redhat/1/stage/zziplib-0.13.62-9.el7.i686.rpm' 2020/02/21 19:47:45 +08:00 [Errno 24] Too many open files: '/var/satellite/redhat/1/stage/zziplib-0.13.62-5.el7.i686.rpm' 2020/02/21 19:47:45 +08:00 [Errno 24] Too many open files: '/var/satellite/redhat/1/stage/zziplib-0.13.62-11.el7.i686.rpm' 2020/02/21 19:47:45 +08:00 Importing packages finished. 2020/02/21 19:47:45 +08:00 2020/02/21 19:47:45 +08:00 Linking packages to the channel. 2020/02/21 19:48:12 +08:00 ERROR: Could not find object [https://www.linkedin.com/company/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 CONFIDENTIALITY NOTICE: “This email is confidential and may also be privileged. If this email has been sent to you in error, please delete it immediately and notify us. Please do not copy, distribute or disseminate part or whole of this email if you are not the intended recipient or if you have not been authorized to do so. We reserve the right, to the extent and under circumstances permitted by applicable laws, to monitor, retain, intercept and block email messages to and from our systems. Thank you.” ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
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 Mail - Von: "Paul Rontanini" An: "Michael Mraka" , "spacewalk-list" CC: "Paul Rontanini" Gesendet: Donnerstag, 20. Februar 2020 16:42:49 Betreff: Re: [Spacewalk-list] can Spacewalk 2.9 be installed on RHEL 8 Good Day Michael, Thanks for the info We are starting our endeavors towards RHEL 8 With that said... Is there any issues with Spacewalk 2.9 ( running on RHEL 7 ) supporting RHEL 8 clients Paul Rontanini System Engineer, 1800Flowers.com -Original Message- From: Michael Mraka Sent: Thursday, February 20, 2020 4:51 AM To: spacewalk-list@redhat.com Cc: Paul Rontanini Subject: Re: [Spacewalk-list] can Spacewalk 2.9 be installed on RHEL 8 Paul Rontanini: > I have an old version 2.4 on RHEL 6 > I want to upgrade to the latest on github, which looks to be Spacewalk 2.9 > It only lists RHEL 7 compatibility , any progress towards RHEL 8? > Is a newer version of Spacewalk coming to a theater nearby soon? Hello, Currently there is no version of Spacewalk available for RHEL 8. We are working on new version but there is still a lot of missing dependencies for RHEL 8. Regards, -- Michael Mráka System Management Engineering, Red Hat ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
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 wishes, Stefan Von: "Brodie, Kent" An: "spacewalk-list" Gesendet: Mittwoch, 19. Februar 2020 17:19:06 Betreff: [Spacewalk-list] Packages listed as available to update, but no update done (Appstream/module issue for redhat8?) Hi- I am testing a couple of version 8 clients for spacewalk (One redhat8, one centos8). I have a server for each OS doing a full reposync, then I sync the repositories into spacewalk. No problems so far. Everything pretty much works great EXCEPT for each of those 2 clients, I have about 16 packages that are listed in Spacewalk as being new versions that can be updated. But when I try to update those clients, nothing. “No updates available”. I am pretty sure this is related to the new redhat appstream/module functionality. And I’m guessing that those 16 packages can’t actually be upgraded YET because of a module version limitation of something installed on those clients. (I confirmed this more or less by eliminating spacewalk…. And just using centos/redhat repos. Same answer: no updates available). BUT… my question is this: How can I tweak spacewalk (or my repos) so that the Spacewalk doesn’t show update packages that I actually can’t install? In other words, those 2 clients should NOT show any updates available to install……. Is this spacewalk essentially not knowing how to handle modules/appstreams yet? Thanks for any tips/pointers -kcb ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
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] "Invalid function call attempted (code 6)" Ezequiel, When I run rhn_check -, the only line in there that looks like an error message is "couldn't find any keys in /var/lib/rpm/pubkeys/*.key", (the pubkey folder doesn't exist) but then the next line is "loading keyring from rpmdb", so it looks like it gets the key from there. I get those same messages though on both the machines that fail and the ones that succeed. Paul On Fri, Feb 14, 2020 at 11:51 AM Paul Greene < [ mailto:paul.greene...@gmail.com | paul.greene...@gmail.com ] > wrote: What version of 7 are you running? (including kernel #?) On Fri, Feb 14, 2020 at 11:17 AM Ezequiel Sozzi < [ mailto:soz...@gmail.com | soz...@gmail.com ] > wrote: BQ_BEGIN Hi Paul, Versions should not be the problem, I'm managing almost 4000 servers with spacewalk and 35% are Centos6 while the other 65% are Centos7. have you tried to perform a rhn_check - from the client? That could bring you more information. BR, El vie., 14 de feb. de 2020 a la(s) 13:12, Paul Greene ( [ mailto:paul.greene...@gmail.com | paul.greene...@gmail.com ] ) escribió: BQ_BEGIN Ezequiel, I tried it but it didn't seem to do anything. These systems have no connection to the internet - our repositories are all internal to the network (one repo for base, one for updates, and one for EPEL), and they have all the latest updates anyway, so there was nothing to update. Not sure where to go with this. Just to add to my second post - older versions of CentOS 7 aren't having issues, and there's many systems still on CentOS 6 that don't have any issues either. So that leads me to believe there's something about the differences in OS versions that are the root of the problem. Paul On Thu, Feb 13, 2020 at 7:23 PM Ezequiel Sozzi < [ mailto:soz...@gmail.com | soz...@gmail.com ] > wrote: BQ_BEGIN Hi Paul, This a more often issue than everybody things, in order to fix this, what we do is to run the next commands on the client side: Disable all the plugins to disable rhnplugin: sed -i 's/plugins=1/plugins=0/g' /etc/yum.conf Disable all the external repositores: yum-config-manager --disable \* Re-enable all the plugins to enable rhnplugin: sed -i 's/plugins=0/plugins=1/g' /etc/yum.conf Update all the packages related to rpm, rhn, and yum: yum update rpm* rhn* yum* -y This fix the issue. At least that's my experience. Hope this helps. BR, Ezequiel El jue., 13 de febrero de 2020 7:26 p. m., Paul Greene < [ mailto:paul.greene...@gmail.com | paul.greene...@gmail.com ] > escribió: BQ_BEGIN I have a spacewalk 2.9 server with CentOS 7 clients. When I run a scheduled remote command on 50 systems, usually about half of the systems will get marked as "failed" with the error "Invalid function call attempted (code 6)". They all have the same configuration, and every line put in the remote command will run just fine from a command prompt. If I go into a system that has been marked "failed" and manually verify if the command did what it was supposed to do, many times it actually did succeed, but was still marked "failed". And there are some that did in fact fail. How can I address this error to get rid of the false "failed" messages? I looked in /var/log/up2date on the clients that failed and get just these messages at the time the scheduled task failed: up2date updateLoginfo() login info up2date logging into up2date server up2date successfully retrieved authentication token from up2date server ___ Spacewalk-list mailing list [ mailto:Spacewalk-list@redhat.com | Spacewalk-list@redhat.com ] [ https://www.redhat.com/mailman/listinfo/spacewalk-list | https://www.redhat.com/mailman/listinfo/spacewalk-list ] ___ Spacewalk-list mailing list [ mailto:Spacewalk-list@redhat.com | Spacewalk-list@redhat.com ] [ https://www.redhat.com/mailman/listinfo/spacewalk-list | https://www.redhat.com/mailman/listinfo/spacewalk-list ] BQ_END ___ Spacewalk-list mailing list [ mailto:Spacewalk-list@redhat.com | Spacewalk-list@redhat.com ] [ https://www.redhat.com/mailman/listinfo/spacewalk-list | https://www.redhat.com/mailman/listinfo/spacewalk-list ] BQ_END ___ Spacewalk-list mailing list [ mailto:Spacewalk-list@redhat.com | Spacewalk-list@redhat.com ] [ https://www.redhat.com/mailman/listinfo/spacewalk-list | https://www.redhat.com/mailman/listinfo/spacewalk-list ] BQ_END BQ_END ___
[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 Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-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. Putting the DB onto a different server fails. And there should not be a need to put the DB server into hosts. That's why i use DNS. Did you manage to split the servers? best wishes, Stefan Hi Stefan This is usually a hostname/FQDN issue. Make sure your /etc/hosts file is 100% clean and contains: 127.0.0.1 localhost.localdomain localhost ip addressFQDNhostname Then restart spacewalk Regards Bruce ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Spacewalk only works with local DB
Hi Travis, it is a central DB server without any security lockdown. I am using it for one other web application (also on a different app server). Also the installation works fine and it seems to put all data into the DB. Via the SQLplus client or during installation. Only the osa-dispatcher 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: 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. Putting the DB onto a different server fails. And there should not be a need to put the DB server into hosts. That's why i use DNS. Did you manage to split the servers? best wishes, Stefan Hi Stefan This is usually a hostname/FQDN issue. Make sure your /etc/hosts file is 100% clean and contains: 127.0.0.1 localhost.localdomain localhost ip addressFQDNhostname Then restart spacewalk Regards Bruce ___ Spacewalk-list mailing list Spacewalk-list@redhat.com mailto:Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[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:
Starting osa-dispatcher:
/usr/lib/python2.6/site-packages/jabber/jabber.py:68:
DeprecationWarning: the sha module is deprecated; use the hashlib module
instead
import sha, time
RHN 4765 2010/02/20 09:51:36 +02:00: ('Traceback (most recent call
last):\n File /usr/share/rhn/osad/jabber_lib.py, line 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in
_get_jabber_client\nc.connect()\n File
/usr/share/rhn/osad/jabber_lib.py, line 577, in connect\n
jabber.Client.connect(self)\n File
/usr/lib/python2.6/site-packages/jabber/xmlstream.py, line 464, in
connect\nelse: self._sock.connect((self._hostIP, self._port))\n
File string, line 1, in connect\nerror: [Errno 111] Connection
refused\n',)
when I run b), the system works fine.
Now I tried to play around with the scenarios and found the following:
When the DB is installed after Spacewalk has been configured for the
first time, I again get the above error message. The DB must be
configured before the spacewalk-setup is run.
To use an external DB, I have to set up scenario c). The local DB MUST
be runnning otherwise again I get the error message.
There is something wrong with the osa-dispatcher that it is always
trying to access the local DB when starting.
Not only that, the DB has to be started together with the
/usr/sbin/rhn-satellite restart script. If the DB is running and the
/usr/sbin/rhn-satellite restart script is started (obviously, the DB
part has been taken out of the start), it will again fail with the same
error message
Can someone please analyse that and fix it? I am happy to help out as I
have all the test scenarios saved
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
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:
DeprecationWarning: the sha module is deprecated; use the hashlib module instead
import sha, time
RHN 4682 2010/02/09 21:36:39 +02:00: ('Traceback (most recent call last):\n File /usr/share/rhn/osad/jabber_lib.py, line
254, in setup_connection\nc = self._get_jabber_client(js)\n File /usr/share/rhn/osad/jabber_lib.py, line 311, in
_get_jabber_client\nc.connect()\n File /usr/share/rhn/osad/jabber_lib.py, line 577, in connect\n
jabber.Client.connect(self)\n File /usr/lib/python2.6/site-packages/jabber/xmlstream.py, line 464, in connect\nelse:
self._sock.connect((self._hostIP, self._port))\n File string, line 1, in connect\nerror: [Errno 111] Connection
refused\n',)
Now I am testing around a bit:
telnet spacewalk 5222 - Connection Successful
netstat -ptnl - c2s is listening on 5222 IPv4
db_verify authreg.db sm.db ; echo $? - 0
xmllint --noout /etc/jabberd/*.xml - no error
/etc/rhn/rhn.conf looks ok
Some log extracts which might mean something:
osa-dispatcher.log
2010/02/09 21:01:17 +02:00 4701 0.0.0.0:
rhnSQL/driver_cx_Oracle.connect('Connecting to database', 'XE')
2010/02/09 21:01:17 +02:00 4701 0.0.0.0: osad/jabber_lib.__init__
2010/02/09 21:01:17 +02:00 4701 0.0.0.0: osad/jabber_lib.print_message('socket
error',)
2010/02/09 21:01:17 +02:00 4701 0.0.0.0: osad/jabber_lib.print_message('Could
not connect to jabber server', 'spacewalk.domain.com')
messages log on /usr/sbin/rhn-satellite stop
Feb 9 21:49:51 spacewalk jabberd/c2s[7024]: connection to router closed
Feb 9 21:49:51 spacewalk jabberd/c2s[7024]: attempting reconnect (3 left)
Feb 9 21:49:51 spacewalk jabberd/sm[7001]: connection to router closed
Feb 9 21:49:51 spacewalk jabberd/sm[7001]: attempting reconnect (3 left)
Feb 9 21:49:51 spacewalk jabberd/s2s[7047]: connection to router closed
Feb 9 21:49:51 spacewalk jabberd/s2s[7047]: attempting reconnect (3 left)
Feb 9 21:49:52 spacewalk jabberd/sm[7001]: attempting connection to router at
127.0.0.1, port=5347
Feb 9 21:49:52 spacewalk jabberd/sm[7001]: shutting down
Feb 9 21:49:53 spacewalk jabberd/c2s[7024]: attempting connection to router at
127.0.0.1, port=5347
Feb 9 21:49:53 spacewalk jabberd/c2s[7024]: [5] [router] write error:
Connection refused (111)
Feb 9 21:49:53 spacewalk jabberd/c2s[7024]: connection to router closed
Feb 9 21:49:53 spacewalk jabberd/c2s[7024]: attempting reconnect (2 left)
Feb 9 21:49:53 spacewalk jabberd/s2s[7047]: attempting connection to router at
127.0.0.1, port=5347
Feb 9 21:49:53 spacewalk jabberd/s2s[7047]: [6] [router] write error:
Connection refused (111)
Feb 9 21:49:53 spacewalk jabberd/s2s[7047]: connection to router closed
Feb 9 21:49:53 spacewalk jabberd/s2s[7047]: attempting reconnect (2 left)
Feb 9 21:49:53 spacewalk jabberd/c2s[7024]: attempting connection to router at
127.0.0.1, port=5347
Feb 9 21:49:53 spacewalk jabberd/c2s[7024]: shutting down
Feb 9 21:49:54 spacewalk jabberd/s2s[7047]: attempting connection to router at
127.0.0.1, port=5347
Feb 9 21:49:54 spacewalk jabberd/s2s[7047]: shutting down
Feb 9 21:49:54 spacewalk jabberd/s2s[7047]: connection to router closed
the start only shows successes in the messages log.
I keep getting these errors via email. Are they of any concern?
com.redhat.rhn.common.hibernate.HibernateRuntimeException: HibernateException
executing CachedStatement
at
com.redhat.rhn.common.db.datasource.CachedStatement.execute(CachedStatement.java:280)
at
com.redhat.rhn.common.db.datasource.SelectMode.execute(SelectMode.java:105)
at
com.redhat.rhn.taskomatic.task.repomd.ChannelRepodataDriver.getCandidates(ChannelRepodataDriver.java:86)
at
com.redhat.rhn.taskomatic.task.threaded.TaskQueue.run(TaskQueue.java:106)
at
com.redhat.rhn.taskomatic.task.ChannelRepodata.execute(ChannelRepodata.java:58)
at
com.redhat.rhn.taskomatic.task.SingleThreadedTestableTask.execute(SingleThreadedTestableTask.java:54)
at org.quartz.core.JobRunShell.run(JobRunShell.java:203)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
Caused by: org.hibernate.StaleStateException: Batch update returned unexpected
row count from update [0]; actual row count: 0;
expected: 1
at
org.hibernate.jdbc.Expectations$BasicExpectation.checkBatched(Expectations.java:61)
at
org.hibernate.jdbc.Expectations$BasicExpectation.verifyOutcome(Expectations.java:46)
at
org.hibernate.jdbc.NonBatchingBatcher.addToBatch(NonBatchingBatcher.java:24)
at
org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:2520)
at
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
getsockname(7, {sa_family=AF_NETLINK, pid=2557, groups=}, [12]) = 0
sendto(7, \24\0\0\0\26\0\1\3f\332qK\0\0\0\0\0\0\0\0, 20, 0,
{sa_family=AF_NETLINK, pid=0, groups=}, 12) = 20
recvmsg(7, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{0\0\0\0\24\0\2\0f\332qK\375\t\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 108
recvmsg(7, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{@\0\0\0\24\0\2\0f\332qK\375\t\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 128
recvmsg(7, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{\24\0\0\0\3\0\2\0f\332qK\375\t\0\0\0\0\0\0\1\0\0\0\24\0\1\0\0\0\0\0...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 20
socket(PF_INET, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 7
connect(7, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr(192.168.0.12)}, 28) = 0
send(7, \26\332\1\0\0\1\0\0\0\0\0\0\tspacewalk\10bluhm-de\3..., 40,
MSG_NOSIGNAL) = 40
recvfrom(7,
\26\332\205\200\0\1\0\1\0\1\0\0\tspacewalk\10bluhm-de\3..., 1024, 0,
{sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr(192.168.0.12)}, [16]) = 78
connect(6, {sa_family=AF_INET, sin_port=htons(5222),
sin_addr=inet_addr(192.168.0.28)}, 16) = 0
send(6, ?xml version='1.0' encoding='UT..., 165, 0) = 165
recv(6, ?xml version='1.0'?stream:str..., 1024, 0) = 459
send(6, starttls xmlns='urn:ietf:params..., 52, 0) = 52
recv(6, proceed xmlns='urn:ietf:params:..., 1024, 0) = 50
RHN 2557 2010/02/09 22:58:24 +02:00: ('Error caught:',)
RHN 2557 2010/02/09 22:58:24 +02:00: ('Traceback (most recent call
last):\n File /usr/share/rhn/osad/jabber_lib.py, line 122, in
main\nself.process_forever(c)\n File
/usr/share/rhn/osad/jabber_lib.py, line 180, in process_forever\n
self.process_once(client)\n File
/usr/share/rhn/osad/osa_dispatcher.py, line 146, in process_once\n
client.retrieve_roster()\n File /usr/share/rhn/osad/jabber_lib.py,
line 718, in retrieve_roster\nstanza = self.get_one_stanza()\n File
/usr/share/rhn/osad/jabber_lib.py, line 790, in get_one_stanza\n
self.process(timeout=tm)\n File /usr/share/rhn/osad/jabber_lib.py,
line 1048, in process\nraise SSLError(OpenSSL error; will retry,
str(e))\nSSLError: (\'OpenSSL error; will retry\', (-1, \'Unexpected
EOF\'))\n',)
To me it looks like it might have something to do the SSL or so.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
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 clean and fresh install just for the spacewalk purpose so not adding the FQDN to hosts seems to be a Fedora 12 default. So is your domain domain.com? No, I obscured it as I didn't want all my details to be archived on the internet Thanks a lot for this pointer Bruce. I guess I would have never found it as manual testing worked. Best wishes, Stefan ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[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 stop processes:
Stopping s2s: [FAILED]
And these two messages on the start process.
Starting osa-dispatcher:
/usr/lib/python2.6/site-packages/jabber/jabber.py:68:
DeprecationWarning: the sha module is deprecated; use the hashlib module
instead
import sha, time
RHN 7447 2010/02/08 12:00:55 +02:00: ('Traceback (most recent call
last):\n File /usr/share/rhn/osad/jabber_lib.py, line 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in
_get_jabber_client\nc.connect()\n File
/usr/share/rhn/osad/jabber_lib.py, line 577, in connect\n
jabber.Client.connect(self)\n File
/usr/lib/python2.6/site-packages/jabber/xmlstream.py, line 464, in
connect\nelse: self._sock.connect((self._hostIP, self._port))\n
File string, line 1, in connect\nerror: [Errno 111] Connection
refused\n',)
So I guess some socket or so could not be opened. Does anyone have any
advise on what to do?
Thanks and best wishes,
Stefan
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] FW: Spacewalk-list Digest, Vol 21, Issue 19
:
rhnSQL/driver_cx_Oracle._execute_wrapper('Executing SQL: select sysdate
as ID from dual with bind params: {}',)
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.setup_connection('Connecting to', 'spacewalk.domain.com')
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib._get_jabber_client
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib._get_jabber_client('Connecting to', 'spacewalk.domain.com')
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib.__init__
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib.__init__
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.check_cert('Loading cert', X509Name object
'/C=DE/ST=Lower
Saxony/L=Hannover/O=ABC/OU=spacewalk.domain.com/CN=spacewalk.domain.com')
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib.connect
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.connect('Attempting to connect',)
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.print_message('socket error',)
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.print_message('Could not connect to jabber server',
'spacewalk.domain.com')
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.setup_connection('ERROR', 'Traceback (most recent call
last):\n File /usr/share/rhn/osad/jabber_lib.py, line 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in
_get_jabber_client\nc.connect()\n File
/usr/share/rhn/osad/jabber_lib.py, line 577, in connect\n
jabber.Client.connect(self)\n File
/usr/lib/python2.6/site-packages/jabber/xmlstream.py, line 464, in
connect\nelse: self._sock.connect((self._hostIP, self._port))\n
File string, line 1, in connect\nerror: [Errno 111] Connection
refused\n')
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.setup_connection('Could not connect to any jabber server',)
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib.main('Unable
to connect to jabber servers, sleeping 10 seconds',)
This one is repeating a couple of times. After restart it also shows the
same scenario.
Are there any other logs to check?
On 08.02.2010 14:01, not applicable wrote:
---
*From:* spacewalk-list-boun...@redhat.com on behalf of
spacewalk-list-requ...@redhat.com[smtp:spacewalk-list-requ...@redhat.com]
*Sent:* Monday, February 08, 2010 2:01:48 PM
*To:* spacewalk-list@redhat.com
*Subject:* Spacewalk-list Digest, Vol 21, Issue 19
*Auto forwarded by a Rule*
Send Spacewalk-list mailing list submissions to
spacewalk-list@redhat.com
To subscribe or unsubscribe via the World Wide Web, visit
https://www.redhat.com/mailman/listinfo/spacewalk-list
or, via email, send a message with subject or body 'help' to
spacewalk-list-requ...@redhat.com
You can reach the person managing the list at
spacewalk-list-ow...@redhat.com
When replying, please edit your Subject line so it is more specific
than Re: 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 2010 13:13:51 +0100
From: Stefan Bluhm stefanblu...@alice-dsl.net
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] osa-dispatcher problems. no system ever
reports
Message-ID: 4b6f.5060...@alice-dsl.net
Content-Type: text/plain; charset=iso-8859-1; Format=flowed
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 stop processes:
Stopping s2s: [FAILED]
And these two messages on the start process.
Starting osa-dispatcher:
/usr/lib/python2.6/site-packages/jabber/jabber.py:68:
DeprecationWarning: the sha module is deprecated; use the hashlib module
instead
import sha, time
RHN 7447 2010/02/08 12:00:55 +02:00: ('Traceback (most recent call
last):\n File /usr/share/rhn/osad/jabber_lib.py, line 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in
_get_jabber_client\nc.connect()\n File
/usr/share/rhn/osad/jabber_lib.py, line 577, in connect\n
jabber.Client.connect(self)\n File
/usr/lib/python2.6/site-packages/jabber/xmlstream.py, line 464, in
connect\nelse: self._sock.connect((self._hostIP, self._port))\n
File string, line 1, in connect\nerror: [Errno 111] Connection
refused\n',)
So I guess some socket or so could not be opened. Does anyone have any
advise on what to do?
Thanks and best wishes,
Stefan
-- next part --
An HTML attachment was scrubbed...
URL:
https://www.redhat.com/archives
Re: [Spacewalk-list] osa-dispatcher problems. no system ever reports
Saxony/L=Hannover/O=ABC/OU=spacewalk.domain.com/CN=spacewalk.domain.com')
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
rhnSQL/driver_cx_Oracle._execute_wrapper('Executing SQL: select sysdate
as ID from dual with bind params: {}',)
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.setup_connection('Connecting to', 'spacewalk.domain.com')
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib._get_jabber_client
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib._get_jabber_client('Connecting to', 'spacewalk.domain.com')
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib.__init__
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib.__init__
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.check_cert('Loading cert', X509Name object
'/C=DE/ST=Lower
Saxony/L=Hannover/O=ABC/OU=spacewalk.domain.com/CN=spacewalk.domain.com')
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib.connect
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.connect('Attempting to connect',)
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.print_message('socket error',)
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.print_message('Could not connect to jabber server',
'spacewalk.domain.com')
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.setup_connection('ERROR', 'Traceback (most recent call
last):\n File /usr/share/rhn/osad/jabber_lib.py, line 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in
_get_jabber_client\nc.connect()\n File
/usr/share/rhn/osad/jabber_lib.py, line 577, in connect\n
jabber.Client.connect(self)\n File
/usr/lib/python2.6/site-packages/jabber/xmlstream.py, line 464, in
connect\nelse: self._sock.connect((self._hostIP, self._port))\n
File string, line 1, in connect\nerror: [Errno 111] Connection
refused\n')
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.setup_connection('Could not connect to any jabber server',)
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib.main('Unable
to connect to jabber servers, sleeping 10 seconds',)
This one is repeating a couple of times. After restart it also shows the
same scenario.
Are there any other logs to check?
On 08.02.2010 14:01, not applicable wrote:
---
*From:* spacewalk-list-boun...@redhat.com on behalf of
spacewalk-list-requ...@redhat.com[smtp:spacewalk-list-requ...@redhat.com]
*Sent:* Monday, February 08, 2010 2:01:48 PM
*To:* spacewalk-list@redhat.com
*Subject:* Spacewalk-list Digest, Vol 21, Issue 19
*Auto forwarded by a Rule*
Send Spacewalk-list mailing list submissions to
spacewalk-list@redhat.com
To subscribe or unsubscribe via the World Wide Web, visit
https://www.redhat.com/mailman/listinfo/spacewalk-list
or, via email, send a message with subject or body 'help' to
spacewalk-list-requ...@redhat.com
You can reach the person managing the list at
spacewalk-list-ow...@redhat.com
When replying, please edit your Subject line so it is more specific
than Re: 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 2010 13:13:51 +0100
From: Stefan Bluhm stefanblu...@alice-dsl.net
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] osa-dispatcher problems. no system ever
reports
Message-ID: 4b6f.5060...@alice-dsl.net
Content-Type: text/plain; charset=iso-8859-1; Format=flowed
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 stop processes:
Stopping s2s: [FAILED]
And these two messages on the start process.
Starting osa-dispatcher:
/usr/lib/python2.6/site-packages/jabber/jabber.py:68:
DeprecationWarning: the sha module is deprecated; use the hashlib module
instead
import sha, time
RHN 7447 2010/02/08 12:00:55 +02:00: ('Traceback (most recent call
last):\n File /usr/share/rhn/osad/jabber_lib.py, line 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in
_get_jabber_client\nc.connect()\n File
/usr/share/rhn/osad/jabber_lib.py, line 577, in connect\n
jabber.Client.connect(self)\n File
/usr/lib/python2.6/site-packages/jabber/xmlstream.py, line 464, in
connect\nelse: self._sock.connect((self._hostIP, self._port))\n
File string, line 1, in connect\nerror: [Errno 111] Connection
refused\n',)
So I guess some socket or so could not be opened. Does anyone have any
advise on what to do?
Thanks and best wishes,
Stefan
Re: [Spacewalk-list] osa-dispatcher problems. no system ever reports
xmllint gave no output
netstat -ptnl returns NO open port 5222. Telnetting to it also refuses a
connection
These are the open ports/apps
PID/Program name
14607/python:25151
14565/java
14690/java
14107/router:5347
14176/s2s:5347
888/sshd
740/cupsd
911/sendmail: accep
14258/java
14258/java
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/sbin/rhn-satellite stop (this
is when I got the error Stopping s2s: [FAILED]):
Feb 8 14:35:23 spacewalk jabberd/router[12237]: [127.0.0.1, port=58524]
connect
Feb 8 14:35:25 spacewalk jabberd/router[12237]: [127.0.0.1, port=58524]
error: XML parse error (not well-formed (invalid token))
Feb 8 14:35:25 spacewalk jabberd/router[12237]: [127.0.0.1, port=58524]
disconnect
Hmm, that XML error is strange. I wonder if that's from the config
files? Can you check the following:
# xmllint --noout /etc/jabberd/*.xml
Now heading straight for a /usr/sbin/rhn-satellite start:
...
So I can't really see any indications of an error in the logs. Note that
I can now do a telnet 127.0.0.1 5347 and connect successfully. So i am
not sure why the connection is refused on shut down. Do I need a FQDN or
should it all work on the 127.0.0.1 IP?
Now same thing for the log at /var/log/rhn/osa-dispatcher
Whilst stopping:
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib.main('Unable
to connect to jabber servers, sleeping 10 seconds',)
The port osa-dispatcher will try to connect to is 5222, which is run
by c2s. See what programs are listening:
# netstat -ptnl
Let's check for a common problem:
# cd /var/lib/jabberd/db/
(you may need to install db4-utils for the next step)
# db_verify authreg.db sm.db ; echo $?
0
--
Josh
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
[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 'server.rhnSQL.sql_base.SQLStatementPrepareError'
Exception Handler Information
Traceback (most recent call last):
File /usr/share/rhn/satellite_tools/reposync.py, line 136, in
import_packages
self.upload_package(pack, path)
File /usr/share/rhn/satellite_tools/reposync.py, line 157, in
upload_package
package.checksum_type, package.checksum)
File /usr/share/rhn/server/rhnPackage.py, line 419, in
get_package_for_checksum
h.execute(org_id=org_id, checksum=checksum, checksumtype=checksum_type)
File /usr/share/rhn/server/rhnSQL/sql_base.py, line 168, in execute
return apply(self._execute_wrapper, (self._execute, ) + p, kw)
File /usr/share/rhn/server/rhnSQL/driver_cx_Oracle.py, line 108, in
_execute_wrapper
raise apply(sql_base.SQLStatementPrepareError, args)
SQLStatementPrepareError: ('ORA-00942: table or view does not exist\n',
942, 'select p.id from rhnPackage p, rhnChecksumView c where p.org_id =
:org_id and p.checksum_id = c.id and c.checksum = :checksum and
c.checksum_type = :checksumtype')
I am not sure which version I ran before this latest nightly built but
it was certainly working ok. Let me know how I can help debugging it.
Best wishes,
Stefan
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
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 same error on starting. Also the new DB is not recreated.
So i recreated the db folder (mkdir /var/lib/jabberd/db; chmod
jabberd:jabberd /var/lib/jabberd/db) and restarted. Now the DB files are
also recreated.
Another restart and now I keep getting:
Stopping c2s: [ OK ]
Stopping s2s: [ OK ]
Yay, one problem fixed. But still, I get the same error on starting:
Starting osa-dispatcher:
/usr/lib/python2.6/site-packages/jabber/jabber.py:68:
DeprecationWarning: the sha module is deprecated; use the hashlib module
instead
import sha, time
RHN 27988 2010/02/08 21:35:11 +02:00: ('Traceback (most recent call
last):\n File /usr/share/rhn/osad/jabber_lib.py, line 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in
_get_jabber_client\nc.connect()\n File
/usr/share/rhn/osad/jabber_lib.py, line 577, in connect\n
jabber.Client.connect(self)\n File
/usr/lib/python2.6/site-packages/jabber/xmlstream.py, line 464, in
connect\nelse: self._sock.connect((self._hostIP, self._port))\n
File string, line 1, in connect\nerror: [Errno 111] Connection
refused\n',)
I remember at some point, there was a patch inserted in the previous
digests but I think this patch is already part of the nightly build.
Any other ideas how i could find the problem?
Thanks for your commitment,
Stefan
It looks like your .db files are corrupt, then... I recommend a:
(back it up first, if you want)
# rm -rf /var/lib/jabberd/db/
This seems to happen to a lot of people... look through the list
archives:
https://www.redhat.com/archives/spacewalk-list/2009-December/msg00147.html
https://www.redhat.com/archives/spacewalk-list/2010-January/msg00162.html
and then try to start jabberd again, via rhn-satellite or service.
Hope to help,
Josh
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
