Difference between revisions of "Extraction Browser"
From Knowitall
| (31 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | = | + | = Restarting the Extraction Browser Web Demo on Reliable = |
| − | # Log in to reliable as knowall | + | == Restarting the Servlet Process == |
| − | # check | + | # Log in to reliable as knowall via SSH |
| − | # | + | # Run the command '<tt>screen -ls</tt>' and check for a detached screen called '<tt>extractionBrowser</tt>'. If it is already running: |
| − | # | + | ## Switch to it using the command '<tt>screen -r extractionBrowser</tt>' |
| − | # 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. | + | ## Press <tt>Control-c</tt> to kill any extraction browser process that might already be running. |
| − | # Verify that | + | # If the '<tt>extractionBrowser</tt>' screen was not already running, start a new one with the command '<tt>screen -S extractionBrowser</tt>'. |
| − | # Detach the screen session by pressing ' | + | # 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 reliable.cs:8088, to which openie.cs forwards 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 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) | ||
| + | # Detach the screen session by pressing <tt>Control-a d</tt>. | ||
| + | |||
| + | == 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 '<tt>ps aux | grep memcached</tt>'. If memcached is running, you will see a process that looks like <tt>knowall 17054 0.0 0.0 341780 16836 ? Ssl 01:10 0:00 ./memcached -d -m 2048 -l 128.95.1.229 -p 11211</tt> | ||
| + | # If memcached is already running, kill it using the command '<tt>kill <pid></tt>' where <tt><pid></tt> is memcached's PID. | ||
| + | # Start a new memcached daemon process by running the command '<tt>/home/knowall/local/opt/memcached/bin/memcached -d -m 2048 -l `hostname --ip` -p 11211</tt>' | ||
| + | # 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: | ''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 | + | * <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> |
| + | |||
| + | = 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 <tt>monitor-*</tt> and are located in version control under the <tt>extractionbrowser</tt> project in the <tt>src/main/resources/scripts/</tt> directory. | ||
| + | These files have also been copied to the knowall account at /homes/gws/knowall/scripts/monitor/. The monitoring script runs on the machine <tt>recycle</tt>, 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 <tt>screen -dmS browserMonitor /homes/gws/knowall/scripts/monitor/monitor.sh</tt> | ||
| − | == | + | = Troubleshooting notes = |
| − | + | [[ExtractionBrowserTroubleshooting]] | |
| − | |||
Latest revision as of 02:24, 12 January 2012
Contents
Restarting 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 for a detached screen called 'extractionBrowser'. If it is already running:
- Switch to it using the command 'screen -r extractionBrowser'
- Press Control-c to kill any extraction browser process that might already be running.
- If the 'extractionBrowser' screen was not already running, start a new one with the command 'screen -S extractionBrowser'.
- 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.
- 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, refer them to wreq #173026)
- 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
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
