RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive
Hi, I have upgraded fresh installed 5.4-RELEASE to 5.4-STABLE today. With 5.4R I was able to mount nfs from another 5.4R box. But after I did cvsup and buildworld and buildkernel today, I'm no longer able to use nfs. This is what I get when I try mount: RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive This message is what I get whenever I try mounting anything with nfs no matter is it exported or not or no matter does host exists or not like this: hosting# mount 10.10.10.10:/backup /mnt [udp] 10.10.10.10:/backup: RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive ^C hosting# mount 1.1.1.1:/blabla /mnt [udp] 1.1.1.1:/blabla: RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive ^C hosting# mount 255.255.255.255:/blabla /mnt [udp] 255.255.255.255:/blabla: RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive ^C hosting# Regards, gg. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive
On Thursday 09 June 2005 12:42, Goran Gajic wrote: Hi, RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive (jmg: I cc'd you on the off chance you have not seen this already, another user identified your changes as related, but I have not tested this myself.) Yes, it seems that changes to the kernel (specifically kqueue?) broke NFS (and other things) in -STABLE. See these messages for related reports. 1 [EMAIL PROTECTED] 2 [EMAIL PROTECTED] HTH, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive
Dominic Marks wrote this message on Thu, Jun 09, 2005 at 12:56 +0100: On Thursday 09 June 2005 12:42, Goran Gajic wrote: Hi, RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive (jmg: I cc'd you on the off chance you have not seen this already, another user identified your changes as related, but I have not tested this myself.) Yes, it seems that changes to the kernel (specifically kqueue?) broke NFS (and other things) in -STABLE. See these messages for related reports. could you try backing out uipc_socket.c v1.208.2.19? If it broke because of my commits, it would of been this one, though I'm puzzeled as to why it didn't break in -current... P.S. Could you teach your mailer not to cc -stable twice? (once as freebsd.org and again as www.freebsd.org) -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive
On Thursday 09 June 2005 16:44, John-Mark Gurney wrote: Dominic Marks wrote this message on Thu, Jun 09, 2005 at 12:56 +0100: On Thursday 09 June 2005 12:42, Goran Gajic wrote: Hi, RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive (jmg: I cc'd you on the off chance you have not seen this already, another user identified your changes as related, but I have not tested this myself.) Yes, it seems that changes to the kernel (specifically kqueue?) broke NFS (and other things) in -STABLE. See these messages for related reports. could you try backing out uipc_socket.c v1.208.2.19? If it broke because of my commits, it would of been this one, though I'm puzzeled as to why it didn't break in -current... Will do. P.S. Could you teach your mailer not to cc -stable twice? (once as freebsd.org and again as www.freebsd.org) Sorry about that. -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive
On Thursday 09 June 2005 16:57, Dominic Marks wrote: On Thursday 09 June 2005 16:44, John-Mark Gurney wrote: Dominic Marks wrote this message on Thu, Jun 09, 2005 at 12:56 +0100: On Thursday 09 June 2005 12:42, Goran Gajic wrote: Hi, RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive (jmg: I cc'd you on the off chance you have not seen this already, another user identified your changes as related, but I have not tested this myself.) Yes, it seems that changes to the kernel (specifically kqueue?) broke NFS (and other things) in -STABLE. See these messages for related reports. could you try backing out uipc_socket.c v1.208.2.19? If it broke because of my commits, it would of been this one, though I'm puzzeled as to why it didn't break in -current... Will do. That fixes it. Thank you. P.S. Could you teach your mailer not to cc -stable twice? (once as freebsd.org and again as www.freebsd.org) Sorry about that. -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive
I can also confirm that mount of NFS exports works ok with uipc_socket.c v1.208.2.18 - so there are some problems with v1.208.2.19 Regards, gg. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive
On Thu, 9 Jun 2005, Goran Gajic wrote: I can also confirm that mount of NFS exports works ok with uipc_socket.c v1.208.2.18 - so there are some problems with v1.208.2.19 1.209 introduced a significant bug, so I backed it out as 1.210: revision 1.210 date: 2004/08/20 16:24:23; author: rwatson; state: Exp; lines: +1 -3 Back out uipc_socket.c:1.208, as it incorrectly assumes that all sockets are connection-oriented for the purposes of kqueue registration. Since UDP sockets aren't connection-oriented, this appeared to break a great many things, such as RPC-based applications and services (i.e., NFS). Since jmg isn't around I'm backing this out before too many more feet are shot, but intend to investigate the right solution with him once he's available. Apologies to: jmg Discussed with: imp, scottl The merges to RELENG_5 and RELENG_4 need to be backed out ASAP. I've CC'd John-Mark since he's the author of the original change, and just did the MFC. You'll want to back out the change locally until the fix has been committed. Robert N M Watson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
