I verified that the corporate VPN was the problem in my case, with error detail "Operation timed out (60)". Of course this does not count as a malfunctioning server.
On Thu, May 15, 2025 at 5:51 AM Dave Allured - NOAA Affiliate < dave.allu...@noaa.gov> wrote: > I was seeing the same thing intermittently over the last few days. I'm on > MP 2.10.7 on Sonoma and Intel. At one point, exiting my corporate VPM > enabled the rsync to complete. This is not conclusive because the behavior > was not consistent. One might try different mirrors as described in this > FAQ. > > https://trac.macports.org/wiki/FAQ#selfupdatefails > > > On Thu, May 15, 2025 at 4:44 AM Sergey Fedorov <vital....@gmail.com> > wrote: > >> This is on Sonoma, not PowerPC: >> >> Synchronizing local ports tree from rsync:// >> rsync.macports.org/macports/release/tarballs/ports.tar >> >> rsync: failed to connect to rsync.macports.org: Connection refused (61) >> >> rsync error: error in socket IO (code 10) at >> /AppleInternal/Library/BuildRoots/289ffcb4-455d-11ef-953d-e2437461156c/Library/Caches/com.apple.xbs/Sources/rsync/rsync/clientserver.c(109) >> [receiver=2.6.9] >> >> Command failed: /usr/bin/rsync -rtzvl --delete-after --include=/ports.tar >> --include=/ports.tar.rmd160 --exclude=* rsync:// >> rsync.macports.org/macports/release/tarballs/ >> /opt/local/var/macports/sources/ >> rsync.macports.org/macports/release/tarballs >> >> Exit code: 10 >> >> Error: Synchronization of the local ports tree failed doing rsync >> >> port sync failed: Synchronization of 1 source failed >> >
