Hi Javier,
Please help to resolve this issue
Thanks,
Prashant Koli
From: Prashant Koli
Sent: 13 August 2018 10:53
To: spacewalk-list@redhat.com
Subject: RE: [Spacewalk-list] cannot retrieve repository metadata ( repomd.xml )
Importance: High
Hi Javier,
Good morning, thanks for your update
My
to resolve this issue
Thanks for your time and support
Regards,
Prashant Koli
From: spacewalk-list-boun...@redhat.com On
Behalf Of Flores, Javier (D4\INF\IT ID)
Sent: 10 August 2018 18:31
To: 'spacewalk-list@redhat.com'
Subject: Re: [Spacewalk-list] cannot retrieve repositor
redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Prashant Koli
Gesendet: Freitag, 10. August 2018 14:52
An: spacewalk-list@redhat.com
Betreff: [Spacewalk-list] cannot retrieve repository metadata ( repomd.xml )
Priorität: Hoch
Dear Team,
I am facing issue with spacewalk server 2.2 ,
Dear Team,
I am facing issue with spacewalk server 2.2 , repository : oraclelinux6_x86_64
While doing yum update its showing "Error : cannot retrieve repository metadata
( repomd.xml ) for repository : oraclelinux6_x86_64. Please verify its path and
try again "
Kindly help to resolve this issue
T
delete that directory
>and let
>> taskomatic recreate it.
>>
>> Sent from my BlackBerry - the most secure mobile device
>> *From:* prmari...@gmail.com
>> *Sent:* August 2, 2017 11:21 AM
>> *To:* spacewalk-list@redhat.com
>> *Subject:* Re: [Spacewalk-list
11:21 AM
> *To:* spacewalk-list@redhat.com
> *Subject:* Re: [Spacewalk-list] Cannot retrieve repository metadata
>
> First things first try restarting taskomatic
> There are more steps after that but they are very intrusive and 7 times
> out of 10 that will fix it
>
> Sent fr
eviceFrom: prmari...@gmail.comSent: August 2, 2017 11:21 AMTo: spacewalk-list@redhat.comSubject: Re: [Spacewalk-list] Cannot retrieve repository metadataFirst things first try restarting taskomaticThere are more steps
: spacewalk-list@redhat.comReply-to: spacewalk-list@redhat.comSubject: [Spacewalk-list] Cannot retrieve repository metadata I need some quick help from some one immediately as I am
facing problem when registering RedHat 6 client with Spacewalk Server
and below is the error. Kindly help on this.Below
Hi All,
Also please find some more output when I enabled debug mode in
/etc/sysconfig/rhn/up2date file , before registering client with spacewalk
server. Please share your input on this.
[root@ip-10-65-228-47 ec2-user]# cat /etc/sysconfig/rhn/up2date | grep
debug=1
debug=1
[root@ip-10-65-228-47
Hi All,
Anybody has any update for above spacewalk issue ?
Thanks
Suresh S
On Tue, Aug 1, 2017 at 4:01 PM, sureshskja skja
wrote:
> Hi All,
>
> I need some quick help from some one immediately as I am facing problem
> when registering RedHat 6.7 client with Spacewalk Server and below is the
>
I need some quick help from some one immediately as I am facing problem
when registering RedHat 6 client with Spacewalk Server and below is the
error. Kindly help on this.
Below is the error details.
REGISTRATION
* registering
/usr/sbin/rhnreg_ks --force --activationkey 1-East_Non_Pr
AM
To: spacewalk-list@redhat.com; Jérémie Pradet
Subject: Re: [Spacewalk-list] Cannot retrieve repository metadata (repomd.xml)
Am 9. Januar 2017 08:23:13 MEZ schrieb "Jérémie Pradet"
:
>Before, ask my question, I wish you a good new year.
>
>I have a Spacewalk 2.4, and I use it to
Am 9. Januar 2017 08:23:13 MEZ schrieb "Jérémie Pradet"
:
>Before, ask my question, I wish you a good new year.
>
>I have a Spacewalk 2.4, and I use it to download packages and Errata
>from
>redhat.
>For some time, I can't update my Erratas.
>When I run spacewalk-repo-sync. I have the below error
Before, ask my question, I wish you a good new year.
I have a Spacewalk 2.4, and I use it to download packages and Errata from
redhat.
For some time, I can't update my Erratas.
When I run spacewalk-repo-sync. I have the below error message.
/usr/bin/spacewalk-repo-sync --channel rhel-6-server
Great, yeah that stuff is usually taken care of in the bootstrap, which is
how we register our systems to Spacewalk initially. The hard part is when
we have to reregister systems after they already have
/etc/sysconfig/rhn/systemid and so on... but that's another story.
On Thu, Mar 31, 2016 at 4:4
Eventually this script fixed all the stuff :).
rpm -Uvh
http://spacewalk/repos/spacewalk_client6/2.3-client/RHEL/6/x86_64/spacewalk-client-repo-2.3-2.el6.noarch.rpm
rpm -Uvh http://spacewalk/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm
cat > /etc/yum.repos.d/spacewalk-client.repo << EOF
[spacewal
Oh, that error you're seeing is because your system(s) don't recognize the
SSL cert generated by Spacewalk. In your bootstrap script, is the
RHN-ORG-TRUSTED-CERT (or something like that) being pushed correctly to the
clients? Otherwise they won't recognize the SSL cert being presented by
your Spa
The problem is - my servers don't have internet access. I set up epel repo
sync on spacewalk...For example epel
[epel]
name=Extra Packages for Enterprise Linux 6 - $basearch
baseurl=https://spacewalk/repos/epel6/x86_64/
#mirrorlist=
https://mirrors.fedoraproject.org/metalink?repo=epel-6&arch=$bas
I had a similar issue for systems that had old versions of nss, they
couldn't deal with an HTTPS repo for some reason. Is your
/etc/sysconfig/rhn/up2date pointing to https://something by chance? If so
try changing it to http, updating yum and nss fully, then changing it back
to https.
One liner:
Deployed a new machine, it didn't have internet access, added manually epel
repo & spacewalk repo and installed client, registered on the spacewalk.
The system shows this error, when I try to do anything:
Cannot retrieve repository metadata (repomd.xml) for repository:
epel_sci_6. Please verify i
line. And then there are some systems that arent working with
> this ...
>
> But finally it worked!!!
>
> Thanks :)
>
>
> --
> *From: *"Loïc Chanel"
> *To: *spacewalk-list@redhat.com
> *Sent: *Monday, November 30, 2015 11:36:59 A
ery desperate ...
>
> But now it works!
>
> thanks ;)
>
> --
> *From: *"Kobus Bensch"
> *To: *"spacewalk-list"
> *Sent: *Monday, November 30, 2015 11:37:54 AM
> *Subject: *Re: [Spacewalk-list] Cannot retrieve repository
&
Hello,
I did it because I was already very desperate ...
But now it works!
thanks ;)
- Original Message -
From: "Kobus Bensch"
To: "spacewalk-list"
Sent: Monday, November 30, 2015 11:37:54 AM
Subject: Re: [Spacewalk-list] Cannot retrieve repository metada
configuration
line. And then there are some systems that arent working with this ...
But finally it worked!!!
Thanks :)
- Original Message -
From: "Loïc Chanel"
To: spacewalk-list@redhat.com
Sent: Monday, November 30, 2015 11:36:59 AM
Subject: Re: [Spacewalk-list] Canno
acewalk-list@redhat.com
> *Sent: *Monday, November 30, 2015 11:00:45 AM
> *Subject: *Re: [Spacewalk-list] Cannot retrieve
> repositorymetadata(repomd.xml)
>
> I had this issue and restarting the spacewalk server solved it.
>
> -Original Message
dhat.com] On Behalf Of Kobus Bensch
> Sent: Monday, November 30, 2015 11:23 AM
> To: spacewalk-list@redhat.com
> Subject: Re: [Spacewalk-list] Cannot retrieve repository metadata
> (repomd.xml)
>
> what happens when you do rhncfg-client get and rhn-profile-sync and
> rhn-channel --lis
Hello,
serverURL=http://spacewalk.domain.de/XMLRPC
kind regards,
Philipp
- Original Message -
From: "Kobus Bensch"
To: "spacewalk-list"
Sent: Monday, November 30, 2015 11:23:08 AM
Subject: Re: [Spacewalk-list] Cannot retrieve repository metadata (repomd
ewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Cannot retrieve repository metadata (repomd.xml)
what happens when you do rhncfg-client get and rhn-profile-sync and
rhn-channel --list
On 30/11/2015 09:05, Philipp Wehling wrote:
> Hello,
>
> Im using spacewalk for roundabout 60 syste
:23 AM
> To: spacewalk-list@redhat.com
> Subject: Re: [Spacewalk-list] Cannot retrieve repository metadata
> (repomd.xml)
>
> what happens when you do rhncfg-client get and rhn-profile-sync and
> rhn-channel --list
>
>
> On 30/11/2015 09:05, Philipp Wehling wrote:
> &
6-x86_64
> sl6-x86_64-fastbugs
> sl6-x86_64-security
> spacewalkclient-x86_64-sl6
>
>
>
> But still the error is persistent...
>
> ------
> *From: *"Kobus Bensch"
> *To: *spacewalk-list@redhat.com
> *Sent: *Monday, November 30, 2
-list] Cannot retrieve repository metadata (repomd.xml)
what happens when you do rhncfg-client get and rhn-profile-sync and
rhn-channel --list
On 30/11/2015 09:05, Philipp Wehling wrote:
> Hello,
>
> Im using spacewalk for roundabout 60 systems.
>
> Only 3 of them have problems
age -
From: "Kobus Bensch"
To: spacewalk-list@redhat.com
Sent: Monday, November 30, 2015 10:22:45 AM
Subject: Re: [Spacewalk-list] Cannot retrieve repository metadata (repomd.xml)
what happens when you do rhncfg-client get and rhn-profile-sync and
rhn-channel --list
On
Hello,
already did this. Didnt work.
kind regards,
Philipp
- Original Message -
From: "Loïc Chanel"
To: spacewalk-list@redhat.com
Sent: Monday, November 30, 2015 10:13:04 AM
Subject: Re: [Spacewalk-list] Cannot retrieve repository metadata (repomd.xml)
Did you tr
what happens when you do rhncfg-client get and rhn-profile-sync and
rhn-channel --list
On 30/11/2015 09:05, Philipp Wehling wrote:
Hello,
Im using spacewalk for roundabout 60 systems.
Only 3 of them have problems with repository metadata:
# yum update
Loaded plugins: rhnplugin, security
Thi
Did you try to clean entirely yum's cache (via yum clean all and rm -rf
/var/cache/yum/* ) ?
It may be a corrupted cache related problem.
Regards,
Loïc
Loïc CHANEL
System & virtualization engineer
TO - XaaS Ind - Worldline (Villeurbanne, France)
2015-11-30 10:05 GMT+01:00 Philipp Wehling :
>
Hello,
Im using spacewalk for roundabout 60 systems.
Only 3 of them have problems with repository metadata:
# yum update
Loaded plugins: rhnplugin, security
This system is receiving updates from RHN Classic or Red Hat Satellite.
Error: Cannot retrieve repository metadata (repomd.xml) for
Hello,
Im having trouble with some particular client.
Due to old systems, there was spacewalk client 1.7 installed. The server runs
under version 2.3.
A co-worker tried to register the client with version 1.7. This worked without
problems, but when I try to use yum, there is following error
Hi Folks,
So, all of a sudden over the course of a week, my Spacewalk server can't
kickstart RHEL 6.6 systems anymore... I'm getting an strange "unable to read
package metadata" error from anaconda.
The issue seems to be I'm getting a 404 when it tries to pull:
http:///ks/disk/org/1/rhel-x86_6
Hey Kazi,
Did you ever get this worked out? I'm in a similar boat with spacewalk 1.7
w/ postgresql.
I can successfully add a client, and it checks in, but when I do any yum
functions, it barfs with the same error as you. I checked time and I am not
using ssl so that isn't the problem for me.
Wha
Is the time set right on the client? I was having a similar problem and
it was due to time and the ssl certificate.
On 04/28/2012 08:23 AM, Kazi Hossain wrote:
I recently installed Spacewalk 1.7 and Create new channel.
I am having an issue where I cannot get a system that is subscribed to
t
I recently installed Spacewalk 1.7 and Create new channel.
I am having an issue where I cannot get a system that is subscribed to the
new channel to update any packages. There seems to be an issue with the
channel config. When I run a “yum list” command on the client of the new
channel I get the f
On Fri, Aug 26, 2011 at 04:09:57PM +0200, Razvan Cosma wrote:
> Problem was solved with some random deletions from qrtz_triggers and
> alter table qrtz_fired_triggers alter column priority drop not null;
> Not sure if this is a bug in taskomatic or something that went wrong
> while I was installin
On Thu, Aug 25, 2011 at 02:55:22PM +0200, Razvan Cosma wrote:
>
> /var/log/rhn/rhn_taskomatic_daemon.log:
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:2449)
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.run(JobStoreSupport.ja
Problem was solved with some random deletions from qrtz_triggers and
alter table qrtz_fired_triggers alter column priority drop not null;
Not sure if this is a bug in taskomatic or something that went wrong
while I was installing the application, but I will say that taskomatic
fails way too easily
Update on the below:
I have cleared the table rhntaskorun, deleted all non-default lines
from rhntaskoschedule, still when restarting the taskomatic service I
get
FATAL | jvm 1| 2011/08/26 15:28:45 | Failure occured during job recovery.
com.redhat.rhn.taskomatic.core.TaskomaticException: Fail
Hello,
Just testing a nightly spacewalk, with postgresql backend, have
deployed (kickstart, bare metal) a RHEL 6.1 machine, and everything
seemed fine, i.e. hostname is set from dhcp, install goes on with no
errors, rhnreg_ks is OK and the host shows up in the web interface. Up
to the first 'yum u
I found the issue:
Sascha Frey wrote:
>The HTTPd logs on the server show a bad request (400):
>129.70.137.XX - - [24/Jun/2011:15:57:50 +0200] "POST /XMLRPC HTTP/1.1" 200 1544
>129.70.137.XX - - [24/Jun/2011:15:57:50 +0200] "GET
>/XMLRPC/GET-REQ/sl-x86_64-6/repodata/repomd.xml HTTP/1.1" 400 309
Hi,
we just set up a spacewalk server and got our first client kickstarted.
The client cannot access any channel on the spacewalk server.
'yum update' returns 'Error: Cannot retrieve repository metadata
(repomd.xml) for repository: sl-x86_64-6. Please verfiy its path and try
again'.
It does work
I have a spacewalk 1.0 install running on a x86 CentOS 5.5 install. I
followed the instructions found at
http://wiki.centos.org/HowTos/PackageManagement/Spacewalk. I have
synced the repositories that I think that I am going to need and I
have one client CenOS 5.5 system pointing at the spacewalk se
Hi,
I have been kickstarting a number of machines from our Spacewalk 0.5 server,
and I'm struggling to get Fedora 11 x86_64 going. I have created a
distribution, by following
https://fedorahosted.org/spacewalk/wiki/HowToKickstartCobbler . Mostly that
seemed to work; a few oddnesses (eg, under sect
Fraginhell wrote:
> Hi.
>
> I have configured about 6 Centos 32bit machines on our spacewalk
> server. Centos 5.3 x64, spacewalk 0.5
> One of the clients can perform a yum check-update fine without any
> problems, the rest all report
>
> Error: Cannot retrieve repository metadata (repomd.xml) for
: [Spacewalk-list] Cannot retrieve repository metadata
Hi.
I have configured about 6 Centos 32bit machines on our spacewalk
server. Centos 5.3 x64, spacewalk 0.5
One of the clients can perform a yum check-update fine without any
problems, the rest all report
Error: Cannot retrieve repository
Hi.
I have configured about 6 Centos 32bit machines on our spacewalk
server. Centos 5.3 x64, spacewalk 0.5
One of the clients can perform a yum check-update fine without any
problems, the rest all report
Error: Cannot retrieve repository metadata (repomd.xml) for
repository: rpmforge-el5-i386 Pl
53 matches
Mail list logo
