similar to: NUT loses communications with the UPS

I know, I know, this again :) The company I work for would like to use squid for proxy authentication purposes using NTLM, using a Windows 2008 R2 server as a DC. I've managed to setup samba/winbind to use ads and successfully joined the domain. Configured nsswitch.conf to lookup winbind entities (however I didn't touch PAM configuration, as I don't actually want the users to be able

I've noticed a weirdness in rsync. Let me explain it briefly with an example. Below is a test script: #!/bin/sh cat >rsyncd.conf <<EOF address = localhost use chroot = no hosts allow = localhost [from] path = /tmp/from read only = yes comment = r/o EOF RSYNC_CONNECT_PROG="rsync --address=localhost --config=rsyncd.conf --daemon" \ rsync -av --address=localhost

https://bugzilla.samba.org/show_bug.cgi?id=7514 Summary: Fix socketpair_tcp() 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: polatel at gmail.com QAContact:

I have an FC5 system with a powerware 5110 usb ups. The system seems to find the UPS ------------------------------ [root@b1 src]# lsusb Bus 004 Device 001: ID 0000:0000 Bus 003 Device 002: ID 0592:0002 Powerware Corp. Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 ------------------------------- [root@b1

Hello, Control HP R1500 G2 with nut via USB. Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-72-generic x86_64) nut V2.7.1 installed from repository /etc/nut/ups.conf [HPR1500] driver=usbhid-ups port=auto After dealing hours with this, hope this will help some : rename udev rule to higher priority and move it to its right location, reload udev rules mv /lib/udev/rules.d/52-nut-usbups.rules

Ok, I installed the ups, and installed nut, and /proc/bus/usb/devices says this T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=06da ProdID=0002 Rev= 0.01 S: Manufacturer=POWERWARE S: Product=Powerware UPS C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 20mA I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00

THE GOOD: NUT is able to communicate with my Powerware 5115A over USB using the bcmxcp_usb driver: ambient.temperature: 38 battery.charge: 99 battery.runtime: 9000 battery.voltage: 27.07 driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.2.1 driver.version.internal: 0.13 input.frequency: 50.34 input.voltage: 235 output.current: 0.0

On Jan 30, 2015, at 4:22 PM, Melvin Call <melvincall979 at gmail.com> wrote: > At this point I unplugged the UPS and plugged it into a different USP port, but > that did not change the above. Figuring this was likely a udev problem, I > created the following /etc/udev/rules.d/52-nut-usbups.rules (based on an example > on our database server, and changing the vendor and product

I've been using nut to manage a variety of smart and dumb UPS's for about a year now, so I've got no excuse for just subscribing to the list now. Except maybe that the debian-user lists provide plenty of reading material. Anyway, I recently updated a couple of boxes to 2.6.15 kernels from 2.4.x and got to learn fun things about udev. I'm happy to do a write up on a simple udev

These patches allow this device to function in nut.. diff --git a/trunk/drivers/tripplite-hid.c b/new/drivers/tripplite-hid.c index c36da98..dddd13c 100644 --- a/trunk/drivers/tripplite-hid.c +++ b/new/drivers/tripplite-hid.c @@ -71,6 +71,8 @@ static usb_device_id_t tripplite_usb_device_table[] = { { USB_DEVICE(TRIPPLITE_VENDORID, 0x2005), battery_scale_0dot1 }, /* e.g. TrippLite

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:

I have been testing out my new MGE Nova 1100 on a system (dual Athlon) running Fedora Core 5 and the newhidups driver seems to be regularly dying. The UPS is the USB model, I have nut-2.0.3-0.1.fc5 and nut-cgi-2.0.3-0.1.fc5 installed. I am running a 2.6.16 kernel. (I haven't upgraded to FC5's 2.6.17 kernel yet as there seem to be some complaints about it.) The driver initially works.

A couple of years ago, Arnaud helped me get my Apollo Line Interactive UPS working, using the blazer_usb driver. Now I've run into another problem, having rebuilt my HP Proliant Microserver into an ESXi 5.5 managed hypervisor with various VMs. One of the VMs is a FreeNAS server which manages the storage for the other VMs so graceful shutdowns are important. I built a single VM to monitor the

On Jun 10, 2019, at 2:32 PM, Marc Finns wrote: > > Hello, I read all FAQ and other sources but I could not find this situation, so I thought of asking the experts. > I successfully configured a Raspberry NUT server to control my UPS that powers several devices (NUC with ESXI VMs, Synology NAS etc). > All works well in principle, but I have the following behaviours that I could not

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

hi NUT 2.4.3 on new server can not see serial number, but old nut on different hardware can? I have 2 USB-hid ups from APC, 1500 and 3000 RM, i use the serial number to identify them. However my new UPS monitor server can not see the serial number? It works on Linux dkserver 2.6.22.18-vs2.2.0.6 #1 SMP Sat Feb 16 20:54:32 CET 2008 i686 GNU/Linux debian package 2.2.2-6.5 it does not work on

On 12/14/2013 09:04 PM, Charles Lepple wrote: >> Is there someway nut can be modified to probe the 0664 permission usb >> devices >>> and then connect as root before dropping permissions back to the "nut" >>> gid? > Given that the udev method should still work (and seems to, for handcrafted > udev rules files), I would like to run that to ground first.

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:

[please keep the list CC'd for future reference.] On Dec 4, 2013, at 1:10 AM, Danijel ?ili wrote: > Even if there is, I just checked and all of the rules have MODE=664. I had concerns that the MODE parameter might need an explicit leading "0" for octal, but at least in the latest code, it is being parsed with strtol(..., 8). > Also, I don't know how to check which rules

On 6/19/19 5:59 AM, Charles Lepple wrote: >> >> “The 62-nut-usbups.rules file looks pretty standard. Do you know if the changes to 42-usb-hd-pm.rules are needed? It seems like none of the USB devices would have the right permissions if 62-nut-usbups.rules isn't sufficient (though this happened in Debian once).” >> >> My means of testing wasn’t the most rigorous,