Table of Contents
| Table of Contents | ||||
|---|---|---|---|---|
|
Introduction
Squirro consists of several services that are started and stopped individually. The Overview section talks a bit about those components. A detailed list of the services is available below.
When a Squirro server is started, all the services are started automatically using the Linux initd subsystem.
Interacting with services
Services are controlled with the service command on the Linux console. The service command must be run as root. This can be achieved by either becoming root first (using sudo -i) or by prefixing every service command with the sudo command.
The first argument for the command is the service name to interact with, then the operation to execute.
Check service status
The service status is returned with the status sub-command. For example:
| Code Block | ||
|---|---|---|
| ||
[root@localhost ~]# service sqtopicd status
sqtopicd (pid 3164) is running... |
Start service
If a service is not running, the start sub-command can be used to launch it.
| Code Block | ||
|---|---|---|
| ||
[root@localhost ~]# service sqtopicd start
Starting sqtopicd: [ OK ] |
Stop service
| Code Block | ||
|---|---|---|
| ||
[root@localhost ~]# service sqtopicd stop
Stopping sqtopicd: [ OK ] |
If you now execute the status sub-command, it will report the service as being stopped.
| Code Block | ||
|---|---|---|
| ||
[root@localhost ~]# service sqtopicd status
sqtopicd is stopped |
Restart service
The restart sub-command attempts to stop a service first and will then start it again.
| Code Block | ||
|---|---|---|
| ||
[root@localhost ~]# service sqtopicd restart
Stopping sqtopicd: [ OK ]
Starting sqtopicd: [ OK ] |
Services
The following services form part of Squirro or are built-in services that Squirro uses. They can all be controlled with the service command as shown in the previous section.
...
Manages data loading process. See Data Loading and Processing manual.
...
This page can now be found at Services on the Squirro Docs site.