Skip to content

Infrastructure service restart workflow

The Infrastructure service restart workflow outlines the standard operating procedures for restarting services within a managed IT environment, specifically detailing the steps for Linux-based systems and Windows-based systems^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md].

Linux Workflow

The Linux workflow follows a strict sequence of configuration updates, backup, service manipulation, and verification.^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md]

1. Configuration Update and Backup

Before restarting, the service configuration files must be updated and backed up. * Backup: Create a timestamped backup of the configuration file (e.g., zabbix_agentd.conf or tomcat.service) to prevent data loss during the modification^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md]. * Modification: Update the configuration settings using text editors or command-line utilities like sed^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md].

2. Service Control

Services managed by systemd are restarted using a specific set of commands.^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md] * Reload Daemon: If a unit file (such as a service definition) has been modified, run systemctl daemon-reload to notify systemd of the changes^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md]. * Enable/Disable: To ensure the service starts correctly on boot or to reset triggers, the service is typically disabled and then re-enabled^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md]. * Restart: Execute the restart command (e.g., systemctl restart zabbix-agent.service) to apply the changes^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md].

3. Verification

Following the restart, the operational status of the service must be verified^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md].

Windows Workflow

For Windows environments, the workflow relies on the net command to control services^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md].

  • Stop Service: Use net stop "[Service Name]" to halt the service^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md].
  • Start Service: Use net start "[Service Name]" to resume the service^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md].

Common services requiring this procedure include the "Zabbix Agent" and "Tomcat8"^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md].

Sources

^[600-developer__operation-maintenance__zabbix__zabbix-agentd.md]