Re: Spawning ping for packages.macports.org failed

On Mon, Feb 29, 2016 at 9:09 AM, Daniel J. Luke wrote: > lsof might help you find the culprit - but yeah, you're going to get strange > failures if you're hitting resource limits. I couldn't see anything obvious when I looked after it failed with that error but I'll take

Re: Spawning ping for packages.macports.org failed

On Feb 28, 2016, at 11:04 PM, Adam Mercer wrote: > I have however found something else weird with this machine, when > trying to install a port I sometimes get the following: > > :debug:archivefetch failed verification with key > /opt/local/share/macports/macports-pubkey.pem

Re: Spawning ping for packages.macports.org failed

On Fri, Feb 26, 2016 at 1:52 PM, Daniel J. Luke wrote: > dig @131.215.125.1 packages.macports.org > > and > > dig @131.215.254.100 packages.macports.org > > to help rule out basic dns problems. Both those commands return what I would expect: builder-osx-1:~ ram$ dig

Re: Spawning ping for packages.macports.org failed

On Fri, Feb 26, 2016 at 02:52:33PM -0500, Daniel J. Luke wrote: > ok. > > Try: > > dig @131.215.125.1 packages.macports.org > > and > > dig @131.215.254.100 packages.macports.org > > to help rule out basic dns problems. I'd suggest: dig @131.215.125.1 any packages.macports.org Sometimes,

Re: Spawning ping for packages.macports.org failed

ok. Try: dig @131.215.125.1 packages.macports.org and dig @131.215.254.100 packages.macports.org to help rule out basic dns problems. > On Feb 26, 2016, at 2:15 PM, Adam Mercer wrote: > On Feb 26, 2016 09:42, "Daniel J. Luke" wrote: > > What does

Re: Spawning ping for packages.macports.org failed

On Feb 26, 2016 09:42, "Daniel J. Luke" wrote: > What does /etc/resolv.conf contain? # This file is automatically generated. # search ligo.caltech.edu ligo.org nameserver 131.215.125.1 nameserver 131.215.254.100 Cheers Adam ___

Re: Spawning ping for packages.macports.org failed

On Feb 26, 2016, at 8:53 AM, Brandon Allbery wrote: > On Fri, Feb 26, 2016 at 8:10 AM, Rainer Müller wrote: > In particular, do you have a /opt/local/bin/grep which fails to execute? > > I don't think this matters much since it tries the fetch anyway

Re: Spawning ping for packages.macports.org failed

On Fri, Feb 26, 2016 at 8:10 AM, Rainer Müller wrote: > In particular, do you have a /opt/local/bin/grep which fails to execute? I don't think this matters much since it tries the fetch anyway and that also fails to resolve the hostname. -- brandon s allbery kf8nh

Re: Spawning ping for packages.macports.org failed

On Fri, Feb 26, 2016 at 7:10 AM, Rainer Müller wrote: > The command would be: > > ping -noq -c3 -t3 $host | grep round-trip | cut -d / -f 5 If I run that for packages.macports.org, the first one it says that fails then I get the following: builder-osx-1:~ ram$ ping -noq

Re: Spawning ping for packages.macports.org failed

On 2016-02-25 23:29, Adam Mercer wrote: > From this machine I can ping and contact all the hosts it complains about. The command would be: ping -noq -c3 -t3 $host | grep round-trip | cut -d / -f 5 > Any ideas what's going on here? Did you have any ports installed before? Is the machine really

Re: Spawning ping for packages.macports.org failed

On Thu, Feb 25, 2016 at 7:50 PM, Ryan Schmidt wrote: > You apparently can't resolve hosts, or at least MacPorts and programs it > spawn can't. I don't know why that would be, if you can do it outside of > MacPorts. Yes it's very weird... I'm open to any suggestions on

Re: Spawning ping for packages.macports.org failed

> On Feb 25, 2016, at 4:29 PM, Adam Mercer wrote: > > Hi > > Just setting up MacPorts on a new machine and when I try to install a > port it fails with the following: > > DEBUG: Starting logging for expat > DEBUG: changing euid/egid - current euid: 0 - current egid: 0 >