Extraction Browser

Restarting the Extraction Browser Web Demo on Reliable

Restarting the Servlet Process

1. Log in to reliable as knowall via SSH
2. Run the command 'screen -ls' and check for a detached screen called 'extractionBrowser'. If it is already running:
   1. Switch to it using the command 'screen -r extractionBrowser'
   2. Press Control-c to kill any extraction browser process that might already be running.
3. If the 'extractionBrowser' screen was not already running, start a new one with 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 reliable.cs:8088, to which openie.cs forwards requests.
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 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, refer them to wreq #173026)
7. Detach the screen session by pressing Control-a d.

Restarting memcached

1. Log in to reliable as knowall via SSH (if you haven't already)
2. 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
3. If memcached is already running, kill it using the command 'kill <pid>' where <pid> is memcached's PID.
4. 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'
5. 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

Configuring the Demo Monitoring and Notification service

The extraction browser includes a bash script and a set of text files that are used for monitoring the health of the demo and notifying people if there is a problem. These files have names like monitor-* and are located in version control under the extractionbrowser project in the src/main/resources/scripts/ directory.

These files have also been copied to the knowall account at /homes/gws/knowall/scripts/monitor/. The monitoring script runs on the machine recycle, in a screen called 'browserMonitor'. Check for this screen to be running before you try to start a new one. The command to start a new browser monitor daemon is screen -dmS browserMonitor /homes/gws/knowall/scripts/monitor/monitor.sh

Troubleshooting notes

ExtractionBrowserTroubleshooting