Difference between revisions of "Extraction Browser"
From Knowitall
Line 6: | Line 6: | ||
# 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) | # 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 "<tt>STARTING</tt>", 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 "<tt>STARTING</tt>", without any error messages or stack traces. At this point, the Servlet is ready to serve demo requests. | ||
− | # Verify that | + | # Verify that the demo is accessible at http://openie.cs.washington.edu and http://reliable.cs.washington.edu:8088, and check that a few example queries behave correctly. (If only the latter URL works, support should be able to help) |
# Detach the screen session by pressing <tt>Control-a d</tt>. | # Detach the screen session by pressing <tt>Control-a d</tt>. | ||
Revision as of 01:50, 24 December 2011
(Re)starting the Extraction Browser Web Demo on Reliable
Restarting the Servlet Process
- Log in to reliable as knowall via SSH
- Run the command 'screen -ls' and 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.
- run the command 'screen -S extractionBrowser'. to start a new screen session for the demo.
- 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)
- 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 the demo is accessible at http://openie.cs.washington.edu and http://reliable.cs.washington.edu:8088, and check that a few example queries behave correctly. (If only the latter URL works, support should be able to help)
- Detach the screen session by pressing Control-a d.
Restarting memcached
- Log in to reliable as knowall via SSH (if you haven't already)
- Check that memcached is not already running with the command 'ps aux | grep memcached'. If memcached is running, you will see a process that looks like knowall 17054 0.0 0.0 341780 16836 ? Ssl 01:10 0:00 ./memcached -d -m 2048 -l 128.95.1.229 -p 11211
- If memcached is already running, kill it using the command 'kill <pid>' where <pid> is memcached's PID.
- Start a new memcached daemon process by running the command '/home/knowall/local/opt/memcached/bin/memcached -d -m 2048 -l `hostname --ip` -p 11211'
- Verify that both the demo and memcached are working properly by checking that demo queries either report "cache miss" or "from cache" at the top of the results page.
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:
(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