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/nut-driver@seveneves-ups.service → /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