Managing servers and processes

From HEWIKI
Jump to: navigation, search

Contents

He server.png Documentation on this page is intended for customers of HeroEngine managing their own server(s).

Servers and processes and managed via the Master Control Console client, which communicates with the Master Control Daemon on the server. It displays the structure of the component tree, which it gets from the Master Control Database, along with the status of those components, which it gets from the Master Control Daemon. It also allows you to view logging information from the various processes, and control the various servers, such as to open and close them to new processes, or to stop processes entirely.

Starting up a server

  • If it is red, that means the fireup daemon is not running on that machine. In this case, it will be necessary to VNC to it, and start it manually.
  • VNC stands for Virtual Network Computer. It is a way to remotely run one computer from another. To do this, you need to have a VNC application on your computer, as well as the necessary password for the remote system.
MasterControlConsole.png

Determining whether or not a server is up

Note: Processes can go into a "bad" state, meaning that a process may look like it's up, but may be halted after detecting a non-recoverable error. This can be detected by looking at the process's statistics, which should have a label such as, "STATE: BAD". If this happens, then:

Determining if the Service Directory Process is up

The different Service Directory Process are defined as services under their respective world.

Each Service Directory process should have two other supporting processes:

If all three processes do not exist, or one of the processes shows up as being in a bad state, shut it down and restart it (see above section).

Shutting down a server

If a process fails to shutdown within the allotted time, an error message will show up. The message will state that the process didn't shut down, and that the automated shutdown process was stopped. In most cases this is just because some of the processes took longer to shutdown than others, and timed out. The best practice at this point is simply to wait for a moment, and then try again.

Terminate a server

If a process is flashing, that means something bad happened to it, like a crash, or it shut itself down because it sensed a problem of some sort. To learn more, expand the tree to view that process and select it by clicking on it. This will then display information about that process in the Status Window.

A process that is flashing red or hung firing up/shutting down will need to be dealt with before it can be started again. If necessary, select the process and select TERMINATE.

Issuing the terminate command will order the system to immediately kill the specified process without giving it a chance to cleanly shutdown. It will then switch to the shutdown state.

Listening to log messages

Through the Master Control, you can listen to current log messages from any process, and view the history of log messages from any process, going back 500 log messages per process.

While you are watching, log messages will show up in the Logging window below the Component Tree.

Performance metrics

Through the Master Control Console, it is possible to view the performance of any process or server, such as its CPU load. Whichever servers are currently visible in the Component Tree, will be displayed in the CPU Load window.

Status window

Selecting a single server or process will cause that server or process's information to be displayed in the Status Window. Various tabs within the window provide additional information:

Performance

Not currently implemented

Processes

Similar to the Windows Task Manager, this displays dynamic and static processes.

To stop a process, locate it in the Component Tree, select it, and choose the SHUTDOWN option in the top menu.

Server logs

The server side logs are located at:

 C:\Program Files\HeroEngine\FIRESTORMDAEMONS(name)\log

The file path may change depending on name, which will usually be the name or an abbreviation of your own company. (only active for source licensees running their own servers)

See also

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox