project8 / psyllid

Data acquisition package for the ROACH2 system
Other
0 stars 1 forks source link

psyllid sometimes not repsonsive after switching files #69

Open cclaessens opened 6 years ago

cclaessens commented 6 years ago

We have observed that during triggering data taking psyllid sometimes stops taking data and ends up in a non-responsive state.

So far all we know about it is that this seems to happen at the transition from one file to another. Both times this occurs the last file written was full (1GB) and the next file was still empty.

hornet logs for run 5980

1c 02:13:17.729 INFO [Mover] ▶ File copy took 990.38178ms to transfer 1007602328 bytes 51d 02:13:17.850 INFO [finishFile] ▶ Completed work on file 51e 02:13:46.791 NOTI [summaryLoop] ▶ Scheduler summary: In the past 1m0s,

and from run 6062

7330 20:59:06.766 INFO [Mover] ▶ File copy took 980.864339ms to transfer 1007605664 bytes 7331 20:59:06.882 INFO [finishFile] ▶ Completed work on file 7332 20:59:48.548 NOTI [summaryLoop] ▶ Scheduler summary: In the past 1m0s,

cclaessens commented 6 years ago

Happened again on August 27th 2018. sterr reads:

ESC[1;31m2018-08-27 11:20:02 [ERROR] _receiver_fpa.cc(246): Exiting due to stream errorESC[0m /var/log/supervisor/psyllid_ch_b-stderr---supervisor-rG6nS8.log (END)