`port self update` fails

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

`port self update` fails

Rasku, Stephen (GE Digital)
I am trying to do a “selfupdate” but it’s failing.  Note that our company may be blocking outgoing pings so that might explain the problematic ping/traceroute results.  I am able to get to rsync.macports.org but it re-directs to distfiles.macports.org.  Usually I am behind a proxy but I ran this test on our external network.

Is there any way I can fix this?
 
$ sudo port -d selfupdate
DEBUG: Copying /Users/212434537/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences
DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs
--->  Updating MacPorts base sources using rsync
DEBUG: system: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/macports/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs
rsync: failed to connect to rsync.macports.org: No route to host (65)
rsync error: error in socket IO (code 10) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-51/rsync/clientserver.c(106) [receiver=2.6.9]
Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/macports/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs
Exit code: 10
$ sudo /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/macports/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs
rsync: failed to connect to rsync.macports.org: No route to host (65)
rsync error: error in socket IO (code 10) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-51/rsync/clientserver.c(106) [receiver=2.6.9]
$ ping rsync.macports.org
PING ftp.rrze.uni-erlangen.de (131.188.12.211): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
^C
$ traceroute rsync.macports.org
traceroute to ftp.rrze.uni-erlangen.de (131.188.12.211), 64 hops max, 52 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
$ route get rsync.macports.org
   route to: ftp.rrze.uni-erlangen.de
destination: ftp.rrze.uni-erlangen.de
    gateway: 172.16.21.1
  interface: en0
      flags: <UP,GATEWAY,HOST,DONE,WASCLONED,IFSCOPE,IFREF>
 recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu     expire
       0         0         0         0         0         0      1500         0
$ host rsync.macports.org
rsync.macports.org is an alias for nue.de.rsync.macports.org.
nue.de.rsync.macports.org is an alias for ftp.fau.de.
ftp.fau.de is an alias for ftp.rrze.uni-erlangen.de.
ftp.rrze.uni-erlangen.de has address 131.188.12.211
ftp.rrze.uni-erlangen.de has IPv6 address 2001:638:a000:1021:21::1

…Stephen



Unsubscribe from GE's commercial electronic messages: http://sc.ge.com/*casl-unsubscribe 
Désabonner des messages électroniques commerciaux de GE: http://sc.ge.com/*lcap-desabonnement
Reply | Threaded
Open this post in threaded view
|

Re: `port self update` fails

Ryan Schmidt-24

> On Mar 7, 2017, at 09:32, Rasku, Stephen (GE Digital) <[hidden email]> wrote:
>
> I am trying to do a “selfupdate” but it’s failing.

Has it ever worked?

> Note that our company may be blocking outgoing pings so that might explain the problematic ping/traceroute results.

Tell your company to fix that; that's broken and it will interfere with MacPorts being able to determine what server is closest to you for fastest service.

> I am able to get to rsync.macports.org but it re-directs to distfiles.macports.org.

rsync.macports.org is an rsync server, not a web server, so there's no reason to access it in a web browser. If you do, it will, for historical reasons, redirect to distfiles.

> Usually I am behind a proxy but I ran this test on our external network.
>
> Is there any way I can fix this?
>
> $ sudo port -d selfupdate
> DEBUG: Copying /Users/212434537/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences
> DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs
> --->  Updating MacPorts base sources using rsync
> DEBUG: system: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/macports/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs
> rsync: failed to connect to rsync.macports.org: No route to host (65)

Consult your network administrator.


Reply | Threaded
Open this post in threaded view
|

Re: `port self update` fails

Rasku, Stephen (GE Digital)
In reply to this post by Rasku, Stephen (GE Digital)


On 2017-03-07, 8:33 AM, "Ryan Schmidt" <[hidden email]> wrote:
   
    > On Mar 7, 2017, at 09:32, Rasku, Stephen (GE Digital) <[hidden email]> wrote:
    >
    > I am trying to do a “selfupdate” but it’s failing.
   
    Has it ever worked?

It used to work.
   
    > Note that our company may be blocking outgoing pings so that might explain the problematic ping/traceroute results.
   
    Tell your company to fix that; that's broken and it will interfere with MacPorts being able to determine what server is closest to you for fastest service.
   
Unfortunately, that’s not going to accomplish anything.  It’s a company policy and the company has over 300k employees.  I have zero chance of influencing this.

    > I am able to get to rsync.macports.org but it re-directs to distfiles.macports.org.
   
    rsync.macports.org is an rsync server, not a web server, so there's no reason to access it in a web browser. If you do, it will, for historical reasons, redirect to distfiles.
   
    > Usually I am behind a proxy but I ran this test on our external network.
    >
    > Is there any way I can fix this?
    >
    > $ sudo port -d selfupdate
    > DEBUG: Copying /Users/212434537/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences
    > DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs
    > --->  Updating MacPorts base sources using rsync
    > DEBUG: system: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/macports/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs
    > rsync: failed to connect to rsync.macports.org: No route to host (65)
   
    Consult your network administrator.

OK, thanks.    
   
   


Unsubscribe from GE's commercial electronic messages: http://sc.ge.com/*casl-unsubscribe 
Désabonner des messages électroniques commerciaux de GE: http://sc.ge.com/*lcap-desabonnement