IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links * -- restricted access

Return to the Main Page

  1. Download the IPP code from our SVN repository
  2. Build & Install (unify and clarify)
  3. Install only Ohana
  4. Site-Specific Configuration
  5. Camera-Specific Configuration
  6. ippMonitor Installation
  7. Nebulous Installation
    1. Nebulous/Apache? server installation
  8. Notes

Download the IPP code from our SVN repository

  • our operation tags are listed under the 'tags' directory
  • Download from the trunk​ for the current bleeding-edge 'head' of the development tree.
  • older 'numbered version' can be found at ​IPP download page, but these are not supported.
  • if you want to build the IPP on your desktop Ubuntu based machine, it is safest to have the developer versions of critical libraries installed. This is safer than installing the IPP supplied versions because the developer versions are consistent with the build of existing packages on your machine. Here is an apt-get command that installs all of the developer packages we need: 
    apt-get install libx11-dev libncurses-dev automake libtool libjpeg-dev zlib1g-dev libgsl0-dev libmysqlclient-dev libpng12-dev libgtk-3-dev

Build & Install (unify and clarify)

Install only Ohana

See OhanaStandAlone

Site-Specific Configuration

Camera-Specific Configuration

ippMonitor Installation

  • ippMonitor : Notes on installing PHP modules to allow ippMonitor to run - Michael Wood-Vasey and Mark Huber.
  • IppMonitor setup : Notes on IPP commands for setting up ippMonitor

Nebulous Installation

Nebulous/Apache? server installation

The installation script and source tar.gz files needed for the apache configuration of nebulous are located in ~ipp/src/nebulous-apache-dependencies. The README file contains instructions on executing the install-nebulous.sh script, which must be run as root to ensure that the installation is global (and therefore visible to the apache server). The install-nebulous.sh script lists all the possible perl dependencies that are needed, but most have been commented out as they appear to be installed by default on the ipp cluster. The only exception (as of 2015-06-25 and the installation on ippc20) is the Apache2::SOAP module. This has been left uncommented so it will be installed. The script will then copy the apache configuration files (which should be checked against those currently in use on the active apache servers) into place. Finally, the Nebulous-Server package is exported from SVN and installed.

At this point, the script stops and restarts the apache server, and assuming no modules are missing, the configuration can be tested by setting the NEB_SERVER variable (for the ippc20 install, setenv NEB_SERVER http://ippc20.ipp.ifa.hawaii.edu/nebulous) and executing nebulous script commands. Errors of the sort: 

500 Internal Server Error at /home/panstarrs/watersc1/ipp/install/default.lin64/lib/Nebulous/Client.pm line 1325

suggest a missing perl module on the server, and for this installation, /var/log/apache/error_log pointed to the problem: 

[Thu Jun 25 15:20:55 2015] [error] [client 10.10.20.80] failed to resolve handler `Apache2::SOAP': Can't locate Apache2/SOAP.pm in @INC (@INC contains: /home/httpd/perl /etc/perl /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux /usr/lib64/perl5/vendor_perl/5.8.8 /usr/lib64/perl5/vendor_perl /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux /usr/lib64/perl5/site_perl/5.8.8 /usr/lib64/perl5/site_perl /usr/lib64/perl5/5.8.8/x86_64-linux /usr/lib64/perl5/5.8.8 /usr/local/lib/site_perl . /usr/lib64/apache2) at (eval 133) line 3, <DATA> line 13.\n

Notes

  • mysql can fill up its disk with log files. It is easy to flush the files if this happens:

mysql> flush logs; mysql> reset master;

It is also possible to limit the max size. See discussion on ​this site.

Last modified 2 years ago Last modified on Oct 22, 2018, 8:28:45 AM