Top
ServerView Resource Orchestrator Cloud Edition V3.0.0 Setup Guide
Chapter 7 Logging in to Resource Orchestrator > 7.2 Starting and Stopping the Manager
PreviousNext

7.2 Starting and Stopping the Manager

The Resource Orchestrator manager starts automatically on the admin server.
This section explains how to manually start or stop the manager and how to check its running state.

[Windows]
The manager is made up of the following two groups of Windows services:

From the Windows Control Panel, open "Administrative Tools". Then, open the [Services] window to check the state of each service.

Services are started and stopped using the rcxmgrctl command (start and stop subcommands).

As this command collectively controls both manager and related services, use the command to start and stop services.

For details on the rcxadm network command, refer to "1.7.17 rcxmgrctl" in the "Reference Guide (Resource Management) CE".

To start or stop a manager in a clustered configuration, right-click the manager application shown under the failover cluster manager tree, and select either [Bring this service or application online] or [Take this service or application offline].

[Linux]
The manager is made up of the following two groups of Linux services:

The status of each of those services can be confirmed from the service command, as shown below.

# service rcvmr status <RETURN>
# service scwdepsvd status <RETURN>
# service scwpxesvd status <RETURN>
# service scwtftpd status <RETURN>

Services are started and stopped using the rcxmgrctl command (start and stop subcommands).

As this command collectively controls both manager and related services, use the command to start and stop services.

For details on the rcxadm network command, refer to "1.7.17 rcxmgrctl" in the "Reference Guide (Resource Management) CE".

To start or stop a manager in a clustered configuration, use the cluster administration view (Cluster Admin).

For details, refer to the PRIMECLUSTER manual.

Note

  • When using ServerView Deployment Manager on an admin LAN, all services related to Resource Orchestrator will be automatically disabled. To prevent conflicts with ServerView Deployment Manager, do not start these services in order. For details, refer to "Appendix L Co-Existence with ServerView Deployment Manager".

  • Resource Orchestrator cannot operate if any of the manager services are stopped. Ensure that all services are running when Resource Orchestrator is running.

  • If the manager is unable to communicate on the admin LAN when started up (because of LAN cable disconnections or any other causes), PXE Services may not start automatically. If PXE Services are stopped, investigate the network interface used for the admin LAN and confirm whether it can communicate with other nodes on the admin LAN.

    If the manager cannot communicate with admin LAN nodes, restore the admin LAN itself and restart the manager.

  • If the manager fails to start, check if the admin server has multiple IP addresses. If it has, refer to "2.1.4 Setup" in the "Installation Guide CE", and perform the procedure of the note "When configuring an environment on the admin server with multiple IP addresses, use the following procedure before initiating setup.".

  • In Basic mode, the following manager services are started.

    In Basic mode, the procedure to start and stop the services and the procedure to check their statuses are same as those in standard mode.

    [Windows]

    • Manager Services

      Resource Coordinator Manager
      Resource Coordinator Task Manager
      Resource Coordinator Web Server (Apache)
      Resource Coordinator Sub Web Server (Mongrel)
      Resource Coordinator Sub Web Server (Mongrel2)
      Resource Coordinator DB Server (PostgreSQL)

    [Linux]

    • Manager Services

      rcvmr

      Manager services also include the following daemons.

      rcxmanager
      rcxtaskmgr
      rcxmongrel1
      rcxmongrel2
      rcxhttpd

PreviousNext
Copyright FUJITSU LIMITED 2010-2012