F38 and NUT

[Greg Woods]

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:01:42 seveneves.gregandeva.net upsd[326151]: Can't connect to UPS
[seveneves-ups] (usbhid-ups-seveneves-ups): No such file or directory

Apr 26 17:24:00 seveneves.gregandeva.net nut-monitor[326253]: Poll UPS
[seveneves-ups@localhost] failed - Driver not connected

All I could find on the net suggested that "Driver not connected" means I'm
using the wrong driver, but this is the identical configuration (including
the driver) that worked in F36. It's also a nearly identical configuration
that is still working for an identical UPS unit monitored from a Raspberry
Pi running Raspbian.

Any Nut gurus here that could help me troubleshoot this, and has anyone
else seen Nut quit working on F37 using a configuration that worked with
F36?

Here's what I have in my config files:

nut.conf:MODE=netserver
ups.conf:[seveneves-ups]
ups.conf:       driver = "usbhid-ups"
ups.conf:       port = "auto"
ups.conf:       vendorid = "0463"
ups.conf:       productid = "FFFF"
ups.conf:       product = "Ellipse PRO"
ups.conf:       serial = "P344L44127"
ups.conf:       vendor = "EATON"
ups.conf:       bus = "001"
ups.conf:        maxretry=3
upsd.conf:LISTEN 192.168.1.56 3493
upsd.conf:LISTEN 127.0.0.1 3493
upsmon.conf:MONITOR seveneves-ups@localhost 1 upsmon <redacted password>
master
upsmon.conf:MINSUPPLIES 1
upsmon.conf:SHUTDOWNCMD "/sbin/shutdown -h +0"
upsmon.conf:POLLFREQ 5
upsmon.conf:POLLFREQALERT 5
upsmon.conf:HOSTSYNC 15
upsmon.conf:DEADTIME 15
upsmon.conf:POWERDOWNFLAG /etc/killpower
upsmon.conf:RBWARNTIME 43200
upsmon.conf:NOCOMMWARNTIME 300
upsmon.conf:FINALDELAY 5

Thank you,
--Greg

[Greg Woods]

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.
> 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:01:42 seveneves.gregandeva.net upsd[326151]: Can't connect to
> UPS [seveneves-ups] (usbhid-ups-seveneves-ups): No such file or directory
>
> Apr 26 17:24:00 seveneves.gregandeva.net nut-monitor[326253]: Poll UPS
> [seveneves-ups@localhost] failed - Driver not connected
>
> All I could find on the net suggested that "Driver not connected" means
> I'm using the wrong driver, but this is the identical configuration
> (including the driver) that worked in F36. It's also a nearly identical
> configuration that is still working for an identical UPS unit monitored
> from a Raspberry Pi running Raspbian.
>
> Any Nut gurus here that could help me troubleshoot this, and has anyone
> else seen Nut quit working on F37 using a configuration that worked with
> F36?
>
> Here's what I have in my config files:
>
> nut.conf:MODE=netserver
> ups.conf:[seveneves-ups]
> ups.conf:       driver = "usbhid-ups"
> ups.conf:       port = "auto"
> ups.conf:       vendorid = "0463"
> ups.conf:       productid = "FFFF"
> ups.conf:       product = "Ellipse PRO"
> ups.conf:       serial = "P344L44127"
> ups.conf:       vendor = "EATON"
> ups.conf:       bus = "001"
> ups.conf:        maxretry=3
> upsd.conf:LISTEN 192.168.1.56 3493
> upsd.conf:LISTEN 127.0.0.1 3493
> upsmon.conf:MONITOR seveneves-ups@localhost 1 upsmon <redacted password>
> master
> upsmon.conf:MINSUPPLIES 1
> upsmon.conf:SHUTDOWNCMD "/sbin/shutdown -h +0"
> upsmon.conf:POLLFREQ 5
> upsmon.conf:POLLFREQALERT 5
> upsmon.conf:HOSTSYNC 15
> upsmon.conf:DEADTIME 15
> upsmon.conf:POWERDOWNFLAG /etc/killpower
> upsmon.conf:RBWARNTIME 43200
> upsmon.conf:NOCOMMWARNTIME 300
> upsmon.conf:FINALDELAY 5
>
> Thank you,
> --Greg

[Jeffrey Walton]

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] (usbhid-ups-seveneves-ups): No such file or directory
> Apr 26 17:01:42 seveneves.gregandeva.net upsd[326151]: Can't connect to UPS [seveneves-ups] (usbhid-ups-seveneves-ups): No such file or directory
>
> Apr 26 17:24:00 seveneves.gregandeva.net nut-monitor[326253]: Poll UPS [seveneves-ups@localhost] failed - Driver not connected
>
> All I could find on the net suggested that "Driver not connected" means I'm using the wrong driver, but this is the identical configuration (including the driver) that worked in F36. It's also a nearly identical configuration that is still working for an identical UPS unit monitored from a Raspberry Pi running Raspbian.
>
> Any Nut gurus here that could help me troubleshoot this, and has anyone else seen Nut quit working on F37 using a configuration that worked with F36?
>
> Here's what I have in my config files:
>
> nut.conf:MODE=netserver
> ups.conf:[seveneves-ups]
> ups.conf:       driver = "usbhid-ups"
> ups.conf:       port = "auto"
> ups.conf:       vendorid = "0463"
> ups.conf:       productid = "FFFF"
> ups.conf:       product = "Ellipse PRO"
> ups.conf:       serial = "P344L44127"
> ups.conf:       vendor = "EATON"
> ups.conf:       bus = "001"
> ups.conf:        maxretry=3
> upsd.conf:LISTEN 192.168.1.56 3493
> upsd.conf:LISTEN 127.0.0.1 3493
> upsmon.conf:MONITOR seveneves-ups@localhost 1 upsmon <redacted password> master
> upsmon.conf:MINSUPPLIES 1
> upsmon.conf:SHUTDOWNCMD "/sbin/shutdown -h +0"
> upsmon.conf:POLLFREQ 5
> upsmon.conf:POLLFREQALERT 5
> upsmon.conf:HOSTSYNC 15
> upsmon.conf:DEADTIME 15
> upsmon.conf:POWERDOWNFLAG /etc/killpower
> upsmon.conf:RBWARNTIME 43200
> upsmon.conf:NOCOMMWARNTIME 300
> upsmon.conf:FINALDELAY 5

I recall seeing something similar in the past. In the past, the
problem was related to nut-driver-enumerator.service. The enumerator
service did not run, so there was nothing for the NUT driver to
connect to.

The solution was systemctl enable nut-driver-enumerator.service.

Someone made the comment it was a bug in Fedora's packaging.

Also see https://github.com/networkupstools/nut/issues/1851#issuecomment-1439224990

Jeff

[Greg Woods]

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 not fix my problem. The enumerator service appears to run:

[root@seveneves mythtv]# systemctl status nut-driver-enumerator
Apr 27 09:16:33 seveneves.gregandeva.net systemd[1]: Starting
nut-driver-enumerator.service - Network UPS Tools - enumeration of
configure-file devices into systemd unit instances...
Apr 27 09:16:33 seveneves.gregandeva.net nut-driver-enumerator[466627]:
Error reading the list of systemd service instances for UPS drivers, or
none are defined - before manipulations
Apr 27 09:16:33 seveneves.gregandeva.net nut-driver-enumerator[466627]: Thu
Apr 27 03:16:33 PM UTC 2023 : Detected changes in global section of
'/etc/ups/ups.conf', will restart all drivers
Apr 27 09:16:33 seveneves.gregandeva.net nut-driver-enumerator[466627]: OK
Apr 27 09:16:33 seveneves.gregandeva.net nut-driver-enumerator[466627]:
Adding new systemd service instance for power device [seveneves-ups]...
Apr 27 09:16:33 seveneves.gregandeva.net nut-driver-enumerator[466673]:
Created symlink
/etc/systemd/system/nut-driver.target.wants/[e-mail]
→ /usr/lib/systemd/system/nut-driver@.service.
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]:
Enabled instance: 'nut-driver@seveneves-ups' for NUT configuration section
'seveneves-ups'
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]:
Adding 'Wants'+After dependency for 'seveneves-ups' on
'systemd-udev.service systemd-udev-settle.service'...
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]: OK
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]: OK
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]:
Started instance: 'nut-driver@seveneves-ups' for NUT configuration section
'seveneves-ups'
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]: ===
The currently defined service instances are:
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]:
seveneves-ups
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]: ===
The currently defined configurations in '/etc/ups/ups.conf' are:
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]:
seveneves-ups
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]: Thu
Apr 27 03:16:34 PM UTC 2023 : OK: No more changes to reconcile between
systemd service instances and device configurations in '/etc/ups/ups.conf'
Apr 27 09:16:34 seveneves.gregandeva.net systemd[1]:
nut-driver-enumerator.service: Deactivated successfully.
Apr 27 09:16:34 seveneves.gregandeva.net systemd[1]: Finished
nut-driver-enumerator.service - Network UPS Tools - enumeration of
configure-file devices into systemd unit instances.
Apr 27 09:17:54 seveneves.gregandeva.net systemd[1]: Starting
nut-driver-enumerator.service - Network UPS Tools - enumeration of
configure-file devices into systemd unit instances...
Apr 27 09:17:54 seveneves.gregandeva.net nut-driver-enumerator[467256]: Thu
Apr 27 03:17:54 PM UTC 2023 : OK: No changes to reconcile between systemd
service instances and device configurations in '/etc/ups/ups.conf'
Apr 27 09:17:54 seveneves.gregandeva.net systemd[1]:
nut-driver-enumerator.service: Deactivated successfully.
Apr 27 09:17:54 seveneves.gregandeva.net systemd[1]: Finished
nut-driver-enumerator.service - Network UPS Tools - enumeration of
configure-file devices into systemd unit instances.

But I still get the same error:

[root@seveneves ups]# upsc seveneves-ups@localhost
Error: Driver not connected
[root@seveneves ups]# systemctl status nut-server
● nut-server.service - Network UPS Tools - power devices information server
     Loaded: loaded (/usr/lib/systemd/system/nut-server.service; enabled;
preset: disabled)
     Active: active (running) since Thu 2023-04-27 09:20:04 MDT; 9min ago
   Main PID: 1716 (upsd)
      Tasks: 1 (limit: 38356)
     Memory: 884.0K
        CPU: 13ms
     CGroup: /system.slice/nut-server.service
             └─1716 /usr/sbin/upsd -F

Apr 27 09:20:04 seveneves.gregandeva.net nut-server[1716]: listening on
127.0.0.1 port 3493
Apr 27 09:20:04 seveneves.gregandeva.net nut-server[1716]: not listening on
192.168.1.56 port 3493
Apr 27 09:20:04 seveneves.gregandeva.net upsd[1716]: listening on 127.0.0.1
port 3493
Apr 27 09:20:04 seveneves.gregandeva.net nut-server[1716]: Can't connect to
UPS [seveneves-ups] (usbhid-ups-seveneves-ups): No such file or directory
Apr 27 09:20:04 seveneves.gregandeva.net nut-server[1716]: Running as
foreground process, not saving a PID file
Apr 27 09:20:04 seveneves.gregandeva.net upsd[1716]: not listening on
192.168.1.56 port 3493
Apr 27 09:20:04 seveneves.gregandeva.net upsd[1716]: Can't connect to UPS
[seveneves-ups] (usbhid-ups-seveneves-ups): No such file or directory
Apr 27 09:20:04 seveneves.gregandeva.net upsd[1716]: Running as foreground
process, not saving a PID file
Apr 27 09:25:04 seveneves.gregandeva.net nut-server[1716]: Can't connect to
UPS [seveneves-ups] (usbhid-ups-seveneves-ups): No such file or directory
Apr 27 09:25:04 seveneves.gregandeva.net upsd[1716]: Can't connect to UPS
[seveneves-ups] (usbhid-ups-seveneves-ups): No such file or directory

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, and I'm not getting continuous broadcast
("wall") messages either, so it may actually be monitoring, but something
is clearly not right and  I still can't get a status report:

[root@seveneves ups]# upsc seveneves-ups@localhost
Error: Driver not connected

I will need to go through the rather lengthy discussion that Jeff linked to
and see if I can find further clues there.

--Greg

On Wed, Apr 26, 2023 at 9:06 PM Jeffrey Walton  wrote:
> 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] (usbhid-ups-seveneves-ups): No such file or
> directory
> > Apr 26 17:01:42 seveneves.gregandeva.net upsd[326151]: Can't connect to
>
> UPS [seveneves-ups] (usbhid-ups-seveneves-ups): No such file or directory
> > Apr 26 17:24:00 seveneves.gregandeva.net nut-monitor[326253]: Poll UPS
>
> [seveneves-ups@localhost] failed - Driver not connected
> > All I could find on the net suggested that "Driver not connected" means
>
> I'm using the wrong driver, but this is the identical configuration
> (including the driver) that worked in F36. It's also a nearly identical
> configuration that is still working for an identical UPS unit monitored
> from a Raspberry Pi running Raspbian.
> > Any Nut gurus here that could help me troubleshoot this, and has anyone
>
> else seen Nut quit working on F37 using a configuration that worked with
> F36?
> > Here's what I have in my config files:
> >
> > nut.conf:MODE=netserver
> > ups.conf:[seveneves-ups]
> > ups.conf:       driver = "usbhid-ups"
> > ups.conf:       port = "auto"
> > ups.conf:       vendorid = "0463"
> > ups.conf:       productid = "FFFF"
> > ups.conf:       product = "Ellipse PRO"
> > ups.conf:       serial = "P344L44127"
> > ups.conf:       vendor = "EATON"
> > ups.conf:       bus = "001"
> > ups.conf:        maxretry=3
> > upsd.conf:LISTEN 192.168.1.56 3493
> > upsd.conf:LISTEN 127.0.0.1 3493
> > upsmon.conf:MONITOR seveneves-ups@localhost 1 upsmon <redacted
>
> password> master
> > upsmon.conf:MINSUPPLIES 1
> > upsmon.conf:SHUTDOWNCMD "/sbin/shutdown -h +0"
> > upsmon.conf:POLLFREQ 5
> > upsmon.conf:POLLFREQALERT 5
> > upsmon.conf:HOSTSYNC 15
> > upsmon.conf:DEADTIME 15
> > upsmon.conf:POWERDOWNFLAG /etc/killpower
> > upsmon.conf:RBWARNTIME 43200
> > upsmon.conf:NOCOMMWARNTIME 300
> > upsmon.conf:FINALDELAY 5
>
> I recall seeing something similar in the past. In the past, the
> problem was related to nut-driver-enumerator.service. The enumerator
> service did not run, so there was nothing for the NUT driver to
> connect to.
>
> The solution was systemctl enable nut-driver-enumerator.service.
>
> Someone made the comment it was a bug in Fedora's packaging.
>
> Also see
> https://github.com/networkupstools/nut/issues/1851#issuecomment-1439224990
>
> Jeff
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Greg Woods]

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 like I spoke too soon; I noticed that the nut-monitor service had
stopped running. I restarted it, and:

Apr 27 09:52:26 seveneves.gregandeva.net nut-monitor[11136]: Poll UPS
[seveneves-ups@localhost] failed - Driver not connected

This is being logged every 5 seconds. So I'm more-or-less back to square
one.

--Greg

[Chris Adams]

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
all the rest of the necessary bits.

The config files I have edited under /etc/ups are:

- nut.conf
  set "MODE=standalone"

- ups.conf
  add a section for the UPS

- upsd.conf
  add "LISTEN ::" (not needed for most, I'm monitoring UPS status remotely)

- upsd.users
  add a section for a monitoring user

- upsmon.conf
  add a MONITOR line for the UPS+user

F38 and NUT -- SOLVED

[Greg Woods]

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
[e-mail] - Network UPS Tools - device driver for
NUT device 'seveneves-ups'...
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver@seveneves-ups[466866]:
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver@seveneves-ups[466866]:
USB communication driver (libusb 1.0) 0.43
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver@seveneves-ups[466866]:
Fatal error: 'maxretry' is not a valid variable name for this driver.

So it seems that an edit to ups.conf was also needed. Commenting out the
maxtry line (which has been there literally for years) gets things working
again. Thanks again to Robert and Jeff for pointing me in the right
direction.

--Greg

[Robert Nichols]

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] (usbhid-ups-seveneves-ups): No such file or directory
> Apr 26 17:01:42 seveneves.gregandeva.net http://seveneves.gregandeva.net upsd[326151]: Can't connect to UPS [seveneves-ups] (usbhid-ups-seveneves-ups): No such file or directory

Do you have nut-driver-enumerator.service enabled?