port selfupdate: "macPorts sources: command execution failed"

Question

I am trying to selfupdate my Macports, but I am getting the following message:

Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing 
MacPorts sources: command execution failed

I checked my /opt/local/bin/macports and the directory does not exist. Instead, it is in /opt/local/var. Could that be the issue?

Running with -dt, I get the following:

[Users/user] > selfupdate
DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/base
--->  Updating MacPorts base sources using rsync
rsync: failed to connect to rsync.macports.org: Connection refused (61)
rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-42/rsync/clientserver.c(105) [receiver=2.6.9]
Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/base/ /opt/local/var/macports/sources/rsync.macports.org/release/base
Exit code: 10
DEBUG: Error synchronizing MacPorts sources: command execution failed
    while executing
"macports::selfupdate [array get global_options] base_updated"
Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed

What is error 61? Any ideas how I can fix that?

Are you behind a firewall ? [here](https://trac.macports.org/ticket/20436) is a ticket similar to your issue. — Olwaro, Jul 15 '12 at 14:44
Ah, I remember... I once ran into that, too. The trac ticket behind Olwaro's link contains [a link to the macports FAQ](https://trac.macports.org/wiki/FAQ#selfupdatefails). Was searching for ages back then... ty and +1! — nobody, Jul 15 '12 at 22:09
possible duplicate of [Macport self update failed](http://stackoverflow.com/questions/10821755/macport-self-update-failed) — outis, Feb 12 '13 at 01:40

score 119 · Answer 1 · edited Nov 19 '17 at 18:12

119

I had this same problem recently, and I forgot to run the command under root. If anyone else is having the problem, be sure to run command as so:

sudo port selfupdate

edited Nov 19 '17 at 18:12

nbro

15,395
32
113
196

answered Feb 11 '13 at 19:13

Eric K.

1,349
2
8
6

7

That is not the error in the question - he can't run self update as behind a firewall - fif just needing sudo there would be a different error – mmmmmm Feb 26 '14 at 11:56

score 46 · Accepted Answer · answered Jul 16 '12 at 05:25

46

I was behind a firewall. Tried on a different network and it worked.

answered Jul 16 '12 at 05:25

darksky

20,411
61
165
254

3

Exactly my problem. Company firewall appeared to be blocking the connection. – Apollo Jul 18 '13 at 09:43
2

In case you are not able to change a different network, try these two solutions below (try both of them together), it solves my problem perfectly: 1.[rvm-macports-wont-update-through-proxy](http://stackoverflow.com/questions/16520919/rvm-macports-wont-update-through-proxy) ; 2.[rvm-install-issue-unable-to-execute-port-autoconf](http://stackoverflow.com/questions/17086996/rvm-install-issue-unable-to-execute-port-autoconf) – Jing Li Oct 02 '13 at 10:31
I was able to open/enable/allow port 873 (rsync daemon's port) for my router's firewall to resolve the issue. – Brent Self May 20 '15 at 23:12
University's eduroam firewall was the issue in my case. – fabiomaia Apr 21 '19 at 14:43

score 21 · Answer 3 · answered Jul 12 '12 at 08:45

21

There is no /opt/local/bin/macports. The executable you need is /opt/local/bin/port. (Port files are in /opt/local/var/..., which is correct.)

Based on the command execution failed:

you might have forgotten to run as root.
port forks the following programs: rsync, tclsh, openssl, tar, chmod, chown. Are these executable and in the PATH? (Is /opt/local/bin in your PATH as well?)

If that doesn't help, run port with -dt to get all sorts of debug info. That might help with finding the problem. Append the interesting parts to your question, maybe.

answered Jul 12 '12 at 08:45

nobody

4,074
1
23
33

1

I did run as root. I have all those forked programs. I'll try to debug it as you said. – darksky Jul 12 '12 at 09:59
4

"you might have forgotten to run as root." Solved it for me! Thank you! – Matt Phillips May 22 '13 at 14:56

score 17 · Answer 4 · edited Mar 23 '16 at 19:53

17

I faced the same issue.But I used to this method in the after.

Go to: $prefix/etc/macports/sources.conf (my path is like this):

/opt/local/etc/macports/sources.conf

comment out the rsync entry, and add a new entry as follows:

#rsync://rsync.macports.org/release/tarballs/ports.tar [default]
https://distfiles.macports.org/ports.tar.gz [default]

After that you can run:

sudo port -d sync

It's also explained on MacPorts.com.

edited Mar 23 '16 at 19:53

rawr

20,481
4
44
78

answered Feb 24 '15 at 08:59

beautifulcode

364
3
6

1

I think that the problem is firewall. – Rui Martins Sep 10 '15 at 14:44

score 14 · Answer 5 · edited Nov 10 '13 at 21:18

14

Update for Mavericks: to ensure the XCode command line tools are installed, open a terminal and run xcode-select –-install, then follow the instructions in the resulting pop-up window:

accept license

Of course, this is in addition to the other tips such as making sure to run sudo port selfupdate.

edited Nov 10 '13 at 21:18

Wolfgang Fahl

15,016
11
93
186

answered Oct 23 '13 at 19:02

Miles

141
1
3

1

I get `xcode-select: error: invalid argument '–install'`, xcode-select's version is 2333. – lynxoid Oct 28 '13 at 01:19

score 11 · Answer 6 · answered Jul 07 '13 at 02:49

If anybody else is having this issue and they've recently updated XCode, the root of my problem was that Command Line Tools had been omitted from the latest build.

Opening XCode and installing Command Line Tools via the XCode preference panel fixed this error being thrown by MacPorts.

iGranDav · Answer 7 · 2014-06-10T12:21:23.013

5

If your company block the access via rsync you can use the http tarball. Explained here

Hope this helps.

EDIT: Now prefer to use homebrew

edited Jun 10 '14 at 12:21

answered Jun 10 '13 at 08:02

iGranDav

2,450
1
21
25

score 4 · Answer 8 · answered Apr 10 '15 at 10:16

I too had the same error. It is because the network connection is rejected. If you are using University/Company WiFi or public connection, firewall would be refusing the connection.

As you can see from the output of -dt "rsync: failed to connect to rsync.macports.org: Connection refused (61)"

There are workarounds available which are provided on the macports site:

1) Using svn.

2) If svn fails too, you can try using Daily tarball.

You can test the changes by running "sudo port -d sync"

Note: If the https fails, you can replace it with http. But doing so is not recommended, as you will be fetching from insecure connection.

That's the much better answer than the current! – StefMa Apr 22 '15 at 10:46 — StefMa, Apr 22 '15 at 10:46

score 2 · Answer 9 · edited Jun 30 '14 at 23:04

2

I faced the same issue. The main problem was my network. Because the NETWORK Port was blocked for;

rsync://rsync.macports.org/release/tarballs/ports.tar

Try to use use another network.

edited Jun 30 '14 at 23:04

mmohab

2,303
4
27
43

answered Jun 30 '14 at 22:27

Koza

51
2

This was the problem for me. Signed out of corp wifi, tried on another network and it worked fine – Thomas Jan 30 '16 at 01:16

score 1 · Answer 10 · edited Apr 23 '16 at 15:24

1

for someone who's problem still exists, maybe you've forgot agree the Xcode license:

# sudo xcodebuild license

remember to look through and type 'agree' in the end.

edited Apr 23 '16 at 15:24

Tunaki

132,869
46
340
423

answered Apr 23 '16 at 15:16

rain cheng

71
1
5

score 0 · Answer 11 · answered May 20 '16 at 07:51

In my case, the problem was internal to Macports! I updated rsync (the one delivered by Apple is old) with Macports and then Macports failed to use it (/opt/local/bin/rsync) but asked instead to use /usr/bin/rsync which does not exist (or has been erased to force using Macports rsync ?). I created a soft link between the two and now it works again.

port selfupdate: "macPorts sources: command execution failed"

11 Answers11

Linked