Managing Kinetica Services

Typical maintenance of the system may require starting & stopping of database services. The instructions for that are provided here:

• Start Database Services
• Stop Database Services

During a Kinetica system upgrade or other major system administration event, all Kinetica services may need to be started & stopped. The instructions for that are provided here:

• Start System Management Processes
• Stop System Management Processes

A variety of service status checks are available for assessing the health of the system and troubleshooting.

Start Database Services

The following database services can be started via GAdmin or command-line:

• Database
  • httpd
  • ODBC Server
  • Text Search
• Reveal

GUI Startup

1. Log in to GAdmin
2. Click Admin on the left menu
3. Click Start
4. On the Start Service? pop-up, click Start
5. Click Continue when the database has started

Command-Line Startup

Run the following as the root user:

service gpudb start

Note

This will, in turn, start system management processes, as well

Verify that Kinetica is running by browsing to http://<yourhostname>:8080/gadmin

Stop Database Services

The following database services can be stopped via GAdmin or command-line:

• Reveal
• Database
  • httpd
  • ODBC Server
  • Text Search

GUI Stop

1. Log in to GAdmin
2. Click Admin on the left menu
3. Click Stop
4. On the Stop Service? pop-up, click Stop
5. Click Continue when the database has stopped

Command-Line Stop

Run the following as the root user:

service gpudb stop

Start System Management Processes

To start all system management processes:

• Host Manager
• GAdmin
• Stats Services

Run the following as the root user:

service gpudb_host_manager start

Stop System Management Processes

To stop database services and all system management processes:

• GAdmin
• Stats Services
• Host Manager

Run the following as the root user:

service gpudb_host_manager stop

Note

This will, in turn, stop database services, as well

Managing Individual Components

The /opt/gpudb/core/bin/gpudb script has several options available to assist in managing the individual Kinetica components.

Important

The /opt/gpudb/core/bin/gpudb script should always be run as the gpudb user

Options:

Option	Description
<component>-start	Starts the given component if it's not currently running
<component>-stop	Stop the given component if it's not stopped
<component>-restart	Stop the given component if it's not stopped then start it
<component>-status	Prints status information, including the process IDs it is using
<component>-pids	Prints the process IDs the component is using
<component>-enabled	Returns 1 is the component is enabled and 0 otherwise. Used internally by the gpudb script
<component>-installed	Returns 1 is the component is enabled and 0 otherwise. Used internally by the gpudb script

Available components:

• host-manager
• gpudb
• reveal
• httpd
• odbc
• stats
• text-search
• tomcat (GAdmin web server)

For example, restarting the stats server:

/opt/gpudb/core/bin/gpudb stats-restart

Note

• If external_text_search = true in the /opt/gpudb/core/etc/gpudb.conf file, then the text search server can be managed using the options below. If external_text_search = false, then the text search server will not be able to be managed individually.
• The Host Manager service manages the HTTPD and ODBC components. It's possible to stop these components, but Host Manager will restart them immediately. Stopping Host Manager and attempting to start these components individually will not work.

System Status Checks

There are several means to check the status of system components:

• Processes
• GAdmin
• API

Processes

To check the status of the database processes:

• Host Manager
• GAdmin
• Stats Services
• Database
  • httpd
  • ODBC Server
  • Text Search
• Reveal

Run the following as the root or gpudb user:

service gpudb status

GAdmin

The Kinetica Administration Application (GAdmin) provides a GUI for monitoring various aspects of the system:

• Cluster Health
• Running Jobs
• Information & Diagnostics

API

To determine whether the REST endpoint services are operating, the Python API can be invoked, as follows:

$ /opt/gpudb/bin/gpudb_python /opt/gpudb/kitools/gadmin_sim.py
**********************
Total tables:              0
Total top-level tables:    0
Total collections:         0
Total number of elements:  0
Total number of objects:   0

Statuses

The tables below list the various statuses you could experience in GAdmin or in logs for the system itself, the nodes and ranks employed by the system, or all three.

Important

It's likely you won't see many of the node and rank statuses in GAdmin as they are transient and only last for a few seconds during start up or shut down.

System

Status	Description
init	The INIT signal has been received and the system is initializing
rebalancing	The system is rebalancing data due to the addition/subtraction of ranks
running	The system is up and available for requests
shutdown	The system has shut down and is not available
starting	The system is in the process of starting up
stopped	The system has stopped all requests and is preparing for shutdown
system_limited	Something is interfering with the systems's ability to communicate between all ranks

Node

Status	Description
enum_hardware	The node is processing the hardware being used and checking the license
establishing_cluster	The node is ensuring its connection to the system and the other hosts in the cluster
fatal_init_error	An error occurred while validating the gpudb.conf configuration file
init	The INIT signal has been received and the node is initializing
parsed_conf	The node has parsed configuration files for any changes
post	The node has started and informed the system
ready	The node has successfully shutdown and is ready to be started
running	The node is up and available for requests
shutdown	The node has shut down and is not available
shutting_down	The node is in the process of shutting down and will not take requests
started	The node has been started and is nearly ready for requests
starting	The node is in the process of starting up
stopping	The node is stopping all requests and preparing for shutdown
validating_cluster	The node and any other nodes in the cluster are being validated by the system

Rank

Status	Description
enum_hardware	The rank is processing the hardware being used and checking the license
fatal_init_error	An error occurred while validating the gpudb.conf configuration file
init	The INIT signal has been received and the rank is initializing
initialized	The rank has been primed for start-up
loaded_data	The rank has successfully loaded data from the persist directory(ies)
loading_data	The rank is in the process of loading data from the persist directory(ies)
not_responding	The rank is currently not responding to requests
parsed_conf	The rank has parsed configuration files for any changes
post	The rank has started and informed the system
running	The rank is up and available for requests
shutdown	The rank has shut down and is not available
shutting_down	The rank is in the process of shutting down and will not take requests
start	The rank has received a start signal
started	The rank has been started and is nearly ready for requests
starting	The rank is in the process of starting up
syncing	The rank is in the process of syncing types, tables, records, etc.
terminated	The rank has encountered an error and was terminated; the rank will often restart if possible