1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 <2013> 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 <2013> 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: autosave failure S_rpcLib_RPC_CANTSEND |
From: | Ron Sluiter <[email protected]> |
To: | "J. Lewis Muir" <[email protected]> |
Cc: | [email protected] |
Date: | Tue, 3 Sep 2013 14:02:34 -0500 |
Hello Lewis, You stated earlier; "NFS server is a machine running RHEL 5.9."Did these S_rpcLib_RPC_CANTSEND problems 1st appear after switching to the RHEL 5.9 NFS server?
What version of NFS is your RHEL 5.9 server running? What was your NFS server before RHEL 5.9? We had problems with corrupted saveData *.mda files at 2-ID-D that were only resolved by upgrading to VxWorks 6.9. We never found the root cause. Ron On 9/3/2013 11:43 AM, J. Lewis Muir wrote:
On 5/30/13 5:32 PM, J. Lewis Muir wrote:On 5/30/13 3:06 PM, J. Lewis Muir wrote:Using nfsstat on the NFS server, I can confirm that the IOC NFS client is using NFSv3. Yes, if you'd be willing, I would love it if you could send that image! I'd like to try that to see if it helps.Hi, Andrew. Thanks for the image. After booting with the new image, I've confirmed the IOC NFS client is using NFSv2 now. And 'ls' works. Now I'll just wait and see if the RPC problem comes up again.Hi, Andrew. Just following up to let you know that I have had no problems since making this change. It would be great if the root cause could be tracked down and fixed, or if there was a way to easily configure whether to use NFSv2 or NFSv3, or I'd even be fine with always using NFSv2, but I don't know if others feel the same way. Thanks, Lewis