-
Notifications
You must be signed in to change notification settings - Fork 0
Role NUT Client
Osotechie edited this page Jun 22, 2026
·
2 revisions
Configures Network UPS Tools (NUT) in client mode to monitor the UPS via a NUT server running elsewhere on the network.
- Installs
nut-client - Configures
/etc/nut/nut.confwithMODE=netclient - Configures
/etc/nut/upsmon.confwith the UPS monitor line - Starts and enables the
nut-clientservice
flowchart LR
UPS[UPS] --> Server[NUT Server<br/>10.1.1.3<br/>primary/master]
Server --> Client[NUT Client<br/>NAS<br/>secondary/slave]
The NAS runs as a secondary NUT client. It monitors the UPS state via the primary NUT server (running on another device — in my case, the Proxmox server connected to the UPS via USB). When the UPS signals low battery, the NAS can initiate a safe shutdown.
Key variables from group_vars:
| Variable | Default | Purpose |
|---|---|---|
nut_client_ups |
dynamix |
UPS name as defined on the NUT server |
nut_client_server |
10.1.1.3 |
IP of the NUT server |
nut_client_type |
secondary |
Client type (secondary = safe shutdown on low battery) |
nut_client_user |
(from KeyVault) | NUT authentication user |
nut_client_password |
(from KeyVault) | NUT authentication password |
Restarts the nut-client service when configuration files change.
Overview
Secrets & Networking
Ansible
- Ansible Structure
- Role: Docker
- Role: Storage
- Role: Samba
- Role: NUT Client
- Role: Backup
- Role: Coral TPU
Pipelines
Operations