Hi Andrew,
Ø
Were there any changes to your file-server? I'm hoping that's not the system that Mrinal was upgrading to CentOS-8 last week.
The file server has not changed, it is Centos 7.
Ø
1058 bytes is less than a single UDP packet; can you try writing some other largeish file from VxWorks, just to make sure that isn't related. There is a "copy"
command which might work for that, you give it an existing filename and a new one.
I just copied a file of about 16 kB using the vxWorks shell.
ioc13ida> copy "motors.template","junk.txt"
value = 0 = 0x0
It worked fine, the output file junk.txt is the same as the input file.
corvette:CARS/iocBoot/ioc13ida>ls -l motors.template junk.txt
-rwxrwxrwx 1 epics domain users 16959 Jan 1 2020 junk.txt
-rwxrwxr-x 1 epics domain users 16959 Jan 1 2020 motors.template
I am adding some debugging to save_restore:write_it to figure out which fprintf failed and perhaps why.
Mark
From: Johnson, Andrew N. <anj at anl.gov>
Sent: Wednesday, May 18, 2022 4:59 PM
To: Mark Rivers <rivers at cars.uchicago.edu>; mooney at aps.anl.gov
Cc: tech-talk at aps.anl.gov
Subject: Re: autosave problem
Hi Mark,
Were there any changes to your file-server? I'm hoping that's not the system that Mrinal was upgrading to CentOS-8 last week. 1058 bytes is less than a single UDP packet; can you try writing some other largeish file from VxWorks, just to make sure that isn't
related. There is a "copy" command which might work for that, you give it an existing filename and a new one.
- Andrew
On 5/18/22 4:52 PM, Mark Rivers wrote:
Folks,
I just upgraded my VME IOCs to base 7.0.6.1 and the master branch of autosave (some changes since 5-10-2). I am getting these errors at the vxWorks prompt:
ioc13ida> save_restore:write_it: fprintf returned 0 [220518-163829].
save_restore:write_it: Giving up on this attempt to write 'auto_settings.sav'. [220518-163829]
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
save_restore:write_save_file: Can't write save file. [220518-163829]
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Recent files in the autosave/ directory are:
-rw-rw-rw- 1 epics domain users 2749 May 18 16:37 auto_positions.sav_220518-163750
-rw-rw-rw- 1 epics domain users 1058 May 18 16:37 auto_settings.sav_RBAD_220518-163750
-rw-rw-rw- 1 epics domain users 1058 May 18 16:37 auto_settings.sav_220518-163751
-rw-rw-rw- 1 epics domain users 1058 May 18 16:37 auto_settings.sav_RBAD_220518-163751
-rw-rw-r-- 1 epics domain users 2749 May 18 16:37 auto_positions.sav
-rw-rw-rw- 1 epics domain users 2749 May 18 16:37 auto_positions.savB
-rw-rw-r-- 1 epics domain users 1058 May 18 16:41 auto_settings.sav
Note that it is writing files. However, the auto_settings.sav file is only 1058 bytes long, while it should be about 160 kB. It seems like save_restore:write_it
is writing some information to the file and then it gets an error.
This is the contents of the auto_settings.sav file:
corvette:iocBoot/ioc13ida/autosave>more auto_settings.sav
# autosave R5.3 Automatically generated - DO NOT MODIFY - 220518-164400
13IDA:ip2:SAUTOS 0
13IDA:ip2:DIS 0
13IDA:ip2:SSIZE 400
13IDA:ip2:ULCK 1
13IDA:ip2:SIZE.SCAN 6
13IDA:ip2:STAT.SCAN 6
13IDA:ip8:SAUTOS 0
13IDA:ip8:DIS 0
13IDA:ip8:SSIZE 400
13IDA:ip8:ULCK 0
13IDA:ip8:SIZE.SCAN 4
13IDA:ip8:STAT.SCAN 6
13IDA:ip9:SAUTOS 0
13IDA:ip9:DIS 0
13IDA:ip9:SSIZE 400
13IDA:ip9:ULCK 0
13IDA:ip9:SIZE.SCAN 4
13IDA:ip9:STAT.SCAN 6
13IDA:tsp1:TSP_FIL 0
13IDA:tsp1:TSP_AUTO_ADV 0
13IDA:tsp1:TSP_VALUE 50
13IDA:tsp1:TSP_UNITS 0
13IDA:tsp1:TSP_SECONDS 50
13IDA:tsp1:TSP_MINUTES 240
13IDA:tsp1:TSP_NCYCLES 900
13IDA:tsp1:TSP_MIN_PRESS 1e-10
13IDA:tsp1:TSP_STAT.SCAN 9
13IDA:DMM1dmm_chan.VAL 1
13IDA:DMM1ch_mode_sel.VAL 6
13IDA:DMM1init_string.VAL *rst;form:elem read
13IDA:DMM1onesh_cont.VAL 1
13IDA:DMM1single_multi.VAL 1
13IDA:DMM1scanner.SCAN 6
13IDA:DMM1Dmm_raw.DESC Dmm raw desc
13IDA:DMM1Dmm_calc.DESC Dmm Units
13IDA:DMM1Dmm_calc.PREC 4
13IDA:DMM1Dmm_calc.SCAN 0
13IDA:DMM1Dmm_calc.CALC A
13IDA:DMM1Dmm_calc.INPA 13IDA:DMM1Dmm_raw.VAL NPP NMS
13IDA:DMM1Dmm_calc.INPB
The disk that autosave it writing to has plenty of room. What could be causing this error.
It is happening on all 8 of my VME IOCs, it is not just with one of them.
Thanks,
Mark
--
Complexity is free, it's Simplicity that takes work.