Experimental Physics and
Industrial Control System

Mark Rivers <[email protected]> · Tue, 9 Aug 2016 00:45:38 +0000

Hi Nino,

For your first error you should set ASYN_TRACEIO_DRIVER in the underlying drvAsynIPPort driver that talks to camserver just before you change the exposure time.  Then you will see the full communication with camserver, and will be able to tell what command is generating the error "Not applicable to single module detectors".  What detector model is this, and what version of camserver?

The second error is coming from these lines in the autosave module, in save_restore.c line 1664
/* open() doesn't seem to set file permissions anymore */
status = fchmod (filedes, (mode_t) file_permissions);
if (status) printf("write_it: fchmod returned %d\n", status);

I don't think either of these problems is likely to be related to the crash you are seeing.  You need to enable core dump file creation and then run gdb on the resulting core file to track down the crashes.

Mark

From: [email protected] [[email protected]] on behalf of Miceli, Antonino [[email protected]]
Sent: Monday, August 08, 2016 5:22 PM
To: EPICS tech talk
Cc: Woods, Russell; Quaranta, Orlando
Subject: Pilatus AD 2-4 errors

Hi all,

We are hunting down some intermittent IOC crashes.  We are getting the following errors in a Pilatus AD 2-4 ioc which  may or not be related to the intermitted ioc crashing.

1.)    Any time we change the exposure time, period, etc we get an error like this:

2016/08/08 17:00:03.577 pilatusDetector:readCamserver unexpected response from camserver, no OK, response=15 ERR Not applicable to single module detectors

2.)    Every once in a while get this error:

write_it: fchmod returned -1

The detector seems to run to acquire images ok, except for these intermittent crashes (every 80k images or so).

Thanks,
Nino

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System