Changes between Version 7 and Version 8 of PS1_IPP_Czarlog_20190426

Timestamp:

Apr 30, 2019, 12:37:33 PM (7 years ago)

Author:

fairlamb

Comment:

--

PS1_IPP_Czarlog_20190426

@@ -380 +380 @@
 
 
+''' Making another apache server for nebulous''' by JRF
+
+We want to add ippc76 as a nebulous apache server
+
+Check out:
+{{{
+  /etc/apache2/httpd.conf
+  /etc/apache2/modules.d/apache2-mod_perl-startup.pl
+  /etc/apache2/modules.d/00_mpm.conf 
+}}}
+They contain information on the configuration of the nebulous apache server. Have a look at the current servers to see how they are setup
+
+There is a config for the nebulous servers:
+{{{
+  ~ippitc/ippconfig/nebservers.csh
+}}}
+This is referenced only by the .tcshrc file of ippitc  - '''which is not tracked!'''
+In here we can set which nodes should be used for nebulous, so make a copy of the file and add the new server.
+{{{
+  set nebservers = ($nebservers http://ippc76/nebulous);
+}}}
+We will not do this step just yet.
+
+NOTE: That the total connections from the apache nodes should be less than the max connections allowed in the nebulous database, you can check this with: 
+{{{
+  mysql -uXXXXXX -pXXXXXXX -h ippdb09 nebulous
+
+  mysql> select @@max_connections;
+}}}
+At present the mas connections are 2048. If we are using ippc71-76, which have 256 connections each, then fortunately: 6*256 < 2048
+
+Right, we need to make sure that ippc76 is actually ready to be used as a nebulous server:
+One of these steps it to make sure it has a nebulous log file that it can use, which should be located under /tmp/ :
+{{{
+  ls -l /tmp/
+  -rw-rw-r-- 1 apache nebulous   0 Apr 22 03:10 nebulous_server.log
+}}}
+It should belong to apache and be part of the nebulous group.
+
+We also need to have the apache server running! Check the status with:
+{{{
+  /etc/init/d/apache2 status
+}}}
+
+The apache server also needs to be pointing to the correct database (this is in the perl script). Once you're happy with all of the config, then go ahead and add:
+{{{
+  set nebservers = ($nebservers http://ippc76/nebulous);
+}}}
+to the nebservers.csh file
+
+After this the server started getting used, but the nebulous_server.log file disappeared. Simply restarting the apache server recreated it. However, if it does not you may need to touch the file (and make sure the permissions are correct).
+
+NEW PRBOLEMS!
+The log file is just not updating at all, even when we are using ippc76 to connect to the nebulous database (you can forcably change to use a specfic apache node by {{{set NEB_SERVER = http://ippc76}}}).
+Not sure what the problem is so we'll remove ippc76 from the nebservers list for the time being...
+
+
+''' Tidying up labels '''
+
+Under ~ippitc/stdscience/input are all the labels that are added when pantasks starts up. We've commented out some lesser used ones.
+
+
+To do: 
+ 
+
+
 TODO:
  - once the PDU is done for ipp134-136:
    -- check the console
-   -- put them to up to allow updates to continue and check on them
+   -- put them to up to allow updates to continue and check on them (but put to repair for nightly...maybe)
+ - check that the commented out labels are gone after reset.
+ - For remaining update problems:
+    -- if they complain about missing cm (camera) files then they should be reprocessed.
+    -- revert the stuck jobs once ipp134-139 are available again