5. Run the DMS3 Components

With all the DMS³ components properly configured and redistributed across various server and client devices, it's now possible to run DMS³.

5a. Run DMS³ Components as Executables

Run the DMS³Server Component

On the server, run DMS³Server by typing dms3server. The component should now be started, and if configured correctly, generating logging information either to the display or to a log file.

An example of DMS³Server logging output is displayed below:

INFO: 2022/01/25 19:27:11 lib_log.go:81: dms3server started
 INFO: 2022/01/25 19:27:11 lib_log.go:81: server started
 INFO: 2022/01/25 19:27:39 lib_log.go:81: OPEN connection from: 10.10.10.183:52624
 INFO: 2022/01/25 19:27:39 lib_log.go:81: Sent dashboard enable state as: 0
 INFO: 2022/01/25 19:27:41 lib_log.go:81: /usr/sbin/ip command: no device mac address found
 INFO: 2022/01/25 19:27:41 lib_log.go:81: Sent motion detector state as: 1
 INFO: 2022/01/25 19:27:41 lib_log.go:81: CLOSE connection from: 10.10.10.183:52624
 INFO: 2022/01/25 19:27:49 lib_log.go:81: OPEN connection from: 10.10.10.183:52626
 INFO: 2022/01/25 19:27:49 lib_log.go:81: Sent dashboard enable state as: 1
 INFO: 2022/01/25 19:27:50 lib_log.go:81: /usr/sbin/ip command: no device mac address found
 INFO: 2022/01/25 19:27:50 lib_log.go:81: Sent motion detector state as: 1
 INFO: 2022/01/25 19:27:50 lib_log.go:81: CLOSE connection from: 10.10.10.183:52626

In this example, logging is set to the INFO level and is reporting that DMS³Server is sending out to all participating DMS³Client components an initial motion detector state of 0 (disabled). Shortly thereafter, and after not detecting the presence of a user proxy (e.g., the end user's smartphone MAC address), the motion detector state is set to 1 (enabled).

Run the DMS³Client Component

On each of the smart clients, run DMS³Client by typing dms3client. The component should now be started, and if configured correctly, generating logging information either to the display or to a log file.

An example of DMS³Client logging output is displayed below:

INFO: 2022/01/25 19:28:24 lib_log.go:81: dms3client started
 DEBUG: 2022/01/25 19:28:24 lib_log.go:90: dms3client.configDashboardClientMetrics
 DEBUG: 2022/01/25 19:28:24 lib_log.go:90: dms3dashboard.InitDashboardClient
 DEBUG: 2022/01/25 19:28:24 lib_log.go:90: dms3dashboard.(*DeviceMetrics).checkImagesFolder
 DEBUG: 2022/01/25 19:28:24 lib_log.go:90: dms3client.startClient
 INFO: 2022/01/25 19:28:24 lib_log.go:81: OPEN connection from: 10.10.10.183:49300
 DEBUG: 2022/01/25 19:28:24 lib_log.go:90: dms3client.processClientRequest
 DEBUG: 2022/01/25 19:28:24 lib_log.go:90: dms3dashboard.ReceiveDashboardRequest
 DEBUG: 2022/01/25 19:28:24 lib_log.go:90: dms3dashboard.receiveDashboardEnableState
 INFO: 2022/01/25 19:28:24 lib_log.go:81: Received dashboard enable state as: 1
 DEBUG: 2022/01/25 19:28:24 lib_log.go:90: dms3dashboard.sendDashboardData
 INFO: 2022/01/25 19:28:24 lib_log.go:81: Sent client dashboard data
 DEBUG: 2022/01/25 19:28:24 lib_log.go:90: dms3client.receiveMotionDetectorState
 DEBUG: 2022/01/25 19:28:24 lib_log.go:90: dms3client.ProcessMotionDetectorState
 INFO: 2022/01/25 19:28:24 lib_log.go:81: Process not found when running '/usr/bin/pgrep -i motion'
 INFO: 2022/01/25 19:28:24 lib_log.go:81: Received motion detector state as: 0
 INFO: 2022/01/25 19:28:24 lib_log.go:81: CLOSE connection from: 10.10.10.183:49300

In this example, logging is set to the DEBUG level and is reporting that DMS³Client is receiving from the DMS³Server component a motion detector state of 0 (disabled).

5b. Optional: Run DMS³ Components as Services

Running either the DMS³Client or DMS³Server components as services (daemons) is preferred, as these services can be configured to run in the background at machine startup, recover from failures, etc.

As different Unix-like systems use different approaches for system service management and startup, service configuration is beyond the scope of the install procedure. However, the DMS³ project does include sample systemd unit files for both the DMS³Client and the DMS³Server components called dms3client.service, and dms3client.service, respectively, and are located in the dms3_release folder at dms3_release/dms3client and dms3_release/dms3server.

5c. Optional: View the DMS³Dashboard Component

By default (as configured in dms3dashboard.toml), the DMS³Dashboard component is enabled and configured to run locally with the DMS³Server component on port 8081. To view the DMS³Dashboard in a web browser, go to localhost:8081.

Note that the DMS³Server component must be running in order to view the DMS³Dashboard.