New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #34298 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

rsync and distfiles server is down

Reported by: ahelfer1971@… Owned by: admin@…
Priority: High Milestone:
Component: server/hosting Version: 2.0.4
Keywords: Cc: md14-macports@…, macports@…, ryandesign@…, nurvzy@…, susheel.varma@…, nonstop.server@…, lukasz.olek@…, charlie.clark@…, mitch@…, marco.comini@…, poirierg@…, tj.trevelyan@…, captainproton1971@…, mas@…, f.baart@…, d.s.hunnisett@…, yangseungdo@…, defa@…, whcordis@…, info@…, ajb78@…, Joe.Rohde@…, ram@…, josephwinston@…, bertrand.zuchuat@…
Port:

Description (last modified by ryandesign@…) (diff)

trying to use self update. neither it nor sync work.

DEBUG: Copying /Users/ahelfer1971/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences
DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
--->  Updating MacPorts base sources using rsync
@ERROR: chdir failed
rsync error: error starting client-server protocol (code 5) at /SourceCache/rsync/rsync-42/rsync/main.c(1398) [receiver=2.6.9]
shell command "/usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs" returned error 5
DEBUG: Error synchronizing MacPorts sources: shell command failed (see log for details)
    while executing
"macports::selfupdate [array get global_options] base_updated"
Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: shell command failed (see log for details)

I also just upgraded Xcode to 4.3.2. any ideas? What more info do you need?

Change History

comment:1 Changed 2 years ago by ryandesign@…

  • Description modified (diff)

Hmm, well it says "chdir failed"... does the location /opt/local/var/macports/sources/rsync.macports.org/release/tarballs exist?

comment:2 Changed 2 years ago by obartunov@…

I have the same problem and ,yes, the directory exists.

comment:3 Changed 2 years ago by macports@…

I am seeing the same thing on 10.7.3 running MacPorts 2.0.4 after a selfupdate.

comment:4 Changed 2 years ago by md14-macports@…

  • Cc md14-macports@… added

Cc Me!

comment:5 Changed 2 years ago by support@…

I too am getting the same error:

  • Xcode: 4.3.2
  • OS X: 10.7.3
$ port version
Warning: port definitions are more than two weeks old, consider using selfupdate
Version: 2.0.4
$ sudo port -d selfupdate
Password:
DEBUG: Copying /Users/sikoram/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences
DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
--->  Updating MacPorts base sources using rsync
@ERROR: chdir failed
rsync error: error starting client-server protocol (code 5) at /SourceCache/rsync/rsync-42/rsync/main.c(1398) [receiver=2.6.9]
shell command "/usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs" returned error 5
DEBUG: Error synchronizing MacPorts sources: shell command failed (see log for details)
    while executing
"macports::selfupdate [array get global_options] base_updated"
Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: shell command failed (see log for details)

comment:6 Changed 2 years ago by macports@…

  • Cc macports@… added

Cc Me!

comment:7 Changed 2 years ago by tachoknight@…

I am also suddenly experiencing this problem as well, even on a machine that worked several hours ago; I did a selfupdate around 6pm CST and now on the same machine it fails with the same error.

comment:8 Changed 2 years ago by vivien.badaut@…

I am also getting the same error, but I have Snow Leopard (10.6.8) - Xcode: 3.2.6

$ port version
Version: 2.0.4

$ sudo port -d selfupdate
Password:
DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/base
--->  Updating MacPorts base sources using rsync
@ERROR: chdir failed
rsync error: error starting client-server protocol (code 5) at /SourceCache/rsync/rsync-40/rsync/main.c(1398) [receiver=2.6.9]
shell command "/usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/base/ /opt/local/var/macports/sources/rsync.macports.org/release/base" returned error 5
DEBUG: Error synchronizing MacPorts sources: shell command failed (see log for details)
    while executing
"macports::selfupdate [array get global_options] base_updated"
Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: shell command failed (see log for details)

$ pwd
/opt/local/var/macports/sources/rsync.macports.org/release/base

comment:9 Changed 2 years ago by dotswing@…

Getting the same error. may bechdir has not been installed.

Xcode: 4.3.2 OS X: 10.7.3 I installed the Xcode and the command line tool yesterday.

comment:10 Changed 2 years ago by jon.olsson@…

It seems that the problem lies with rsync server, just running the rsync command yields the exact error message:

$ /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
@ERROR: chdir failed
rsync error: error starting client-server protocol (code 5) at /SourceCache/rsync/rsync-42/rsync/main.c(1398) [receiver=2.6.9]

comment:11 in reply to: ↑ description Changed 2 years ago by lupincho25@…

Same here; it was working yesterday just fine. Seems like a problem with the rsync server indeed.

comment:12 Changed 2 years ago by ryandesign@…

  • Priority changed from Normal to High
  • Owner changed from macports-tickets@… to admin@…
  • Component changed from base to server/hosting
  • Cc ryandesign@… added

The distfiles server is down too (same server), and our usual administrator is unavailable this week. We've notified the temporary administrator. Please just wait for it to be fixed. Thanks.

