System Services Commands

connectorctl systemservice service-manager

To restart or view the status of the Service Manager service, use the connectorctl systemservice service-manager command. To enable debug logs, use the -l keyword. 

connectorctl systemservice service-manager -r [ -l debug-level [ -d debug-period-in-minutes ] ]

connectorctl systemservice service-manager -s

Syntax Description

Keywords and Variables

Description

-s

Shows the running status of the service manager

-r

Restarts the service manager service.

-l debug-level

Restarts the service manager service and configures debugging at the specified debug-level. The values are DEBUG, INFO, and WARNING.

  • If debug-level is unspecified, the default value is DEBUG.

Note

 

Running the service at DEBUG log level could significantly impact performance

-d debug-period-in-minutes

(Optional) Specify the debug period in minutes. If unspecified, the default value is ten minutes.

  • If -l is unspecified, the service manager service is restarted but debugging is not logged.

Command History

Release 3

This command is introduced.

Examples

The following example shows how to view the running status of the service manager service. 
[spacesadmin@connector ~]$ connectorctl systemservice service-manager -s
Executing command:systemservice
Command execution status:Succescs
-----------------------
Service Manager is running with version:3.0.1.41(9m 47s)
The following example shows how to restart the service manager service at a specified debug level. 
[spacesadmin@connector ~]$ connectorctl systemservice service-manager -r [-l DEBUG -d 1]
Executing command:systemservice
Command execution status:Success
-----------------------
Scheduled Service Manager restart. It will take few minutes

connectorctl systemservice service-agent

To restart or view the status of the service agent service, use the connectorctl systemservice service-agent command. To enable debug logs, use the -l keyword. 

connectorctl systemservice service-agent -r [ -l debug-level [ -d debug-period-in-minutes ] ]

connectorctl systemservice service-agent -s

Syntax Description

Keywords and Variables

Description

-s

Shows the running status of the service agent service.

-r

Restarts the service agent service.

-l debug-level

Restarts service agent service and configure debugging at the specified debug-level. The values are DEBUG, INFO, and WARNING.

  • If debug-level is unspecified, the default value is DEBUG.

Note

 

Running the service at DEBUG log level would significantly impact performance

-d debug-period-in-minutes

(Optional) Debug period in minutes. If unspecified, the default value is 10 minutes.

  • If -l is unspecified, the service agent service is restarted but debugging is not logged.

Command History

Release 3

This command is introduced.

Examples

The following example shows how to see the running status of the service:
[spacesadmin@connector ~]$ connectorctl systemservice service-agent -s
Executing command:systemservice
Command execution status:Success
-----------------------
=================service-agent status=================
service-agent.service - service agent starting script
   Loaded: loaded (/etc/systemd/system/service-agent.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2022-07-28 12:20:55 PDT; 1 months 9 days ago
 Main PID: 859 (run_service_age)
    Tasks: 7 (limit: 24285)
   Memory: 118.7M
   CGroup: /system.slice/service-agent.service
           ├─859 /bin/bash /opt/dnaspaces-connector/static/service-agent/run_service_agent.sh
           └─902 python3.9 src/application.py

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
=========================end===========================
The following example shows how to restart the service at a specified debug level:
[spacesadmin@connector ~]$ connectorctl systemservice service-agent -r [-l DEBUG -d 1]
Executing command:systemservice
Command execution status:Success
-----------------------
Restarted service-agent service

connectorctl systemservice docker

To restart or view the status of the docker service, use the connectorctl systemservice docker command.

connectorctl systemservice docker { -s | -r }

Syntax Description

Keywords and Variables Description

-s

Shows the status of the docker service.

-r

Restarts the docker service

Command History

Release 3

This command is introduced.

Examples

The following example shows how to view the status of the docker service. 
[spacesadmin@connector ~]$ connectorctl systemservice docker -s
Executing command:systemservice
Command execution status:Success
-----------------------
=================docker status=================
 docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2022-07-28 12:21:19 PDT; 1 months 9 days ago
     Docs: https://docs.docker.com
 Main PID: 1180 (dockerd)
    Tasks: 10
   Memory: 186.6M
   CGroup: /system.slice/docker.service
           └─1180 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

Sep 06 01:36:29 conn3-la61-212-23 dockerd[1180]: time="2022-09-06T01:36:29.281017425-07:00" level=info msg="ignoring event" container=19f30610cb760c8d73abb6d6119a3d9f479334cf1d914242b75cbd2a54590018 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Sep 06 01:36:34 conn3-la61-212-23 dockerd[1180]: time="2022-09-06T01:36:34.512812745-07:00" level=info msg="Firewalld: interface docker0 already part of docker zone, returning"
Sep 06 01:36:34 conn3-la61-212-23 dockerd[1180]: time="2022-09-06T01:36:34.669396274-07:00" level=info msg="Firewalld: interface br-77efcfe528f1 already part of docker zone, returning"
Sep 06 01:36:34 conn3-la61-212-23 dockerd[1180]: time="2022-09-06T01:36:34.808767362-07:00" level=info msg="Firewalld: interface docker0 already part of docker zone, returning"
Sep 06 01:36:34 conn3-la61-212-23 dockerd[1180]: time="2022-09-06T01:36:34.840664442-07:00" level=info msg="Firewalld: interface docker0 already part of docker zone, returning"
Sep 06 01:47:06 conn3-la61-212-23 dockerd[1180]: time="2022-09-06T01:47:06.126501950-07:00" level=info msg="ignoring event" container=7bbcc6bc2cb33623f05d57768a4a1bba08b40cad282eddbeb53c8c6dec6157a9 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Sep 06 01:47:11 conn3-la61-212-23 dockerd[1180]: time="2022-09-06T01:47:11.264882240-07:00" level=info msg="Firewalld: interface docker0 already part of docker zone, returning"
Sep 06 01:47:11 conn3-la61-212-23 dockerd[1180]: time="2022-09-06T01:47:11.424043921-07:00" level=info msg="Firewalld: interface br-77efcfe528f1 already part of docker zone, returning"
Sep 06 01:47:11 conn3-la61-212-23 dockerd[1180]: time="2022-09-06T01:47:11.562900640-07:00" level=info msg="Firewalld: interface docker0 already part of docker zone, returning"
Sep 06 01:47:11 conn3-la61-212-23 dockerd[1180]: time="2022-09-06T01:47:11.596127048-07:00" level=info msg="Firewalld: interface docker0 already part of docker zone, returning"
=========================end===========================

The following example shows how to restart the docker service. 

[spacesadmin@connector ~]$ connectorctl systemservice docker -r
Executing command:systemservice
Command execution status:Success
-----------------------
Restarted docker service