Install Using CLI: Linux/Mac OS

Perform an interactive or silent installation of the Seeker Enterprise Server on a Linux or Mac OS machine using the command line interface (CLI).

Start

Important: Make sure you are not logged in as a root user.

To install, run the downloaded seeker-server-<OS>-<VERSION>.sh in a CLI of the target operating system, substituting OS by linux64 or linux-arm64 or macos, and VERSION by the actual Seeker version. For example: seeker-server-linux64-2024.10.0.sh

Interactive installation

You are prompted to:
  1. Select an installation type: Trial/Evaluation or Deployment/Production.
  2. Review and accept the license agreement.
  3. For Linux only, select a deployment option: Standard or Kubernetes.
    Note:

    If you have chosen the Kubernetes option, the Seeker Docker deployment package will be downloaded and extracted into your current folder. To continue, follow the instructions in Deploy Seeker Server on Kubernetes.

    If you have chosen the Standard option, perform the steps below.

  4. Select the database installation type: Seeker-managed database: Default. Seeker's own fully managed PostgreSQL instance or User-managed database: A PostgreSQL 10.10 instance fully managed by the user. In the latter case, enter the database connection properties.
    Important:

    If you want Seeker to use your own fully-managed PostgreSQL database instance, make sure to comply with PostgreSQL Database Requirements.

  5. Enter the installation folder and port numbers.
sh ./seeker-server-<OS>-<VERSION>.sh

Silent installation

You can run a silent installation by running the script with preset argument values. To install with a Seeker-managed database, run the following command, substituting the actual values:

sh ./seeker-server-<OS>-<VERSION>.sh accept-license=agree install-dir=/home/<user_name>/seeker server-http-port=8080 server-https-port=8443
If you are going to install Seeker with a user-managed PostgreSQL database, set the following database-related arguments:
Name Description Sample value
external-database false (default) to use the Seeker-managed database, true to use an external database. true
database-host Hostname or IP of the server where the external database is deployed. 10.120.1.1
database-port TCP port that the external database is using. 5432
database-name External database name. seekerdb
database-user Username for database connection. seeker
database-password Password for database connection. my-password

For example:

sh ./seeker-server-linux64-2024.10.0.sh accept-license=agree install-dir=/home/user/seeker server-http-port=8080 server-https-port=8443
external-database=true database-host=10.120.1.1 database-port=5432 database-name=seekerdb database-user=seeker database-password=test

Results

At the end of the installation, the following output appears:
Seeker configuration:
Seeker installation directory: /Users/<user_name>/seeker/install
Seeker home directory: /Users/<user_name>/seeker/data
Seeker database port: 5432
Seeker HTTP port: 8080
Seeker HTTPS port: 8443
Installation completed successfully.
Note: at this point, the Enterprise Server is installed, but NOT started.
To start the server, run: /Users/<user_name>/seeker/install/sk_ctl start
For other actions, run: /Users/<user_name>/seeker/install/sk_ctl status

SK_CTL exit codes

The sk_ctl script is used to start and stop Seeker, and obtain its status. The following list of exit codes can be handy when creating automated workflows using this script.

  • 0 - success.
  • 1 - general error.
  • 150 - server is down.
  • 151 - sensor is down.
  • 152 - nginx is down.
  • 153 - database is down.