Working with Services
You can manually start and stop appliance services.
To view all appliance services and their statuses, login to the CLI Manager, navigate to Administration > Services.
Use caution before stopping or restarting a particular service. Make sure that no important actions are being performed by other users using the service that must be stopped or restarted.
Some services, such as, LDAP Proxy auth, member source services, and so on, are available after they have been successfully configured on ESA.
In the Services dialog box, you can start, stop, or restart the following services:
Table 1. Appliance Services
| Services | ESA | DSG |
| OS | ✓ | ✓ |
| Web UI, Secure Shell (SSH), Firewall, Real-time Graphs, SNMP Service, NTP Service, Cluster Status, Appliance Heartbeat* Server, Appliance Heartbeat* Client, Log Filter Server, Messaging System, Appliance Queues Backend, Docker, Rsyslog Service | ||
| LDAP | ✓ | ✓ |
| LDAP Server, Name Service Cache Daemon | ||
| Web Services Engine | ✓ | ✓ |
| Web Services Engine | ||
| Service Dispatcher | ✓ | ✓ |
| Service Dispatcher | ||
| Logging | ✓ | |
| Management Server, Management Server Database, Reports Repository, Reporting Engine | ||
| Policy Management | ✓ | |
Policy Repository, HubController, PIM Cluster, Soft HSM
Gateway, Key Management Gateway, Member Source Service,
Meteringfacade, DevOps, Logfacade For more information about
the Meteringfacade and Logfacade services, refer to the section
Services. | ||
| Reporting Server | ✓ | |
| Reports repository and reporting engine | ||
| Distributed Filesystem File Protector | ✓ | |
DFS Cache Refresh | ||
| ETL Toolkit | ||
| ETL Server | ||
| Cloud Gateway | ✓ | |
| Cloud Gateway Cluster | ||
| td-agent | ✓ | ✓ |
| td-agent | ||
| Audit Store | ✓ | |
| Audit Store Repository | ||
| Audit Store Management | ||
| Analytics | ✓ | |
| Analytics, Audit Store Dashboards | ||
| RPS | ✓ |
* Heartbeat services are used to discover other appliance nodes present in the network. When Set operations, such as, set ESA communication or TAC are performed, then the available list of nodes are displayed due to this service. If these services are stopped, the available nodes are not visible while performing the above operations. However, the the IP address can be entered manually.For the appliance-heartbeat-server a fixed port is not required. This is because this service is not listening for an incoming message.Appliance-heartbeat-client allows listening the incoming messages and hence needs a fixed port, i.e., 10100.
You can change the status of any service when you select it from the list and choose Select. In the screen that follows the Service Management screen, select stop, start, or restart a service, as required.
When you apply any action on a particular service, the status message appears with the action applied. Press ENTER again to continue.
You can also use the Web UI to start or stop services. In the Web UI Services, you have additional options for stopping/starting services, such as Enable/Disable Auto-start for most of the services.
Important: Although the services can be started or stopped from the Web UI, the start/stop/restart action is restricted for some services, such as, networking, td-agent, docker, exim4, and so on. These services can be operated from the OS Console. Run the following command to start/stop/restart a service.
/etc/init.d/<service_name> stop/start/restart
For example, to start the docker service, run the following command.
/etc/init.d/docker start