9.1 Starting and Stopping OES Cluster Services

OES Cluster Services automatically starts after it is installed. It also automatically starts when you reboot your OES server.

IMPORTANT:If you are using iSCSI for shared disk system access, ensure that you have configured iSCSI initiators and targets to start prior to starting Cluster Services. You can do this by entering the following at the Linux terminal console:

systemctl enable iscsi.service

9.1.1 Starting OES Cluster Services

If you stop OES Cluster Services, you can restart it by doing the following:

  1. Open a terminal console, then log in as the root user.

  2. To start Cluster Services, at the command prompt, enter

    rcnovell-ncs start

    Or

    systemctl start novell-ncs.service
  3. To verify the cluster service status, at the command prompt, enter

    rcnovell-ncs status

    Or

    systemctl status novell-ncs.service
  4. Verify the cluster status:

    cluster status

9.1.2 Stopping OES Cluster Services

OES Cluster Services is a kernel-space application. As with any kernel-space application, unloading it is a best effort and is not guaranteed to stop the modules. If Cluster Services is busy providing services from the kernel when you attempt to stop it, the process might not stop, and a reboot might be required.

  1. Open a terminal console, then log in as the root user.

  2. Check whether the node is active in the cluster. Enter

    cluster view

    If the node is in the cluster (and not still in a process of joining the cluster), it is relatively safe to attempt to stop it.

  3. To stop Cluster Services, at the command prompt, enter

    rcnovell-ncs stop

    or

    systemctl stop novell-ncs.service
  4. To verify the cluster service status, at the command prompt, enter

    rcnovell-ncs status

    Or

    systemctl status novell-ncs.service
  5. If you get in a state where the node has not joined the cluster and Cluster Services cannot be stopped:

    1. Disable autostart on reboot. Enter

      systemctl disable novell-ncs.service
    2. Reboot the server.

    3. Start Cluster Services manually. Enter

      rcnovell-ncs start

      or

      systemctl start novell-ncs.service
    4. Diagnose why the node had trouble joining the cluster.

    5. (Optional) Re-enable autostart for the node. Enter

      systemctl enable novell-ncs.service

9.1.3 Enabling and Disabling the Automatic Start of OES Cluster Services

OES Cluster Services automatically starts by default after it is installed and on server reboot.

To cause OES Cluster Services to not start automatically after a server reboot:

  1. Open a terminal console, then log in as the root user.

  2. Enter the following at a Linux terminal console:

    systemctl disable novell-ncs.service
  3. Reboot the server.

  4. After rebooting, you must manually start Cluster Services by entering

    rcnovell-ncs start

    or

    systemctl start novell-ncs.service

To cause OES Cluster Services to resume starting automatically after a server reboot:

  1. Open a terminal console, then log in as the root user.

  2. Enter the following at a Linux terminal console:

    systemctl enable novell-ncs.service 
  3. Reboot the server.