Date: Mon, 30 May 2016 10:54:21 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Mark Johnston <markj@FreeBSD.org> Cc: "Ngie Cooper (yaneurabeya)" <yaneurabeya@gmail.com>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: r 300949: rpcbind rejects to start: couldn't create ip6 socket Message-ID: <20160530105421.75a44be4@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <20160529195035.GA89115@raichu> References: <20160529093230.68a5da55.ohartman@zedat.fu-berlin.de> <AF252790-6857-4BE5-AD10-7B380543264D@gmail.com> <20160529133907.4566f2bf.ohartman@zedat.fu-berlin.de> <20160529195035.GA89115@raichu>
index | next in thread | previous in thread | raw e-mail
On Sun, 29 May 2016 12:50:35 -0700 Mark Johnston <markj@FreeBSD.org> wrote: > On Sun, May 29, 2016 at 01:39:07PM +0200, O. Hartmann wrote: > > Recompiled sources with flag -DNO_CLEAN (I mention this because it might > > have impact). > > > > After that, I tried restarting rpcbind via: > > > > root@localhost: [src] service rpcbind restart > > rpcbind not running? > > Starting rpcbind. > > rpcbind debugging enabled. > > can't get local ip6 address: hostname nor servname provided, or not known > > couldn't create ip6 socketSegmentation fault (core dumped) > > /etc/rc.d/rpcbind: WARNING: failed to start rpcbind > > > > > > Now the "segmentation fault" is new. I regret not having the core or any > > more infos on that, I disabled all core dumping options and debugging > > facilities on that host of mine ... > > The segfault should be addressed by r300972 - could you give that > revision a try? [...] I did, and on several systems, the upgrade from r300830 to r300985 went without problems, but the systems I discovered the problem are to be updated this evening. But so far, it seems to be fixed. Thank you very much.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160530105421.75a44be4>