[PRad] [Revised Logentry] run 1139 to 1141 , junk run, CODA crashed can not recover

[Dipangkar Dutta]

Hi Serguei,
I will let Chao reply to this question since he has been keeping track of
all the changes in configuration.

But there was also the issue of the deadtime being higher when the zero
suppression is included (somehow the busy changed from the usual ~200 usec
to ~350 usec). Chao had disabled zero suppression yesterday.


Cheers
Dipangkar


On Tue, Jun 7, 2016 at 11:13 AM, Serguei Boiarinov <boiarino at jlab.org>
wrote:

> Anyway, 'PRAD' has different configuration for secondary ET, do you want
> it to be the same as in 'prad' ?
>
> ----- Original Message -----
> From: ly150 at msstate.edu
> To: "Mahbub Khandaker" <mahbub at jlab.org>
> Cc: "Serguei Boiarinov" <boiarino at jlab.org>, prad at jlab.org, "Li Ye" <
> liye at jlab.org>
> Sent: Tuesday, June 7, 2016 12:10:23 PM
> Subject: Re: [PRad] [Revised Logentry] run 1139 to 1141 , junk run, CODA
> crashed can not recover
>
> it was PRAD last night
>
> Li Ye
> Mississippi State University
> 662-617-5195
>
> > 在 2016年6月7日，下午12:04，Mahbub Khandaker <mahbub at jlab.org> 写道：
> >
> > CODA configuration was still 'prad' during production run last night.
> >
> >> On Tue, 7 Jun 2016, Serguei Boiarinov wrote:
> >>
> >> What CODA configuration did you use last night ?
> >> Is it still 'prad', or something else ?
> >>
> >> ----- Original Message -----
> >> From: "Mahbub Khandaker" <mahbub at jlab.org>
> >> To: "Serguei Boiarinov" <boiarino at jlab.org>
> >> Cc: "Li Ye" <liye at jlab.org>, prad at jlab.org
> >> Sent: Tuesday, June 7, 2016 10:59:21 AM
> >> Subject: Re: [PRad] [Revised Logentry] run 1139 to 1141 , junk run,
> CODA crashed can not recover
> >>
> >> Yes, Serguei.  We are down now for work in the hall until 3:30 pm.
> >>
> >> Thanks,
> >> Mahbub
> >>
> >>> On Tue, 7 Jun 2016, Serguei Boiarinov wrote:
> >>>
> >>> Can I take a DAQ to debug it ?
> >>>
> >>> ----- Original Message -----
> >>> From: "Li Ye" <liye at jlab.org>
> >>> To: "Serguei Boiarinov" <boiarino at jlab.org>, prad at jlab.org
> >>> Sent: Tuesday, June 7, 2016 4:10:02 AM
> >>> Subject: [Revised Logentry] run 1139 to 1141 ,junk run, CODA crashed
> can not recover
> >>>
> >>> Logentry Text:
> >>> --
> >>> from 3:00am to 4:00am, we had 15mins beam trip , then CODA crashed,
> >>> we tried to reset, re-download , re-configured ,re-start CODA ,
> nothing worked.
> >>> we had harp scan at 3:45am
> >>> error message on ER1 as follow:
> >>> UDP_standard_request >sta:ER1 downloading<
> >>> UDP_standard_request >sta:ER1 downloading<
> >>> UDP_standard_request >sta:ER1 downloading<
> >>> UDP_standard_request >sta:ER1 downloading<
> >>> UDP_standard_request >sta:ER1 downloading<
> >>> UDP_standard_request >sta:ER1 downloading<
> >>> codaUpdateStatus: updating request done
> >>> dbGetInt: ERROR: unknown nrow
> >>> cannot get SPLITMB, set erp->split=2146435072 Bytes
> >>> dbGetInt: ERROR: unknown nrow
> >>> cannot get RECL, set erp->record_length=32768evio format will be used
> >>> got erp->filename >/data/prad/prad<
> >>> INFO: Downloading configuration 'PRAD'
> >>> ++++++======>{CODA}  <
> >>> nrols [0] >CODA<
> >>> INFO: Using inbuilt (CODA) format
> >>> er_et_initialize: start ET stuff
> >>> et_findserver2 1
> >>> et_findserver: send broadcast packet to 129.57.167.255 on port 11111
> >>> et_findserver: send broadcast packet to 10.0.255.255 on port 11111
> >>> et_findserver2 9
> >>> et_findserver: reply to broadcast
> >>> et_findserver: RESPONSE from 129.57.167.227 at 11111 with cast addr =
> 129.57.167.255 and uname = clondaq4.jlab.org
> >>> et_findserver: comparing 129.57.167.60 to incoming 129.57.167.227
> >>> et_findserver: comparing 10.0.0.3 to incoming 129.57.167.227
> >>> et_findserver: comparing 10.0.0.4 to incoming 129.57.167.227
> >>> et_findserver: comparing 10.0.0.5 to incoming 129.57.167.227
> >>> et_findserver: comparing 10.0.0.6 to incoming 129.57.167.227
> >>> et_findserver: no valid response received
> >>> wait: coda request >download PRAD< in progress
> >>> wait: coda request >download PRAD< in progress
> >>> et ERROR: et_wait_for_system, done waiting but ET system not alive
> >>> et ERROR: etl_open: ET system is not active
> >>> ERROR: er ET init: cannot open ET system
> >>> ERROR: er download: cannot initalize ET system
> >>>
> >>>
> >>>
> >>> ---
> >>>
> >>> This is a plain text email for clients that cannot display HTML.  The
> full logentry can be found online at
> https://logbooks.jlab.org/entry/3408889
> >>> _______________________________________________
> >>> PRad mailing list
> >>> PRad at jlab.org
> >>> https://mailman.jlab.org/mailman/listinfo/prad
> > _______________________________________________
> > PRad mailing list
> > PRad at jlab.org
> > https://mailman.jlab.org/mailman/listinfo/prad
>
> _______________________________________________
> PRad mailing list
> PRad at jlab.org
> https://mailman.jlab.org/mailman/listinfo/prad
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/prad/attachments/20160607/4dd99719/attachment-0001.html>