Cannot access rsync.macports.org

[Paul Sijpkes]

Okay, there was  ticket opened on this about 18 months ago, number  
#12684.
Says that if you are running PeerGuardian then it blocks incoming  
connections from that socket.

I've killed peerguardian, but it's still happening...
Is there any other process that could do this?

On 23/03/2009, at 12:38 PM, Paul Sijpkes wrote:

> Just a minute...
>
> it says connection refused, not that it was not found...
>
> This is my selfupdate output... any ideas anyone?
>
> sudo port -dv selfupdate
> Password:
> DEBUG: Synchronizing ports tree(s)
> Synchronizing local ports tree from rsync://rsync.macports.org/ 
> release/ports/
> DEBUG: /usr/bin/rsync -rtzv --delete-after rsync:// 
> rsync.macports.org/release/ports/ /opt/local/var/macports/sources/ 
> rsync.macports.org/release/ports
> rsync: failed to connect to rsync.macports.org: Connection refused  
> (61)
> rsync error: error in socket IO (code 10) at /SourceCache/rsync/ 
> rsync-35.2/rsync/clientserver.c(105) [receiver=2.6.9]
> Error: Synchronization of the local ports tree failed doing rsync
> DEBUG: Couldn't sync the ports tree: Synchronization of 1 source(s)  
> failed
>    while executing
> "macports::selfupdate [array get global_options]"
> Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync  
> the ports tree: Synchronization of 1 source(s) failed
>
>
> On 23/03/2009, at 12:34 PM, Paul Sijpkes wrote:
>
>> Thanks for your help Joshua,
>>
>> Tried telneting, but still no luck... must be an ISP issue.
>> Am I missing something?
>>
>> telnet rsync.macports.org 873
>>
>> Trying 17.254.17.246...
>> telnet: connect to address 17.254.17.246: Connection refused
>> telnet: Unable to connect to remote host
>>
>> cheers,
>> Paul
>>
>> On 23/03/2009, at 12:13 PM, Joshua Root wrote:
>>
>>> Paul Sijpkes wrote:
>>>> Hi all,
>>>>
>>>> I just installed MacPorts 1.7.0 and my machine cannot access the  
>>>> rsync URL
>>>> rsync.macports.org when I use the port -d selfupdate command.
>>>>
>>>> Strangely enough, the url that ping looks up  (alpha.osforge.org)  
>>>> works
>>>> in a browser,
>>>> so this indicates Port 80 is open. Is it possible that whichever  
>>>> port
>>>> that RSYNC uses is
>>>> blocked by my ISP?  I've never had anything else blocked by them,  
>>>> so
>>>> this would be odd...
>>>>
>>>> I've checked my firewall setting and tried pinging the above  
>>>> addresses,
>>>> but I have no access.
>>>> Before I contact my ISP, I'd just like to make sure that the server
>>>> still exists and also find out
>>>> which port that selfupdate uses with rsync.
>>>>
>>>> Thanks for any help on this matter,
>>>> Paul
>>>
>>> It should definitely be working. Rsync uses TCP port 873, check if  
>>> you
>>> can telnet to that port on rsync.macports.org.
>>>
>>> If it is being blocked, there are some alternatives:
>>> <http://trac.macports.org/wiki/howto/PortTreeTarball>
>>> <http://trac.macports.org/wiki/howto/SyncingWithSVN>
>>>
>>> - Josh
>>
>