Re: [Nut-upsuser] Adding a 'refresh' value to the upsstats web page

Citeren Jim Neeland : > I'd like to have the UPS status web page automatically refreshed. > I've found a reference to using @REFRESH@ in the upsstats.html > page, but as far as I can tell in looking at the code, somewhere I > need to provide a value to the refreshdelay variable, and I see no > way

Re: [Nut-upsuser] ordered shutdown

Citeren Lars Täuber : [...] >> The values of X and Y depend on how long the clients need for >> finishing their business with the SQL servers (X) and how long the SQL >> servers needs for doing their thing on the NFS servers (Y). > > This seems dangerous to me. Just think of the following situati

Re: [Nut-upsuser] ordered shutdown

Citeren Charles Lepple : >> Our network system is quite complex and we need shutdown sequence >> levels. The servers depend on each other because of NFS and SQL >> connections and the like. > There is a bit of sequencing in the master/slave protocol, but I have > not had the time to set someth

Re: [Nut-upsuser] ordered shutdown

Citeren Lars Täuber : > it seems I understood how NUT works now. But then it is not the > solution for us. The reason simply is we have one big ups for so > many servers. And it's a bad idea to have one point in time to > shutdown all servers. So one »battery low« signal for all servers is

Re: [Nut-upsuser] ordered shutdown

Citeren Marco Chiappero : > I think I know what he meant, because my needs are similar. I already > explained them some time ago, when I discovered that NUT comes with no > features at all about programmable outlets (right now I still have no > shutdown sequence settled yet). > When you have one u

Re: [Nut-upsuser] ordered shutdown

Citeren Marco Chiappero : >> If you want to conserve power on your UPS, you should simply send a >> client a command to shutdown. > How can I do that? How can I shutdown different systems at different > battery charge levels (or expected runtime)? I thought the only option > aviable was using upss

Re: [Nut-upsuser] ordered shutdown

Citeren Julian Stacey : > As batteries age, they might (or not) retain most of their Amp Hour > capacity, but as their internal resistance increases, can't deliver > same peak current load as a newer lower internal resistance battery. The internal resistance usually increases because of loss of a

Re: [Nut-upsuser] ordered shutdown

Citeren Gabor Gombas : > Most server-grade boxes have IPMI support and that's _very_ convenient > not just for turning the machine on/off. Also, we have good experiences > with simple Wake-on-LAN for cheap boxes: it's not 100% reliable, but it > is good enough to be useful (and if a machine does n

Re: [Nut-upsuser] ordered shutdown

Citeren Marco Chiappero : > NUT is handy if you want to shut down one or many systems in the same > moment but not in such case (upssched, is not even part of the core and > does not fully fits these needs). No, at the moment NUT only support if the decision to shutdown is made at the same time

Re: [Nut-upsuser] ordered shutdown

Citeren Marco Chiappero : >> And "centralized" is a very important keyword here; having >> to modify upssched scripts on dozens of machines when the plan changes >> is a real PITA. > I agree, and that's the reason why I said there is a need for a > director. It takes care about settings and action

Re: [Nut-upsuser] ordered shutdown

Citeren Gabor Gombas : > The first step would be to have a _central_ way to manage when to shut a > specific class of clients down. Having to muck with upssched scripts on > every client just does not scale. IMHO the clients should just say > "hello, I'm of class X" when logging into the UPS, and

Re: [Nut-upsuser] ordered shutdown

Citeren Marco Chiappero : > This would be useful too, but I would be happy enough just having > different shutdown moments based on timer|charge|runtime as apcupsd and > MGE's psp[1] do natively (and as it should be)! It's funny that you mention MGE PSP here, since except for the shutdown timer

Re: [Nut-upsuser] ordered shutdown

Citeren Marco Chiappero : >> Please elaborate here, because as far as I know we already have this >> (the 'upsd' server). > Please read the last mail from Gabor, his idea it's really close to > mine. To me clients have to be as "stupid" as possible (requiring almost > no configuration) and simply

Re: [Nut-upsuser] ordered shutdown

Citeren Marco Chiappero : >> It's funny that you mention MGE PSP here, since except for the >> shutdown timer (reason explained in the FAQ), NUT already provides >> *all* functionality it has (including shutdown based on charge and >> runtime). What you may be missing is the fact that this require

Re: [Nut-upsuser] early shutdown of VMware VMs

Citeren David Newman : > How to shut down VMWare guest virtual machines earlier than the host > machine they run on? (For example, if everything normally shuts down at > 5% UPS battery, then the VMs should shut down at 10%.) First question is, why do you want to do that? > I also read upssched.t

Re: [Nut-upsuser] early shutdown of VMware VMs

Citeren David Newman : >>> How to shut down VMWare guest virtual machines earlier than the host >>> machine they run on? (For example, if everything normally shuts down at >>> 5% UPS battery, then the VMs should shut down at 10%.) >> First question is, why do you want to do that? > Because a clean

Re: [Nut-upsuser] ordered shutdown

Citeren Marco Chiappero : >> You're wrong. :-) > I don't think so :-) Yes you are. :-) > Yesterday I had a try with my windows laptop. Here you can see how it > works: http://i43.tinypic.com/2n20778.png You can configure NUT to shutdown at a certain battery.charge too, with the UPS you're usi

