Opened 10 years ago

Closed 9 years ago

#46264 closed defect (worksforme)

Failure to connect to rysnc.macports.org

Reported by: gerard.cummins@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version:
Keywords: Cc:
Port:

Description (last modified by dbevans (David B. Evans)) 

sudo port -v selfupdate
--->  Updating MacPorts base sources using rsync
rsync: failed to connect to rsync.macports.org: Operation timed out (60)
rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-45/rsync/clientserver.c(105) [receiver=2.6.9]
Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
Exit code: 10
Error: Error synchronizing MacPorts sources: command execution failed
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed

Change History (3)

comment:1 Changed 10 years ago by dbevans (David B. Evans)

Component: ports → base
Description: modified (diff)
Version: 2.3.3

Please use WikiFormatting to enhance readability when submitting log excerpts or terminal messages.

comment:2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Does this always happen? If so, has it ever worked? Usually this type of error indicates either a temporary network or server issue which will resolve itself, or a deliberate or accidental blockage of rsync traffic on your network (if so, contact your network administrator).

comment:3 Changed 9 years ago by larryv (Lawrence Velázquez)

Resolution: → worksforme
Status: new → closed

No response from OP. Assuming it was a non-MacPorts problem.

Note: See TracTickets for help on using tickets.