This looks like a „simple” parsing error within the “updateinfo.xml.gz” of that
repo. Maybe the information was not written correctly….I don’t know.
What version of SW are you using?
Robert
Von: spacewalk-list-boun...@redhat.com Im
Auftrag von oogiej...@yahoo.com
Gesendet: Montag, 11. Juni
It's not spacewalks responsibility to check for package dependencies. It just
downloads the packages and stores them. That's it.
The "client" is responsible to calculate the dependencies and "get" the missing
packages from the repo
Also it sounds strange to me, that net-snmp depends on
s: (0, 'package list refreshed', {})
D: rpcServer: Calling XMLRPC registration.welcome_message
Robert
-Ursprüngliche Nachricht-
Von: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> Im
Auftrag von Paschedag, Robert
Gesendet: Freitag, 25. Mai 2018 16:10
An: spacewa
D: Sending back response(6, 'Invalid function call attempted', {}) "
Thanks,
Eric
-Original Message-
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paschedag, Robert
Sent: Friday, May 25, 2018 9:43 AM
To: spacewalk-list@redhat.com;
nly=None):
rpm -qf /usr/share/rhn/actions/packages.py
yum-rhn-plugin-2.0.1-10.el7.noarch
-Original Message-
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paschedag, Robert
Sent: Friday, May 25, 2018 7:51 AM
To: spacewalk-list@redhat.com; Robert P
OK.
My mistake. Was not the file "/usr/share/rhn/actions/errata.py" but
"/usr/share/rhn/actions/packages.py"
grep checkNeedUpdate /usr/share/rhn/actions/packages.py
'checkNeedUpdate',
def checkNeedUpdate(rhnsd=None, cache_only=None):
rpm -qf /usr/share/rhn/actions/packages.py
Ok. Never mind. Seems to be a problem at home ☹
-Ursprüngliche Nachricht-
Von: spacewalk-list-boun...@redhat.com Im
Auftrag von Robert Paschedag
Gesendet: Mittwoch, 23. Mai 2018 23:25
An: spacewalk-list@redhat.com
Betreff: [Spacewalk-list] Error with
ke a snapshot of the vm before testing the downgrade and test if
it fix the issue.
By the way, I cannot find the 2.8.28-1 version of the package in the 2.8 report
2018-05-23 10:58 GMT+02:00 Paschedag, Robert
<paschedag.netlut...@swr.de<mailto:paschedag.netlut...@swr.de>>:
Angelo,
___
Von: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> im
Auftrag von Paschedag, Robert <paschedag.netlut...@swr.de>
Gesendet: Mittwoch, 23. Mai 2018 10:22
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] Spacewalk 2.8 configure-proxy.sh Error
spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> im
Auftrag von Paschedag, Robert <paschedag.netlut...@swr.de>
Gesendet: Mittwoch, 23. Mai 2018 08:37
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] Spacewalk 2.8 configure-proxy.sh Error
__
che...@web.de>> ha scritto:
Am 22.05.2018 um 09:32 schrieb Paschedag, Robert:
>
>
>
>
> *Von:*
> spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>
> <spacew
Von: spacewalk-list-boun...@redhat.com im
Auftrag von Raymond Setchfield
Gesendet: Dienstag, 22. Mai 2018 12:04
An: spacewalk-list@redhat.com
Betreff: [Spacewalk-list] Cobbler Invalid Profile
Von: spacewalk-list-boun...@redhat.com im
Auftrag von Robert Paschedag
Gesendet: Montag, 21. Mai 2018 23:29
An: spacewalk-list@redhat.com; Angelo Lisco
Betreff: Re: [Spacewalk-list] Spacewalk 2.8
Von: spacewalk-list-boun...@redhat.com im
Auftrag von Mario Mikocevic
Gesendet: Freitag, 11. Mai 2018 13:28
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] Package refresh in UI
Some
at.com <spacewalk-list-boun...@redhat.com> on
behalf of Paschedag, Robert <paschedag.netlut...@swr.de>
Sent: Tuesday, May 08, 2018 13:37
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Problems syncing EPEL repositories
A possible quick hack??
https://emea01.safelinks.protectio
A possible quick hack??
https://github.com/spacewalkproject/spacewalk/pull/650
Robert
-Ursprüngliche Nachricht-
Von: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> Im
Auftrag von Paschedag, Robert
Gesendet: Dienstag, 8. Mai 2018 13:17
An: spacewal
and others.
Fedora EPEL 7
None <=== severity
nodejs-install-0.2.6-1.el7 newpackage update
Update to new version
...
Robert
-Ursprüngliche Nachricht-
Von: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> Im
Auftrag vo
Hmm...I'm not sure if SW is directly to blame here.
I think the error lies within the "yum" package which provides the python
libraries to parse the "updateinfo" XMLs
On my SW 2.7 system on CentOS 9, this is
yum-3.2.29-81.el6.centos.noarch
...
/usr/lib/python2.6/site-packages/yum/update_md.py
a 26 channel
On 05/03/2018 10:10 AM, Paschedag, Robert wrote:
Von:
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>
<spacewalk-list-boun...@redhat.com><mailto:spacewalk-list-boun...@redhat.com>
im Auftrag von Michae
Von: spacewalk-list-boun...@redhat.com im
Auftrag von Michael Watters
Gesendet: Donnerstag, 3. Mai 2018 15:25
An: spacewalk-list@redhat.com
Betreff: [Spacewalk-list] Error syncing Fedora 26 channel
When
ag, 24. April 2018 12:11:58
An: Paschedag, Robert; spacewalk-list@redhat.com
Betreff: RE: PCX boot for spacewalk client
Thanks rob, I got the same error I see on the console ,
Apr 23 23:57:53 vm1 in.tftpd[14018]: RRQ from 10.222.21.2 filename
//images/centos7-x86_64-server:2:usip-lab/vmlinu
og]#
See the colons? No problem here on SW 2.7.
Robert
Von: Afify, Sherif S (IBS) <sherif.af...@se1.bp.com>
Gesendet: Dienstag, 24. April 2018 10:48:49
An: spacewalk-list@redhat.com; Paschedag, Robert
Betreff: PCX boot for spacewalk client
Hi Robert, the
The colon sign is normally no problem. This is the default for all of our
profiles and they work without a problem.
Please look into the webserver log in /var/log/httpd/ to check for errors.
Robert
Von: spacewalk-list-boun...@redhat.com
No official documentation, but @phils blog
(http://www.devops-blog.net/category/spacewalk) is a good starting point when
you want to manage Ubuntu clients with spacewalk
This is a "repository" I created just to be able get the spacewalk "clients" to
work on a fresh Debian system
[root@srv
You did not mention, if the 32 packages have been successfully "downgraded"? If
not, then showing 0 packages to upgrade is correct.
Robert
Von: spacewalk-list-boun...@redhat.com Im
Auftrag von Yakin, Francis
Gesendet: Samstag, 31. März 2018 02:29
An:
You can check the path with
select * from rhnpackage where id = 11570;
But the message indicates some sort of error while you were synchronizing your
repos. I would try to locate this problem "package" within SW in the "Channels"
-> "Manage Software Channels" -> "Manage software packages" and
You are using old jpp5 repositories, you should no longer use. I don’t think,
that it is stated to use these repos. Earlier versions of spacewalk needed these
Java 5 packages. See the install page again
(https://github.com/spacewalkproject/spacewalk/wiki/HowToInstall)
Robert
Von:
Is that really all??
With this information only, it is impossible to help.
You can try to run osa-dispatcher manually
Stop it
/etc/init.d/osa-dispatcher stop
Run it manually
/usr/sbin/osa-dispatcher -N -v -v -v -v -v -v -v
and post errors you get.
Robert
Von:
-Ursprüngliche Nachricht-
Von: spacewalk-list-boun...@redhat.com Im
Auftrag von Yakin, Francis
Gesendet: Montag, 12. März 2018 19:25
An: spacewalk-list@redhat.com; Robert Paschedag
Betreff: Re: [Spacewalk-list]
Hi all,
just a quick question. I might need to "reimport" all my custom errata. In case
I want to remove the "old" errata, I need to
* first remove all packages within that errata from the errata itself and
* then remove the errata
?
Removing an errata directly (with containing
This is how I backup my spacewalk db
# crontab -l -u postgres
# make backup of spacewalk db
0 22 * * * /usr/bin/pg_dump --clean rhnschema 2>&1 1>
/var/lib/pgsql/backups/spacewalk_rhnschema_backup_daily.sql
And this file gets backed up every night from backup software.
Robert
Maybe your systems are just "up-to-date" or are you sure, you have a package
installed in a lower version than exists on the server?
Otherwise, this is just correct. SW won't show you available "updates" to
packages installed on your system.
-Ursprüngliche Nachricht-
Von:
-Ursprüngliche Nachricht-
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Paul-Andre Panon
Gesendet: Mittwoch, 18. Oktober 2017 05:38
An: spacewalk-list@redhat.com; Robert Paschedag
Betreff: Re: [Spacewalk-list]
ne
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@stretch:~#
Robert
-Ursprüngliche Nachricht-
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Paschedag, Robert
Gesendet: Dienstag, 17. Oktobe
-Ursprüngliche Nachricht-
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Paul-Andre Panon
Gesendet: Dienstag, 17. Oktober 2017 03:53
An: Robert Paschedag ; spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list]
x-12722-1 | slessp4-MozillaFirefox-12722 | 1
(1 Zeile)
rhnschema=#
Just wanted to know, why this broke
Robert
-Ursprüngliche Nachricht-
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Paschedag, Robert
Gesendet: Mittwoch, 1
Hi Bernhard,
thanks for that info. I have to try that after the Debian synchronization is
over.
-Ursprüngliche Nachricht-
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Lichtinger, Bernhard
Gesendet: Mittwoch, 11. Oktober 2017 12:29
one*
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Paschedag, Robert
Gesendet: Mittwoch, 11. Oktober 2017 08:44
An: spacewalk-list@redhat.com
Betreff: [Spacewalk-list] Anybody syncing SLES repositories with SW 2.7?
Hi all,
is anybody h
Hi all,
is anybody here that is also syncing SLES repositories and has updated to SW
2.7?
While I was testing 2.7 (also nightly) on my test system, I was so focused
primary on "deployment" of SLES and Debian systems, that I did not have an eye
on the repo synchronization.
Now, when I try to
at.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Paschedag, Robert
Gesendet: Freitag, 29. September 2017 15:36
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] Importing errata from RPM channel failes with
ERROR: 'list' object has no attribute 'keys'
I think I spotted an
I think I spotted an error.
In “errataImport.py” an errata may be ignored because a newer version has
already been found.
for errata in self.batch:
advisory = errata['advisory_name']
release = errata['advisory_rel']
if advisory in advisories:
Hi all,
just upgraded my test SW server to 2.7 and noticed an error when trying to sync
SUSE repos. The import of erratas seems to fail.
This system has been set up to 2.7 nightly before and to be honest, I did not
yet check the repo synchronization while I was on nightly.
Here is an error
Further information. With a SLES12 channel, the message is slightly different
14:56:26 Repo http://server/repo/SUSE/Updates/SLE-SDK/12-SP1/x86_64/update/ has
507 errata.
14:56:33 Syncing 507 new errata to channel.
14:56:36 Sync of channel completed in 0:15:36.
14:56:36 Total time: 0:15:36
edhat.com] On Behalf Of Paschedag, Robert
Sent: Monday, 11 September 2017 4:35 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]
Hmma hard one.
What errors do you get on the "client" side?
-Ursprüngliche
iled to start.
None of the clients have OSAD installed and nor can they hit port 5222 due to
firewall rules.
The only error we get is when we try to start OSA Dispatcher.
Regards
Andrew
-Original Message-
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On
sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/>subscription='both' />
>
>--> 'jabber:iq:roster' />
>
><-- />
>
>Spacewalk 17712 2017/09/11 00:52:44 -00:00: ('Received an error stanza:
>', />)
>Spacewalk 17712 2017/09/11 00:52:44 -00:00: ('Received
Hi Andrew,
it is this "id" that looks odd (to me)
>>to='rhn-dispatcher-sat@FQDN-censored-address/superclient'
>>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'>=
And later set to another id
>>to='rhn-dispatcher-sat@FQDN-censored-address/superclient'
>>type='set'
Can you verify, that the oracle user password is correctly set within
/etc/rhn/rhn.conf?
If not, you might “lock” the account again because spacewalk tries to login too
often and therefore gets locked.
Robert
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com]
I think the CN value of the SSL certificate generated does not match the
hostname URL you are using with your browser. That's why you are getting the
info "your connection is not secure".
-Ursprüngliche Nachricht-
Von: spacewalk-list-boun...@redhat.com
Hi all,
I think I found a bug within spacewalk that is triggered from the SLES PXE
installer.
The SLES installer (autoyast) seems to encode the URL for the kickstart config
file from
"GET /cblr/svc/op/ks/profile/SLES12-SP1-Standard-LVM:1:COMP HTTP/1.1"
to
"GET
The credentials for the postgres db should be stored within /etc/rhn/rhn.conf
on the satellite server.
By default, this is
User: rhnuser
PW: rhnpw
DB: rhnschema
So..switching to user postgres
Su – postgres
And
psql -U -d
and entering password should give you access.
There is also a
Hi all,
I just wanted to inform, that the PR 500
(https://github.com/spacewalkproject/spacewalk/pull/500) seems to work pretty
good in the "nightly" spacewalk version.
We tested this on our "TESTING" system and upgraded to "2.7 nightly".
Because we already have synced several Debian
Maybe you are facing this bug?
https://www.redhat.com/archives/spacewalk-list/2017-June/msg00103.html
Robert
Mit freundlichen Grüßen
Robert Paschedag
Netlution GmbH
Landteilstr. 33
68163 Mannheim
im Auftrag des
SWR
Südwestrundfunk
HA IT, Medientechnik und Programmverbreitung
Neckarstraße 230
Hi,
I'm just upgraded my spacewalk testing system to SW 2.6 on CentOS 6 and am
trying to synchronize the Debian jessie main repository.
I did this 2 times now. Both completed successfully (according to the logfile),
but the packages are not listed within the channel
See some output of the
54 matches
Mail list logo