Shutting Down the Server

There are several ways to shut down the AggreGate Server:

  • Using AggreGate Client application, when connected to the server with appropriate permissions.

  • Using Web UI, when logged on with appropriate permissions.

  • Using the System Tray Icon menu.

  • Using the Net Admin interface.

  • By stopping Windows/Linux service if the server is running in service mode.

  • By manually killing all server processes if the server is not responding to any other shutdown attempts.

In some cases, it may take up to several minutes for the AggreGate Server to complete the shutdown sequence and save cached data to the database. Terminating server process during shutdown by using operating system tools can cause data loss.

When shutting down the virtual machine the AggreGate Server is running on, the AggreGate Server shutdown sequence is automatically executed as well.

Server Shutdown Methods

Using AggreGate Client

To stop the server via AggreGate Client connection:

  • Find the server node () in the System Tree

  • Right-click on it

  • Select Stop Server from the context menu

You should have Administrator permissions in the Root context to be able to stop the server remotely.

Using Web UI

To stop the server from inside the Web UI:

  • Find the server node () in the System Tree

  • Right-click on it

  • Select Stop Server from the context menu

You should have Administrator permissions in the Root context to be able to stop the server.

Using Tray Menu

Select the Stop Server item from the AggreGate Server tray menu.

The tray menu is not available if server is running in service mode.

Stopping the Operating System Service

To stop the AggreGate Server if it is running in service mode:

  • Under Windows, go to Start Menu > Control Panel > Administration > Services, find AggreGate Server service, right-click on it and select Stop.

  • Under Linux, open a console and type:

    • service %LS_BINARY%_service stop if the server was started via service %LS_BINARY%_service start command

    • initctl stop ag_server if the server was started via initctl start ag_server command

Using Net Admin

Access the Net Admin interface via telnet to port 6440, and use it to shut the server down (S command) or restart it (R command).

Manually Kill the Processes

This method is not recommended, as it might kill other Java processes running on the host. It should be used only if the server is not responding to all other shutdown attempts.

Under Windows, the processes to kill are ag_server.exe, %LS_BINARY%_service.exe, %LS_BINARY%_console.exe. Kill all instances of these processes using the Task Manager (Ctrl+Shift+Esc under Windows).

Under Unix, the processes to kill are ag_server, %LS_BINARY%_service, %LS_BINARY%_console and java. There are many Java processes active at any one time. Kill the process with the lowest PID (Process ID). This is important. Killing another process will not resolve the problem.

There are specific instances where one should kill another process than the one with the lowest PID, but these are special cases, which depend on specific server configurations. Killing the process with the lowest PID will most likely resolve this situation.

Was this page helpful?