sudo port -v selfupdate

[stevenhaggerty@…]

bash-3.2# 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 /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/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
bash-3.2# 

[ryandesign (Ryan Carsten Schmidt)]

Apparently you're not able to reach our rsync server.

Has it ever worked?

Does your network allow connections to rsync servers?

[stevenhaggerty@…]

Has it ever worked? No first attempt.

Does your network allow connections to rsync servers? I turned off my firewall. How can I test if RSYNC works? Steve

[stevenhaggerty@…]

I turned off my firewall. Do I have to talk with my ISP ... Comcast? How can I test if RSYNC works?

Steve

[ryandesign (Ryan Carsten Schmidt)]

Usually we only find this kind of problem on restrictive corporate networks, not home networks.

You could try running:

rsync rsync://rsync.macports.org

If you get a few lines describing the rsync modules we serve, it's working. If you get an error like the one you reported above, it's not working.

The OS X firewall shouldn't be a problem. Third party firewall products might be a problem.

If you use antivirus software or anything else that might modify network connections, you could try disabling that as well.

[raimue (Rainer Müller)]

Network error on user's end, so we cannot do anything about it.