>> > > Could we please queue up the following patch as a stable fix for >> > > commit a974deee47? It needs to be applied to v4.10 and older. >> > >> > Now applied, thanks. >> >> Until kernel 4.11.9 is into Fedora's updates, I downgraded our server >> acting as the NIS master to 4.10.16-200. But all NIS users time out >> with "ypserv: #011-> Error #-3. Could this be a different issue with >> rpcbind or nfs-utils? Here are some debug enabled logs for RPC with a >> different error "xs_error_report client ffff8d8223caa000, error=113" >> > > Error 113 is EHOSTUNREACH. It means that either your server is down, or > there is some other networking issue that is preventing the client from > connecting to it (e.g. a firewall setting, route configuration, arp > cache pollution?). Either way, it is unrelated to this particular > patch. Ahh indeed it was firewalld. Not sure why this just cropped up, perhaps some update? Anyways once I ran: firewall-cmd --permanent --add-service=nfs firewall-cmd --permanent --add-service=mountd firewall-cmd --permanent --add-service=rpc-bind firewall-cmd --reload We were back in business with NFS sharing. Thanks so much for the reply & hint as I couldn't find what error 113 meant. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
