Troubleshooting - RedwoodAdmin/RedwoodFramework GitHub Wiki

Recovering Frozen Sessions

Every effort has been made to make Redwood as stable as possible but in some rare circumstances experiments can freeze up preventing subjects from advancing to the next period. The default admin page for each experiment provides a "Recover Session" button which should be the solution to try when an experiment freezes. This function will cause all subject pages to be refreshed and "lost" messages will be resent. This is often enough to recover the session. The only other option that can sometimes recover the session is to refresh the browser of the "offending" subject (usually the subject that is on a different period to the rest). If this still doesn't recover session it is best to download the data and restart the experiment. Also, make sure to read the timers and gotchas pages since these describe things to avoid when developing experiments that can often lead to stalling.

Starting/Restarting the Router

The router may need to be started or restarted for a number of reasons. Either it doesn't start automatically when the server boots, or it has either crashed or stalled.

Ubuntu
The Redwood router runs as a service and can be controlled using the following command in a terminal.
start: $service redwood-router start
stop: $service redwood-router stop
restart: $service redwood-router restart

Windows
In Windows the Redwood router simply runs as a desktop application.
start: double click on /redwood/go/bin/expecon-router.exe
stop: close the window named "expecon-router"