Assist in the setup of an artdaq-database (MongoDB) instance on np04-srv-009 for RunControl testing there
Here is an excerpt from an email from Giovanna today:
There have been a few emails going in circles about preparing a test instance of the new run control on np04-srv-009 without disrupting the production version on np04-srv-010. Let me re-explain what we need exactly; how this can be achieved is free for experts to choose. We have started a different instance of the winccoa project on srv-009. We must use it parasitically for testing while the main instance remains running on np04-srv-010 for shifters. There seems to be a constraint (or is it a legend?) that the mongoldb database instance must run on the same machine as the winccoa project. Is this true? If yes: - we need a separate snapshot of the existing DB that will not affect the running instance on np04-srv-010. If no: - I suppose only DAQInterface needs to know where the DB is. Where is this set? Can we have the instance(s) of daq interface on srv-009 access the mongodb on srv-010?
#1 Updated by John Freeman over 1 year ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Running the following set of commands sent to me by Gennadiy as root on np04-srv-009:
kill -9 34994 #kills the currently running ssh-tunnel that I started from a command line for testing cp /nfs/sw/database/ssh-tunnel.service /etc/systemd/system/ systemctl enable ssh-tunnel.service systemctl start ssh-tunnel.service
...I was able to set up an ssh-tunnel which allows DAQInterface when run on np04-srv-009 to access the database on np04-srv-010; I successfully tested this using command line DAQInterface in protoDUNE run 1001509.