Changes between Version 8 and Version 9 of shepherding_the_pstamp_server

Timestamp:

May 10, 2013, 11:48:35 AM (13 years ago)

Author:

bills

Comment:

--

shepherding_the_pstamp_server

@@ -97 +97 @@
 '''Common Failures'''
 
-Requests can fault for two reasons either at the parse stage or when finishing the request. Request
-faults rarely happen and are usually due to software bug. 
+Requests can fault for three reasons either at the parse stage or when finishing the request. 
+
+The most common fault gets set in the database as fault = 200. This happens when one of the source
+data stores responds with a HTTP 500 (Internal Server Error). MOPS' data store does this occasionally.
+These usually require no intervention as there is a revert task that will clear the fault allowing
+the system to try again.
+
+Other request faults rarely happen and are usually due to software bug. 
 
 Jobs can fault due to typical nfs errors. There is a revert task for jobs. It only resets jobs with
@@ -157 +163 @@
  * change label priority until fixed/cleared? labeltool not working/right to use?
 
-
+To make a request and it's jobs just go away set the request's state to goto_cleaned.
 
 == Postage Stamp Error Codes ==
@@ -186 +192 @@
 == Monitoring the Apache Server ==
 
-It is a good idea to check the Apache error log (/var/log/apace2/error_log) from time to time to look for unusual activity. On June 4, 2010 I found a user furtively looking for a results file for a request that was submitted May 24, 2010.
-
-
-
-
+It is a good idea to check the proxy's Apache error log (/var/log/apace2/error_log) from time to time to look for unusual activity.
+
+We get hourly requests from Google and Baidu for files long gone that their crawlers found prior to the time that we locked down
+the data store.
+
+
+
+