Hello, I had running OpenMediaVault server with NUT 2.4.3 megatec_usb driver. After the OMV upgrade, NUT also upgraded to 2.6.4. I realised that megatec_usb removed in this version. So I have configured to use blazer_usb driver. However NUT behaves incorrectly after switching blazer_usb. System is being halted upon booted up. Is it possible to use megatec_usb driver in the new version? # NUT 2.4.3 with megatec_usb driver battery.charge: 98.3 battery.voltage: 27.00 battery.voltage.nominal: 23.5 device.mfr: TUNCMATIK device.model: DG1200VA VER1.01C device.serial: unknown device.type: ups driver.name: megatec_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3 driver.version.internal: 1.6 input.frequency: 50.0 input.frequency.nominal: 50.0 input.voltage: 220.0 input.voltage.fault: 165.0 input.voltage.maximum: 226.0 input.voltage.minimum: 217.0 input.voltage.nominal: 220.0 output.voltage: 220.0 ups.beeper.status: disabled ups.delay.shutdown: 0 ups.delay.start: 2 ups.load: 0.0 ups.mfr: TUNCMATIK ups.model: DG1200VA VER1.01C ups.serial: unknown ups.status: OL OFF ups.type: standby # NUT 2.6.4 with blazer_usb driver battery.charge: 100 battery.voltage: 27.00 battery.voltage.high: 25.46 battery.voltage.low: 20.37 battery.voltage.nominal: 23.5 device.mfr: TUNCMATIK device.model: DG1200VA device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.6.4 driver.version.internal: 0.08 input.current.nominal: 8.0 input.frequency: 50.0 input.frequency.nominal: 50 input.voltage: 212.0 input.voltage.fault: 165.0 input.voltage.nominal: 220 output.voltage: 212.0 ups.alarm: Shutdown imminent! ups.beeper.status: disabled ups.delay.shutdown: 30 ups.delay.start: 180 ups.firmware: VER1.01C ups.load: 0 ups.mfr: TUNCMATIK ups.model: DG1200VA ups.productid: 0000 ups.status: ALARM OL FSD ups.temperature: 0.0 ups.type: offline / line interactive ups.vendorid: 0001 #NUT logs 1. Feb 22 19:48:43 microserver upsd[2586]: listening on 127.0.0.1 port 3493 2. Feb 22 19:48:43 microserver upsd[2586]: Connected to UPS [ups]: blazer_usb-ups 3. Feb 22 19:48:43 microserver upsd[2596]: Startup successful 4. Feb 22 19:48:43 microserver upsd[2596]: User monmaster at 127.0.0.1 logged into UPS [ups] 5. Feb 22 19:48:43 microserver upsmon[2608]: Startup successful 6. Feb 22 19:48:48 microserver upsmon[2610]: UPS ups at localhost: forced shutdown in progress 7. Feb 22 19:48:48 microserver upsd[2596]: Client monmaster at 127.0.0.1 set FSD on UPS [ups] 8. Feb 22 19:48:48 microserver upsmon[2610]: Executing automatic power-fail shutdown 9. Feb 22 19:48:48 microserver upsmon[2610]: Auto logout and shutdown proceeding 10. Feb 22 19:48:48 microserver upssched[2760]: Executing command: notify 11. Feb 22 19:48:48 microserver upssched[2758]: Executing command: forced-shutdown 12. Feb 22 19:48:48 microserver upsmon[2610]: Signal 10: User requested FSD 13. Feb 22 19:48:49 microserver upssched-cmd: UPS ups at localhost: - Forced shutdown in progress 14. Feb 22 19:48:49 microserver upssched-cmd: Automatic logout and shutdown proceeding # dmesg usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 128 rq 6 len 255 ret -110 Regards. Mustafa T. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150314/4d4faca5/attachment.html>
On Mar 13, 2015, at 6:30 PM, cinowell <cinowell at gmail.com> wrote:> Hello, > > I had running OpenMediaVault server with NUT 2.4.3 megatec_usb driver. After the OMV upgrade, NUT also upgraded to 2.6.4. I realised that megatec_usb removed in this version. So I have configured to use blazer_usb driver. However NUT behaves incorrectly after switching blazer_usb. System is being halted upon booted up. > Is it possible to use megatec_usb driver in the new version?It might be possible, but the correct solution would be to fix the current drivers. (Note that blazer_usb has been superseded by nutdrv_qx in later versions of NUT.)> # NUT 2.6.4 with blazer_usb driver > battery.charge: 100 > battery.voltage: 27.00 > battery.voltage.high: 25.46 > battery.voltage.low: 20.37 > battery.voltage.nominal: 23.5 > device.mfr: TUNCMATIK > device.model: DG1200VA > device.type: ups > driver.name: blazer_usb > driver.parameter.pollinterval: 2 > driver.parameter.port: auto > driver.version: 2.6.4 > driver.version.internal: 0.08 > input.current.nominal: 8.0 > input.frequency: 50.0 > input.frequency.nominal: 50 > input.voltage: 212.0 > input.voltage.fault: 165.0 > input.voltage.nominal: 220 > output.voltage: 212.0 > ups.alarm: Shutdown imminent! > ups.beeper.status: disabled > ups.delay.shutdown: 30 > ups.delay.start: 180 > ups.firmware: VER1.01C > ups.load: 0 > ups.mfr: TUNCMATIK > ups.model: DG1200VA > ups.productid: 0000 > ups.status: ALARM OL FSD > ups.temperature: 0.0 > ups.type: offline / line interactive > ups.vendorid: 0001I am curious whether the UPS is always sending FSD, or if the bit controlling FSD is inverted. Does the UPS have a "force shutdown" feature? If so, here's how to test: 1) Power down, and disconnect the UPS USB cable from the computer. 2) Power up the computer attached to a different UPS or wall outlet 3) Turn the UPS on 4) Kill the upsmon process (this will prevent automatic shutdown) 5) Plug the UPS USB cable back in 6) Turn the UPS off, and watch "upsc ups.status" If the "FSD" indication disappears, then the bit is inverted, otherwise it needs to be ignored. -- Charles Lepple clepple at gmail
I've done all the steps. However FSD indication did NOT disappear. So it seems UPS always send the FSD flag. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150316/fd7ccc7a/attachment.html>