Skip to main content
Version: 5.3

Restarting Other Smart Monitor Components

After successfully restarting OpenSearch nodes, it's necessary to restart all related components:

  • OpenSearch Dashboards

  • Logstash

  • Smart Beat Manager

  • Smart Beat

This ensures updated configurations (such as new certificates) are applied and maintains proper communication between services and the OpenSearch cluster.

Restarting OpenSearch Dashboards​

  1. Stop OpenSearch Dashboards:
systemctl stop opensearch-dashboards
  1. Start OpenSearch Dashboards:
systemctl start opensearch-dashboards
  1. Verify connection to OpenSearch

Restarting Logstash​

  1. Stop Logstash:
systemctl stop logstash
  1. Start Logstash:
systemctl start logstash
  1. Check logs for errors:
tail -f /app/logs/logstash/logstash-plain.log

Restarting Smart Beat Manager​

  1. Stop Smart Beat Manager:
systemctl stop smartBeatManager
  1. Start Smart Beat Manager:
systemctl start smartBeatManager
  1. Check logs for errors:
tail -f ${SBM_HOME}/logs/smartBeatManagerLog_*.log

Restarting Smart Beat​

On Unix systems

  1. Stop Smart Beat:
systemctl stop smartBeat
  1. Start Smart Beat:
systemctl start smartBeat
  1. Check logs for errors:
tail -f ${SB_HOME}/logs/smartbeat/smartBeat.log

For Windows Systems

  1. Stop Smart Beat:
net stop smartBeat
  1. Start Smart Beat:
net start smartBeat
  1. Check logs for errors:
${SB_HOME}/logs/smartbeat/smartBeat.log