netstat --listen --inet # warning IPv4 only
netstat --numeric --listen --tcp
netstat -peanut
Use curl to check that the local stack is running:
curl -H 'Host: dev.genometranslationcommons.org' http://127.0.0.1/
any response from this means that apache is running;
if you get the (expected) 302 redirect then it means apache is correctly configured to use
sites-enabled/25-refinery.conf
To make a curl that reached the Django app, you have to fake being an AWS ELB by adding the X-Fordwarded-Proto
header:
curl -H 'X-Forwarded-Proto: https' -H 'Host: dev.genometranslationcommons.org' http://127.0.0.1/
The output should be the front page of Refinery, which is a big bunch of templated HTML (and JavaScript).
pstree
is pretty useful. Especially to see if could-init is still running.
ps waxwux
ps waxwux | grep supervisord
should show the supervisord
process if it is running.
Also, there should be a /tmp/supervisord.pid
file.
Similarly, ps waxwux | grep celery
should show the celery processes.
Log files appear in /srv/refinery-platform/refinery/log
(or in general, refinery/log
relative to whereever the git repo is checked out).
The usual ps waxwux | grep solr
does in fact work.