Thanks for the response Melcon.  This thread was resolved, but for posterity’s 
sake it was a virtual server who was having trouble getting updates as a result 
of a Squid configuration issue on the pfSense box.  Once the issue with the 
proxy server was identified and fixed, the yum update issue went away.


Dave.

 

From: [email protected] 
[mailto:[email protected]] On Behalf Of Melcon Moraes
Sent: Friday, May 04, 2012 6:31 PM
To: sipXecs developer discussions
Subject: Re: [sipx-dev] new 4.6 RPMs published

 

Was it on bare metal or virtual?

 

-

MM

On Thu, Apr 19, 2012 at 7:12 PM, Michael Picher <[email protected]> wrote:

I did a clean install on a CentOS 6.2 minimal install with no issues.

 

Using this procedure:

 

1.      Update CentOS 6.2 to most current

        1.      yum update

2.      Install bind & nano

        1.      yum install bind nano

3.      Add repo file to your system
        curl \
        
http://download.sipfoundry.org/pub/sipXecs/sipxecs-0.0.4.5.2-centos.repo > \
        /etc/yum.repos.d/sipxecs.repo
4.      Install
        yum install epel-release
        yum groupinstall sipxecs
5.      Run setup and answer questions
        sipxecs-setup

 

Thanks,

  Mike

 

On Thu, Apr 19, 2012 at 5:57 PM, George Niculae <[email protected]> wrote:

On Thu, Apr 19, 2012 at 11:46 PM, Dave May <[email protected]> wrote:
> George,
>
> I'm getting the following error when trying to yum update across a few
> different CentOS 6.2 x64 boxes.  The errors persist even after a "yum
> clean all".  Is this a known issue?
>
>        [root@sipx2 ~]# yum update
>        Loaded plugins: fastestmirror, refresh-packagekit, security
>        Loading mirror speeds from cached hostfile
>         * base: centos.mirrorcatalogs.com
>         * epel: mirror.clarkson.edu
>         * extras: mirror.5ninesolutions.com
>         * updates: centos.mirrorcatalogs.com
>
> http://download.sipfoundry.org/pub/sipXecs/snapshot/CentOS_6/x86_64/repo
> data/primary.xml.gz: [Errno 14] PYCURL  ERROR 22 - "The requested URL
> returned error: 416"

This looks like you're behind a proxy, if it so you need to specify it
in /etc/yum.conf, is that the case?


George
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/





 

-- 
Michael Picher, Director of Technical Services
eZuce, Inc.

300 Brickstone Square

Suite 201

Andover, MA. 01810

O.978-296-1005 X2015 <tel:978-296-1005%20X2015>  
M.207-956-0262
@mpicher <http://twitter.com/mpicher> 
www.ezuce.com

 

------------------------------------------------------------------------------------------------------------

There are 10 kinds of people in the world, those who understand binary and 
those who don't.

 


_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

 

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to