similar to: (no subject)

On Wed, Apr 1, 2009 at 10:54 PM, Lelsie Rhorer <lrhorer at satx.rr.com> wrote: > > Gentlemen, > > I am running a Tripp Lite OMNISV1500XL under NUT using the > tripplite_usb driver on a Debian "Lenny" Linux system. The platform is an > AMD Athlon 64 x 2 processor running kernel 2.6.26. The driver is up and > running, but there are several issues.

Leslie, This message is most appropriate for the NUT user list. I kept Rik Faith's and Nicholas Kain's copyright information because the tripplite_usb driver borrows heavily from the tripplite (serial) driver, but they are not responsible for the mess that I made in the USB driver. See below. On Dec 28, 2008, at 5:28 PM, Lelsie Rhorer wrote: > Gentlemen, > >

OK, can someone tell me what utterly moronic thing I am doing wrong? I have two roughly identical Linux system running NUT, and one works properly. The other almost does. The second system works well once everything is up, but after booting, the system does not have connectivity to the UPS. I have to manually run `upsdrvctl start backup`, `/etc/init.d/nut start`, and `upsd` to get NUT

Hello. I need some help. I was running uw-imap on my IMAP server (so I am using mbox email files), but I was having trouble with Outlook 2013, so I decided to move to dovecot. At first things were looking much better, except that most of my folders, other than the Inbox, were not showing up. I started changing both the dovecot configuration and the folder structure of my mail files,

Up until a few days ago, I had SAMBA running just fine on several different systems, but very recently on of the server has quit announcing itself to the newtwork. Smbd, nmbd, and winbindd are all running on the server, and the machines on the network can all still reach the shares on the system, but an attempt to browse for the server and its available shares from a client PC does not produce a

I have the same issue of incorrect output voltage being reported by usbhid-ups, as run on NAS4Free (FreeBSD). UPS is as shown below. There is a thread on this list from 2014 that has these same issues, apparently never addressed by any of the later usbhid-ups releases. I?m using 2.7.3. The value I am especially concerned with is the output voltage; if ANY thing should be right on the report, it?s

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

I recently purchased a Tripp Lite OmniSV1500XL and I've had no luck getting nut to work. # lsusb Bus 001 Device 001: ID 0000:0000 Bus 006 Device 002: ID 05e3:0702 Genesys Logic, Inc. USB 2.0 IDE Adapter Bus 006 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 007 Device 001: ID 0000:0000 Bus 004 Device 009: ID 09ae:0001 Tripp Lite Bus 004 Device

On 9/6/2014 12:47 PM, Charles Lepple wrote: > On Sep 6, 2014, at 12:39 PM, Leslie Rhorer <lrhorer at mygrande.net> wrote: > >> I made a number of hardware and software changes, including an upgrade to the latest software versions for that distro (Debian Wheezy), > > Can you be more specific about the changes? Well, I did an automated upgrade (apt-get upgrade), I changed

On Sep 6, 2014, at 12:39 PM, Leslie Rhorer <lrhorer at mygrande.net> wrote: > I made a number of hardware and software changes, including an upgrade to the latest software versions for that distro (Debian Wheezy), Can you be more specific about the changes? Key variables: * USB controller information (old and new hardware) * Kernel versions, for both working and non-working setups

Hi Leslie, 2014-09-29 17:14 GMT+02:00 Leslie Rhorer <lrhorer at mygrande.net>: > > I just did a fresh installation of Debian Jessie on one of my > servers, but NUT won't configure and install. When I try to install, I get > the following: > > Setting up nut-client (2.7.2-1+b2) ... > Job for nut-monitor.service failed. See 'systemctl status >

On Sep 6, 2014, at 4:16 PM, Leslie Rhorer <lrhorer at mygrande.net> wrote: > Oh, hey! That seems to have worked. I'm sure the UPS got plugged into a different port one of the (many) times the server was removed from the relay rack, and it was on a USB 3.0 port. I moved it to a 1.0 port and everything seems to be working just fine. The specifics of the motherboard and its USB

Hello. I have had NUT working for several years on my servers. Recently I made changes to the main server, where the UPS is local, and now upsd won't properly load there, which essentially disables the entire UPS shutdown system. I made a number of hardware and software changes, including an upgrade to the latest software versions for that distro (Debian Wheezy), although I did not

I just did a fresh installation of Debian Jessie on one of my servers, but NUT won't configure and install. When I try to install, I get the following: Setting up nut-client (2.7.2-1+b2) ... Job for nut-monitor.service failed. See 'systemctl status nut-monitor.service' and 'journalctl -xn' for details. invoke-rc.d: initscript nut-client, action "start" failed.

On December 2, 2018 7:29:38 PM GMT+02:00, raul <raulvior.bcn at gmail.com> wrote: >I have restored original configuration and enabled the ignorelb flag. I > >didn't point out in the original e-mail that after every poweroff the >battery percentage is reported at 40% instead of 100% and charges >slowly again to 100%. Maybe the UPS sends a LB event and shuts down

Hi All, I have what is probably a 12 year old (or older) Compaq R3000 UPS plugged into a FreeBSD 8 system running NUT version 2.6.5 This UPS contains a total of 16 batteries in 2 banks of 8, each battery is 6 volts and the bank produces 50 volts. The UPS monitors battery voltage and the battery charger in the UPS works like this. For about 2 days it will apply a charge/float/topping

Hi, I am sorry for possible offtopic as this question is not quite NUT-related but I cannot imagine any other place with people of such deep and intimate knowledge of UPS behavior. One day all of a sudden my APC Back-UPS RS 1000 refused to go online (green led) even though mains was connected. I used upsc to see what is going on, and ups.status was "OB DISCHRG", battery.charge was

Does anyone have disconnect supervision working on their TDM400P or X101P cards (to/from the telco)? Googling "telco disconnect supervision," I found the following description: http://mirror.lcs.mit.edu/telecom-archives/telecom-archives/TELECOM_Digest_Online/1559.html [cut] Re: How Do I Get "Kewlstart" From my Phone Company? Paul A Lee Tue, 24 Aug 2004 16:58:16 -0400 ... It

I connected two plain old telephones to FXS lines of a TDM400P (defined as fxoks in zaptel.conf), one of them dials the other with Dial(Zap/2), I talk to myself for a while, hang up either of the phones, and the phone that remains off-hook gets the congestion tone until it goes on-hook (at least as long as I've cared to wait). I don't have a voltmeter on the line, but if I'm hearing

Is the battery old? PbAc ones usually last for 2-3 years and then degrade. Should be a field-replaceable part. Some 20 years ago I had an APC BackUPS become a glorified power strip every few years, so when the wall power disappeared - load went down immediately. It was also beeping about battery replacement (but in the closet, was not often noticed quickly). This is also a way for you to check if