similar to: Powerware 5119 = Exide NETUPS SE = Deltec name was PowerRite Pro II

Displaying 20 results from an estimated 100 matches similar to: "Powerware 5119 = Exide NETUPS SE = Deltec name was PowerRite Pro II"

2008 Dec 23
2
Exide NetUPS SE (aka Powerware 5119 etc)
My UPS is an Exide NetUPS SE PRC1500i (1500 VA), also known as Powerware 5119, according to Karl Schmidt (http://lists.alioth.debian.org/pipermail/nut-upsuser/2005-July/000026.html) also Deltec PowerRite Pro II, and according to http://www.usedups.de/compaq_ups.html also Compaq R3000h. I am not sure if the information in http://www.bps.hu/powerware/model_en.html is to be interpreted as that it was
2008 Dec 23
2
Exide NetUPS SE (aka Powerware 5119 etc)
My UPS is an Exide NetUPS SE PRC1500i (1500 VA), also known as Powerware 5119, according to Karl Schmidt (http://lists.alioth.debian.org/pipermail/nut-upsuser/2005-July/000026.html) also Deltec PowerRite Pro II, and according to http://www.usedups.de/compaq_ups.html also Compaq R3000h. I am not sure if the information in http://www.bps.hu/powerware/model_en.html is to be interpreted as that it was
2011 Feb 22
1
Hardware compatibiltiy list -- NetUPS
Hallo, I own a NETUPS 450 (Model on the sticker: PRM 450i; upsstats reports "UPS 450 VA FW -0024") which perfectly works with the upscode2 driver. Maybe you want to add it to your list, even if the model is >10 years old. I suppose this is true for the whole series. According manual the come in the 450VA, 700VA, 1000VA and 1500VA strengths. They have been sold under different
2005 Dec 29
1
Deltec PRA1500 UPS and FC4
I recently bought new batteries for this old "Compaq" Deltec PRA 1500 ups and downloaded LanSafe3 and haven't had much luck communicating with the UPS via a serial cable. Does anyone out there have a manual on this UPS? Or has anyone else gotten this to work with LanSafe3 and/or upsd? Any help would be greatly appreciated! Jon Moss __________________________________
2024 Dec 04
1
XCP documentation?
Once again, I am attempting to refine NUT support for my older (Eaton)Powerware Prestige 9 UPS units. The issue is that the BCMXCP driver currently in NUT, optimistically assumes that everything in the XCP protocol document (C1 - as in the NUT archives) is available on all units, and that (even stated in the doc) is not the case.? For instance, the "Extended" block is stated to have
2006 Feb 04
1
Old Contact UPS Info
I tried to find a search button for the mailing list but could not. So rtfm me with the link please. If not.. I have an old Deltec PowerRite Pro 2 UPS which has a 9 pin serial cable. By trial and error Im pretty sure I found LB = DCD, but can not get the combination for OB / OL. No matter what I do I get the results below. driver.name: genericups driver.parameter.CP: CTS driver.parameter.LB:
2020 Jan 26
1
Timer doesn't appear to start
I have a Raspberry PI that I have connected to a Deltec UPS via serial (upscode2 driver). I had an older version of Rasbian running. The nut configuration worked fine but I had mail issues I couldn't resolve when gmail changed how it handled MTAs. Plus it was running an old version of Deb that is no longer supported. It was broken enough I could not upgrade to a never version so I started from
2005 Nov 07
0
deleteing e-Mail, quota and dovecot
Hi, we run a RHEL4 E-Mail-Server with dovecot-0.99.11-2.EL4.1. we use mbox and most users use imap. So I have set quota for the devices where the user mailfiles are saved. No I'm getting the situation, that users exide there quota but yet not the grace limit and the user isn't able to delete messages. e.g. the the soft limit is 100 MB, the hard limit is 110 MB. So there should be
2020 Jan 27
1
Timer doesn't appear to start
Here is the output root at nutpi:/etc/nut# ps -elf | grep -E '[n]ut|ups[dms]' 4 S avahi 246 1 0 80 0 - 1472 poll_s Jan26 ? 00:00:31 avahi-daemon: running [nutpi.local] 1 S nut 451 1 0 80 0 - 678 poll_s Jan26 ? 00:03:41 /lib/nut/upscode2 -a deltec-PRA1500 1 S nut 454 1 0 80 0 - 1173 poll_s Jan26 ? 00:00:28 /lib/nut/upsd 1
2020 Jan 27
3
Nut-upsuser Digest, Vol 175, Issue 32
Here are my permissions and user info. Let me know if there is anything else I should check pi at nutpi:~ $ ls -alt /etc/nut total 56 drwxr-xr-x 87 root root 4096 Jan 26 15:22 .. drwxr-xr-x 2 root nut 4096 Jan 26 13:53 . -rw-r----- 1 root nut 4719 Jan 26 13:15 upssched.conf -rw-r----- 1 root nut 15347 Jan 26 11:25 upsmon.conf -rw-r----- 1 root nut 1543 Jan 26 10:02 nut.conf -rw-r-----
2020 Jan 28
0
Timer doesn't appear to start
One last update. I needed to log out and in to get the group add of my user nutmon to be recognized. My permissions are now root:nut on upssched.conf and it works. On Tue, Jan 28, 2020 at 7:00 AM <nut-upsuser-request at alioth-lists.debian.net> wrote: > Send Nut-upsuser mailing list submissions to > nut-upsuser at alioth-lists.debian.net > > To subscribe or unsubscribe
2020 Jan 28
1
Timer doesn't appear to start
The time and upssched-cmd are now working. Here are the issues I had: 1) Did not define NOTIFYCMD in upsmon.conf Added NOTIFYCMD /sbin/upssched 2) Added +EXEC to NOTIFYMSG rules I am using 3) Change ownership of upssched.conf to my nut user nutmom. I had added nutmon to the group nut but it didn't work. Thanks again for all your guidance On Tue, Jan 28, 2020 at 7:00 AM
2020 Jan 28
0
Timer doesn't appear to start
If you look closer at: > pi at nutpi:~ $ sudo ls -alt /home/nutmon > total 32 > -rw------- 1 nutmon nutmon 172 Jan 26 12:32 .bash_history > drwxrwx--- 2 nutmon nutmon 4096 Jan 26 12:32 upssched there is a d in the first position of the upssched permissions showing this is a directory. This is the directory location for PIPEFN and LOCKFN as defined in
2020 Jan 27
0
Timer doesn't appear to start
I only pasted a subset of my upsmon.conf. NOTIFYCMD is in my upsmon.conf AFA nutmon user. I was trying different things I had the directory as nutmon nut but changed it to nutmon nutmon to see if that worked. It didn't make a difference. Sorry about the digest this. I needed to hit a line in gmail web client to see the subject line. Know I know. Thanks for the heads up.. [root at donner
2020 Jan 27
1
Nut-upsuser Digest, Vol 175, Issue 30
Roger, here is my output of ps -elf |grep upssched root at nutpi:~# ps -elf |grep upssched 0 S root 1242 1191 0 80 0 - 1834 pipe_w 05:23 pts/0 00:00:00 grep upssched No timer, just the grep of upssched.. On Mon, Jan 27, 2020 at 4:27 AM <nut-upsuser-request at alioth-lists.debian.net> wrote: > Send Nut-upsuser mailing list submissions to >
2007 Apr 04
3
Compaq T2400H UPS model 242688-006
Hi, I have a Comapq T2400H model 242688-003 and do not have the special cable to connect it to my serial port. I have tried all sorts of cable wirings that I found on the net, including ones for the powerware 5119 which appears to be the same model. I have read the documentation that comes with NUT, tried to read the source code and looked at the genericups code too.? I have
2015 Jun 08
2
UPower: 95-upower-hid.rules update
2015-06-08 13:09 GMT+02:00 Bastien Nocera <hadess at hadess.net>: > On Mon, 2015-06-08 at 10:13 +0200, Arnaud Quette wrote: > > -ATTRS{idVendor}=="06da", ENV{UPOWER_VENDOR}="Liebert" > > > > +ATTRS{idVendor}=="06da", ENV{UPOWER_VENDOR}="Phoenixtec Power Co., Ltd" > > I'm guessing this would require changes in NUT, so I
2010 Mar 03
1
using upscode2 driver with Powerware 5119 RM
I've got a Powerware 5119 RM UPS. driver.list says to use "genericups upstype=20", however I know this UPS supports the UPS Code II protocol, so I wanted to use the upscode2 driver. It took some hacking but finally it works. I'm using NUT 2.4.1 and upscode2 driver version 0.87 (however the latest r2350 version of upscode2.c isn't significantly different, so I think all
2012 May 12
2
NUT for Windows + Eaton/PW 5110
Nut for Windows 2.6.3-3 + Eaton/PW 5110 (103004256-5591). I had to manually install libusb driver and I'm using bcmxcp_usb. upsd.exe is reporting to me "Out of memory". It will run, but once anything connects to the daemon, it dies with that message. I don't have much experience with NUT yet so I'm not sure what the next course of action is. I do have NUT for Windows
2013 Mar 18
0
[linux-linus test] 17325: regressions - trouble: broken/fail/pass
flight 17325 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17325/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl 9 guest-start fail REGR. vs. 12557 test-amd64-i386-xl-credit2 15 guest-stop fail REGR. vs. 12557 test-amd64-i386-xl 15 guest-stop