[dsg-hallb_rich] [EXTERNAL] Re: RICH S4 CRIO heartbeat stopped
Marco Mirazita
Marco.Mirazita at lnf.infn.it
Thu Jul 10 10:06:50 EDT 2025
Hello,
I agree with Valery, no reason to stop the data taking, but in case
please be ready.
Thank you,
Marco
Il 2025-07-10 16:04 Valery Kubarovsky via dsg-hallb_rich ha scritto:
> I understand this, and I have no intention of interrupting data
> taking. Nevertheless, if there is significant downtime, I would prefer
> to take the opportunity to fix the cRio. Please be prepared.
>
> -------------------------
>
> From: Brian Eng <beng at jlab.org>
> Sent: Thursday, July 10, 2025 09:37
> To: Valery Kubarovsky <vpk at jlab.org>; Christopher Dilks
> <dilks at jlab.org>; Tyler Lemon <tlemon at jlab.org>
> Cc: Valery Kubarovsky via dsg-hallb_rich <dsg-hallb_rich at jlab.org>
> Subject: Re: RICH S4 CRIO heartbeat stopped
>
> It can probably wait until the next planned maintenance window on
> 7/17; at the very least I don't think this is something the beam
> should be stopped for as troubleshooting can take longer than expected
> if it isn't something obvious/simple.
>
> Since we know there's still flow to S1, S4 should also be okay.
>
> -------------------------
>
> From: Valery Kubarovsky <vpk at jlab.org>
> Sent: Thursday, July 10, 2025 9:25 AM
> To: Brian Eng <beng at jlab.org>; Christopher Dilks <dilks at jlab.org>;
> Tyler Lemon <tlemon at jlab.org>
> Cc: Valery Kubarovsky via dsg-hallb_rich <dsg-hallb_rich at jlab.org>
> Subject: Re: RICH S4 CRIO heartbeat stopped
>
> Hi Brian,
> Thanks for the update. I will let you know when the access will be
> available.
> Regards,
> Valery
>
> -------------------------
>
> From: Brian Eng <beng at jlab.org>
> Sent: Thursday, July 10, 2025 09:22
> To: Christopher Dilks <dilks at jlab.org>; Tyler Lemon <tlemon at jlab.org>;
> Valery Kubarovsky <vpk at jlab.org>
> Cc: Valery Kubarovsky via dsg-hallb_rich <dsg-hallb_rich at jlab.org>
> Subject: Re: RICH S4 CRIO heartbeat stopped
>
> It looks like the sbRIO that was replaced 3 weeks ago is offline, or
> at least isn't responding to pings.
>
> There's nothing that can be done remotely so it would require an
> access to further troubleshoot.
>
> -------------------------
>
> From: dsg-hallb_rich <dsg-hallb_rich-bounces at jlab.org> on behalf of
> Valery Kubarovsky via dsg-hallb_rich <dsg-hallb_rich at jlab.org>
> Sent: Thursday, July 10, 2025 9:05 AM
> To: Christopher Dilks <dilks at jlab.org>; Tyler Lemon <tlemon at jlab.org>
> Cc: Valery Kubarovsky via dsg-hallb_rich <dsg-hallb_rich at jlab.org>
> Subject: Re: [dsg-hallb_rich] RICH S4 CRIO heartbeat stopped
>
> Hi Tyler,
> Please take a look to the RICH cRIO sector 4.
> Thank you,
> Valery
>
> -------------------------
>
> From: Christopher Dilks <dilks at jlab.org>
> Sent: Thursday, July 10, 2025 02:15
> To: Tyler Lemon <tlemon at jlab.org>
> Cc: Valery Kubarovsky <vpk at jlab.org>
> Subject: RICH S4 CRIO heartbeat stopped
>
> Hi Tyler,
>
> The heartbeat stopped around 1am:
> https://logbooks.jlab.org/entry/4415043
>
> All Sector 4 N2 volume PVs are frozen. The frozen values look normal.
>
> Can you take a look when you get this message? Meanwhile the shift
> crew is calling engineering on-call (following the alarm guidance).
>
> Thanks,
> Chris
>
>> Christopher Dilks
>>
>> Jefferson Lab Staff Scientist
>>
>> Office: B122
>>
>> Phone: 757-269-7750
>>
>> Email: dilks at jlab.org
> _______________________________________________
> dsg-hallb_rich mailing list
> dsg-hallb_rich at jlab.org
> https://mailman.jlab.org/mailman/listinfo/dsg-hallb_rich
More information about the dsg-hallb_rich
mailing list