zenigame-restart-worker

Restart Zenigame workers safely inside a systemd container by executing preflight checks, obtaining explicit user approval, and performing post-restart status verification and log inspection to ensure reliable operation.

Yes, you can restart individual Zenigame worker services like zenigame-worker-edinet or apply the restart to all services simultaneously, maintaining audit-friendly workflow and explicit approval for either scope.

The pre-restart supervision check validates system conditions and containment inside the container before restarting Zenigame workers, ensuring the environment is ready and preventing error-prone or risky production operations.

Yes, the workflow supports non-local execution and provides an audit-friendly process with explicit user approval, ensuring that Zenigame worker restarts are tracked and safely managed within the systemd container.

Verify Zenigame worker status and inspect logs after a restart by using the built-in post-restart status verification and error handling steps to confirm the workers are running correctly within the systemd container.

The best way to handle error-prone production restarts for Zenigame workers is to automate the process with preflight checks, explicit approval, and post-restart log inspection to ensure a safe and auditable operation.