Project

General

Profile

DM - Expert Documentation » History » Version 2

Version 1 (Michael Kirby, 06/23/2015 04:14 PM) → Version 2/72 (Michael Kirby, 06/23/2015 04:23 PM)

h1. DM - Expert Documentation

h2. Starting the PUBS daemon running

<pre>
>kinit
>ssh -Y ubdaq-prod-ws01.fnal.gov
</pre>
Once you are logged into ubdaq-prod-ws01, you can now access the online cluster. There are two machines where we run PUBS daemons, ubdaq-prod-evb and ubdaq-prod-near1. To start the daemon, you will want to log in as user uboonepro.
<pre>
ws01>ssh -Y uboonepro@ubdaq-prod-evb.fnal.gov
</pre>
Once there, you will need to setup the PUBS environment. The production version of PUBS is installed in /home/uboonepro/pubs/ and is the only version that should be run for production operations.
<pre>
evb> cd pubs
evb> source config/setup_uboonepro_online.sh
evb> conn_test
</pre>
This last commands makes sure that the account can connect to the procdb database with the correct authorization. Everything should connect and disconnect successfully. Once once you've done that, you need to make sure that the daemon is running on ubdaq-prod-evb and ubdaq-prod-near1. You can check the status of the daemon using these commands.
<pre>
evb> list_log
</pre>
And check each of the servers for the last time that they were updated. Note that if there are no projects enable on a server, the log won't update even if the daemon is running. And if you update the configuration of a project, you must restart the daemon.

In order to
start and stop the daemon on each of the machines, evb, near1, and smc using the following commands as uboonepro.
<pre>
evb>cd pubs
evb>source config/setup_uboonepro_online.sh
evb>daemon.sh
>bin/daemon.sh stop
evb>daemon.sh >bin/daemon.sh start
</pre>
Then check again with list_log to make sure that the projects are updating.

Questions? "Ask Kirby":mailto:kirby@fnal.gov