From the System Administration tool you can view the JobServer Runtime Log and startup and shutdown times for each particular run of JobServer. Each JobServer start/stop sequence is shown as a separate row over the given time range requested. For example, this GUI will let you know if the the JobServer Scheduling engine was started or if the server remained in IDLE state and when the JobServer Scheduling Engine was shutdown and how it was shutdown.
These logs are displayed based on a time range of interest to the user. So a user can search back in time to know exactly when JobServer was started and how it was shutdown. The start and end times entered into the search will display all JobServer runs that started during the time range specified. The details of each JobServer run (from startup to a shutdown) are available by clicking on the "view" button. This will bring up a window showing all logging information during that particular run of the JobServer.
After the JobServer Scheduling Engine has successfully started running (starated from an IDLE state), all logging information regarding JobServer's operating status can be found in this log. Click the "view" button to see the specific startup and runtime logs for each particular JobServer Scheduler run.
This shows when the JS Container was started. This does not necessarily mean the JS Scheduling Engine was started. It only lets you know when the JS Container was initialized and put into "Idle" state.
This shows when the JS Scheduling Engine was started and jobs could possible be allowed to run. If you click the "view" button for each row you can see the detailed startup conditions for each run of the JS Scheduling Engine and all of the runtime logs that happened during that run including job level system errors and warnings. If the value of this column is "NA", this typically means the JS Scheduling Engine was never started. Basically this means the JS Container was started in "Idle" state and then shutdown without ever going into "Running" state.
This shows when the JS Container stopped running. If the Scheduling Engine was running, then this date also indicates when the Scheduling Engine was shutdown (or detected to be shutdown).
This shows the current runtime status of the JobServer environment. The possible runtime states are "Running" or "Idle". Running means the JobServer Scheduling Engine is active and jobs could be running. Idle means the the JS Scheduling is NOT running yet, but instead waiting for someone to start it. If the row entry is for an older time period (start/stop in the past), then this column shows how the JS system was shutdown and under what conditions it was shutdown. The valid JobServer status types are: "Immediate Shutdown", "Graceful Shutdown" and "Hard Shutdown". The Immediate and Graceful Shutdown status types indicate that JobServer was shutdown by the user using the Start/Stop controls. The "Hard Shutdown" status indicates that JobServer was shutdown abruptly possible due to a crash of the JVM or the OS. Note, that each JobServer new run/startup has a unique "run id".
Name of the host computer that the primary scheduling engine will run on. This is only useful if you are using a secondary failure server so that you can tell where the primary scehduler is running.
Startup Mode indicates how the JobServer system was started. It can be started "manual", meaning it was started from a user initiated startup script or from the GUI. "auto" means JobServer engine was started automatically by the monitor scripts within the JobServer environment.