Monitor application status

The PureWeb server's Status page, which is the landing page displayed when you first log in, provides a visual dashboard for information about sessions, node capacity, and usage.

To access this page, log into the server and click the Status link, or you can navigate to the page directly if you are already logged in:
http://[server]:[port]/pureweb/server/status


  You can set up a monitoring tool such as Nagios (www.nagios.org) to send an alarm in the event that the Status page returns a 404 error or times out.

The page is organized in three sections: the status bar, the node and display details, and a list of queued unmanaged applications.


Status bar

The status bar indicates how much of the node’s total graphic display allocation (typically GPUs) is currently in use relative to overall availability. The red indicates current usage, the green indicates current availability.

For information on configuring display devices available for the server, see Display properties.

The status bar and its timestamp are not updated automatically at regular intervals. To update them, refresh the page in the browser.

 

The status bar is labeled "Cluster Status", since it is possible to cluster several nodes on the same server. However, note that while the current clustering mechanism is still supported for small multi-server environments (2 to 3 servers), it is recommended that a load balancer be used for such environments instead. See Multi-server environments.


Node and display information

This section of the Status page is used to manage active image sessions. It provides the following information:

  • The server node's unique name, in the format myserver.mydomain.com. In the rare instance where you may need to configure this name explicitly, you would do so by editing the value for hostname in Node properties.
  • The node status. Changing a node from Active to Inactive, for example, can be useful to temporarily take a node offline and test it. For most information, see Nodes states.
     Changes made to the node state from the Status page are not persistent. When you restart the server, it uses the values in the cluster-plugin.xml file. For more information, see Node properties.
  • Each node can have several displays. You can think of a display as a collection of slots for available sessions. For each display, the Status page provides the following information:
    • Name: the unique name identifying the display, for example unix:0.0 and unix:0.1 on Linux, or gpu.0 or gpu.1 on Windows.

    • Capacity and usage: this is the information in parenthesis after the display name. For example (2/20) means that there are two active imaging sessions out of 20; this second number, 20, indicates the maximum capacity for the display.

    To edit a display name, or the maximum number of sessions allowed for that display, edit the cluster-plugin.properties file as described in Display properties.

Below the display name is a sessions list.

If users are connected to an image session, additional lines will appear below that session in the list. For example:

Session: #1 DDx 7992 506A1336BCFD44E763431D030F04082C Release

Connection: admin@111.111.11.111 connected since May 13, 2014 8:52:57 AM Disconnect

These lines contain links for disconnecting users and terminating active rendering sessions:

  • Click the Release link to forcibly release the session. This disconnects all connected clients and shuts down the associated process.
  • Click the Disconnect link to disconnect a single user interacting in a session. The session is automatically released when the last client is disconnected.

Queued unmanaged applications

This section lists any unmanaged services deployed on the server and for which no client is currently logged in.

Once a client application logs into an unmanaged service, that service is no longer queued but appears in the list of active sessions.