LDAS Control Pages



LDAS API Control

This page submits request to bootstrap, shutdown, remove an existent API or add an API to LDAS system.

  1. Select an API from the list.
  2. Fill in the change log with your name and reason for the change.
  3. Hit SUBMIT to forward request to server.
Response:

The response will be displayed in status window or an alert will popup if there is an error in executing the request.

LDAS System Control

This page submits request to shutdown or restart the LDAS system at a site. You must first shutdown an existing LDAS system before restarting a new one. To start a new LDAS system,
  1. Select an LDAS site. If you need to add a new site, under File, select Update Sites, select other from list of sites and enter the relevant site information.
  2. Enter the key word.
  3. Pick a default database among the choices
  4. Hit SUBMIT to forward request to server.

Currently with openssh on ldas systems, a ldas dedicated ssh agent is needed to be running prior to startup of LDAS to support batch mode ssh into various machines to start up the APIs on those machines. To check for an existing agent, on an ldas gateway machine e.g. ldas-dev.ligo.caltech.edu, run the program /ldas/bin/ldasagent; if an agent exist, it reports the existence of a ssh temp file: e.g. /tmp/ssh-vWcN7555/agent.7555. If not it gives instructions on how to start an agent.

If there is an ssh agent or an agent has been started, set up the environment variable as by running:


/ldas/bin/ssh-agent-mgr --agent-file=/ldas_outgoing/managerAPI/.ldas-agent  --shell=tclsh check
# md5 1024 7b:93:91:fb:ed:9d:6f:08:c4:59:ed:b3:84:05:b5:2f /usr1/ldas/.ssh/id_rsa(RSA)
set ::env(SSH_AGENT_PID) 26008
set ::env(SSH_AUTH_SOCK) /tmp/ssh-qSJ26007/agent.26007
Now use cmonClient to restart LDAS.

Response:

If you request to restart a new LDAS system, eventually you will be connected to the cntlmonAPI server when it comes up; cntlmonAPI is the last API to come up; verify from the status display that all APIs have come up.

To shutdown a running LDAS system, select the LDAS site, connect to it, select Stop LDAS and hit button.

Response:

A popup notifies you when cntlmonAPI is shutdown and you will be disconnected. Verify from the status display that all APIs are down except the maanger. LDAS has been shutdown successfully. The managerAPI is the last to shutdown.

LDAS Resources

LDAS Resources are configurable global variables that can be edited to fit the specific site needs.

cmonClient resources are automatically displayed for editing; changes are in effect for the client session when the APPLY CHANGES button is hit and saved permanently to cmonClient.rsc file if APPLY & SAVE CHANGES button is hit. The resource file can be re-read back into the current client session by hitting RESCAN RESOURCES button.

For LDAS API resources, select an API and hit GET RESOURCE button to first retrieve the current values from the selected API; once the values are displayed, they can be edited and set via the APPLY CHANGES button, and saved permanently to a local rsc file in /ldas_outgoing if APPLY & SAVE CHANGES button is hit. Global resources, if saved, will affect all of LDAS when the system is rebooted.

Hitting the Undo button next to each variable restores the displayed value to the original value in the API.

Response:

The current list of resource variables and their values are displayed. If the values have been modified and the APPLY buttons have been hit, the display returned contains the new set of values.

LDAS Utilities

This page allows restart of helper utilities; they consist of:

LDAS User Administration

This page supports

Block DSO

This page blocks a named DSO for being used in dataPipeline commands.

LDAS Core Files

This page displays the list of core files in the core archive. You can filter core files based on API. If all is selected, all core files names are returned, including those that may not belong to an API.

To debug a core file, click on "core file", e.g. /ldas_outgoing/savedCores/metadata.701971239.core and select gdb or ddd.

To delete a core file from archive, click on "core file" e.g. /ldas_outgoing/savedCores/metadata.701971239.core and select delete to mark it for deletion. Hit Delete Cores to remove the file on LDAS. There are buttons to select/deselect all core files.