Re: r 300949: rpcbind rejects to start: couldn't create ip6 socket
Am Sun, 29 May 2016 03:00:56 -0700 "Ngie Cooper (yaneurabeya)" schrieb: > > On May 29, 2016, at 00:32, O. Hartmann wrote: > > > > After updating sources and build- and installworld, I realize that all > > rpcbind related > > services, so far NFS, are not working. On a client I check the start of > > rpcbind by > > setting option -d and receive the output shown below. > > > > Well, prior to r300949 rpcbind started without complains - as it did with > > r300901. > > > > [...] > > 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 socket/etc/rc.d/rpcbind: WARNING: failed to start > > rpcbind > > Hi, > Could you please try this patch with -d (it’ll continue on instead of > exiting… > I’m curious as to why it was failing before). Does IPv6 work in your > environment? > Thanks! > -Ngie Well, funny is: staring rpcbind with options "-h 192.168.xxx.xxx -l -s -W" does not make the rpcbind trying to create an IPv6 socket - which it fails due to absence of IPv6 in kernel, but only "-h 192.168.xxx.xxx" does! I can reproduce this weird behaviour on several CURRENT systems on which IPv6 is disabled by default. pgpqnSAzDajGw.pgp Description: OpenPGP digital signature
Re: r 300949: rpcbind rejects to start: couldn't create ip6 socket
On Sun, 29 May 2016 12:50:35 -0700 Mark Johnston 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. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r 300949: rpcbind rejects to start: couldn't create ip6 socket
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? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r 300949: rpcbind rejects to start: couldn't create ip6 socket
Am Sun, 29 May 2016 03:00:56 -0700 "Ngie Cooper (yaneurabeya)" schrieb: > > On May 29, 2016, at 00:32, O. Hartmann wrote: > > > > After updating sources and build- and installworld, I realize that all > > rpcbind related > > services, so far NFS, are not working. On a client I check the start of > > rpcbind by > > setting option -d and receive the output shown below. > > > > Well, prior to r300949 rpcbind started without complains - as it did with > > r300901. > > > > [...] > > 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 socket/etc/rc.d/rpcbind: WARNING: failed to start > > rpcbind > > Hi, > Could you please try this patch with -d (it’ll continue on instead of > exiting… > I’m curious as to why it was failing before). Does IPv6 work in your > environment? > Thanks! > -Ngie 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 ... Oliver pgpwB0YflJv8U.pgp Description: OpenPGP digital signature
Re: r 300949: rpcbind rejects to start: couldn't create ip6 socket
Am Sun, 29 May 2016 03:00:56 -0700 "Ngie Cooper (yaneurabeya)" schrieb: > > On May 29, 2016, at 00:32, O. Hartmann wrote: > > > > After updating sources and build- and installworld, I realize that all > > rpcbind related > > services, so far NFS, are not working. On a client I check the start of > > rpcbind by > > setting option -d and receive the output shown below. > > > > Well, prior to r300949 rpcbind started without complains - as it did with > > r300901. > > > > [...] > > 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 socket/etc/rc.d/rpcbind: WARNING: failed to start > > rpcbind > > Hi, > Could you please try this patch with -d (it’ll continue on instead of > exiting… > I’m curious as to why it was failing before). Does IPv6 work in your > environment? > Thanks! > -Ngie Give me a second, will try ... I disabled IPv6 in kernel and we do not use IPv6 yet, so I'm wondering why rpcbind now insists relying on IPv6 ... pgp1PoMkFeXmV.pgp Description: OpenPGP digital signature
Re: r 300949: rpcbind rejects to start: couldn't create ip6 socket
> On May 29, 2016, at 00:32, O. Hartmann wrote: > > After updating sources and build- and installworld, I realize that all > rpcbind related > services, so far NFS, are not working. On a client I check the start of > rpcbind by > setting option -d and receive the output shown below. > > Well, prior to r300949 rpcbind started without complains - as it did with > r300901. > > [...] > 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 socket/etc/rc.d/rpcbind: WARNING: failed to start rpcbind Hi, Could you please try this patch with -d (it’ll continue on instead of exiting… I’m curious as to why it was failing before). Does IPv6 work in your environment? Thanks! -Ngie ohartmann-rpcbind-util-break.patch Description: Binary data signature.asc Description: Message signed with OpenPGP using GPGMail
