| Back | Main view | Parent doc

Starting / Stoping IMiS/ARChive storage server

IMiS/ARChive provides scripts which comply to UNIX standards for starting, stopping and restarting system daemons (servers). These scripts are stored in /etc/init.d/ directory. Also RUNLEVEL links are made in runlevel directories for automatically starting processes. IMiS/ARChive usually runs in runlevel 3.

Following commands are understood by the scripts:

START: /etc/init.d/iarcd start
STOP: /etc/init.d/iarcd stop
RESTART: /etc/init.d/iarcd restart
STATUS: /etc/init.d/iarcd status


Starting IMiS/ARChive

Administrator can start IMiS/ARChive server by issuing command /etc/inid.d/iarcd start.


[root@imisarc /]# /etc/init.d/iarcd start
Starting IMiS/ARC database driver:                         [  OK  ]
Starting IMiS/ARC storage server:                          [  OK  ]
[root@imisarc /]#


Both IMiS/ARChive tasks should return OK. In this case, IMiS/ARChive has started. If you list the processes, you might see a similar output.


[root@imisarc iarc]# ps aux -H
USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
root         7  0.0  0.0     0    0 ?        SW   Feb05   0:02 [kupdated]
root         6  0.0  0.0     0    0 ?        SW   Feb05   0:00 [bdflush]
root         5  0.0  0.0     0    0 ?        SW   Feb05   0:00 [kreclaimd]
root         4  0.0  0.0     0    0 ?        SW   Feb05   1:25 [kswapd]
root         3  0.0  0.0     0    0 ?        SWN  Feb05   0:00 [ksoftirqd_CPU0]
root         1  0.0  0.0  1412   72 ?        S    Feb05   0:03 init [3]
root         2  0.0  0.0     0    0 ?        SW   Feb05   0:00   [keventd]
root         8  0.0  0.0     0    0 ?        SW<  Feb05   0:00   [mdrecoveryd]
root        16  0.0  0.0     0    0 ?        SW   Feb05   0:28   [kjournald]
root       146  0.0  0.0     0    0 ?        SW   Feb05   0:00   [kjournald]
root       147  0.0  0.0     0    0 ?        SW   Feb05   0:11   [kjournald]
root       483  0.0  0.0  1472  332 ?        S    Feb05   0:01   syslogd -m 0
root       488  0.0  0.0  2068    4 ?        S    Feb05   0:00   klogd -2
rpc        508  0.0  0.0  1552  112 ?        S    Feb05   0:00   portmap
root       710  0.0  0.0  2264  124 ?        S    Feb05   0:00   xinetd -stayalive -reuse -pidfile /var/run/x...
root       737  0.0  0.0  1584  108 ?        S    Feb05   0:00   crond
root     16645  0.0  0.0  1384    4 tty1     S    Feb24   0:00   /sbin/mingetty tty1
root       745  0.0  0.0  1384    4 tty2     S    Feb05   0:00   /sbin/mingetty tty2
root       746  0.0  0.0  1384    4 tty3     S    Feb05   0:00   /sbin/mingetty tty3
root       747  0.0  0.0  1384    4 tty4     S    Feb05   0:00   /sbin/mingetty tty4
root       748  0.0  0.0  1384    4 tty5     S    Feb05   0:00   /sbin/mingetty tty5
root       749  0.0  0.0  1384    4 tty6     S    Feb05   0:00   /sbin/mingetty tty6
root     30683  0.0  0.9 46836 6084 ?        S    Feb28   0:03   /usr/sbin/httpd -DHAVE_ACCESS -DHAVE_PROXY...
apache   31821  0.0  0.9 46932 6296 ?        S    04:02   0:00     /usr/sbin/httpd -DHAVE_ACCESS -DHAVE_PROXY...
apache   31822  0.0  0.9 46908 6284 ?        S    04:02   0:00     /usr/sbin/httpd -DHAVE_ACCESS -DHAVE_PROXY...
apache   31823  0.0  0.9 46932 6296 ?        S    04:02   0:00     /usr/sbin/httpd -DHAVE_ACCESS -DHAVE_PROXY...
apache   31824  0.0  0.9 46908 6284 ?        S    04:02   0:00     /usr/sbin/httpd -DHAVE_ACCESS -DHAVE_PROXY...
apache   31825  0.0  0.9 46932 6296 ?        S    04:02   0:00     /usr/sbin/httpd -DHAVE_ACCESS -DHAVE_PROXY...
apache   31833  0.0  0.9 46908 6284 ?        S    04:02   0:00     /usr/sbin/httpd -DHAVE_ACCESS -DHAVE_PROXY...
apache   31834  0.0  0.9 46932 6296 ?        S    04:02   0:00     /usr/sbin/httpd -DHAVE_ACCESS -DHAVE_PROXY...
apache   31835  0.0  0.9 46908 6284 ?        S    04:02   0:00     /usr/sbin/httpd -DHAVE_ACCESS -DHAVE_PROXY...
root      1174  2.0  0.2  2264 1128 pts/0    S    12:10   0:00   /iarc/bin/iadbraima
root      1181  4.0  0.2  2476 1320 ?        S    12:10   0:00   /iarc/bin/iarcd
root      1184  0.5  0.1  3984  712 ?        S    12:10   0:00     iavol
root      1186  0.0  0.1  3984  712 ?        S    12:10   0:00       iavol
root      1187  3.5  0.1  3984  712 ?        S    12:10   0:00         iavol
root      1185  0.5  0.2 27112 1436 ?        S    12:10   0:00     /iarc/bin/iarcd
root      1189  1.0  0.2 27112 1436 ?        S    12:10   0:00       /iarc/bin/iarcd
root      1190  0.0  0.2 27112 1436 ?        S    12:10   0:00         /iarc/bin/iarcd
root      1191  0.0  0.2 27112 1436 ?        S    12:10   0:00         /iarc/bin/iarcd
root      1192  0.0  0.2 27112 1436 ?        S    12:10   0:00         /iarc/bin/iarcd
root      1192  0.0  0.2 27112 1436 ?        S    12:10   0:00         /iarc/bin/iarcd


Pay attention to output marked in red colour. This is usually a "healthy" system. If you don't see a similar output, consult IMiS/ARChive logs (/var/log/iarc.log) to see if IMiS/ARChive encountered any errors during startup.

Stoping IMiS/ARChive

Administrator can stop IMiS/ARChive server by issuing command /etc/inid.d/iarcd stop.


[root@imisarc /]# /etc/init.d/iarcd start
Shutting down IMiS/ARC storage server:                     [  OK  ]
Shutting down IMiS/ARC database driver:                    [  OK  ]
[root@imisarc /]#


If you see any of the tasks FAIL ([FAILED]), rerun /etc/inid.d/iarcd stop until all tasks finish (run ps aux -H to check process list).


| Back | Main view | Parent doc