Displaying 20 results from an estimated 2000 matches similar to: "NUT Installation Issue"
2020 Oct 31
1
NUT Installation Issue
upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
Fatal error: 'maxretry' is not a valid variable name for this driver.
Look in the man page or call this driver with -h for a list of
valid variable names and flags.
||/ Name Version Architecture Description
2020 Oct 31
0
NUT Installation Issue
On Oct 30, 2020, at 3:00 PM, bobby <architectofthefuture at gmail.com> wrote:
>
> I installed NUT on my raspberry pi. I've been following this tutorial: https://melgrubb.com/2016/12/11/rphs-v2-ups/. I am trying to use NUT to monitor my cyberpower UPS. I seem to have this problem though: upsc cyberpower at localhost Init SSL without certificate database Error: Driver not
2023 Jan 13
1
Problem with Multiple USB UPSs, including multiple apparent CyberPower
Trying to configure multiple UPS on one Raspberry Pi 4 (Bullseye).
Issue: Whenever more than one is plugged in, one shows as all - as in "upsc
x" for all of them shows identical information for one UPS rather distinct
for each plugged in.
OS:
/proc/version = "Linux version 5.10.103-v7l+ (dom at buildbot)
(arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld
(GNU
2020 Sep 03
3
Moving Spam to Junk Folder
I am following this tutorial:
https://www.linuxbabe.com/redhat/spamassassin-centos-rhel-block-email-spam.
I followed the steps in "Move Spam into the Junk Folder". When I send an
email from a blacklisted e-mail address, I get a bounce e-mail from my
e-mail server. Here is what is in my spamass-milter file:
EXTRA_FLAGS="-m -r 8 -R NO_SPAM -i 127.0.0.1 -g sa-milt --
2020 Nov 01
4
ups.test.result meaning
On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com> wrote:
> I'm going to guess that since your test runtime of 305 is very close to
> the low limit of 300, that's the warning. Not yet a fail, but very, very
> close.
>
I tried setting
override.battery.runtime.low = 60
in ups.conf, and waited for the UPS to reach 100% charge, and ups.status to
report only
2020 Oct 31
2
ups.test.result meaning
Hi folks, new to list...
nut 2.7.2 on Ubuntu 16.04 with Cyberpowersystems CP1350PFCLCD.
After performing upscmd cp1350 at localhost test.battery.start.quick the
result was "Done and warning". I searched through syslog but could find no
additional information.
What is the warning?
Battery charge was 100% before test was performed.
Here's the full output from upsc after test:
2024 Nov 09
1
NUT stopped working after an upgrade
Nut should be running as user nut. As far as I can tell, the udev rules
have not changed. And the system IS seeing the UPS at a low level.
I looked through /dev/ but did not see a device that jumps out as the UPS.
=====================
[root at mythtv rules.d]# dmesg | grep -i 0764
[ 2.021485] usb 1-1.8: New USB device found, idVendor=0764,
idProduct=0501, bcdDevice= 0.01
[ 2.049515]
2024 Nov 09
1
NUT stopped working after an upgrade
Running NUT version 2.8.2 on Fedora 40. NUT installed from the Fedora
package. CyberPower CP1000AVRLCD connected by USB.
I updated the system yesterday with all the latest Fedora packages. Now
NUT will not run. Chasing the issue through the layers, I come to this:
=====================
[root at mythtv rules.d]# upsc cyberpower
Error: Driver not connected
[root at mythtv rules.d]#
2024 Nov 09
1
NUT stopped working after an upgrade
Did the upgrade by chance install/alter any udev rules causing the UPS devices to now have incorrect permissions? And what user is nut running as?
On November 9, 2024 9:58:57 AM EST, Bill Gee <bgee at campercaver.net> wrote:
>Running NUT version 2.8.2 on Fedora 40. NUT installed from the Fedora package. CyberPower CP1000AVRLCD connected by USB.
>
>I updated the system yesterday
2024 Nov 10
2
NUT stopped working after an upgrade
Check /dev/hidraw6, as noted in your dmesg output (and any other *hid* devices under /dev). User nut has almost zero privs to devices unless a udev rule changes the perms on the dev for nut . . .
On November 9, 2024 1:25:29 PM EST, Bill Gee <bgee at campercaver.net> wrote:
>Nut should be running as user nut. As far as I can tell, the udev rules have not changed. And the system IS
2005 Oct 23
1
Nut setup with CyberPower AVR900
Hello,
I'm a new to NUT and I'm having some setup problems.
Here's my setup:
Nut 2.0.2
Gentoo Linux 2.6.13-r3
CyberPower AVR900
According to the hardware compatibility guide this setup should work.
Here's what I get:
root@gentoo (0) [552] % upsdrvctl start
Network UPS Tools - UPS driver controller 2.0.2
Network UPS Tools - CyberPower driver 1.00 (2.0.2)
2016 Jan 02
2
Please review my smb.conf
Hi Rowland
> (just a thought, you have given the Samba server a fixed ipaddress,
> hostname and domain name, haven't you ?).
The Pi has a fixed IP address and hostname. I see:
$ cat /etc/hostname
RPHS
$ cat /etc/resolv.conf
# Generated by resolvconf
nameserver 208.67.222.123
nameserver 208.67.220.123
So the DNS seems arbitrary. I don't understand what the DNS should be for a
2011 Nov 30
2
Patch for addition of Cyberpower RMCARD100, 201, 202, 301 (snmp mib)
I did a bunch of work on this today. It should be all set to go.
This patch is to add support for the Cyberpower RMCARD snmp cards.
I basically copied the driver for bestpower, changed the name and
updated the mib map.
I have this running on two separate systems (two separate ups's) and it
looks good.
The only thing I could not figure out was updating the Makefile.am (my
aclocal/libtools
2006 Nov 15
1
CyberPower PR2200
Hi, guys.
I have a new CyberPower PR2200 which I'm trying to control using NUT. It
has a serial port and I'm connected serially. I am using the cyberpower
driver and before a power failure it seems to mostly be working:
jeff@backup:~$ upsc cyberpower@localhost
battery.charge: 000
driver.name: cyberpower
driver.parameter.port: /dev/ttyS0
driver.version: 2.0.4
driver.version.internal: 1.00
2024 Feb 21
1
System keeps going into FSD mode after power on
Hello,
I am a new user of NUT and trying to wrap my ahead around a couple of
things. I installed NUT 2.7.4-13 from package on RasPi 4, running Raspbian
Linux 11 (bullseye). I have Cyberpower SL700U connected to it. For testing
I set battery.charge.low to 90, so I wouldn't have to wait a long time. See
all relevant config below.
First of all, what seems to happen is that UPS gets to the low
2005 Oct 19
4
Cyberpower CP550SL/AE550 Serial
Is anyone working on anything to support the Cyberpower CP550SL/AE550
Serial? Any idea if it uses the same or similar protocol as the other
Cyberpower models?
I have an HP 4952A Serial Protocol Analyzer and a Cyberpower CP550SL.
Once I get the CP550SL up and working in Windows over RS232 I'll hook up
the 4952A and see whats going on. I'm not sure what it uses for default
baud rate.
2007 Apr 13
2
Problem with GeekSquad GS-1500 (Cyberpower 1500 avr lcd)
Hi,
I've installed Nut 2.0.5 on a RedHat 9 box.
I have a GeekSquad 1500 UPS. (GeekSquad is a BestBuy brand) I've found out
that
it's actually a CyberPower 1500 AVR LCD.
I'm using it with the serial cable.
I'm unable to get it working with any of the drivers provided with NUT.
I've tried cpsups, cyberpower and powerpanel.
here's the output of the different drivers
2007 Nov 28
4
CyberPower 1500AVRT won't load driver!
Hello! I got my hands on a CyberPower 1500AVRT, and i'm trying to get it
connected to my Gentoo machine.
I've followed all the basic guides on setting up NUT and UPS' but have had
no luck.
My current ups.conf is:
[cyberpower-gentoo]
driver = cyberpower
port = /dev/ttyS0
desc = Workstation
Upon running /etc/init.d/upsd start or upsdrv start I get:
* Starting
2015 Dec 13
2
Windows 7 can't see Pi Samba server
On 13/12/15 09:36, DavidA wrote:
> Hi
>
> Here's some more info about my problem:
>
> ==========================================
>
> log.nmbd contains:
>
> Samba name server RPHS is now a local master browser for workgroup
> HOME on subnet 192.168.2.8
>
> *****
> [2015/12/12 20:48:19.709456, 0]
>
2007 Oct 11
1
CyberPower CPS1500AVR (rack mount) options
This unit works fine with the "cyberpower" driver (which reports it as
"Unknown model - 15"). It reads this much from it:
battery.charge : 100
driver.name : cyberpower
driver.parameter.pollinterval : 2
driver.parameter.port : /dev/ttyS0
driver.version : 2.2.0-
driver.version.internal : 1.00
input.frequency : 60.2
input.voltage : 121
ups.firmware : 5.100