Changes between Initial Version and Version 1 of PS1_IPP_Czarlog_20190503

Timestamp:

May 3, 2019, 9:38:44 AM (7 years ago)

Author:

fairlamb

Comment:

--

PS1_IPP_Czarlog_20190503

@@ +1 @@
+== PS1 IPP Czar Logs for the week 2019.05.03 - 2019.05.09 == 
+[[PageOutline]]
+
+(Up to [wiki:PS1_IPP_CzarLogs PS1 IPP Czar Logs])
+
+
+=== Friday : 2019.05.03 ===
+
+''' pstamp requests ''' by JRF
+
+Received some error emails about pstamp requests. checking out the pstamp server we can see that over 800,000 jobs have been submitted by QUB. 
+
+The errors come from a script run by the crontab on ippc26 (this is mentioned in the emails). The script checks if pstamp has over 100,000 jobs done as this is were pantasks becomes flaky.
+
+Checking out the status of the pstamp pantasks keep an eye on:
+{{{
+  request.finish.run
+}}}
+as we '''DO NOT''' want to restart if this is running as it will cause funkiness.
+
+So let's restart pstamp, doing the usual:
+{{{
+  pantasks> stop
+  pantasks> shutdown now    --check that the jobs have finished first
+
+  ~ippitc/pstamp> pantasks_server & pantasks_client
+  pantasks> server input input
+  pantasks> setup
+  pantasks> run
+}}}
+
+I have added ippc76 to the {{{hosts_apache}}} group in the {{{~ippitc/ippconfig/pantasks_hosts.input}}} file. This is so that when the nodes are allocated that ippc76 will be turned off when the apache group is removed.
+
+Since over 800,000 requests were made the pstamp pantasks will need restarting about every hour or so.
+
+=== Saturday : 2019.05.04 ===
+
+=== Sunday : 2019.05.05 ===
+
+=== Monday : 2019.05.06 ===
+  
+=== Tuesday : 2019.05.07 ===
+
+=== Wednesday : 2019.05.08 ===
+
+=== Thursday : 2019.05.09 ===