1 |
prodtest |
1.2 |
dcs1x:/home/prodtest/cvs/JSOC/doc/new_dcsx_run.txt |
2 |
|
|
21Aug2013 16:58 |
3 |
|
|
|
4 |
prodtest |
1.1 |
Here's info on the new dcs0x and dcs1x that will replace the |
5 |
|
|
original datacapture machines dcs0 (aia) and dcs1 (hmi). |
6 |
|
|
|
7 |
|
|
The new datacapture will now make lev0 data as well as continue |
8 |
|
|
to ingest the qac/tlm files into the SUMS and archive to tape. |
9 |
|
|
|
10 |
prodtest |
1.2 |
As user prodtest set up the ssh-agent: |
11 |
|
|
> ssh-agent | head -2 > /var/tmp/ssh-agent.env |
12 |
|
|
> chmod 600 /var/tmp/ssh-agent.env |
13 |
|
|
> source /var/tmp/ssh-agent.env |
14 |
|
|
> ssh-add |
15 |
|
|
(The password is written on my whiteboard (old production prod... passwd)) |
16 |
|
|
NOTE: cron jobs use this /var/tmp/ssh-agent.env file |
17 |
prodtest |
1.1 |
|
18 |
|
|
================================================================== |
19 |
|
|
The postgres is started/stopped by user postgres like so: |
20 |
|
|
|
21 |
|
|
/var/lib/pgsql> pg_ctl -D /var/lib/pgsql/data_drms -l |
22 |
|
|
/tmp/postgres.drms.log start |
23 |
|
|
|
24 |
|
|
> pg_ctl -D /var/lib/pgsql/data_sums -l /tmp/postgres.sums.log start |
25 |
|
|
|
26 |
|
|
> pg_ctl -D /var/lib/pgsql/data_drms stop |
27 |
|
|
|
28 |
|
|
> pg_ctl -D /var/lib/pgsql/data_sums stop [-m fast] |
29 |
|
|
|
30 |
|
|
================================================================== |
31 |
|
|
|
32 |
|
|
The sums is run by user sumsadmin (uid 5947). |
33 |
|
|
dcs1x:/home/sumsadmin> sum_start |
34 |
|
|
|
35 |
|
|
dcs1x:/home/sumsadmin> ps -ef |g sum_svc |
36 |
|
|
5947 52650 1 0 13:22 pts/0 00:00:00 sum_svc hmidb_sums sum_svc_2013.06.10.132205.log |
37 |
|
|
|
38 |
|
|
dcs1x:/home/sumsadmin> sum_stop [-f] |
39 |
|
|
|
40 |
|
|
The data processing is run by user prodtest. |
41 |
|
|
|
42 |
|
|
dcs1x:/home/prodtest/cvs/JSOC/proj/datacapture/scripts> ./socdc |
43 |
|
|
|
44 |
|
|
Select the button for hmi which runs on dc1x. |
45 |
|
|
|
46 |
|
|
Data should be flowed into /dds/dds2soc/hmi. |
47 |
|
|
You will see these processes after data starts: |
48 |
|
|
|
49 |
|
|
> px prodtest |
50 |
|
|
root 46161 2688 0 May29 ? 00:00:00 sshd: prodtest [priv] |
51 |
|
|
prodtest 46163 46161 0 May29 ? 00:00:02 sshd: prodtest@pts/1 |
52 |
|
|
prodtest 46164 46163 0 May29 pts/1 00:00:00 -tcsh |
53 |
|
|
prodtest 52694 120151 0 13:25 pts/0 00:00:00 /home/jsoc/bin/linux_x86_64/pe |
54 |
|
|
rl -S ./socdc |
55 |
|
|
prodtest 52744 52694 8 13:26 pts/0 00:00:11 ingest_lev0_hmiaia vc VC02 ind |
56 |
|
|
ir /dds/soc2soc/hmi outdir /dds/soc2pipe/hmi pipedir /dds/pipe2soc/hmi logfile / |
57 |
|
|
usr/local/logs/soc/soc_hmi_VC02_prodtest_2013.06.10_13:25:12.log JSOC_DBNAME hmi |
58 |
|
|
db JSOC_DBHOST dcs1x |
59 |
|
|
prodtest 52745 52694 0 13:26 pts/0 00:00:00 ingest_lev0_hmiaia vc VC05 ind |
60 |
|
|
ir /dds/soc2soc/hmi outdir /dds/soc2pipe/hmi pipedir /dds/pipe2soc/hmi logfile / |
61 |
|
|
usr/local/logs/soc/soc_hmi_VC05_prodtest_2013.06.10_13:25:12.log JSOC_DBNAME hmi |
62 |
|
|
db JSOC_DBHOST dcs1x |
63 |
|
|
postgres 52749 52592 0 13:26 ? 00:00:00 postgres: prodtest hmidb 192.1 |
64 |
|
|
68.0.111(34129) idle in transaction |
65 |
|
|
postgres 52750 52592 0 13:26 ? 00:00:00 postgres: prodtest hmidb 192.1 |
66 |
|
|
68.0.111(34128) idle in transaction |
67 |
|
|
postgres 52755 52592 0 13:26 ? 00:00:00 postgres: prodtest hmidb 192.1 |
68 |
|
|
68.0.111(34132) idle |
69 |
|
|
postgres 52756 52829 0 13:26 ? 00:00:00 postgres: prodtest hmidb_sums |
70 |
|
|
192.168.0.111(33990) idle |
71 |
|
|
postgres 52757 52829 0 13:26 ? 00:00:00 postgres: prodtest hmidb_sums |
72 |
|
|
192.168.0.111(33991) idle |
73 |
|
|
postgres 52785 52592 0 13:26 ? 00:00:00 postgres: prodtest hmidb 192.1 |
74 |
|
|
68.0.111(34142) idle |
75 |
|
|
prodtest 52866 46164 0 13:29 pts/1 00:00:00 ps -ef |
76 |
|
|
prodtest 52867 46164 0 13:29 pts/1 00:00:00 grep prodtest |
77 |
|
|
root 120148 2688 0 Jun05 ? 00:00:00 sshd: prodtest [priv] |
78 |
|
|
prodtest 120150 120148 0 Jun05 ? 00:00:05 sshd: prodtest@pts/0 |
79 |
|
|
prodtest 120151 120150 0 Jun05 pts/0 00:00:00 -tcsh |
80 |
|
|
|
81 |
prodtest |
1.2 |
=========================================================================== |
82 |
|
|
The dcs1x has been tested and the tararc also and is ready to go. |
83 |
|
|
A rsync has been done to save the code on a backend machine: |
84 |
|
|
|
85 |
production |
1.3 |
NOTE: Chaged from original info below. Now does |
86 |
|
|
rsync's dcs1x:/home/prodtest/cvs/JSOC to dcs1x:/data-dcs2x/BACKUPS/dcs1x |
87 |
|
|
|
88 |
|
|
|
89 |
prodtest |
1.2 |
/usr/bin/rsync --rsh=/usr/bin/ssh --rsync-path=/usr/bin/rsync -avz |
90 |
|
|
/home/prodtest/cvs/JSOC d00:/scr21/jim/dcs1x_backup |
91 |
|
|
|
92 |
|
|
/usr/bin/rsync --rsh=/usr/bin/ssh --rsync-path=/usr/bin/rsync -avz /srv/www |
93 |
|
|
d00:/scr21/jim/dcs1x_backup |
94 |
|
|
|
95 |
|
|
|
96 |
|
|
|
97 |
|
|
on dcs1x as prodtest: |
98 |
|
|
> vncserver -geometry 1280x1024 |
99 |
|
|
use the -beer passwd |
100 |
|
|
|
101 |
|
|
j0:/home/prodtest> vncviewer |
102 |
|
|
|
103 |
prodtest |
1.1 |
|