Re: [Nut-upsuser] ordered shutdown

Citeren Marco Chiappero : > Well, right, but PSP it's not intended for network use, while NUT indeed > it is. I took it as example for showing the above reason and how easy is > to choose from different criteria in a standalone environment: > http://i39.tinypic.com/2mpy9s6.png You hit the nail on

Re: [Nut-upsuser] NUT 2.4.1 crashes on FreeBSD - additional info

Citeren Volker Theile : > Ahmmm, just wondering how this could happen and why nobody has realized > this bug during the testing phase :-) Testing can only confirm the presence of bugs, not the absence. This error was already present since (at least) January 2005, which probably means that you

Re: [Nut-upsuser] megatec_usb vs Mustek NetGuard / Ippon SmartWinner problem

Citeren Oleg Pshenychnyy : > I have Mustek NetGuard 1000 UPS which is equivalent to Ippon SmartWinner > 1000. > I have tried to run several latest builds of NUT, but run megatec_usb driver > still failed with my device. > I hope the information below might help. [...] Try the 'blazer_usb' driver

Re: [Nut-upsuser] megatec_usb vs Mustek NetGuard / Ippon SmartWinner problem

Citeren Arnaud Quette : > Alex, be sure to also address blazer_usb since it's the long run approach. It will already work with this UPS. The problem is in the way how the phoenix subdriver in megatec_usb deals with reading data from the UPS. Currently, it reads data until it receives a timeou

Re: [Nut-upsuser] megatec_usb vs Mustek NetGuard / Ippon SmartWinner problem

Citeren "Alexander I. Gordeev" : >> Alex, be sure to also address blazer_usb since it's the long run approach. > Sure, actually I rechecked blazer_usb after Arjen's mail. Well, it is > not really working but it can read Q1 response at least! I didn't notice > this previously because the driver the

Re: [Nut-upsuser] ups.delay.shutdown clarification

Citeren Des Dougan : > A client of mine has an APC Back-UPS 350 model (USB connected). His > office had a power incident yesterday, where there was an interruption > of about 30 seconds. During that time, the server shut down. As soon > as it went on battery, the daemon initiated a shutdown. In ch

Re: [Nut-upsuser] driver for HP/Compaq T750 ?

Citeren KP Kirchdoerfer : [...] > And the upshid-ups driver ends with: > No matching HID UPS found > Driver failed to start (exit status=1) Try this driver again, but make sure to add productid = 1f06 to the ups.conf entry for this device. Chances are that it is a re-branded Tripplite u

Re: [Nut-upsuser] RFC: Use tcp-wrapper for all connections to upsd

Citeren Joerg Pulz : > after some experimenting and digging through the code i found no solution > how to completely disable access to upsd from specific hosts. On multi-homed servers the LISTEN directive will deal with this, by only listening on interfaces from which clients are allowed to c

Re: [Nut-upsuser] Nut with megatec_usb

Citeren Gabriel Hahmann : [...] > My device is connected in the bus 001, device 004, and when i do a lsusb -s > 001:004 -vvv the result is as follows: > > Bus 001 Device 004: ID 04b4:5500 Cypress Semiconductor Corp. HID->COM RS232 > Adapter > Device Descriptor: > bLength18 > b

Re: [Nut-upsuser] Nut with megatec_usb

Citeren Gabriel Hahmann : > I tried your sugestion, changing the protocol to megatec and putting the > port with /dev/ttyUSB0. > > This didn't work, the output is as follows: > > r...@comserver:/lib/nut# ./megatec -a sms -DD > Network UPS Tools 2.2.1- - Megatec protocol driver 1.5.13 [megatec]

