EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  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  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: autosave failure S_rpcLib_RPC_CANTSEND
From: "J. Lewis Muir" <[email protected]>
To: Andrew Johnson <[email protected]>
Cc: [email protected]
Date: Fri, 8 Nov 2013 17:46:10 -0600
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 Mark Rivers
Re: autosave failure S_rpcLib_RPC_CANTSEND Ron Sluiter
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

Navigate by Date:
Prev: RE: BEAUTY Archiver and data from Area detector Malitsky, Nikolay D
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  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: autosave failure S_rpcLib_RPC_CANTSEND Ron Sluiter
Next: RE: autosave failure S_rpcLib_RPC_CANTSEND Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 20 Apr 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·