This page submits request to bootstrap, shutdown, remove an existent API or add an API to LDAS system.
The response will be displayed in status window or an alert will popup if there is an error in executing the request.
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:
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
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.
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.
When selection to compare databases is made, a dialog comes up to present the choices of
databases for a site.
Select all the databases you desire and hit OK to close the dialog.
The database names are placed in the entry.
Hit SUBMIT button to submit the request to server after providing your priviledged user name and password
at the prompt.
Response:
If there are no difference between two databases, the report shows nothing after
the names of the databases.
The following are convenience functions directed to an API by cntlmonAPI.
To get a list of registered LDAS users, hit Refresh user's List button.
After the list is displayed, hit a user's button ( papaya color) to set the entries
on the top with the selected user's information.
First select a user via the user's button to display the information in the entries; if the user is not
currently blocked, the administrator can block this user from submitting jobs to LDAS by
hitting Block user button. If the user has been blocked,
blocked, hitting the Unblock user button will enable this user to be
active again.
To get a list of registered LDAS users, hit Refresh DSO List button.
After the list is displayed, hit a DSO's button ( papaya color) to set the entries
on the top with the selected DSO name. To enter one not on the list, hit user_specified
and enter the DSO name in entry.
First select a DSO via the DSO's button to display the information in the entries; if the DSO is not
currently blocked, the administrator can block this DSO in dataPipeline jobs to LDAS by
hitting Block DSO button. If the DSO has been blocked,
blocked, hitting the Unblock DSO button will enable this DSO to be
active again.
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.
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,
/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.
LDAS Resources
LDAS Resources are configurable global variables that can be edited to
fit the specific site needs.
LDAS Utilities
This page allows restart of helper utilities; they consist of:
The first three are started by the cntlmonAPI server and output logs in cntlmonAPI
directory. Errors from utilities are also recorded to cntlmonAPI logs.
Create/Recreate LDAS database
This function creates or recreates the LDAS database. This is used to create
a brand new database or to set up a clean test database. Normally this function
is not applied to production database since data is in use or needs to be archived.
When the command is submitted to cntlmonAPI server, it returns a work in progress
status:
box-i,06-02-2003 14:31:34> Working on it ... (createLDASdb mlei_tst /usr1/databases)
When the database has been created, it returns the entire log of the process:
Here is just a section of it:
db2 response:
Database Connection Information
Database server = DB2/LINUX 7.2.0
SQL authorization ID = LDASDB
Local database alias = MLEI_TST
db2 cmd: terminate
db2 response: DB20000I The TERMINATE command completed successfully.
db2 cmd: drop database mlei_tst
db2 response: DB20000I The DROP DATABASE command completed successfully.
db2 cmd: create database mlei_tst on /usr2/databases alias mlei_tst
db2 response: DB20000I The CREATE DATABASE command completed successfully.
db2 response:
Database Connection Information
Database server = DB2/LINUX 7.2.0
SQL authorization ID = LDASDB
Local database alias = MLEI_TST
db2 cmd: update database configuration for mlei_tst using logsecond 100
db2 response: DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
DB21026I For most configuration parameters, all applications must disconnect
from this database before the changes become effective.
...
db2 cmd: terminate
db2 response: DB20000I The TERMINATE command completed successfully.
mlei_tst created on /usr2/databases
LDAS database comparison
This function allows databases to be compared for tables, column data ( fields,data types, default nulls ),
primary and foreign keys, indexes and database configuration parameters.
----> ldas_tst vs dev_beta <-----
If there are differences between two databases, the report tells what the areas
are and what is different in each.
----> cprod_1 vs ldas_tst <-----
tables,only in cprod_1: EXTERNAL_TRIGGER
tables,only in ldas_tst: DBMDCTEST
COINC_SNGL:foreign,only in ldas_tst: H1_BURST_ID H1_BURST_CDB H2_BURST_ID H2_BURST_CDB L1_BURST_ID L1_BURST_CDB
SUMM_CSD primary keys only in cprod_1, CHANNEL1 CHANNEL2 SPECTRUM_TYPE START_TIME END_TIME
SUMM_CSD:indexes,only in cprod_1: SUMMCSD_PK
SUMM_CSD:indexes,only in ldas_tst: SUMMCSD_IND_CHAN
index SUMMCSD_PK, columns +CHANNEL1+CHANNEL2+SPECTRUM_TYPE+START_TIME+END_TIME
index SUMMCSD_IND_CHAN, columns +CHANNEL1+CHANNEL2
SUMM_SPECTRUM:indexes,only in ldas_tst: SUMMSPECT_CHAN
index SUMMSPECT_CHAN, columns +CHANNEL
----> cprod_1 vs tst_beta <-----
tables,only in cprod_1: EXTERNAL_TRIGGER
COINC_SNGL:foreign,only in tst_beta: H1_BURST_ID H1_BURST_CDB H2_BURST_ID H2_BURST_CDB L1_BURST_ID L1_BURST_CDB
SUMM_CSD primary keys only in cprod_1, CHANNEL1 CHANNEL2 SPECTRUM_TYPE START_TIME END_TIME
SUMM_CSD:indexes,only in cprod_1: SUMMCSD_PK
SUMM_CSD:indexes,only in tst_beta: SUMMCSD_IND_CHAN
index SUMMCSD_PK, columns +CHANNEL1+CHANNEL2+SPECTRUM_TYPE+START_TIME+END_TIME
index SUMMCSD_IND_CHAN, columns +CHANNEL1+CHANNEL2
SUMM_SPECTRUM:indexes,only in tst_beta: SUMMSPECT_CHAN
index SUMMSPECT_CHAN, columns +CHANNEL
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.