similar to: APC SmartUPS 2200XL + UDEV + USB = tcgetattr : Invalid argument

The nut ups daemons seem to be communicating with the UPS but upscmd gives me no joy. Running commands do nothing and produce no output. Using the web interface returns an authentication failure and that is the only clue I have. I believe I have everything setup correctly but it's not working. Can someone review this and give me clues as to what I should research next?

I am migrating from Fedora 8 to CentOS 5.2 I have usb dvd On F8 I have /etc/udev/rules/00-my-custom.rules BUS=="scsi", SYSFS{vendor}=="TSSTcorp", SYSFS{model}=="CDDVDW SH-S203N ",SYMLINK="dvd",OWNER="rray" When I plug in dvd I get $ ll /dev/scd1 lrwxrwxrwx 1 root root 3 Aug 25 08:17 /dev/scd1 -> sr1 ll /dev/sr1 brw-r----- 1 rray disk 11, 1

2009/5/3 Thomas Juerges > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Arnaud, > Hi Thomas, > I just checked the 2.4.1 version of nut and found that you forgot to add > my old UPS model (APC Smart-UPS 900). I guess it is because you were > busy at the time when I sent you the patch. So here it goes again. :) > uh, right sorry. I was pretty sure I applied

We recently had to replace an old APC SmartUPS 3000 with a newer 3000VA (the 2U one). It has both serial and USB in the back (with an RJ-45 on the end of the serial cable). I can't get the apcsmart driver to connect. I figured it should work the exact same as the old UPS, with /dev/ttyS0 as the port (I'm using the same port on the server that the last one was plugged into). I even

Hey guys, I built my own 940-0024C cable as described here: http://www.networkupstools.org/cables/940-0024C.jpg My problem is that I can't receive anything. Sending (e.g. through minicom or my own application) works fine. Nut itself is not able to detect My UPS or anything else. <snip> [myups] driver = apcsmart port = /dev/ttyS0 cable = 940?0024C # also tested without cable option

Hi All, I've got two APC SmartUPS's that behave differently with nut, I have a SmartUPS1400 & a SmartUPS1250. I'm fairly sure this isn't a nut problem but more likely a problem with the age of the SmartUPS1250 and the apcsmart driver not being able to identify it. Under the APC Powerchute software the same monitoring & command parameters are available for both

I have a SmartUPS 750 (SUA750) which has the temperature and humidity SmartSlot card installed. When NUT 2.2 communicates with this UPS over /dev/ttyS0 using apcsmart, using the APC Smart cable connected to the SUA750 serial port, and this ups.conf: [su700] driver=apcsmart port = /dev/ttyS0 I can see the ambient temperature and humidity data with "upsc su700 at

Hello One our customer has two Linux HP-branded servers powered from "clasic" APC Smart-UPS 2200 RM 2U (p/n SUA2200RMI2U). It is connected to first server via RS232c port with APC-branded cable. We have installed NUT 2.6.4 with apcsmart driver. This setup works fine for months. Two weeks ago all the hardware powered from the UPS started to switch off occasionally while on line

I'm trying to setup a server controlling 8 ups, 6 APC Smartups 1500 and two 1000. Because of the number of ups, i connected them using usb cables. I'm using Debian Etch AMD64 and nut 2.2.0 from testing (already tried 2.0 from stable, but had problems reading the ups serials and all the following problems of 2.2). This is my ups.conf: [ups2] driver = usbhid-ups port =

Hej! Hope nut-upsuser is an appropriate place to post additional info about the smartups protocol, please tell me if not. I got an APC Smartups 2200 (5U Rack Mount, European/230V version, 48V batteries) a couple of days ago, was very happy to find the protocol description at http://www.networkupstools.org/protocols/apcsmart.html, and started to play. At the point when everything was working

check_hotplug fails on one of my machines running ubunto 4.10 "Warty Warhog", due to misparsing the udevinfo version string. The problem is caused by an old version of sed that does not appreciate the regexp. This patch fixes it, and also works on debian unstable and SLES9SP2. Please apply... Signed-Off-By: Muli Ben-Yehuda <mulix@mulix.org> Signed-Off-By: Orna Agmon

I have 2 video devices LML33 and PV155 $ lspci 06:00.0 Multimedia video controller: Zoran Corporation ZR36057PQC Video cutting chipset (rev 02) 07:08.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) 07:08.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) 07:09.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture

Dear nut users, I am running nut-2.6.0 on Slackware-Linux-13.37.0 with kernel 2.6.37.6. I am trying to get the software work for a repotec UPS with model name: RPT-1003AU. The UPS communicates with the computer via USB. I know that the model is not officially supported but I want to try out whether it will work with some of the repotec drivers. Here is the result with the genericups upstype=13

On Sep 11, 2014, at 9:48 PM, Stan Gammons <sg063015 at gmail.com> wrote: > I have an APC USB UPS that was working on OpenBSD 5.5 with NUT 2.7.1 When I installed the latest 5.6 snapshot with NUT 2.7.2 the UPS no longer sends status messages when it loses line power. I asked over on the OpenBSD ports list and so far haven't had any luck getting this to work again. I disabled upd at

On Tue, Jan 27, 2004 at 10:54:31PM +0100, Olaf Hering wrote: > On Tue, Jan 27, Olaf Hering wrote: > > > On Tue, Jan 27, Kay Sievers wrote: > > > > > On Tue, Jan 27, 2004 at 09:06:51PM +0100, Olaf Hering wrote: > > > > udevinfo writes to fd 0, all the output is lost somehow. > > > > > > > > olaf@ibook:~> i="`/sbin/udevinfo

We are configuring a server with a Tripplite SmartUPS, Web SNMP Card, and Envirosense Probe. The configuration is good using usbhid driver and we can get it to shutdown clean by producing a "power event" (pull the power cable). It is not very clear how to add or see the values associated with the external probe. We need to be able to shutdown based on the input from the probe as well as

On 09/11/14 21:43, Charles Lepple wrote: > On Sep 11, 2014, at 9:48 PM, Stan Gammons <sg063015 at gmail.com> wrote: > >> I have an APC USB UPS that was working on OpenBSD 5.5 with NUT 2.7.1 When I installed the latest 5.6 snapshot with NUT 2.7.2 the UPS no longer sends status messages when it loses line power. I asked over on the OpenBSD ports list and so far haven't had

On Tue, 8 Oct 2013, Philip Tait wrote: > Here is the upsc output: > > # /usr/local/ups/bin/snmp-ups -DD -a irs2-ups1 > Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) > 0.000000 debug level is '2' > 0.000327 SNMP UPS driver : entering upsdrv_initups() [snip] > 4.457750 No supported device detected I'm using a APC smart ups with a

Bonjour, Je fais suite au message que vous avez post? en 2015 : http://lists.alioth.debian.org/pipermail/nut-upsuser/2015-February/009568.html J'ai le m?me probl?me et ne trouve pas la solution. Comment vous en ?tes-vous sorti ? D'avance, merci pour votre aide. -- Cordialement Herv? BASTET Nouveau num?ro non surtax? 01 69 42 87 94 Ce message est prot?g? par les r?gles relatives au

OS: CentOS 7 NUT Version: 2.7 Installed NUT through: yum install nut UPS: APC smart UPS srt3000 with NMC I am trying to set up NUT with snmp for my apc ups. Heres the config; [ups6]                 Driver = snmp-ups                 Port: ups6.domain.name (also tried 192.168.24.9)                 Snmp_version = v3                 secLevel = authPriv                 secName = ups6