similar to: SMART3000RM2U?

Hello list, I am a pretty green Linux admin managing 3 ROCKS CentOS clusters total about 2,000 cores. My predecessor set up NUT for me on the primary head node. We have about 42 Tripplite UPS units in the room. The way our power systems work I intend to use the NUT connected head node to shut down the entire server room any time power is lost for over 30 seconds or so. It is about 95% likely that

I wouldn't be surprised if they both use the same driver. I think they are essentially the same model, but with one having a slightly larger battery. My issue is primarily with the UPS turning back on after having shut off like it should. @Scott Colby if you take a look at the config files I posted in the github issue I created, perhaps that will give you some hints on your issue. Maybe

Hi. I'm using nut with debian squeeze. When the computer boots and nut is loaded, I get the following messages: "Starting the hotplug events dispatcher: udevdudevd [451]: BUS= will be removed in a future udev version. please use SUBSYSTEM= to match the event device. or SUBSYSTEMS= to match a parent device. in /lib/udev/rules.d/52-nut-usb.rules:6 . Synthesizing the initial hotplug

Dear List, The driver usbhid-ups does not detect my MGE Ellipse 1500. I'm running openSuSE Linux 10.3, kernel 2.6.22 with mgeups-psp-3.0.4-2, nut-2.2.0-20 installed from MGE's rpm's. (Merci MGE!) lsusb shows: Bus 001 Device 004: ID 0463:ffff MGE UPS Systems UPS /etc/ups/ups.conf says: [myups] driver = usbhid-ups port = auto desc = "Local UPS"

On Sat, Jun 27, 2020, at 23:11, Manuel Wolfshant wrote: > On 6/28/20 5:54 AM, Scott Colby wrote: >> >> I'm not convinced this is the problem; I think that pfSense has an alternative way of running the NUT components: # ps aux | grep ups root 45456 0.0 0.1 6796 884 - Is 02:22 0:00.01 /usr/local/sbin/upsmon uucp 45751 0.0 0.1 6796 772 - S 02:22

On Apr 23, 2014, at 3:47 AM, Frantz de Germain wrote: > I've compiled and installed nut-2.7.2 on a Xen server (Actually XCP > 1.6/Centos 5.7) to manage a Dell UPS 2700W. > > Here is my ups.conf : > > [SU27003U-08] > driver = usbhid-ups > port = auto > desc = "SU27003U-08" > > 52-nut-usbups.rules have well been installed in

Hello list, I am configuring NUT on a Dell workstation that is connected to an APC Back UPS Pro 1300, and I am running into an issue where starting everything manually seems to be successful, but fails when using the init.d scripts. The short story is that I get the following error when trying to check the status of the UPS: [root at mypc:/etc/nut]# upsc apc_pro1300 at localhost Error:

Hello, I've compiled and installed nut-2.7.2 on a Xen server (Actually XCP 1.6/Centos 5.7) to manage a Dell UPS 2700W. Here is my ups.conf : [SU27003U-08] driver = usbhid-ups port = auto desc = "SU27003U-08" 52-nut-usbups.rules have well been installed in /lib/udev/rules.d/. I've put it in /etc/udev/rules.d/ too. I've rebooted the machine.

Hi all, Here's a brief history of my adventure: I purchased a CyberPower 685 AVR and decided to connect it through USB to my Gentoo linux machine running kernel 2.6.22. While the device was detected properly and added to /dev, it was added with the wrong permissions (gid was set to 'usb' instead of 'nut', as it was expected to be according to the rules under

Thanks for chiming in @David Zomaya. Tripp Lite replaced my AVRX550U once thinking that the powering back on was a defective unit, but the replacement does the same thing. The SN on the first one is 2935AVHOM87BB00152. NUT has my model listed as protocol 2010, so that needs to be corrected to 2012, but I'm not sure if anyone is doing active development on it right now. I also have a

G'day, all! It's my second trouble with NUT. Latest nut-2.6.1.tar.gz installed from source on Xenserver 5.6 SP2, UPS is Powercom WOW--500U FW3.A4 (USB). Problem with setting permissions for udev (described in /etc/udev/rules.d/52-nut-usbups.rules file): ACTION!="add|change", GOTO="nut-usbups_rules_end" don't work for me. Only when I changed ACTION to:

Hello. I have this UPS: Krauler UP-D1200VA Megatec USB protocol Vendor ID: 0x0001, Device ID: 0x0000 #KRAULER UP-D1200VA VER6.00 #220.0 004 23.50 50.0 Currently I have nut 2.2.0 installed from sources. Installation was successful except that I had to change a string in 52-nut-usbups.rules from: SUBSYSTEM!="usb_device", GOTO="nut-usbups_rules_end" to:

Thought I'd follow up in case someone else runs into this issue. In the end what worked for me was tweaking the udev rules. I have had no USB disconnects or stale data warnings so far. I only used one rule for my UPS: # /etc/udev/rules.d/62-nut-usbups.rules SUBSYSTEM!="usb", GOTO="nut-usbups_rules_end" # TrippLite # e.g. TrippLite SMART1500LCD - usbhid-ups

https://bugzilla.samba.org/show_bug.cgi?id=7618 Summary: symlinks and --link-dest Product: rsync Version: 3.0.7 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: the_majkl at seznam.cz QAContact:

Has anyone gotten this model of tripp-lite to work? sudo /usr/local/bin/upsdrvctl -DDDDD -u root start Network UPS Tools - UPS driver controller 2.0.5 Starting UPS: tripplite exec: /usr/local/bin/tripplite_usb -a tripplite Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.7 (2.0.5) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: TRIPP

I'm trying to set up a single host to monitor the state of several UPS in my data center. I have a mix of several APC and Tripp-Lite in production. The former are great, the latter are not so much. With the APCs (using usbhid-ups), I can set up configs for each based on the value they report from ups.serial. With the Tripp-Lites (using tripplite_usb), there is no value returned for

Hi We have been trying back-up a glusterfs (v3.1.4) area using the Tivoli TSM software to an off-site area. The back-up keeps failing with the following typical error messages 06/14/2011 22:22:58 ANS1587W I/O error reading file attributes for: /gdata/projects/philex/OAG/2011/May16/mdor3km10/coast_den2.in. errno = 22, Invalid argument 06/14/2011 22:22:59 ANS4007E Error processing

Hi! I am using SAMBA 3.5.x and it doesn't work with IBM TSM. IBM TSM works properly with SAMBA 3.2.15. Is there any chance to solve this issue in future SAMBA versions? Best regards /Adrian Berlin -- You Rock! Your E-Mail Should Too! Signup Now at Rock.com and get 2GB of Storage! http://connections.rock.com/user/displayUserRegisterPage.kickAction?as=116748&STATUS=MAIN

On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: >> Don't worry about the battery physical properties for now - the >> problem there is that we don't have enough information from the UPS >> to do a proper calculation. With the V_interval[] settings, you can >> tweak the new state-of-charge calculation to match what you see via >> upsc when the battery is

Hello, I own an older Tripp Lite SMART3000RM2U (protocol 3003). It does not work with usbhid-ups but it mostly works with the tripplite_usb driver (nut 2.7.1, the latest in the Gentoo tree), in the sense that the status (on line, on battery, etc.) is detected correctly, the machine is shut down on critical battery, and I can even get some information from the UPS. This is how it all looks: