[MacPorts] #49596: command execution failed
#49596: command execution failed -------------------------------+-------------------------------- Reporter: vinay0410sharma@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: -------------------------------+-------------------------------- Computer: ~$ 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 -- Ticket URL: <https://trac.macports.org/ticket/49596> MacPorts <https://www.macports.org/> Ports system for OS X
#49596: selfupdate: rsync: failed to connect to rsync.macports.org: Operation timed out (60) --------------------------------+-------------------------------- Reporter: vinay0410sharma@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: Port: | --------------------------------+-------------------------------- Changes (by ryandesign@…): * priority: High => Normal * component: ports => base Old description:
Computer: ~$ 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
New description: {{{ Computer: ~$ 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 }}} -- Comment: Has this ever worked? Maybe there is a network problem at your end. Maybe there is a temporary server issue on our end. Try again later? -- Ticket URL: <https://trac.macports.org/ticket/49596#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#49596: selfupdate: rsync: failed to connect to rsync.macports.org: Operation timed out (60) --------------------------------+-------------------------------- Reporter: vinay0410sharma@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: Port: | --------------------------------+-------------------------------- Comment (by rderosa86@…): I have the same issue. {{{ ---> 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 }}} Also, I tried to ping rsync.macports.org and it just timed out. Has the address changed? -- Ticket URL: <https://trac.macports.org/ticket/49596#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#49596: selfupdate: rsync: failed to connect to rsync.macports.org: Operation timed out (60) --------------------------------+-------------------------------- Reporter: vinay0410sharma@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: Port: | --------------------------------+-------------------------------- Comment (by macports@…): Seems to be down for me too (and it used to work for me). Connection stays stuck on SYN_SENT, but no ACK is ever received. To [comment:2 rderosa86@...]: No the address has not changed. MacPorts' hosting provider has been experiencing intermittent issues over the last few months. This seems to be one of them. You can wait for the service to be back up, or you can [[howto/SyncingWithSVN|sync with the Subversion repository]]. -- Ticket URL: <https://trac.macports.org/ticket/49596#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#49596: selfupdate: rsync: failed to connect to rsync.macports.org: Operation timed out (60) --------------------------------+--------------------- Reporter: vinay0410sharma@… | Owner: admin@… Type: defect | Status: new Priority: High | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | --------------------------------+--------------------- Changes (by ryandesign@…): * priority: Normal => High * owner: macports-tickets@… => admin@… * version: 2.3.4 => * component: base => server/hosting * cc: bradjcox@…, ryandesign@… (added) Comment: Has duplicate #49615. Keith, rsync.macports.org and distfiles.macports.org (same IP address) are not responding to pings or http requests. -- Ticket URL: <https://trac.macports.org/ticket/49596#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
#49596: selfupdate: rsync: failed to connect to rsync.macports.org: Operation timed out (60) --------------------------------+--------------------- Reporter: vinay0410sharma@… | Owner: admin@… Type: defect | Status: new Priority: High | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | --------------------------------+--------------------- Comment (by satindersingh71@…): Replying to [comment:3 macports@…]: Does anyone know when it will be back up?
Seems to be down for me too (and it used to work for me). Connection stays stuck on SYN_SENT, but no ACK is ever received.
To [comment:2 rderosa86@...]: No the address has not changed. MacPorts' hosting provider has been experiencing intermittent issues over the last few months. This seems to be one of them.
You can wait for the service to be back up, or you can [[howto/SyncingWithSVN|sync with the Subversion repository]].
-- Ticket URL: <https://trac.macports.org/ticket/49596#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
#49596: selfupdate: rsync: failed to connect to rsync.macports.org: Operation timed out (60) --------------------------------+--------------------- Reporter: vinay0410sharma@… | Owner: admin@… Type: defect | Status: new Priority: High | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | --------------------------------+--------------------- Changes (by ryandesign@…): * cc: satindersingh71@… (added) Comment: Replying to [comment:5 satindersingh71@…]:
Does anyone know when it will be back up?
I only just assigned the ticket to the administrator 8 minutes ago. I don't know how often he checks his messages or how long it will take him to figure out what the problem is and how to solve it. -- Ticket URL: <https://trac.macports.org/ticket/49596#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X
#49596: selfupdate: rsync: failed to connect to rsync.macports.org: Operation timed out (60) --------------------------------+--------------------- Reporter: vinay0410sharma@… | Owner: admin@… Type: defect | Status: new Priority: High | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | --------------------------------+--------------------- Comment (by ryandesign@…): Has duplicate #49616. -- Ticket URL: <https://trac.macports.org/ticket/49596#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X
#49596: selfupdate: rsync: failed to connect to rsync.macports.org: Operation timed out (60) --------------------------------+--------------------- Reporter: vinay0410sharma@… | Owner: admin@… Type: defect | Status: closed Priority: High | Milestone: Component: server/hosting | Version: Resolution: fixed | Keywords: Port: | --------------------------------+--------------------- Changes (by ryandesign@…): * status: new => closed * resolution: => fixed Comment: This got fixed sometime yesterday (?) or the day before. Thanks. -- Ticket URL: <https://trac.macports.org/ticket/49596#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts