FINALLY! It occurred to me to try this:
[root@seveneves ups]# journalctl -u nut-driver@seveneves-ups
Apr 27 09:16:34 seveneves.gregandeva.net systemd[1]: Starting
nut-driver@seveneves-ups.service - Network UPS Tools - device driver for
NUT device 'seveneves-ups'...
Apr 2
Once upon a time, Greg Woods said:
> Looks like I spoke too soon; I noticed that the nut-monitor service had
> stopped running. I restarted it, and:
NUT is a bit of a bear to get configured, but as far as the systemd
portion, I only have nut.target enabled. It looks like that pulls in
a
On Thu, Apr 27, 2023 at 9:38 AM Greg Woods wrote:
>
> On the positive side, the repetitive error:
> Apr 26 12:49:09 seveneves.gregandeva.net nut-monitor[326253]: Poll UPS
> [seveneves-ups@localhost] failed - Driver not connected
>
> is no longer happening
>
Looks lik
Thanks to Jeff and Robert for the hint about the nut-driver-enumerator
service. This is indeed new with F37; I looked at the F36 RPM and there is
no nut-driver-enumerator.service file. On the F37 system the service file
is there but it is disabled by default. I enabled it and rebooted, but it
did
On 4/26/23 18:30, Greg Woods wrote:
Since upgrading to F37, I am having problems getting Nut to work properly. The
errors I get from the journal are:
Apr 26 17:01:42 seveneves.gregandeva.net <http://seveneves.gregandeva.net>
nut-server[326151]: Can't connect to UPS [seveneves-ups]
On Wed, Apr 26, 2023 at 7:30 PM Greg Woods wrote:
>
> Since upgrading to F37, I am having problems getting Nut to work properly.
> The errors I get from the journal are:
>
> Apr 26 17:01:42 seveneves.gregandeva.net nut-server[326151]: Can't connect to
> UPS [seveneves-ups
Sorry for any confusion, my bad. The subject line should read "F37 and
NUT", consistent with the Fedora versions mentioned in the original post.
--Greg
On Wed, Apr 26, 2023 at 5:30 PM Greg Woods wrote:
> Since upgrading to F37, I am having problems getting Nut to work properly.
&
Since upgrading to F37, I am having problems getting Nut to work properly.
The errors I get from the journal are:
Apr 26 17:01:42 seveneves.gregandeva.net nut-server[326151]: Can't connect
to UPS [seveneves-ups] (usbhid-ups-seveneves-ups): No such file or directory
Apr 26 17:
On 3/30/22 9:24 AM, Roger Heflin wrote:
nut-server seems to connect to the device and tie up its port.
It appears upower only accesses the device every so often and queries it.
So then once nut-server is started upower cannot open the device again.
It comes down to you cannot really have 2
nut-server seems to connect to the device and tie up its port.
It appears upower only accesses the device every so often and queries it.
So then once nut-server is started upower cannot open the device again.
It comes down to you cannot really have 2 separate software stacks managing
any single
I'm running Fedora 34 on three Linux systems that are connected to USB
UPSes. I have installed NUT (Network UPS Tools) on all three.
If I connect with nut-server stopped, upower detects the UPS:
# upower -d
Device:
/org/freedesktop/UPower/de
On Thursday 07 January 2016 17:40:51 Gordon Messmer wrote:
>
> Start with:
> chown -v nut:nut /var/run/nut
> restorecon -v /var/run/nut
>
> What do those commands output?
I did have to manually set up /var/run/nut and set the permissons as the RPM
install didn't do that.
to the UPS.
Your answer helps in no way whatsoever, but thanks anyway.
It does seem that nut is a bit of a problem to install
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of C
On 01/07/16 12:14, Gary Stainburn wrote:
> Hi folks,
>
> I'm trying to get NUT installed on an existing F19 server which sits beside
> my
> shiney new APC SmartUPS. It's connected using a serial cable on ttyS0.
If its an APC UPS, shouldn't you be using apcupsd i
On Thu, 2016-01-07 at 17:14 +, Gary Stainburn wrote:
> However, none of the instructions relate to F19 and even after
> making allowances I still can't get it to work.
F19 is obsolete and unsupported, including for security patches. You
really should be running at least F22, especially on a se
I've just bought a Powercool UPS from my local supplier as it seemed a very
good price for my needs - 1 headless server for home automation etc.
However, I can't get it to work with NUT. Google hasn't returned anything
useful.
I've checked (too late) the hardware compati
Duplicate driver instance detected! Terminating other driver!
Using subdriver: MGE HID 1.31
The "Duplicate driver instance" is a pretty strong hint that
something else has grabbed the device. Before starting nut you might
see if udev saw the UPS and started something for you (perhaps not
: MGE HID 1.31
The "Duplicate driver instance" is a pretty strong hint that something else has
grabbed the device. Before starting nut you might see if udev saw the UPS and
started something for you (perhaps not what you wanted).
lsusb - should identify the USB connection
lsof - may be ab
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/13/2013 03:45 PM, Patrick Dupre wrote:
> Hello,
>
> I am trying to have my UPS OK. After a lot of efforts I am at a point where
> I get:
>
>
> Dependency failed for Network UPS Tools - power devices information
> serv
Hello,
I browsed around to see how I could interface nut,
Several project but nay for Fedora:
nut-monitor
wmnut
python-pynut
PyNut
gknut
knutclient
knutsetting!!
Nut-Graph!!
ups_control!!
mgeops!!
Any comment or suggestion are welcome.
Thank
Hello,
Complementary information:
upsdrvctl start
responds as:
Network UPS Tools - UPS driver controller 2.6.5
Network UPS Tools - Generic HID driver 0.37 (2.6.5)
USB communication driver 0.31
Duplicate driver instance detected! Terminating other driver!
Using subdriver: MGE HID 1.31
nut
Hello,
I am trying to have my UPS OK.
After a lot of efforts I am at a point where I get:
Dependency failed for Network UPS Tools - power devices information server.
-- Subject: Unit nut-server.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo
On Tue, 2012-08-21 at 09:05 -0500, Aaron Konstam wrote:
> I don't know where this fear of updating BIOS comes from.
There's the chance of a foul-up during the process, leaving you with a a
dead, and unresurrectable PC. As a failsafe, some PCs have two BIOS
memories, where you can switch over to a
On Tue, 2012-08-21 at 09:00 -0500, Aaron Konstam wrote:
> On Tue, 2012-08-21 at 01:33 -0400, Chuck Peters wrote:
> >
> > Configured nut as I have with Ubuntu, same machine, and enabled
> > startup on F17... So why isn't it starting?
> >
> > [root@fedora tmp
On Tue, 2012-08-21 at 01:33 -0400, Chuck Peters wrote:
>
> Configured nut as I have with Ubuntu, same machine, and enabled
> startup on F17... So why isn't it starting?
>
> [root@fedora tmp]# systemctl enable nut-server.service
> ln -s '/usr/lib/systemd/system
Configured nut as I have with Ubuntu, same machine, and enabled startup on
F17... So why isn't it starting?
[root@fedora tmp]# systemctl enable nut-server.service
ln -s '/usr/lib/systemd/system/nut-server.service'
'/etc/systemd/system/multi-user.target.wants/nut-server.servi
26 matches
Mail list logo