comment:13 Changed 2 years ago by yfilali@…

Thanks Ryan, any idea how long this will be down? I am up a creek without a paddle (or svn client in my case).

comment:14 Changed 2 years ago by ryandesign@…

  • Cc yfilali@… added

It will be down until a server administrator appears, diagnoses and fixes the problem. Our usual sysadmin is not here this week. I do not know what hours our emergency backup sysadmin is keeping this week, but at the moment it's 11:20 PM in California so we may have to wait until morning. He's been emailed about the problem and I'm sure he'll resolve it as soon as he's able.

In the mean time, there are methods other than rsync to sync your ports tree, for example svn (which all the MacPorts developers use), and the svn server is still up. Instructions for setting that up are here: wiki:howto/SyncingWithSVN.

comment:15 Changed 2 years ago by jmr@…

There are several rsync Mirrors available too.

comment:16 Changed 2 years ago by ryandesign@…

But if the main rsync server is down, the mirrors won't be any more up to date than when the main rsync server went down (and probably several hours more out of date than that). The svn server is completely up to date, on the other hand.

comment:17 Changed 2 years ago by yfilali@…

Thanks, much appreciated.

comment:18 Changed 2 years ago by nurvzy@…

Cc Me! Ignore this ticket I just created: #34300

comment:19 Changed 2 years ago by nurvzy@…

  • Cc nurvzy@… added

Cc Me!

comment:20 Changed 2 years ago by susheel.varma@…

  • Cc susheel.varma@… added

Cc Me!

comment:21 Changed 2 years ago by nonstop.server@…

  • Cc nonstop.server@… added

Cc Me!

comment:22 Changed 2 years ago by lukasz.olek@…

  • Cc lukasz.olek@… added

Cc Me!

comment:23 Changed 2 years ago by charlie.clark@…

  • Cc charlie.clark@… added

Cc Me!

comment:24 Changed 2 years ago by mitch@…

  • Cc mitch@… added

Cc Me!

comment:25 follow-up: ↓ 27 Changed 2 years ago by marco.comini@…

  • Cc marco.comini@… added

Cc Me!

comment:26 Changed 2 years ago by RulerOf@…

Hey guys... Of all the nights for me to decide to install MacPorts on TWO machines! Go figure :D

I was able to work around the issue by syncing over SVN, detailed on the wiki here: wiki:howto/SyncingWithSVN

This worked with the SYNC command, but NOT with the SELFUPDATE command. It was, however, enough to let me install git-core. And I hope it'll let me install wine-devel when I get that far :)

comment:27 in reply to: ↑ 25 Changed 2 years ago by michelbuck@…

Cc Me!

comment:28 Changed 2 years ago by poirierg@…

  • Cc poirierg@… added

Cc Me!

comment:29 Changed 2 years ago by tj.trevelyan@…

  • Cc tj.trevelyan@… added

Cc Me!

comment:30 Changed 2 years ago by captainproton1971@…

  • Cc captainproton1971@… added

Cc Me!

comment:31 Changed 2 years ago by mas@…

  • Cc mas@… added

Cc Me!

comment:32 Changed 2 years ago by f.baart@…

  • Cc f.baart@… added

Cc Me!

comment:33 Changed 2 years ago by raimue@…

  • Summary changed from macports selfupdate fails on Mac os lion to rsync and distfiles server is down

comment:34 Changed 2 years ago by d.s.hunnisett@…

  • Cc d.s.hunnisett@… added

Cc Me!

comment:35 Changed 2 years ago by yangseungdo@…

  • Cc yangseungdo@… added

Cc Me!

comment:36 Changed 2 years ago by defa@…

  • Cc defa@… added

Cc Me!

comment:37 Changed 2 years ago by whcordis@…

  • Cc whcordis@… added

Cc Me!

comment:38 Changed 2 years ago by info@…

  • Cc info@… added

Cc Me!

comment:39 Changed 2 years ago by ajb78@…

  • Cc ajb78@… added

Cc Me!

comment:40 Changed 2 years ago by martin.zeman@…

Cc Me!

comment:41 Changed 2 years ago by Joe.Rohde@…

  • Cc Joe.Rohde@… added

Cc Me!

comment:42 Changed 2 years ago by yfilali@…

  • Cc yfilali@… removed

Cc Me!

comment:43 Changed 2 years ago by ram@…

  • Cc ram@… added

Cc Me!

comment:44 Changed 2 years ago by josephwinston@…

  • Cc josephwinston@… added

Cc Me!

comment:45 Changed 2 years ago by bertrand.zuchuat@…

  • Cc bertrand.zuchuat@… added

Cc Me!

comment:46 Changed 2 years ago by ryandesign@…

Has duplicate #34306.

comment:47 Changed 2 years ago by ryandesign@…

  • Status changed from new to closed
  • Resolution set to fixed

The rsync and distfiles servers are back online. Thanks, Henry!

Note: See TracTickets for help on using tickets.