Nut upsuser - Jul 2024 - Fedora 40 nut-server not starting at boot

Ha!  The secret sauce!  Thanks, Tim - This last bit has got my system 
working.

I had nut-server.service enabled and nut.target disabled.  I cannot tell 
you how they got to that state.  It might be the RPM, or more likely my 
messing around several months ago.  I do not remember ...

In any event, I added the network stuff to the Wants and After lines in 
the nut.target file, then disabled nut-server.service and enabled 
nut.target.  After reboot it is all working.  No more manual 
intervention.  Woot!

I wonder if this will get Rick's system running??

==============Bill Gee

On 7/29/24 16:45, Tim Dawson wrote:
> OK, looking at this on my RH8 test image . . .
> 
> The first thing that I note, is that the *only* thing that needed to be 
> set to "enabled" in systemctl (IE "systemctl enable
....") is the
> nut.target entry.
> 
> All else here are disabled, and "drug along" by nut.target which
ensures
> that they come up in sequence.
> 
> In nut.target I added to the "After" and "Wants" lines
thus to force it
> to wait until network startup is complete:
> 
> After=local-fs.target nut-driver.target nut-server.service 
> nut-monitor.service network.target network-online.target
> Wants=local-fs.target nut-driver.target nut-server.service 
> nut-monitor.service network.target network-online.target
> 
> This should cause nut.target to not run until the network is up, and it 
> will start the other nut modules accordingly.
[snip]

On Tue, Jul 30, 2024 at 7:10?AM Bill Gee <bgee at campercaver.net> wrote:
> I wonder if this will get Rick's system running??
>
Tim/Bill, I removed the nut pkg and deps, deleted the nut*.d dirs created
in /etc/systemd/system, then reinstalled nut.
I added the two network objects to Wants and After in system.target,
restored confs in /etc/ups, rebooted, and sure enough upsd and upsmon were
successfully started. Only caveat was there was no driver connected when
testing from remote with upsc cp1500 at host. I manually ran systemctl start
nut-driver-enumerator, tested again with upsc and got expected results.
Rebooted, tested again from remote and got expected results.

I'm going to update the RH Bugzilla entry with these findings.

Thank you all for your input and help, kudos to Tim and Bill for the
RH-specific insight!

Cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240730/a927d3c3/attachment.htm>