Skip to content

Start Services

Before you start

Goal

  • Bring up the hub
  • Connect to the website

Prerequisites

  • Complete the initial install.
  • Complete the licensing.
  • Complete the Database Config.
  • Complete the Object store config.
  • Complete the bootstrap.
  • Verify the ingress address.
  • Altair SLC Hub configuration privileges for the host.

Start and enable services

The installation process installs the software and installs systemd unit files to the /usr/lib/systemd/system directory.

The installation process installs the software as Windows services.

The installation process does not start or enable the Altair SLC Hub services, these need to be started manually using hubctl. The hubctl interface enables control of the various services that make up the Altair SLC Hub software.

To start the Altair SLC Hub services:

hubctl service start

To check that the services are running, use the following command:

hubctl service status

This command produces a table of all of the services and whether they are active (the service is running) and enabled (the service starts automatically on machine boot).

To configure the Altair SLC Hub services to start automatically on boot, use the following command:

hubctl service enable

Verification

Verify Ingress

Verify Ingress

  • run hubctl verify ingress command

To check that the portal is connectable from the local machine, run the command 

hubctl verify ingress

Connect to the Altair SLC Hub Portal

Verify Portal is up

  • connect to the website

To verify that the installation was successful and that Altair SLC Hub is running, use a supported web browser and navigate to the Altair SLC Hub address defined. This URL can be retrieved using the command

hubctl config print ingress.url

For example, navigate to http://machine.domain.local:9090

Verify that it is possible to log on to the Altair SLC Hub portal as the Hub Administrator user. To do this, in the log on screen enter the HubAdministrator user name and default password changeit. If successful, we recommend changing the password associated with the Hub Administrator user.