Test: Enabling/Disabling the monitoring interface

[jennifer-richards]

Enabling / Disabling Monitoring Interface

Steps

1. Install a trust router and at least a minimal working configuration and logging.console_threshold set to info or lower.
2. If present, remove the monitoing section from the internal config
3. Run the trust router on the console (sudo -u trustrouter trust_router -c <path_to_config>
4. After the trust router starts up, stop it and examine its output

Expected results

• [x] There should be a message tr_mons_event_init: monitoring is disabled, not enabling events or opening sockets after the messages indicating that ports were opened for TIDS and TRPS

Steps

1. Add a monitoring section to the internal configuration, specifying a port to listen on (e.g., 12310) and at least one credential.
2. Set enabled to false.
3. Run the trust router on the console
4. Try connecting using trmon to the specified port with the authorized credential.
5. Stop the trust router and examine the output

Expected results

• [x] The same message about monitoring being disabled should appear
• [x] The trmon connection should be refused

Steps

1. Set enabled to true and start the trust router
2. Use trmon <host> <port> show uptime using the configured port and credential
3. Stop the trust router
4. Remove the enabled key entirely and start the trust router
5. Execute the trmon command again
6. Stop the trust router

Expected results

• [x] The trust router output should indicate that the monitoring port was opened
• [x] Both trmon commands should succeed and return the uptime in seconds

[meadmaker]

This test is blocked by #95.

[meadmaker]

Passed!