Re: [Nut-upsuser] Question about Tripplite SU10KRT3U

Citeren Dave Gibson : > Hello list! I can't seem to get this running via RS232 monitoring; I've > been told that NUT won't support serial connections, and find this hard > to verify. Does anyone else have this running on the SU10KRT3U via > RS232? If so, what driver did you use? I'm getting no sat

Re: [Nut-upsuser] "Master privileges unavailable on UPS" after upgrade to Debian Lenny

Citeren David Smith : > On issuing a "/etc/init.d/nut start" I get the following in my syslog: > > Mar 7 00:27:19 copstick3 upsd[26316]: Connection from 127.0.1.1 > Mar 7 00:27:19 copstick3 upsd[26316]: Client monu...@127.0.1.1 logged > into UPS [copstick_ups] > Mar 7 00:27:19 copstick3 upsmon[

Re: [Nut-upsuser] "Master privileges unavailable on UPS" after upgrade to Debian Lenny

Citeren Arnaud Quette : [...] >> upsd.conf >> # >> ACL all 0.0.0.0/0 >> ACL localhost 127.0.0.1/32 >> ACL localhost2 127.0.1.1/32 >> ACL nobodynet 10.9.2.0/24 >> #ACCEPT all >> ACCEPT localhost >> ACCEPT nobodynet >> ACCEPT localhost2 >> REJECT all >> > > tr

Re: [Nut-upsuser] "Master privileges unavailable on UPS" after upgrade to Debian Lenny

Citeren Arnaud Quette : >> upsd.conf >> # >> ACL all 0.0.0.0/0 >> ACL localhost 127.0.0.1/32 >> ACL localhost2 127.0.1.1/32 >> ACL nobodynet 10.9.2.0/24 >> #ACCEPT all >> ACCEPT localhost >> ACCEPT nobodynet >> ACCEPT localhost2 >> REJECT all >> > > try putti

Re: [Nut-upsuser] NUT and Ablerex MARS 3000RT

Citeren Snoopy Great : > I own some Ablerex MARS 3000 (MS3000RT) UPS. > Following the thread here : > http://osdir.com/ml/monitoring.nut.user/2006-04/msg00091.html > I would have the following issues : > 1. The battery charge displayed seems wrong : It always shows 100.0 - even > when the battery

Re: [Nut-upsuser] NUT and Ablerex MARS 3000RT

Citeren Snoopy Great : > Well, the value should not be static, could it be a data parsing error ? No. > 1. Manuel has the same ups model, and the charge level showed by nut is not > constant. However he seems to be running the initial version from svn. Maybe he read the man page for this drive

Re: [Nut-upsuser] Weird Load and Battery Temp Readings

Citeren Bob Blackwell : [...] > The systems message.log contains several lines with; > > Mar 13 19:16:20 DNS323_NAS user.warn kernel: usb 1-1.2: usbfs: process > 26398 (usbhid-ups) did not claim interface 0 before use This usually means that more than one driver is active for the same USB devi

Re: [Nut-upsuser] Nut-upsuser Digest, Vol 45, Issue 13

Citeren Bob Blackwell : > From what I can tell three's only one active driver. PS shows; > > PID USER COMMAND > 2045 root /ffp/bin/usbhid-ups -a APC_UPS > 2047 root /ffp/sbin/upsd > 2049 root /ffp/sbin/upsmon -u monuser > 2050 nutmon /ffp/sbin/upsmon -u monuser Could it b

Re: [Nut-upsuser] Driver for UPS Eaton 9130

Citeren Attila Csontos : > Hi Kjell and Arnaud, > I was trying Kjell's command (/path/to/bcmxcp -DD -a pw9130 -u root) > and I have got this output: [...] > After that driver finished with Segmentation Fault (core dumped). No > core file in current directory. If you care to attempt to deb

Re: [Nut-upsuser] Driver for UPS Eaton 9130

Citeren Attila Csontos : > Hi Kjell and Arnaud, > I was trying Kjell's command (/path/to/bcmxcp -DD -a pw9130 -u root) > and I have got this output: [...] > After that driver finished with Segmentation Fault (core dumped). No > core file in current directory. If you care to attempt to deb

Re: [Nut-upsuser] blazer_usb - short reply

Citeren Andrew Zabolotny : > [ippon] > driver = blazer_usb > port = auto > vendorid = 06da > productid = 0003 > desc = "Ippon Smart Winner 3000" This vendorid and productid are already supported out-of-the box. Specifying them in the configuration should only be done for devices that are not

Re: [Nut-upsuser] Weird Load and Battery Temp Readings

Citeren Bob Blackwell : >> If you post debug output, make sure to include the report descriptor, >> which would be the most valueable part, together with the initial dump >> of the variables. The dump you posted only contained the report descriptor, however the initial dump of the data was miss

Re: [Nut-upsuser] Weird Load and Battery Temp Readings

Citeren Bob Blackwell : >> The dump you posted only contained the report descriptor, however the >> initial dump of the data was missing. We need both to get an idea what >> is going on. The report descriptor itself looks good (I was able to >> successfully parse it). > Sorry about that. Here's mo

Re: [Nut-upsuser] blazer_usb - short reply

Citeren "Alexander I. Gordeev" : > I've just commited a fix for the blazer_usb driver. I'm still trying to fix > megatec_usb also. There is a very odd and interesting problem which I want to > resolve. I've reverted your fix. This breaks other devices where we need to read until '\r' and will c

Re: [Nut-upsuser] blazer_usb - short reply

Citeren Arjen de Korte : >> I've just commited a fix for the blazer_usb driver. I'm still trying to fix >> megatec_usb also. There is a very odd and interesting problem which >> I want to resolve. > I've reverted your fix. This breaks other devices where w

Re: [Nut-upsuser] Weird Load and Battery Temp Readings

Citeren Bob Blackwell : >>> OK, that looks good too, so the problem must be in the calculation of >>> the unit exponent (probably got something to do with erroneous type >>> casting). I updated the SVN trunk with some more debugging info. Can >>> you check out if this solves this issue? >> Will do

Re: [Nut-upsuser] blazer_usb - short reply

Citeren "Alexander I. Gordeev" : > First of all, IMO you should trust me more because I now have an 06da:0003 > Ippon device. It's not that I don't trust you. I´ll take your word for it that reading until timeout is needed for the 06da:0003 if you say so. You made exactly the same mistake as

Re: [Nut-upsuser] megaline 5000, battery charge

Citeren Alexey Konokhov : > I have Megaline 5000 UPS, which I need to monitor via RS232 interface. > I'm using "metasys" driver, and everything is Ok, but I can't see > battery charge. > From command line and cgi-interface I can see battery voltage, input > and output voltage and load of UPS in %.

Re: [Nut-upsuser] blazer_usb - short reply

Citeren "Alexander I. Gordeev" : > Still I'd rather not duplicate the code by creating a bunch of mostly > identical subdrivers without a good reason. If you say that my change really > breaks something it is quite enough. I mostly feel the same way, but the past shows us that there are many US

Re: [Nut-upsuser] MUSTEK PowerMust 3000 NetGuard RM

Citeren Igor R : > We are using the equipment "MUSTEK PowerMust 3000 NetGuard RM". That is > using Megatec protocol. But unfortunately not all the data can be viewed > correctly when dumping from utility "upsc". > > For example: > > upsbox# upsc mus...@localhost > battery.voltage: 108.00 > battery

Re: [Nut-upsuser] Can't claim USB device

Citeren Brandon Metcalf : When trying to start the driver I get $ sudo ./upsdrvctl start Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31 Can't claim USB device [09ae:3012]: could not detach kernel driver

Re: [Nut-upsuser] Cabac UPS-1700DV2

Citeren mick : KDE Info Centre reports the UPS as: STD UPS MON V1.0 Class 0 ((Defined at Interface level)) Subclass0 Protocol0 USB Version 1.00 Vendor ID 0x1 (Fry's Electronics) Product ID 0x0 This VendorID:ProductID is complet

Re: [Nut-upsuser] Trouble with PowerMan UPS

Citeren Yevgeny Kosarzhevsky : I get a trouble using nut with PowerMan Back Pro N 1400 Plus [...] I have tried it on win xp with WinStar Pro and it works just fine. The cable and UPS are new. Any advice? Read 'man 8 blazer' and try the 'blazer_ser' driver (in that order). Best regards, A

Re: [Nut-upsuser] Poll UPS / Driver not connected with UPS MGE Evolution 850VA USB

Citeren Vianney Lejeune : I reopen this thread because I encounter a minor problem using this UPS with the newhidups driver, this is an extract from my syslog after booting my OS (Debian Etch): =8<= May 10 22:31:51 Inet-Primaire kernel: usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd

Re: [Nut-upsuser] Cyberpower Value 600E UPS (USB) is not recognized by usbhid-ups under FreeBSD 7.2

Citeren forsite : [...] [r...@substance /usr/local/libexec/nut]# ./usbhid-ups -a CyberPower -DDD Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31 debug level is '3' upsdrv_initups... No appropriate HID device found No matching HID UPS found Any ideas what coul

Re: [Nut-upsuser] Where are usbhid-ups driver parameters defined - and what do some of them mean?

Citeren Richard Chapman : I am using the usbhid-ups driver with a Belkin UPS. upsc shows several parameters which I would like to both understand and probably change. In particular the following part of upsc output: battery.charge.low: 30 battery.charge.warning: 30 battery.runtime: 120 My q

Re: [Nut-upsuser] Belkin F6C750-AVR Nut Driver for Linux

Citeren xqa xqa : [...] As you can see the F6C750-AVR appears to be megatec protocol. Does anyone know what I need to do to control how I can control the Belkin F6C750-AVR UPS? Have I missed some config? You probably didn't read the README and INSTALL files, where we document this. You

Re: [Nut-upsuser] Belkin F6C750-AVR Nut Driver for Linux

Citeren Richard Chapman : I am using a very similar Belkin UPS with nut 2.2.0 and Centos 5.3. No, you're not. Belkin devices come in different flavors, depending on the manufacturing date. If you look in the drivers.list, you'll see that some identical Belkin models require different drive

Re: [Nut-upsuser] upsmon shutdown based on Time since power fail.

Citeren Richard Chapman : This sounds like one way to do it. If I do it this way - do you know whether the file: /etc/killpower will be created before the shut-down is issued (as it would if the battery low event occurs). If not - the UPS may not be shut down - and therefore the system m

Re: [Nut-upsuser] APC Smart UPS 900i

Citeren Rene Bartsch : I used the SVN trunk version from about 20 hours ago. Good. At least we know it is something recent... The upper output is from upsc, other commands: The command "upscmd -l su9...@localhost" just returns "Instant commands supported on UPS [su900i]:" The command "up

Re: [Nut-upsuser] APC Smart UPS 900i

Citeren Rene Bartsch : Command: "/lib/nut/apcsmart -a su900i -D" - snip - Network UPS Tools - APC Smart protocol driver 2.00 (2.4.1) APC command table version 2.0 debug level is '5' send_to_all: SETI

Re: [Nut-upsuser] New NUT user with HP R3000XR problem

Citeren Brother Railgun of Reason : babylon4:root:/opt/nut:24 start Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) RS-232 communication subdriver 0.17 Connected to UPS on /dev/tty00 with baudrate 19200 OK, the driver is running, so this is no

Re: [Nut-upsuser] New NUT user with HP R3000XR problem

Citeren Brother Railgun of Reason : babylon4:root:/opt/nut:25 # sbin/upsd Network UPS Tools upsd 2.4.1 listening on 127.0.0.1 port 3493 listening on ::1 port 3493 /opt/nut/var is world readable Connected to UPS [tokamak]: bcmxcp-tokamak Maximum number of connections limited to 256 [requested 102

Re: [Nut-upsuser] New NUT user with HP R3000XR problem

Citeren Brother Railgun of Reason : Oops, looking at the code I saw this isn't a warning, but a (fatal) error instead (this was not one of the most descriptive error messages I ever wrote). I now recall that this value is OS dependent, so you probably want/need to limit this in upsd.conf through

Re: [Nut-upsuser] APC Smart UPS 900i

Citeren Rene Bartsch : Command: "upsc su900i" -- snip --- battery.alarm.threshold: 0 battery.charge: 100.0 battery.charge.restart: 10 battery.date: 11/02/01 battery.runtime: 4440 battery.runtime.low: 120 bat

Re: [Nut-upsuser] APC Smart UPS 900i

Citeren Rene Bartsch : I just reinstalled a current SVN and model is "Smart-UPS", now. :) Good. But I also realized that upsrw can only set "battery.date" and "ups.id" but nothing else. I'd really appreciate to have the capability to set "ups.test.interval" at least. ;) Maybe older devi

