Differences

This shows you the differences between two versions of the page.

--- kvalobs:kvoss:system:qc2:user:run [2010-08-12 19:45:24]
paule created
+++ kvalobs:kvoss:system:qc2:user:run [2022-05-31 09:29:32] (current)
@@ Line 1: / Line 1: @@
-====== Qc2-OPE-RUN ======((NB Change in paths /var/kvalobs -> /var/lib/kvalobs and /var/kvalobs/log -> /var/log/kvalobs now included below, see https://svn.met.no/viewvc/kvoss/kvalobs/trunk/src/kvQabased/InitLogger.cc?view=log ))
+====== Running Qc2 ======
+The QC2 daemon, kvqc2, may be turned on and off with **kvstart** and **kvstop**. All that is required is to add kvqc2 to the kv_ctl.conf file. If this is already achieved, just ignore the configuration section below.
+====== Configuration ======
+Update kv_ctl.conf
-Ok! Kvalobs Qc1 and Qc2 is built in the test environment. Qc2 is now integrated with the Qc1 environment by editing kv_ctl.conf
+Standard location: /etc/kvalobs/kv_ctl.conf edit and include kvQc2, e.g.:
-**STEP 1:** Update kv_ctl.conf
-on dev-vm116 the relevant file is located:
-/metno/kvalobs/etc/kvalobs/kv_ctl.conf and shall be edited to include kvQc2:
 <code>
-#START_PROGS="kvQabased kvManagerd kvDataInputd kvServiced kvAgregated"
 START_PROGS="kvQabased kvManagerd kvDataInputd kvServiced kvQc2"
-#STOP_PROGS="kvQabased kvManagerd kvDataInputd kvServiced kvAgregated"
 STOP_PROGS="kvServiced kvDataInputd kvQabased kvManagerd kvQc2"
+ ...
-TIMEOUT=70
+TIMEOUT=60
 KVUSER=kvalobs
 </code>
-Note the local kvalobs.conf (/metno/kvalobs/etc/kvalobs/kvalobs.conf)
+====== Start ======
-contains:
 <code>
-corba{
+$ kvstart
-  #Where is CORBA nameserver
-  #nameserver="corbans.oslo.dnmi.no"
-  nameserver="corbans.met.no"
-  #Which path in CORBA nameserver shall we use for
-  #this instance of kvalobs
-  path="kv_dev-vm116"
-}
 </code>
-Illustrating a dedicated registration in the CORBA nameserver for the virtual machine kvalobs instance.
+The following result (or similar, depending on the list of daemons installed) is expected:
-**STEP 2:** Remember that we are currently working with a local installation. The html log files for kvQabased are written to:
-/metno/kvalobs/var/log/kvalobs/html
-The script called by the default cron job does not know this and needs to be modified by editing /usr/lib/kvalobs/bin/qabase_cron.sh and making it point to the correct log/html directory.
-<code>
-#! /bin/sh
-QABASELOGDIR=/metno/kvalobs/var/log/kvalobs/html
-##QABASELOGDIR=$(kvconfig --localstatedir)/kvalobs/log/html
-#find $QABASELOGDIR -name '*.html' -type f -mtime +0 -exec rm -f {} \;
-find $QABASELOGDIR -xdev -name '*.html' -type f -mmin +360 -exec rm -f {} \;
-#find $QABASELOGDIR -name '*.html' -type f  -exec rm -f {} \;
-find $QABASELOGDIR -xdev -type d -cmin +120 -exec rmdir --ignore-fail-on-non-empty {} \;
-# create nice map of existing log-files (output: html)
-####find $QABASELOGDIR -name '*.html' -type f | /metno/kvalobs/bin/log_map > $QABASELOGDIR/log_map.html
-</code>
-Then run the corresponding standard cron jobs as described:
-https://dokit.met.no/sysdok/kvalobs/installasjon#cron-jobber
-Clean-up of the html log files is necessary to manage disk space.
-**STEP 3** Now run kvalobs as user kvalobs with kvQc2:
-<del>kvQc2 requires one additional environment variable to be set:</del>
-<del><code></del>
-<del>$ export KVALOBS=/metno/kvalobs</del>
-<del></code></del>
-**NOTE:** The $KVALOBS historic configuration variable is no longer needed.
-<code>
-$ cd $HOME
-$ bin/kvstart
-</code>
-The following result is expected:
 <code>
 KVBIN=/metno/kvalobs/bin
 KVPID=/metno/kvalobs/var/kvalobs/run
-TIMEOUT=70
+TIMEOUT=60
@@ Line 101: / Line 44: @@
 </code>
+====== Stop ======
-**STEP 4** ... and to stop:
+Stop the running kvqc2 process by 'kvstop -l' (lower case L), then type the number corresponding to kvqc2:
-<code>
+For example:
-$ cd
-$ bin/kvstop
-</code>
-The following result is expected:
 <code>
-listopt: 0
+kvalobs@dev-vm101:~$ kvstop -l
+listopt: 1
 killallopt: 0
-KVPID=/metno/kvalobs/var/kvalobs/run
+KVPID=/var/run/kvalobs
-TIMEOUT=70
+TIMEOUT=60
-node: dev-vm116
+node: dev-vm101
-  Stopper kvalobs dette kan ta noe tid!
+Velg et program å stoppe!
-  Hvis det ikke skjer noe på MER enn 70 sekund
+-------------------------
-  bruk CTRL-C for å avbryte!
+: norcom2kv
+: kvqc2
+: kvServiced
-kvServiced .....Stopped!
+: kvDataInputd
-kvDataInputd .....Stopped!
+: kvQabased
-kvQabased .....Stopped!
+: kvManagerd
-kvManagerd .....Stopped!
+: kvAgregated
-kvQc2 .....Stopped!
+: kvbufrd
+: kvsynopd
+  q: quit
+-------------------------
+Stop programmet [1-9]: 2
+kvqc2 .....Stopped!
 </code>
-**NB** The timeout has been set to 70s since kvQc2 checks for new configuration files every minute and the rest of the time either sleeps or processes a given set of instructions.
+Once kvqc2 is running the algorithms carried out are controlled by the configuration files in the Qc2Config directory.
+The Qc2Config directory needs to be created by the kvalobs user if it does not exist. Standard location is "/etc/kvalobs/Qc2Config".