Opened 7 years ago
Closed 7 years ago
#56372 closed defect (invalid)
rsync: failed to connect to rsync.macports.org: No route to host (65)
| Reported by: | dbl001 (dbl) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.4.3 |
| Keywords: | Cc: | ||
| Port: |
Description
I'm on OS X 10.11.6.
$ port MacPorts 2.4.3
$ sudo port -v selfupdate ---> Updating MacPorts base sources using rsync 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-47/rsync/clientserver.c(105) [receiver=2.6.9] Command failed: /usr/bin/rsync -rtzvl --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
Change History (4)
comment:1 Changed 7 years ago by pmetzger (Perry E. Metzger)
comment:2 Changed 7 years ago by dbl001 (dbl)
I can't ping rsync.macports.org from my Mac (but I can from my iPhone). Clearly not a Macports issue.
Investigating.
comment:3 Changed 7 years ago by pmetzger (Perry E. Metzger)
Given that it isn't a macports issue, I'll be closing this.
comment:4 Changed 7 years ago by pmetzger (Perry E. Metzger)
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
It's working fine for me. I suspect this is a problem with your network, and not macports. Have you tried pinging rsync.macports.org? If you can't, then the problem isn't with macports.