Skip to main content
Version: 5.1

Restarting Other Search Anywhere Framework Components

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

  • OpenSearch Dashboards

  • Logstash

  • SAF Beat Manager

  • SAF 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 SAF Beat Manager​

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

Restarting SAF Beat​

On Unix systems

  1. Stop SAF Beat:
systemctl stop SAFBeat
  1. Start SAF Beat:
systemctl start SAFBeat
  1. Check logs for errors:
tail -f ${SB_HOME}/logs/SAFbeat/SAFBeat.log

For Windows Systems

  1. Stop SAF Beat:
net stop SAFBeat
  1. Start SAF Beat:
net start SAFBeat
  1. Check logs for errors:
${SB_HOME}/logs/SAFbeat/SAFBeat.log