No stack on failed connectivity service lookup

DUNE-DAQ / drunc

Dune RUN Control (DRUNC) is the run control for the DUNE experiment

1 stars 1 forks source link

No stack on failed connectivity service lookup #272

Closed plasorak closed 1 month ago

plasorak commented 1 month ago

This PR aims to make it simpler to debug what is going on when the unified shell cannot find the root controller on the connectivity service by printing a couple of hints. Fixes https://github.com/DUNE-DAQ/drunc/issues/267

jcfreeman2 commented 1 month ago

Inside a container, I've confirmed that now if you set up via dbt-setup-release, try to run drunc and daq_rte_.sh isn't available, instead of plowing ahead you'll get a nice clear error message from drunc:


DruncSetupException: Couldn't understand where to find the rte script tentative: 
/cvmfs/dunedaq-development.opensciencegrid.org/nightly/NFD_DEV_241017_A9/daq_app_rte.sh
Exiting...
Checking for remaining gunicorn and drunc-controller processes
ERROR

plasorak commented 1 month ago

Ah... I was hoping it would actually find the RTE with this changes, after using dbt-setup-release?

jcfreeman2 commented 1 month ago

Apologies, wasn't yet finished with my review. Also just confirmed that using a local installation of drunc from this feature branch and pointing dbt-setup-release to it (and not the drunc in the nightly) that things run normally, i.e., I'm getting PASSED from the listrev integration test.