Re: [Nut-upsuser] Can't connect to UPS [mustek] (megatec-mustek): No such file or directory

Citeren Vedran Furač : NUT recently stopped working on my debian. I'm not sure which upgrade broke it. From which version did you upgrade it? ups.conf: [mustek] driver = megatec port = /dev/ttyS0 desc = "mustek ups" # upsd - Network UPS Tools upsd 2.4.1 listen

Re: [Nut-upsuser] Can't connect to UPS [mustek] (megatec-mustek): No such file or directory

Citeren Vedran Furač : Where is "megatec-mustek" file? It should be created by the driver, which apparently isn't running. Either it isn't started at all, fails to detect the UPS or isn't running with the proper permissions. [snip] dstate_init: sock /var/run/nut/megatec-mustek open on fd 5

Re: [Nut-upsuser] Belkin support?

Citeren Gene Heskett : That seems to work, as in doesn't exit even if I run a second invocation of usbhid-ups -a myups, both show up at the bottom of htop's listing, and both responded to a kill from htop. The output was: [r...@coyote /]# usbhid-ups -a myups Network UPS Tools: 0.29 USB communic

Re: [Nut-upsuser] Slave as master

Citeren "Dr. Madhurjya P. Bora" : I need to set up machine as slave which will act as  a master to some subordinate clients. The machine is question is a master node a parallel cluster which I want it to act as a master for the computing nodes but set itself as a slave with a master exclusi

