Reboot Pulse Server and Agent

This page describes how to reboot and restart the Pulse Server and Agent during scheduled maintenance or when a reboot is required to apply configuration changes.

Rebooting Pulse Server

1. Stop the admon self-monitoring service (if enabled).

systemctl stop admon && systemctl status -l admon

1. Run the following command to know the current running services.

accelo info

1. Stop and remove all the running containers.

docker stop $(docker ps -aq) && docker rm $(docker ps -aq)

1. Stop the Docker service and verify its status.

systemctl stop docker && systemctl status -l docker

1. 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

1. Deploy the core and addons components.

# Deploy core services
accelo deploy core
# Get earlier running components from 2nd command accelo info
accelo deploy addons

1. Restart the admon service.

systemctl start admon && systemctl status -l admon
The Pulse server has now completed a restart.
To reboot the Pulse agents follow the steps:

1. Stop all the agents by executing the following command.

systemctl stop pulsenode && systemctl stop pulselogs && systemctl stop pulsejmx

1. Check status with a single command.

systemctl status pulsenode && systemctl status pulselogs && systemctl status pulsejmx

1. Start all agents with a single command

systemctl start pulsenode && systemctl start pulselogs && systemctl start pulsejmx

Rebooting Pulse Legacy Agent

systemctl stop telegraf && systemctl stop filebeat && systemctl stop jmxtrans

1. Check status with a single command

systemctl status telegraf && systemctl status filebeat && systemctl status jmxtrans

1. Start all agents with a single command

systemctl start telegraf && systemctl start filebeat && systemctl start jmxtrans
The restart of Pulse agents is now complete.