What do do if the webserver goes down
- Log in to remote.tjhsst.edu (or if you're already on the internal network, that's fine too)
- If you're on remote,
This restarts nginx/Apache and ensures that the service manager is still in a consistent state. The website should work after this (if not, try clearing cache/etc, it's possible a redirect to an error page might've been cached, although it shouldn't be).
If this doesn't work, there are a few things you can try:
pkill k5start pkill -9 k5start pkill apache2 pkill -9 apache2 pkill nginx pkill -9 nginx service apache2 zap service nginx zap service apache2 start service nginx start
This will make sure k5start/nginx/apache have actually been stopped (although possibly not cleanly) before restarting them. If this doesn't work, it's probably an issue with Kerberos / AFS -- make sure
/etc/krb5.keytab.www-data exists and has the correct keys (
ktlist -K -k /etc/krb5.keytab.www-data, you should see
www-data@CSL.TJHSST.EDU listed at least once).
If all of that doesn't work, it's most likely not a problem with the web server -- perhaps check AFS or Kerberos for issues that might be causing a web problem.
Granting a user access to edit the website
You'll need to be AFS admin, or ask someone who is, but simply run:
pts adduser username web.staging
This will grant full access to
/afs/csl/web/www, which is where website files are located.