-
Notifications
You must be signed in to change notification settings - Fork 1
Bluesky crash: psutil.NoSuchProcess when sending filename to Rigaku #231
Comments
Youch! Process no longer exists?
We have set something to |
Is this different from #230? |
I do not think so, for the Rigaku detector is in 'Ready' state this time and it does not show the 'Hang' state as in #230 |
We have a sleep time of 10 ms while waiting for Rigaku |
The failure was in Python as the new file name was to be sent to the detector. The failure happened because the |
Excerpt from Last lines from logger
|
@prjemian If you look at the logger file, it seems that the file name for 2639 did get sent, and it even started the DM workflow, however for some reason the ipython terminal crashed at the 'sending file name' part. Any suggestions? |
Technically, the logger may report it but python failed to find the process to send the unix command to the detector. Probably logged just before sending the command. |
@prjemian Bluesky crashed again, this time at only 192 measurements: Screen output
|
Last few lines of the logger file: /2020-2/ipython_logger.log
|
From my untrained eye this crash looks exactly the same as the previous one ( @prjemian Please let me know when this problem is fixed so that I can start the Bluesky testing again. |
psutil.NoSuchProcess
when sending filename to Rigaku
psutil.NoSuchProcess
when sending filename to Rigaku
@prjemian C026 crashed at measurement 10165 at 10/02, 10:01 am (ran for ~ 13 hours). Same error: Error from Ipython terminal
Last lines from Logger
LabView interface looks normal too: |
@prjemian C027 crashed at measurement 00085 at 1:10 pm on 10/02 Error message from terminal
Logger
|
@prjemian C031 crashed at measurement 00047 at 3:26 pm on 10/02 Error message from terminal
Logger
|
Ok, failed at a different point. Since this is diagnostic code, perhaps we can avoid this. |
@prjemian C032 crashed at measurement 00709 at 4:27 pm on 10/02 Error message from terminal
Logger
|
py |
@prjemian C034 crashed at measurement 08539 at 4:21 am on 10/03 Error from terminal
|
Ok, that's a different failure (read timeout after 2.0 seconds). Ironic that the read failed while recording metadata (the storage ring fill number) that is not essential to the measurement or analysis, only useful for diagnostics later. On the brighter side, that we ran this far with no error from |
Error message from terminal
The text was updated successfully, but these errors were encountered: