On 2014-05-29 13:20 (GMT-0700) Felix Miata composed: > On 2014-05-29 11:29 (GMT-0700) Adam Williamson composed: >> On Thu, 2014-05-29 at 12:53 -0400, Felix Miata wrote: >> On 2014-05-29 09:08 (GMT-0700) Adam Williamson composed: >>> > On Thu, 2014-05-29 at 00:48 -0400, Felix Miata wrote: >>> >> May 29 00:40:00 g5eas rpcbind[693]: cannot create socket for tcp6 >>> > I don't know what's causing it, but this to me looks like the most >>> > likely candidate for the underlying problem. >>> It shouldn't be. I know the indirect reason must be ipv6.disable=1 on >>> cmdline, but have no idea more directly why something that never needed ipv6 >>> before now stalls because it's not available, and only in Rawhide but not >>> Factory or Cauldron. > >> Can you check boots from before you started seeing the problem, and see >> if that error message is present or not? Can you identify precisely when >> the problem started happening (should be possible using journalctl's >> neat filtering/searching options)? Thanks! > > x32 host gx280 last upgraded 10 May has no delay with nfs-utils-1.3.0-1.2, > kernel 3.15rc5 > > x64 host gx62b last upgraded 26 May has delay with nfs-utils-1.3.0-1.3, > kernel 3.15rc6 > > Would any more precision be available via journalctl? > > On non-afflicted x32 host gx27b last updated 08 May, first journalctl hit on > rpcbind cannot create socket for [udp6,tcp6] dates to 02 December. > Afflicted host gx62b's first such hit is 27 Mar, which is directly followed > by rpcbind no such files /var/lib/rpcbind/[rpcbind.xdr,portmap.xdr]. Also > then were 5 successive firewalld ipv6 errors for not exist or no permissions > for filter, raw, security, mangle, nat, and again rpcbind no xdrs, the > rpc.statd failed to create RPC listeners. Most of these repeated on > subsequent boots through 26 May. The exception was failed RPC listeners, > which skipped from 21 April to 29 May. > I don't know that I have the right kind of bait or fishin pole for this kind > of fishin. :-p Well over a month later this is still very highly annoying: # systemctl status rpc-statd rpc-statd.service - NFS status monitor for NFSv2/3 locking. Loaded: loaded (/usr/lib/systemd/system/rpc-statd.service; enabled) Active: failed (Result: exit-code) since Thu 2014-07-10 16:56:32 EDT; 1min 53s ago Process: 643 ExecStart=/usr/sbin/rpc.statd --no-notify $STATDARGS (code=exited, status=1/FAILURE) # journaltcl -xn â rpc-statd.service - NFS status monitor for NFSv2/3 locking. Loaded: loaded (/usr/lib/systemd/system/rpc-statd.service; enabled) Active: failed (Result: exit-code) since Thu 2014-07-10 16:56:32 EDT; 6min ago Process: 643 ExecStart=/usr/sbin/rpc.statd --no-notify $STATDARGS (code=exited, status=1/FAILURE) Jul 10 16:55:32 gx62b systemd[1]: Starting NFS status monitor for NFSv2/3 locking.... Jul 10 16:55:32 gx62b rpc.statd[644]: Version 1.3.0 starting Jul 10 16:55:32 gx62b rpc.statd[644]: Flags: TI-RPC Jul 10 16:56:32 gx62b rpc.statd[644]: failed to create RPC listeners, exiting Jul 10 16:56:32 gx62b systemd[1]: rpc-statd.service: control process exited, code=exited status=1 Jul 10 16:56:32 gx62b systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking.. Jul 10 16:56:32 gx62b systemd[1]: Unit rpc-statd.service entered failed state. -- Logs begin at Wed 2014-03-26 23:52:34 EDT, end at Thu 2014-07-10 17:01:01 EDT. -- Jul 10 16:56:32 gx62b rpc.statd[660]: Version 1.3.0 starting Jul 10 16:56:32 gx62b rpc.statd[660]: Flags: TI-RPC Jul 10 17:01:01 gx62b systemd[1]: Starting Session 2 of user root. -- Subject: Unit session-2.scope has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-2.scope has begun starting up. Jul 10 17:01:01 gx62b systemd[1]: Started Session 2 of user root. -- Subject: Unit session-2.scope has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-2.scope has finished starting up. -- -- The start-up result is done. Jul 10 17:01:01 gx62b CROND[750]: (root) CMD (run-parts /etc/cron.hourly) Jul 10 17:01:01 gx62b run-parts[753]: (/etc/cron.hourly) starting 0anacron Jul 10 17:01:01 gx62b anacron[759]: Anacron started on 2014-07-10 Jul 10 17:01:01 gx62b run-parts[761]: (/etc/cron.hourly) finished 0anacron Jul 10 17:01:01 gx62b anacron[759]: Will run job `cron.daily' in 18 min. Jul 10 17:01:01 gx62b anacron[759]: Jobs will be executed sequentially -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
