40m
QIL
Cryo_Lab
CTN
SUS_Lab
TCS_Lab
OMC_Lab
CRIME_Lab
FEA
ENG_Labs
OptContFac
Mariner
WBEEShop
|
40m Log |
Not logged in |
 |
|
Tue Apr 17 11:05:04 2012, Jamie, Update, CDS, CDS upgrade in progress
|
Tue Apr 17 19:03:09 2012, Jamie, Update, CDS, CDS upgrade in progress
|
Wed Apr 18 19:59:48 2012, Jamie, Update, CDS, CDS upgrade success
|
Fri Apr 20 19:54:57 2012, Jamie, Update, CDS, CDS upgrade problems
|
Sat Apr 21 17:38:19 2012, Jamie, Update, CDS, dtt, dataviewer working; problem with trend frames
|
Sat Apr 21 21:10:34 2012, Jamie, Update, CDS, trend frame issue partially resolved
|
Tue Apr 24 14:35:37 2012, Jamie, Update, CDS, limited second trend lookback
|
Sat Apr 21 20:40:28 2012, Jamie, Update, CDS, framebuilder frame writing working again
|
Tue Apr 24 14:55:00 2012, Jamie, Update, CDS, cds code paths (rtscore, userapps) have moved
|
|
Message ID: 6555
Entry time: Sat Apr 21 20:40:28 2012
In reply to: 6552
|
Author: |
Jamie |
Type: |
Update |
Category: |
CDS |
Subject: |
framebuilder frame writing working again |
|
|
Quote: |
A big one is that the framebuilder daqd started going haywire when I told it to start writing frames. After restart the logs started showing this:
[Fri Apr 20 17:23:40 2012] main profiler warning: 0 empty blocks in the buffer
[Fri Apr 20 17:23:41 2012] main profiler warning: 0 empty blocks in the buffer
[Fri Apr 20 17:23:42 2012] main profiler warning: 0 empty blocks in the buffer
[Fri Apr 20 17:23:43 2012] main profiler warning: 0 empty blocks in the buffer
[Fri Apr 20 17:23:44 2012] main profiler warning: 0 empty blocks in the buffer
[Fri Apr 20 17:23:45 2012] main profiler warning: 0 empty blocks in the buffer
GPS time jumped from 1019002442 to 1019003041
FATAL: exception not rethrown
FATAL: exception not rethrown
FATAL: exception not rethrown
and the network seemed like it started to get really slow. I wasn't able to figure out what was going on, so I shut the frame writing off again. I'll have to work with Rolf on that next week.
|
So the framebuilder/daqd frame writing issue seems to have been a transient one. Alex said he tried enabling frame writing manually and it worked fine, so I tried re-enabling the frame writing config lines and sure enough it worked fine. So it's a mystery. Alex said the "main profiler warning" lines tend to show up when data is backed up in the buffer, although he didn't explain why exactly that would have been the issue here.
daqdrc frame writing directives:
start frame-saver;
sync frame-saver;
start trender;
start trend-frame-saver;
sync trend-frame-saver;
start minute-trend-frame-saver;
sync minute-trend-frame-saver;
start raw_minute_trend_saver;
|