This page last changed on Aug 11, 2005 by mattlangston.

web007

There are a number of servers running on web007 used by Glast

IIS5

This runs with many virtual servers, mostly unrelated to glast. The ones relevant to glast are:

jira.slac.stanford.edu
confluence.slac.stanford.edu

These both simply forward requests to the relevant tomcat server (see below). IIS5 has so far never gone wrong, so there are no instructions for how to fix it.

MySQL

This is used as the database for jira and confluence, among other things. It has never gone wrong, so there are no instructions for how to fix it.

Tomcat5

There are two instances of tomcat5 running, one which runs jira and confluence, the other which runs miscellaneous services, currently SystemTests and Pipeline (experimental version).

Service Name Apache Tomcat Apache Tomcat extra
CATALINA_HOME D:\java\jakarta-tomcat-5.5.7 D:\java\jakarta-tomcat-5.5.7
CATALINA_BASE D:\java\tomcat-base2 D:\java\tomcat-base
JAVA_HOME d:\java\jdk1.5.0 d:\java\jdk1.5.0
http port 808 8888
AJP13 port 8009 8019

If either of these services fails the easiest way to fix them is via windows service manager. You can run service manager on any node at SLAC or connected via VPN, connect to web007, and use it to stop and restart the services. Currently Richard, Matt and Tony have admin access to perform this operation.

Warning

Currently the tomcat server is experiencing some problems. Details are being tracked here

Rebooting web007

In the extreme case that that the actual web server (web007) needs to be rebooted, please send an email notification to scs-windows-infrastructure@slac.stanford.edu and [softlist@glast.stanford.edu] to give people a heads up that you are rebooting the server. SCS monitors web007 and its services, and has requested that they be notified whenever the machine is rebooted.


servicemanager.png (image/png)
Document generated by Confluence on Jan 21, 2010 11:37