Experimental Physics and Industrial Control System
Hi Lewis,
Which version of Andrew's BSP are you using? The asd6-debug versions fixed a similar problem when vxWorks repeatedly tried to open a socket. This happened with asyn autoConnect ports when the device was offline. Eventually it would lead to mbuf depletion and errors like the ones you are seeing would happen.
Mark
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of J. Lewis Muir
Sent: Friday, November 08, 2013 5:46 PM
To: Andrew Johnson
Cc: [email protected]
Subject: Re: autosave failure S_rpcLib_RPC_CANTSEND
On 9/3/13 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.
Hi, Andrew.
Well, not so fast I guess. It just happened again on Saturday, this
time using NFSv2 (using the image you sent me). The error messages on
the console look the same:
=== console ===
save_restore:write_it: fprintf returned -1. [131101-194540]
../save_restore.c(1636): [0x2f0003]=write_it:S_rpcLib_RPC_CANTSEND
save_restore:write_it: fclose('auto_settings.sav') returned -1
../save_restore.c(1751): [0x2f0003]=write_it:S_rpcLib_RPC_CANTSEND
save_restore:write_it: Giving up on this attempt to write 'auto_settings.sav'. [131101-194540]
===============
This is driving me nuts. Without a fix for this, I'm going to have to
start rebooting this IOC once a week to try to keep it from happening.
I'd strongly prefer not to have to do this. Any ideas on how to
investigate, fix, or work around?
The software running on the IOC has changed a bit since I first reported
this problem; it is now running 3.14.12.3 (+ Known Problems patches) and
synApps 5_6 with autosave 5-1 (+ many other module updates).
Thanks,
Lewis
- Replies:
- Re: autosave failure S_rpcLib_RPC_CANTSEND J. Lewis Muir
- References:
- autosave failure S_rpcLib_RPC_CANTSEND J. Lewis Muir
- Re: autosave failure S_rpcLib_RPC_CANTSEND Andrew Johnson
- Re: autosave failure S_rpcLib_RPC_CANTSEND J. Lewis Muir
- Re: autosave failure S_rpcLib_RPC_CANTSEND J. Lewis Muir
- Re: autosave failure S_rpcLib_RPC_CANTSEND J. Lewis Muir
- Re: autosave failure S_rpcLib_RPC_CANTSEND J. Lewis Muir
- Navigate by Date:
- Prev:
Re: Error while opening OPI Kasemir, Kay
- Next:
Re: autosave failure S_rpcLib_RPC_CANTSEND Hartman, Steven M.
- 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
- Navigate by Thread:
- Prev:
Re: autosave failure S_rpcLib_RPC_CANTSEND J. Lewis Muir
- Next:
Re: autosave failure S_rpcLib_RPC_CANTSEND J. Lewis Muir
- 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