Opened 11 years ago
Closed 11 years ago
#39447 closed defect (invalid)
port selfupdate is faild. @2.1.3 Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed
Reported by: | jam.with.ju2@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.1.3 |
Keywords: | Cc: | ||
Port: |
Description
sh-3.2# port -d selfupdate DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs ---> Updating MacPorts base sources using rsync rsync: getaddrinfo: rsync.macports.org 873: nodename nor servname provided, or not known 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/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs 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
Change History (8)
comment:1 follow-up: 2 Changed 11 years ago by larryv (Lawrence Velázquez)
Component: | ports → base |
---|---|
Priority: | High → Normal |
comment:2 follow-up: 3 Changed 11 years ago by jam.with.ju2@…
Replying to larryv@…:
Please do not set the Priority field.
Did change priority field. I'm sorry.
Try
sudo port -d selfupdate
instead.
i'll attach command log.
sh-3.2# port -d selfupdate DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs ---> Updating MacPorts base sources using rsync rsync: getaddrinfo: rsync.macports.org 873: nodename nor servname provided, or not known 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/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs 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
comment:3 follow-up: 5 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to jam.with.ju2@…:
i'll attach command log.
sh-3.2# port -d selfupdate
You’re still not using sudo
. Are you in a root shell?
---> Updating MacPorts base sources using rsync rsync: getaddrinfo: rsync.macports.org 873: nodename nor servname provided, or not known rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-42/rsync/clientserver.c(105) [receiver=2.6.9]
Is your machine on a network that blocks rsync connections?
comment:4 follow-up: 6 Changed 11 years ago by jmroot (Joshua Root)
It's failing in getaddrinfo which is what does the DNS lookup, so it isn't even getting to a point where the rsync port being blocked would matter.
comment:5 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to larryv@…:
Replying to jam.with.ju2@…:
i'll attach command log.
sh-3.2# port -d selfupdateYou’re still not using
sudo
. Are you in a root shell?
That's what the #
in the prompt usually signifies.
comment:6 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to jmr@…:
It's failing in getaddrinfo which is what does the DNS lookup, so it isn't even getting to a point where the rsync port being blocked would matter.
What could the issue be, then? OP can resolve trac.macports.org
just fine, but not rsync.macports.org
. Temporary DNS problem?
comment:7 Changed 11 years ago by jam.with.ju2@…
Sorry for the late reply.
I did shutdown and reboot. 'port' is not have problem.
but, I don't know. I can't understand problem.
maybe, I'll did change mac setting. (launchctl etc..) That was too bad.
port is running. it is looks like problem nothing.
comment:8 Changed 11 years ago by larryv (Lawrence Velázquez)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Please do not set the Priority field.
Try
sudo port -d selfupdate
instead.