
Como configurar um servidor Debian com um UPS USB independente para:
- Inicie o desligamento do UPS após um minuto quando a bateria estiver fraca.
- Desligar em si.
- E para ter certeza de que quando a energia elétrica for restaurada (mesmo antes de o UPS acabar) o servidor Debian será iniciado.
Essas etapas são descritas emessa questãomas não há explicação de como alcançá-los.
Eu tenho:
- Meu servidor configurado para sempre iniciar quando a energia for restaurada.
- Instalado
nut
e quando executoupsc myups
vejo as informações do no-break, incluindo o nível da bateria. Assim, posso escrever facilmente um script para monitorar a bateria e desligar o servidor.
Minha pergunta é:
Como enviar um comando de desligamento para o UPS?
O UPS é:EATON 5E 650i
Em /etc/nut/nut.conf
eu tenho:
MODE=standalone
Em /etc/nut/ups.conf
eu tenho:
[myups]
driver = usbhid-ups
port = auto
vendorid = 0463
pollfreq = 30
upsc myups
impressões:
Init SSL without certificate database
battery.charge: 100
battery.runtime: 1825
battery.type: PbAc
device.mfr: EATON
device.model: 5E 650i
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.parameter.vendorid: 0463
driver.version: 2.7.4
driver.version.data: MGE HID 1.39
driver.version.internal: 0.41
input.voltage: 230.0
outlet.1.status: on
outlet.desc: Main Outlet
outlet.id: 1
outlet.switchable: no
output.frequency: 49.9
output.frequency.nominal: 50
output.voltage: 230.0
output.voltage.nominal: 230
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: 03.08.0018
ups.load: 19
ups.mfr: EATON
ups.model: 5E 650i
ups.power.nominal: 650
ups.productid: ffff
ups.start.battery: yes
ups.status: OL
ups.timer.shutdown: -1
ups.vendorid: 0463
Responder1
OK, acho que está funcionando agora. Aqui está o que eu fiz:
apt-get install nut-server
apt-get install nut-client
nano /etc/nut/nut.conf
MODE=standalone
nano /etc/nut/ups.conf
[myups]
driver = usbhid-ups
port = auto
vendorid = 0463
pollfreq = 30
/sbin/upsdrvctl start
upsc myups
Imprime alguns problemas.
Reinício
/usr/sbin/shutdown -r now
Agora, ao executar, upsc myups
você deverá ver as informações do seu UPS:
Init SSL without certificate database
battery.charge: 86
battery.runtime: 956
battery.type: PbAc
device.mfr: EATON
device.model: 5E 650i
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.parameter.vendorid: 0463
driver.version: 2.7.4
driver.version.data: MGE HID 1.39
driver.version.internal: 0.41
input.voltage: 226.0
outlet.1.status: on
outlet.desc: Main Outlet
outlet.id: 1
outlet.switchable: no
output.frequency: 49.9
output.frequency.nominal: 50
output.voltage: 225.0
output.voltage.nominal: 230
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: 03.08.0018
ups.load: 27
ups.mfr: EATON
ups.model: 5E 650i
ups.power.nominal: 650
ups.productid: ffff
ups.start.battery: yes
ups.status: OL
ups.timer.shutdown: -1
ups.vendorid: 0463
Se /sbin/upsmon
imprimir algo como:
Network UPS Tools upsmon 2.7.4
fopen /var/run/nut/upsmon.pid: No such file or directory
Using power down flag file /etc/killpower
Fatal error: insufficient power configured!
Sum of power values........: 0
Minimum value (MINSUPPLIES): 1
Edit your upsmon.conf and change the values.
tentar:nano /etc/nut/upsd.users
[upsmon]
password = mypassword
upsmon master
chmod 640 /etc/nut/upsd.users
ls -lahrt /etc/nut/upsd.users
-rw-r----- 1 root nut 2,2K Dec 13 13:15 /etc/nut/upsd.users
nano /etc/nut/upsmon.conf
MONITOR myups@localhost 1 upsmon mypassword master
systemctl enable nut-monitor
/sbin/upsmon
Network UPS Tools upsmon 2.7.4
fopen /var/run/nut/upsmon.pid: No such file or directory
UPS: myups@localhost (master) (power value 1)
Using power down flag file /etc/killpower
Aqui está o que pode ser visto no syslog quando testei cortando a eletricidade:
Dec 13 15:47:01 pc upsmon[604]: UPS myups@localhost on battery
... 12 minutes later
Dec 13 15:59:32 pc upsmon[604]: UPS myups@localhost battery is low
Dec 13 15:59:32 pc upsd[601]: Client upsmon@::1 set FSD on UPS [myups]
Dec 13 15:59:32 pc upsmon[604]: Executing automatic power-fail shutdown
Dec 13 15:59:32 pc upsmon[604]: Auto logout and shutdown proceeding
Dec 13 15:59:37 pc systemd[1]: nut-monitor.service: Succeeded.
Dec 13 15:59:37 pc systemd[1]: unattended-upgrades.service: Succeeded.
Dec 13 15:59:37 pc systemd[1]: Stopping Session 39 of user a.
Dec 13 15:59:37 pc systemd[1]: Stopped target Graphical Interface.
Dec 13 15:59:37 pc upsd[601]: mainloop: Interrupted system call
Dec 13 15:59:37 pc systemd[1]: Stopped target Multi-User System.
Dec 13 15:59:37 pc upsd[601]: Signal 15: exiting
Dec 13 15:59:37 pc systemd[1]: Stopping Network UPS Tools - power devices information server...
Dec 13 15:59:37 pc systemd[1]: postgresql.service: Succeeded.
Dec 13 15:59:37 pc systemd[1]: Stopped PostgreSQL RDBMS.
Dec 13 15:59:37 pc systemd[1]: Stopping PostgreSQL Cluster...
Dec 13 15:59:37 pc systemd[1]: Stopping The Apache HTTP Server...
Dec 13 15:59:37 pc systemd[1]: Stopping LSB: disk temperature monitoring daemon...
Dec 13 15:59:37 pc systemd[1]: sysstat.service: Succeeded.
Dec 13 15:59:37 pc systemd[1]: Stopped Resets System Activity Data Collector.
Dec 13 15:59:37 pc smartd[392]: smartd received signal 15: Terminated
Dec 13 15:59:37 pc smartd[392]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.xxx.ata.state
Dec 13 15:59:37 pc smartd[392]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.yyy.ata.state
Dec 13 15:59:37 pc smartd[392]: smartd is exiting (exit status 0)
Dec 13 15:59:37 pc systemd[1]: Stopping Self Monitoring and Reporting Technology (SMART) Daemon...
Dec 13 15:59:37 pc systemd[1]: Stopping Regular background program processing daemon...
Dec 13 15:59:37 pc systemd[1]: Stopped target Login Prompts.
Dec 13 15:59:37 pc systemd[1]: Stopping OpenBSD Secure Shell server...
... when power is on again
Dec 13 16:01:28 pc kernel: [ 0.000000] Linux version 4.19.0-9-amd64 ([email protected]) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.1$
Após a inicialização, quando executo, upsmon
vejo o seguinte:
/sbin/upsmon
Network UPS Tools upsmon 2.7.4
Fatal error: A previous upsmon instance is already running!
Either stop the previous instance first, or use the 'reload' command.
O que significa que está funcionando e está tudo bem, eu acho :)
Você pode ver o significado das variáveis impressas por upsc
, como ups.status
, ups.timer.shutdown
, battery.charge
, aqui:https://networkupstools.org/docs/user-manual.pdf
Outro URL útil é:https://risc-a-day.blogspot.com/2014/09/getting-my-ups-to-work-with-linux.html