Experimental Physics and Industrial Control System
|
Hi Lewis -
I had a similar problem on an RTEMS IOC when the NTP was not properly configured. After reboot, the times between the RTEMS clock and the NFS host would slowly drift apart ... and then save-restore would stop working and require a reboot.
Just for grins, do a 'date' on the IOC and host to see if the times have substantially drifted apart.
HTH -
Ned
From: "J. Lewis Muir" <[email protected]> To: "EPICS Tech Talk" <[email protected]> Sent: Wednesday, May 29, 2013 5:10:57 PM Subject: autosave failure S_rpcLib_RPC_CANTSEND
I have a problem where, after a number of days of uptime, I start getting the following errors on my IOC console:
=== console === save_restore:write_it: fprintf returned -1. [130528-120034] ../save_restore.c(1402): [0x2f0003]=write_it:S_rpcLib_RPC_CANTSEND save_restore:write_it: fclose('auto_settings.sav') returned -1 ../save_restore.c(1518): [0x2f0003]=write_it:S_rpcLib_RPC_CANTSEND save_restore:write_it: Giving up on this attempt to write 'auto_settings.sav'. [130528-120035] ===============
Does anyone know what's wrong and how to fix this? Or what would be a good way to investigate and fix this?
The error looks like it's coming from the autosave module. I'm guessing maybe the RPC error suggests something wrong with communicating with the NFS server where the auto_settings.sav file is being written, but I don't know. The NFS server log doesn't show any problem. Once the problem starts, it doesn't seem to go away until I reboot the IOC.
This problem has not always existed; it used to work fine. I initially thought it was a problem with autosave 5-0, since it seemed the problem showed up for the first time after I had upgraded to 5-0. But then I rolled back to 4-8, and the problem is still appearing. It's possible the NFS server changed somehow, or maybe a network adapter, cable, switch, etc. is failing, or none of these.
The IOC is running EPICS Base 3.14.12.2 and autosave 4-8. The NFS server is running RHEL 5.9.
I have another VME IOC running the same version of EPICS Base and autosave and using the same NFS server, and it does not have this problem. This makes me lean in the direction of suspecting something is wrong with the IOC or its network connectivity to the NFS server.
The VME IOC that does not have a problem has an auto_settings.sav file that is 9120 lines long (244110 bytes), while the VME IOC that does have the problem has an auto_settings.sav file that is 10448 lines long (270096 bytes). Maybe this is irrelevant.
More IOC environment details: * VME processor module: Motorola MVME-5100 (vxWorks-ppc604_long) - CPU: MPC 750 - Memory: 512 MB * OS: VxWorks 5.5.2 * Kernel: WIND 2.6 * VxWorks image: mv5100-asd6 (from APS) * Build toolchain: Tornado 2.2.2 * EPICS 3.14.12.2 (+ Known Problems patches) * synApps 5.6 (includes autosave 4-8; + various module upgrades)
Thanks,
Lewis
- Replies:
- Re: autosave failure S_rpcLib_RPC_CANTSEND J. Lewis Muir
- References:
- autosave failure S_rpcLib_RPC_CANTSEND J. Lewis Muir
- Navigate by Date:
- Prev:
Re: autosave failure S_rpcLib_RPC_CANTSEND Andrew Johnson
- Next:
Re: Gauge controller with R232 serial port Vahe Sahakyan
- 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 Hartman, Steven M.
- 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
|
ANJ, 20 Apr 2015 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|