similar to: ups not recognized by usbhid-ups

Hi Mutlu, 2009/8/7 Mutlu T. <cmtunc at gmail.com> > Redirecting to debian.org domain due to being rejected as spam by free.fr > > > ------- Forwarded message ------- > From: "Mutlu T." <cmtunc at gmail.com> > To: arnaud.quette at free.fr > Cc: > Subject: New NUT HCL entry / (brand)Inform (series)Informer Compact > Date: Fri, 07 Aug 2009 15:31:04

Greetings: I'm evaluating two replacements for UPS upgrades to my dept. Because the CyberPower OP650 has been retired, we are evaluating the CyberPower600VA and the CyperPower 1000AVRLCD. We will be evaluating others. Initial configuration and communications are established via the usbhid-ups driver, the gambit of tests are all passed with the exception of one. I seem to be failing

If any new Xen developers are interested in a simple project to learn Xen development (and also Xen Transcendent Memory), it would be interesting to test this in Xen. AFAIK, the only extensive use of compression is with Transcendent Memory ("tmem"), so learning about tmem would be a useful side-effect. Thanks, Dan

If any new Xen developers are interested in a simple project to learn Xen development (and also Xen Transcendent Memory), it would be interesting to test this in Xen. AFAIK, the only extensive use of compression is with Transcendent Memory ("tmem"), so learning about tmem would be a useful side-effect. Thanks, Dan

Hi, I managed to run United Devices client on Redhat 6.1 with wine-20010326 (after applying a patch that was posted here), but on Mandrake I get errors (below). It brings up the application, but sometimes gets stuck and doesn't open a System Tray window, as it does on the RedHat. (So once you "minimize" the app it's gone for good). Any help appreciated Zeev $

Hi. I have an improvement suggestion. Say that a careless user starts editing upsmon.conf before having read the complete documentation (not that I know of any such users of course) and starts by adding "RUN_AS_USER = nutmon" and then creates this user. Later he discovers that the rpm package already has created a "nut" user and therefore deletes the nutmon user but forgets to

I recently upgraded from nut-2.4.1 to 2.4.3 and my UPS stopped working. usbhid-ups now fails two communicate with the UPS: With 2.4.1: # /sbin/usbhid-ups -D -a auto Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31 debug level is '1' upsdrv_initups... Using subdriver: Belkin HID 0.12 Path: UPS.BELKINConfig.BELKINConfigVoltage, Type: Feature, ReportID: 0x01,

Hi, I have UPS Socomec ITYS 3000 with Netvision card. OS is Centos 6.5 64-bit. NUT installed with yum,. nut-2.6.5-2.el6.x86_64 nut-client-2.6.5-2.el6.x86_64 Why is ups.status empty? Here is upsc output: upsc myups at localhost battery.charge: 97.00 battery.runtime: -60.00 battery.voltage: -0.10 device.mfr: Net Vision v6.01 (SN 0101414290) device.model: ITYS 3 kVA device.serial: 3I14450043

Hi Alan, sorry for the journalctl output. I have now done the following:L * boot into 3.17-rc7 * mount the usb stick (recovery completed) * unmount, mount, unmount - just to be sure all is fine * started usbmon capturing on bus 3 * mount the usb stick * suspend to ram * wake up now the stick is "officially" mounted (/proc/mounts) * umount error messages pop up * try to mount more

Greetings, I imagine this question must have been answered previously on the list, but I can't search for the answer because the archives are gone. Executive summary: I am trying to install and configure nut 2.0.1 on Fedora Core. I have a SmartUPS Pro plugged into a USB port. Upsmon is logging "UPS myups@localhost is unavailable" to syslog and via wall when it starts up and

Yes: Previous complete boot through shutdown Oct 26 21:02:54 i7 upsdrvctl[1955]: Using subdriver: MGE HID 1.32 Oct 26 21:02:55 i7 upsdrvctl[1955]: Network UPS Tools - Generic HID driver 0.38 (2.7.1) Oct 26 21:02:55 i7 upsdrvctl[1955]: USB communication driver 0.32 Oct 26 21:02:56 i7 upsdrvctl[1955]: Network UPS Tools - UPS driver controller 2.7.1 Oct 26 21:02:56 i7 upsd[2226]: fopen

Hi again, > On Sep 8, 2016, at 10:05 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> > wrote: >> Now that's a problem. I am not sure that I can find >> >> 1) the original software >> 2) a (physical) windows machine in the vicinity of the UPS >> Ha! I jumped several hooks but I think I got it. 01. I contacted the store that sold us the UPS and

Hallo group, I am running openSUSE 10.3 with nut-2.2.0-20 installed. I have configured it as mentioned in /usr/share/doc/packages/nut/README.SUSE. on starting nut using "rcupsd start" i get following: # Starting NUT UPS monitor done Broadcast Message from root at pane (somewhere) at 22:27 ... Communications with UPS myups at localhost

On Mon, 29 Sep 2014, Norbert Preining wrote: > Hi Alan, > > sorry for the journalctl output. I have now done the following:L > > * boot into 3.17-rc7 > * mount the usb stick (recovery completed) > * unmount, mount, unmount - just to be sure all is fine > * started usbmon capturing on bus 3 > * mount the usb stick > * suspend to ram > * wake up > now the

I here is some information I could have provided previously. Here is what I am seeing: ==================================================================== Broadcast message from nut at localhost.localdomain (Fri May 13 22:31:35 2016): UPS myups at localhost on battery upsc myups at localhost battery.charge: 3 battery.charge.low: 10 battery.charge.warning: 30 battery.runtime: 93

On 10/14/2015 12:18 PM, Roger Price wrote: > Is there any command in the list provided by "upscmd -l myups" which is accepted > by this UPS? None of the command sin the list successfully completes, not even beeper.toggle. My list: # upscmd -l myups Instant commands supported on UPS [myups]: beeper.toggle - Toggle the UPS beeper load.off - Turn off the load

Hi Charles; I think its not working yet even though I seem to be getting only one error, but I cannot seem to get upsmon to output the current ups status. So, since I cannot find any manpages (is that a separate package, if so I did not see it in the repo.) about the only error I can get out of it is that it is not listening on localhost:3493. Yet that is specified in the conf files: ene

I have a Dell PE 2850 connected via 940-0024C cable to serial port on the UPS mentioned above. I've used apt-get to install nut-2.0.2-3 and attempted to configure based on the documentation. So far I'm getting the following when I try to start ups daemon: server:/etc/ups # /etc/init.d/ups start Starting service NUT: -> Starting UPS driver: Network UPS Tools - UPS driver controller

On Wed, 14 Oct 2015, Davide Baldini wrote: > upsdrvctl shutdown > ... > instcmd(shutdown.return, [NULL]) > instcmd: FAILED > Shutdown failed! > Driver failed to start (exit status=1) > > This time /var/log/syslog doesn't register anything about the UPS after > issuing the command above. Instead, It logged some errors after a > upscmd -u admin -p mypass

After updating from NUT 2.0.3 to 2.0.5 I got this error from upsd during startup: Can't connect to UPS [myups] (myups): No such file or directory The problem was that newhidups created a pipe on /var/run/nut/newhidups-auto while upsd was looking for /var/run/nut/myups. The solution to the problem was to add the option "-a myups" to the newhidups command line in the init script.