I do have a cheap whatever UPS for my server. It should work with the blazer_usb driver, which it does for a period of several minutes. Then I get the message
and the driver disappears, while the upsd still runs and starts sending
Does anybody have similar trouble with NUT ( Version 2.6.5 )?
(Setup 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64)
During the startup, upsd has a problem to create the PID file, but I can do that manually.
A check with upsc is showing that it work a while:
Maybe there is a special devd.conf setup needed? I have seen also right after the start the following message:
while the system was not touched from a USB point of view. ==> Update: this is not the problem as uhid is already loaded.
Interesting: I have had two blazer_usb processes running in parallel. After a while the first started process stops with permission problem, while the other was still running and continued to work.
Has anybody also used the blazer_usb driver and had similar trouble ?
Code:
blazer_usb[90671]: Permissions problem: Input/output error
Code:
upsd[90673]: Can't connect to UPS [myups] (blazer_usb-myups): No such file or directory
Does anybody have similar trouble with NUT ( Version 2.6.5 )?
(Setup 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64)
During the startup, upsd has a problem to create the PID file, but I can do that manually.
Code:
Network UPS Tools - UPS driver controller 2.6.5
Network UPS Tools - Megatec/Q1 protocol USB driver 0.09 (2.6.5)
Supported UPS detected with mustek protocol
Vendor information unavailable
No values provided for battery high/low voltages in ups.conf
Using 'guestimation' (low: 10.400000, high: 13.000000)!
Battery runtime will not be calculated (runtimecal not set)
Starting nut.
Network UPS Tools upsd 2.6.5
fopen /var/run/upsd.pid: No such file or directory
/usr/local/etc/nut/upsd.conf is world readable
listening on 127.0.0.1 port 3493
Connected to UPS [myups]: blazer_usb-myups
/usr/local/etc/nut/upsd.users is world readable
Code:
upsc myups@localhost
battery.charge: 100
battery.voltage: 13.50
battery.voltage.high: 13.00
battery.voltage.low: 10.40
battery.voltage.nominal: 12.0
device.type: ups
driver.name: blazer_usb
driver.parameter.pollinterval: 2
driver.parameter.port: AUTO
driver.version: 2.6.5
driver.version.internal: 0.09
input.current.nominal: 3.0
input.frequency: 50.1
input.frequency.nominal: 50
input.voltage: 237.1
input.voltage.fault: 237.1
input.voltage.nominal: 230
output.voltage: 237.1
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.load: 9
ups.productid: 5161
ups.status: OL
ups.type: offline / line interactive
ups.vendorid: 0665
Maybe there is a special devd.conf setup needed? I have seen also right after the start the following message:
Code:
devd: Executing 'kldload -n uhid'
Interesting: I have had two blazer_usb processes running in parallel. After a while the first started process stops with permission problem, while the other was still running and continued to work.
Has anybody also used the blazer_usb driver and had similar trouble ?