Reboot Pulse Server and Agents
The following section contains procedures for shutting down and restarting the Pulse server and agent when scheduled maintenance is required:
Rebooting Pulse Server
- Stop the admon self monitoring service (if enabled).
systemctl stop admon && systemctl status -l admon- Run the following command to know the current running services.
accelo info- Stop and remove all the running containers.
docker stop $(docker ps -aq) && docker rm $(docker ps -aq)- Stop the Docker service and verify its status.
systemctl stop docker && systemctl status -l docker- Continue with the scheduled maintenance.
Once the server is back online, perform the following steps to restart the Docker service.
systemctl start docker && systemctl status -l docker- Deploy the core and addons components.
x
# Deploy core servicesaccelo deploy core# Get earlier running components from 2nd command accelo infoaccelo deploy addons- Restart the admon service.
systemctl start admon && systemctl status -l admonThe Pulse server has now completed a restart.
To reboot the Pulse agents follow the steps:
- Stop all the agents by executing the following command.
systemctl stop pulsenode && systemctl stop pulselogs && systemctl stop pulsejmx- Check status with a single command.
systemctl status pulsenode && systemctl status pulselogs && systemctl status pulsejmx- Start all agents with a single command
systemctl start pulsenode && systemctl start pulselogs && systemctl start pulsejmxRebooting Pulse Legacy Agent
Legacy Agent are for Pulse v1.8 or older.
To reboot the Pulse agents follow the steps:
- Stop all the agents with a single command mentioned.
systemctl stop telegraf && systemctl stop filebeat && systemctl stop jmxtrans- Check status with single command
systemctl status telegraf && systemctl status filebeat && systemctl status jmxtrans- Start all agents with single command
systemctl start telegraf && systemctl start filebeat && systemctl start jmxtransThe restart of Pulse agents is now complete.
Was this page helpful?