...
- Copy the opService tarball to the slave poller or master NMIS server (a tarball is a GZIP'd tar file, e.g. opHA-1.1.opService-Linux-x86_64-8.tar.gz)
- You may need to use SCP or FTP to get the file onto the server.
- The file will now likely be in the users home directory.
- If the installation directory does not already exist
- Change into the directory where the tarball was copied
- Untar the file
Code Block |
---|
Version=8
#(not required for Debian/Ubuntu)
unalias cp
cd ~
tar xvf ~/opService-Linux-x86_64-$Version.tar.gz
cd opService-Linux-x86_64-$Version/ |
Run the installation program, answer the questions and opService will be installed. The defaults will normally always work.
Code Block |
---|
./install-opService.pl |
Install opService Daemon
Setup init.d to handle opService
Code Block |
---|
cp /usr/local/opmantek/install/opserviced.init.d /etc/init.d/opserviced
chmod 755 /etc/init.d/opserviced
service opserviced start |
The daemon can be stopped or restarted using the command "service opserviced restart".
Setup the Log Files
Create the empty log files
Code Block |
---|
touch /usr/local/opmantek/logs/opservice.log
touch /usr/local/opmantek/logs/incident.log
touch /usr/local/opmantek/logs/service_event.log
chown -R nmis:nmis /usr/local/opmantek/logs/
chmod 664 /usr/local/opmantek/logs/*log |
Configuring opService
That is the topic for another article.