Skip to Content.
Sympa Menu

sphenix-maps-l - Re: [Sphenix-maps-l] rcdaq setup meeting?

sphenix-maps-l AT lists.bnl.gov

Subject: sPHENIX MAPS tracker discussion

List archive

Chronological Thread  
  • From: Martin Purschke <purschke AT bnl.gov>
  • To: sphenix-maps-l AT lists.bnl.gov
  • Subject: Re: [Sphenix-maps-l] rcdaq setup meeting?
  • Date: Tue, 6 Jun 2023 07:49:23 -0400

All,

sorry I didn't feel up to wrapping up what we discussed yesterday late night, I just did.

I shut down and disabled the firewalls, and (this is still the rc_server that we started yesterday in the session) -

[phnxrc@mvtx-flx0 ~]$ rc_status
mvtx-flx0.sphenix.bnl.gov -1 0 0 1 0
mvtx-flx1.sphenix.bnl.gov -1 0 0 1 0
mvtx-flx2.sphenix.bnl.gov -1 0 0 1 0
mvtx-flx3.sphenix.bnl.gov -1 0 0 1 0
mvtx-flx4.sphenix.bnl.gov -1 0 0 1 0
mvtx-flx5.sphenix.bnl.gov -1 0 0 1 0
[phnxrc@mvtx-flx0 ~]$ rc_close
[phnxrc@mvtx-flx0 ~]$ rc_status
mvtx-flx0.sphenix.bnl.gov -1 0 0 0 0
mvtx-flx1.sphenix.bnl.gov -1 0 0 0 0
mvtx-flx2.sphenix.bnl.gov -1 0 0 0 0
mvtx-flx3.sphenix.bnl.gov -1 0 0 0 0
mvtx-flx4.sphenix.bnl.gov -1 0 0 0 0
mvtx-flx5.sphenix.bnl.gov -1 0 0 0 0

I installed the service.

These are now the systemd-started rcdaqs:

[phnxrc@mvtx-flx0 ~]$ rc_status
mvtx-flx0.sphenix.bnl.gov -1 0 0 0 0
mvtx-flx1.sphenix.bnl.gov -1 0 0 0 0
mvtx-flx2.sphenix.bnl.gov -1 0 0 0 0
mvtx-flx3.sphenix.bnl.gov -1 0 0 0 0
mvtx-flx4.sphenix.bnl.gov -1 0 0 0 0
mvtx-flx5.sphenix.bnl.gov -1 0 0 0 0

I also added sphenix.bnl.gov to the search domains.

BTW, for future reference (but *PLEEEASE* - see the note in the elog about rogue changes that took us down last night by someone (not in this audience) getting creative), here's the ansible file - /home/common/ansible/general/addRcdaqService.yml and test00 is the ansible "control center".

When I get around to it, we'll change the service to dump the log files into a dedicated directory rather than the home dir, which is getting cluttered. We currently keep 5 log files with logrotate so you'll have $HOME/rcdaq_mvtx-flxX.log, .1, .2. .3...

Also, mid-term - I understand the current expert-only nature of configuring the FELIXes. But think longer-term, like in 2 weeks - do you want to be called at night each time something happens, say, rack 3.3 trips off? Think about a sure-fire script that the DO can start to configure basically any detector into a running configuration from scratch.

Best,
Martin

On 6/5/23 14:10, Martin Purschke via sPHENIX-MAPS-l wrote:

All,

should we hop in the DAQ Meeting zoom?

https://bnl.zoomgov.com/j/1605543713?pwd=Z2QvUDFWMDFuOExPMHh3bnMrYlZIQT09

I'm hanging out there...


Martin



--
Martin L. Purschke, Ph.D. ; purschke AT bnl.gov
; http://www.phenix.bnl.gov/~purschke
;
Brookhaven National Laboratory ; phone: +1-631-344-5244
Physics Department Bldg 510 C ; fax: +1-631-344-3253
Upton, NY 11973-5000 ; skype: mpurschke
-----------------------------------------------------------------------




Archive powered by MHonArc 2.6.24.

Top of Page