Steffan,
I had the same thing happen on a complete network cluster.
Your DNS is unable to resolve the name: bluequartz.org
If you use the caching DNS (named) on your server, you simply need to
reinitialise it.
# service named restart
OR
If you don't use the caching DNS (named) on your server, you could
simply initialise it and configure your server (via the GUI or edit
/etc/resolv.conf dirctly) to use it.
# vi /etc/resolv.conf (add nameserver 127.0.0.1)
# chkconfig named on
# service named restart
Hope this helps,
Everard
On Tue, 06 Mar 2007 12:23:55 +0200, Arthur Sherman
<arturs (at mark) netvision.net.il> wrote:
> Sh*t happens.
> Try later.
>
>
> Best,
>
> --
> Arthur Sherman
>
> +972-52-4878851
> http://www.cpt.co.il/
>
>> -----Original Message-----
>> From: Steffan [mailto:snoord (at mark) planet.nl]
>> Sent: Tuesday, March 06, 2007 10:29 AM
>> To: coba-e (at mark) bluequartz.org
>> Subject: [coba-e:08997] yum problems any idees ?
>>
>> yum update
>> Setting up Update Process
>> Setting up repositories
>> Solarspeed.net AVS 100% |=========================|
>> 951 B 00:00
>> NuOnce Networks 100% |=========================|
>> 951 B 00:00
>> update 100% |=========================|
>> 951 B 00:00
>> http://bluequartz.org/pub/BlueQuartz/5100R/CentOS4/bluequartz/
>> i386/repodata/
>> repomd.xml: [Errno 4] IOError: <urlopen error (-3, 'Temporary
>> failure in
>> name resolution')>
>> Trying other mirror.
>> Cannot open/read repomd.xml file for repository: BlueQuartz
>> failure: repodata/repomd.xml from BlueQuartz: [Errno 256] No
>> more mirrors to
>> try.
>> Error: failure: repodata/repomd.xml from BlueQuartz: [Errno
>> 256] No more
>> mirrors to try.
>>
>>
>> Met vriendelijke groet,
>>
>> Steffan Noord
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.