Hi Folks
This isnt a strictly nethserver question but im coming to you because you seem to have made NUT work for network connection to my APC Smart-UPS 1500 ([NS6.8] NUT and APC Network Management Card). I have configured a nethserver to conect to the UPS via TCP and it appears to know all about the unit (on the dashboard tab) so Im assuming success.
My objective is to (supercede) have an identical capability for my Proxmox server and Ive struggled to repeat the install in this environment. Having managed to get nut on Nethserver working (which is a VM guest on the proxmox host) , I have decided to try and use the “working config” from Nethserver as follows (this is everything from the /etc/ups directory - if i have missed anything please let me know!). All of this config has been copied over to an Ubuntu 18 guest which i am using to test (rather than screw around with the proxmox host until I have a better understanding!):
[root@nethserver ups]# cat nut.conf|grep -v “#”
MODE=netserver
[root@nethserver ups]# cat ups.conf|grep -v “#”
pollinterval = 10
[UPS]
driver = snmp-ups
port = 192.168.14.220
[root@nethserver ups]# cat upsd.conf|grep -v “#”
LISTEN 0.0.0.0
[root@nethserver ups]# cat upsd.users|grep -v “#”
[upsmon]
password = <password of “apc” user UPS>
upsmon master
[root@nethserver ups]# cat upsmon.conf|grep -v “#”
MINSUPPLIES 1
SHUTDOWNCMD “/sbin/shutdown -h +0”
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 15
DEADTIME 15
POWERDOWNFLAG /etc/killpower
RBWARNTIME 43200
NOCOMMWARNTIME 300
FINALDELAY 5
MONITOR UPS@127.0.0.1 1 upsmon apc master
[root@nethserver ups]# cat upssched.conf|grep -v “#”
CMDSCRIPT /usr/bin/upssched-cmd
Initial analysis as follws:
NETHSERVER GUEST (working)
[root@nethserver ups]# systemctl -l status nut-driver
● nut-driver.service - Network UPS Tools - power device driver controller
Loaded: loaded (/usr/lib/systemd/system/nut-driver.service; static; vendor preset: disabled)
Active: active (running) since Sat 2020-01-11 13:07:26 GMT; 22h ago
Main PID: 30221 (snmp-ups)
Tasks: 1
CGroup: /system.slice/nut-driver.service
└─30221 /usr/sbin/snmp-ups -a UPS
Jan 11 13:07:25 nethserver systemd[1]: Starting Network UPS Tools - power device driver controller…
Jan 11 13:07:25 nethserver upsdrvctl[30112]: No matching MIB found for sysOID ‘.1.3.6.1.4.1.318.1.3.27’!
Jan 11 13:07:25 nethserver upsdrvctl[30112]: Please report it to NUT developers, with an ‘upsc’ output for your device.
Jan 11 13:07:25 nethserver upsdrvctl[30112]: Going back to the classic MIB detection method.
Jan 11 13:07:25 nethserver upsdrvctl[30112]: Detected Smart-UPS 1500 on host (mib: apcc 1.2)
Jan 11 13:07:25 nethserver upsdrvctl[30112]: [UPS] Warning: excessive poll failures, limiting error reporting (OID = .1.3.6.1.4.1.318.1.1.1.9.2.3.1.5.1.1.3)
Jan 11 13:07:26 nethserver upsdrvctl[30112]: [UPS] Warning: excessive poll failures, limiting error reporting (OID = .1.3.6.1.4.1.318.1.1.1.9.3.3.1.6.1.1.1)
Jan 11 13:07:26 nethserver snmp-ups[30221]: Startup successful
Jan 11 13:07:26 nethserver upsdrvctl[30112]: Network UPS Tools - UPS driver controller 2.7.4
Jan 11 13:07:26 nethserver systemd[1]: Started Network UPS Tools - power device driver controller.
[root@nethserver ups]#
UBUNTU GUEST
(not working!)
me@ubuntu:~$ systemctl -l status nut-driver
● nut-driver.service - Network UPS Tools - power device driver controller
Loaded: loaded (/lib/systemd/system/nut-driver.service; static; vendor preset
Active: failed (Result: exit-code) since Sun 2020-01-12 00:15:11 UTC; 11h ago
Process: 1065 ExecStart=/sbin/upsdrvctl start (code=exited, status=1/FAILURE)
Jan 12 00:15:11 ubuntu systemd[1]: Starting Network UPS Tools - power device dr
Jan 12 00:15:11 ubuntu upsdrvctl[1065]: Can’t start /lib/nut/snmp-ups: No such
Jan 12 00:15:11 ubuntu upsdrvctl[1065]: Network UPS Tools - UPS driver controll
Jan 12 00:15:11 ubuntu systemd[1]: nut-driver.service: Control process exited,
Jan 12 00:15:11 ubuntu systemd[1]: nut-driver.service: Failed with result 'exit
Jan 12 00:15:11 ubuntu systemd[1]: Failed to start Network UPS Tools - power de
lines 1-11/11 (END)
At first inspection it looks like there is a driver issue - any insight into what additional config is required to replicate the amazing nethserver functionality is appreciated! I notice the instruction i referenced stated using the USB driver - is this the default whereby the system searches for the best driver?.. any assistance appreciated on this confusing topic!
Cheers
ALex