Difference between revisions of "Extraction Browser"

From Knowitall
Jump to: navigation, search
Line 2: Line 2:
 
=== Restarting the Servlet Process ===
 
=== Restarting the Servlet Process ===
 
# Log in to reliable as knowall
 
# Log in to reliable as knowall
# check that a screen called 'extractionBrowser' is not already running. If it is, switch to it (using command 'screen -r extractionBrowser') and skip the next step.
+
# check that a screen called '<tt>extractionBrowser</tt>' is not already running. If it is, switch to it (using command '<tt>screen -r extractionBrowser</tt>') and skip the next step.
# run the command 'screen -S extractionBrowser'.
+
# run the command '<tt>screen -S extractionBrowser</tt>'.
# run the command 'java -jar ~/web/jetty/jetty-distribution-8.0.4.v20111024/webapps/extractionbrowser-1.0.0-jetty-console.war --port 8088'. This will start the extraction browser servlet listening on port 8088 (openie.cs forwards requests to reliable.cs:8088)
+
# run the command '<tt>java -jar ~/web/jetty/jetty-distribution-8.0.4.v20111024/webapps/extractionbrowser-1.0.0-jetty-console.war --port 8088</tt>'. This will start the extraction browser servlet listening on port 8088 (openie.cs forwards requests to reliable.cs:8088)
 
# If everything works normally, stdout should display a small amount of output ending with the text "STARTING", without any error messages or stack traces. At this point, the Servlet is ready to serve demo requests.
 
# If everything works normally, stdout should display a small amount of output ending with the text "STARTING", without any error messages or stack traces. At this point, the Servlet is ready to serve demo requests.
 
# Verify that you can see the demo at http://openie.cs.washington.edu and optionally (if troubleshooting) http://reliable.cs.washington.edu:8088
 
# Verify that you can see the demo at http://openie.cs.washington.edu and optionally (if troubleshooting) http://reliable.cs.washington.edu:8088
Line 11: Line 11:
 
=== Restarting memcached ===
 
=== Restarting memcached ===
 
# Log in to reliable as knowall
 
# Log in to reliable as knowall
# Check that memcached is not already running by running the command 'ps aux | grep memcached'. If memcached is running, you will see a process that looks like  
+
# Check that memcached is not already running by running the command '<tt>ps aux | grep memcached</tt>'. If memcached is running, you will see a process that looks like  
  
  
Line 17: Line 17:
 
(current as of 12/23/2011)
 
(current as of 12/23/2011)
 
* <tt>@reboot screen -dmS extractionBrowser java -jar ~/web/jetty/jetty-distribution-8.0.4.v20111024/webapps/extractionbrowser-1.0.0-jetty-console.war --port 8088</tt>
 
* <tt>@reboot screen -dmS extractionBrowser java -jar ~/web/jetty/jetty-distribution-8.0.4.v20111024/webapps/extractionbrowser-1.0.0-jetty-console.war --port 8088</tt>
* @reboot /home/knowall/local/opt/memcached/bin/memcached -d -m 2048 -l `hostname --ip` -p 11211
+
* <tt>@reboot /home/knowall/local/opt/memcached/bin/memcached -d -m 2048 -l `hostname --ip` -p 11211</tt>
  
  

Revision as of 00:18, 24 December 2011

(Re)starting the Extraction Browser Web Demo on Reliable

Restarting the Servlet Process

  1. Log in to reliable as knowall
  2. check that a screen called 'extractionBrowser' is not already running. If it is, switch to it (using command 'screen -r extractionBrowser') and skip the next step.
  3. run the command 'screen -S extractionBrowser'.
  4. run the command 'java -jar ~/web/jetty/jetty-distribution-8.0.4.v20111024/webapps/extractionbrowser-1.0.0-jetty-console.war --port 8088'. This will start the extraction browser servlet listening on port 8088 (openie.cs forwards requests to reliable.cs:8088)
  5. If everything works normally, stdout should display a small amount of output ending with the text "STARTING", without any error messages or stack traces. At this point, the Servlet is ready to serve demo requests.
  6. Verify that you can see the demo at http://openie.cs.washington.edu and optionally (if troubleshooting) http://reliable.cs.washington.edu:8088
  7. Detach the screen session by pressing 'Control-a d'.

Restarting memcached

  1. Log in to reliable as knowall
  2. Check that memcached is not already running by running the command 'ps aux | grep memcached'. If memcached is running, you will see a process that looks like


Note: Extraction Browser should automatically restart itself under knowall on the machine reliable in the event of a reboot, due to the following crontab entries: (current as of 12/23/2011)

  • @reboot screen -dmS extractionBrowser java -jar ~/web/jetty/jetty-distribution-8.0.4.v20111024/webapps/extractionbrowser-1.0.0-jetty-console.war --port 8088
  • @reboot /home/knowall/local/opt/memcached/bin/memcached -d -m 2048 -l `hostname --ip` -p 11211


Bug List

  • Search for predicate:"is located in" yields a null error.
  • Search for argument1:"United States" overconstrains the results.