Re: [Nut-upsuser] Slave as master

Citeren Rob MacGregor : I have a similar question to this as well, in that I have my server set up using NUT with a SOLA-330 (working nicely!) and my desktop is using an APC BackUPS-300 (this model has no serial/USB comms) as the SOLA & APC are rated the same, I was wanting my server to send a b

Re: [Nut-upsuser] Tripplite Smart1500

Citeren Charles Lepple : ups.status: The "ups.status" value is problematic - it should include at least OL or OB. Not sure whether it is due to Protocol 4-related changes, or the aforementioned timeout. The above is due to a problem with calculation of the size of reports in libhid.c that

Re: [Nut-upsuser] Tripplite Smart1500

Citeren Charles Lepple : The above is due to a problem with calculation of the size of reports in libhid.c that was fixed more than a year ago. This fix requires nut-2.2.2 or newer. For many USB devices, anything earlier than that may mean that they run into this limitation (that existed since w

Re: [Nut-upsuser] UPS does not want to power off itself

Citeren "Anton E. Panchenko" : [...] upsshed-cmd #!/bin/sh MSG="The UPS is running on battery about 2 minutes, doing force shutdown" case $1 in fsd) logger -t upssched-cmd $MSG /sbin/upsmon -c fsd ;; *) logger -t upssched-cmd "ERROR!! $0 Unrecognized command:

Re: [Nut-upsuser] Is any ideas about Ippon smart power 2000?

Citeren vk : Hi friends! It is not any answer to my previous letter about problem with nut 2.4.1 and ippon smart power 2000 UPS with megatec_usb driver. Maybe any additional information needed? Please help, any required info i get. Please post the output of /path/to/megatec_usb -u r

Re: [Nut-upsuser] Is any ideas about Ippon smart power 2000?

Citeren Alexander Gordeev : Please post the output of /path/to/megatec_usb -u root -DDD -a IPPON here. If this fails to connect to your UPS, chances are that you haven't prepared your kernel to allow the userspace driver to bind to the USB device. In that case, search the archives. It's

Re: [Nut-upsuser] Premature end of script headers: upsimage.cgi

Citeren ben thielsen : [...] some additional information - i've since added another smart-ups 1500 (not xlm), connected via usb to this same server, and it draws the voltage graph without incident. The latter is useful information, since it means that the problems is probably in the valu

Re: [Nut-upsuser] Premature end of script headers: upsimage.cgi

Citeren benjamin thielsen : working voltage graph: [ups2] driver = usbhid-ups port = auto [...] battery.voltage: 27.7 battery.voltage.nominal: 24.0 This looks normal. non-working voltage graph: [ups4] driver = snmp-ups port = ups4 community = xx snmp_ver

Re: [Nut-upsuser] Premature end of script headers: upsimage.cgi

Citeren benjamin thielsen : aha - thank you, that seems to have done the trick. i suppose that dividing by zero would also explain the floating point error. Yes. That tipped me off that there might be something wrong in the values reported by the UPS. regarding the values you've specifie

Re: [Nut-upsuser] Belkin 800VA Universal AVR doesn't warn about battery

Citeren Gasper Kozak : Since battery.charge.low and battery.charge.warning settings are read-only, and LB doesn't get reported via ups.status, I'm guessing the latter two of these are just advisory -- rather silly, but I guess that's it. Maybe upsmon should watch these as well? No. The very le

Re: [Nut-upsuser] Belkin 800VA Universal AVR doesn't warn about battery

Citeren Gasper Kozak : I've installed the mentioned packages and LB event still doesn't get generated/reported. That is bad. In that case we need the output of /path/to/usbhid-ups -DD -a upsname Note that I want exactly *two* debug flags here. Not more, not less. You'll want to stop al

Re: [Nut-upsuser] Is any ideas about Ippon smart power 2000?

Citeren vk : Hi! There is continue of my story with Ippon smart power 2000 and nut, i'm enable usb in kernel and nut give following information: gate# cat ups.conf [IPPON] driver = megatec_usb port = /dev/ugen0 vendorid = 0665 productid = 5161 subdriver = phoenix desc = "Ipp

Re: [Nut-upsuser] Accurate battery reports? (HP R3000 XR)

Citeren Jon Bendtsen : I have a HP R3000 XR UPS which NUT never says is at 100% battery. It seems stuck in 98 or 99 . something percentage. Please mention the driver you're using when asking for help. How accurate should i expect the reports to be? All my other UPSes has been and is at 100%

Re: [Nut-upsuser] Belkin 800VA Universal AVR doesn't warn about battery

Citeren Gasper Kozak : Here it is, 30 seconds of output: http://pastebin.com/f2c5aa338 This is looking good. The HID path (UPS.BELKINStatus.BELKINBatteryStatus) that we're using is available. Bit 2 of the value reported (when converted to an int) will be set if the battery is low and bit

[Nut-upsuser] CyberPower OP- and PR-series UPS (230 V version)

To be able to calibrate the voltage conversions for the powerpanel driver (binary mode) I need some startup logs for the PowerPanel Plus (Windows) program that is provided by CyberPower. Preferably logs created with the following tool: http://technet.microsoft.com/en-us/sysinternals/bb8

Re: [Nut-upsuser] Problem with APC SMART UPS 1000 (USB)

Citeren Sergey : [...] But, to switch off the electric power After 20 min: -- $upsc usb ..skip... battery.charge: 100 battery.temperature: 36.8 battery.voltage: 23.9 input.voltage: 0.0 output.voltage: 220.4 ups.load: 24.7 ups.status: OL ...skip... ---

Re: [Nut-upsuser] How to connect Trust UPS Energy Protector 400VA with nut

Citeren Peter Werner : I have been trying to figure out the whole day how I can connect our old Trust UPS Energy Protector 400VA with nut. But I have not made any progress yet and the worst is: I have no idea where to start although I read the documentation and search the web. My first problem

Re: [Nut-upsuser] Problem with nut 2.4.1 & Ippon 2000 Smart power on FreeBSD

Citeren vk : gate# /usr/local/libexec/nut/blazer_usb - -a IPPON Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.1) debug level is '4' Checking device (0665/5161) (/dev/usb1//dev/ugen0) - VendorID: 0665 - ProductID: 5161 - Manufacturer: Cypress Semiconductor - Product: USB to Ser

Re: [Nut-upsuser] Problem with nut 2.4.1 & Ippon 2000 Smart power on FreeBSD

Citeren vk : Support for libusb is 'experimental' at best in FreeBSD and depending on the version you're using, 'unusable'. You may try if adding a small delay between sending a command and reading back the reply helps (YMMV): --- trunk/drivers/blazer_usb.c (revision 1861) +++ trunk/drivers/

Re: [Nut-upsuser] Any word on when the ietf mib will be fixed for liebert?

Citeren Maurice Volaski : This mib used to work, so is there a way to go back to the version prior to this one without downgrading the whole package? When did this stop working (from which version to nut-2.4.1 did you upgrade)? The last changes to the IETF are made almost two years ago. A

Re: [Nut-upsuser] Any word on when the ietf mib will be fixed for liebert?

Citeren Maurice Volaski : This mib used to work, so is there a way to go back to the version prior to this one without downgrading the whole package? yes, only take the snmp-ups driver from the previous working release. 2.2.2 and 2.0.5 also complain but with fewer errors. Please don't mis

Re: [Nut-upsuser] Any word on when the ietf mib will be fixed for liebert?

Citeren Maurice Volaski : Please don't mistake warning messages with (fatal) errors. Starting with nut-2.4.0, these messages should only be displayed in debug mode, so I'm surprised you're seeing them in nut-2.4.1. It doesn't seem this way from my reading of the source code: upslogx(LOG_ER

Re: [Nut-upsuser] Any word on when the ietf mib will be fixed for liebert?

Citeren Maurice Volaski : upslogx(LOG_ERR, "[%s] %s: Error in packet: %s", This is a different message from what you reported before. These where logged with 'nut_snmp_get' in them and these lines should now be gone (unless running in debug mode 2 or higher). What message do you think I

Re: [Nut-upsuser] Belkin F6C-1250-TW-RK is supported [patch]

Citeren David Mohr : just wanted to let you know that I have two belkin F6C-1250-TW-RK UPSes which work just fine with nut. I made this small patch so that nut recognizes the usb device id. Thanks for the patch! I committed the change for the belkin-hid subdriver (the other file is a generat

Re: [Nut-upsuser] pebcak or something else?

Citeren "Svein Skogen (listmail account)" : I've set up my ups solution with a dedicated box (laptop with its own powersupply) connected to the ups, and have set up upsmon.conf to use a customized script (SHUTDOWNCMD "/usr/local/upsmonitor-files/shutdown.sh") that shuts down my ESXi boxes proper

Re: [Nut-upsuser] pebcak or something else?

Citeren "Svein Skogen (listmail account)" : Read the section on POWER VALUES in 'man 8 upsmon'. You probably should assign the UPS a 'power value' of 0 (zero) on the laptop that is monitoring it (but isn't powered by it). if it's a value of 0, will it still invoke the SHUTDOWNCMD? No and tha

Re: [Nut-upsuser] Usbhip-ups going wild

Citeren Antoine Gatineau : I am facing some serious issues on customer's site. I looked around on the web and in the archives but didn't find anything. I hope you can help me. Here is my configuration : OS :RHES 4.7 NUT : 2.2.0 NUT-CLIENT : 2.2.0 Hardware : IBM x3250M2 (dual-core intel E3110)

Re: [Nut-upsuser] ups not recognized by usbhid-ups

Citeren Zeev Tarantov : I have a new UPS, actual manufacturer unknown. It comes with USB and serial connections, and a CD with windows software and some old unix software for serial support only. I'm using pretty much bleeding edge linux, and I want to avoid rs-232 if possible. Am I hopelessly n

Re: [Nut-upsuser] Accurate battery reports? (HP R3000 XR)

Citeren Jon Bendtsen : NUT cgi started to report the battery at 100% without i remember doing anything. It could be that the UPS has performed an automatic battery test or runtime calibration in the mean time (which is not unusual for many higher end devices). Note that in general, you'

Re: [Nut-upsuser] I Need help configuring my UPS- Newbie!!

Citeren "John @ BER Ltd" : I keep getting errors from the server regarding loosing and reconnecting with the UPS appx every 10 mins. [...] Can anyone help regarding how to properly configure nut and to edit the config file. The problem is not in the configuration file, it's the version of

Re: [Nut-upsuser] UPS Config

Citeren Brian Hoover : No I just meant that I could not communicate to my APC UPS unless I had the config in hyperterminal the way I stated, and it would not respond to any command until I sent “Y”. The protocol 'documentation' you're referring to is meant to aid the NUT developers. It is

Re: [Nut-upsuser] Selftest intervall, APC Smart-UPS 750 RM

Citeren Arnaud Quette : strange indeed. the data is there, and now know. I've made a minor fix (r1955). please test it and tell me back if input.transfer.reason appears now. No, it won't. The 'input.transfer.reason' value is set through the VRANGE and FRANGE status bits. In the absence of e

Re: [Nut-upsuser] No battery.charge

Citeren vk : I have a nut 2.4.1 on FreeBSD 7.1 i386. UPS model is IPPON smart smart power pro 2000. When i try to see battery charge, in output it have not such variable, and i can't control other servers (Win2k3 + WinNUT) because they not knows about current battery charge. How i can solve

<    2   3   4   5   6   7   8   9   10   11   >