Aha!! Bingo, that resolved the issue for upsd. You may not have picked
iut up Bill but the new "error" message shows it.
Going back to your message from yesterday, upsd logged this:
Dec 01 10:35:01 mythtv.billgee.local nut-server[3445]: fopen
/var/run/upsd.pid: No such file or directory
Dec 0
Bill Gee writes:
However - The only reason I noticed is because I set up logwatch to include
output from upsc in the daily report. When that went missing, I went
hunting. If I did not have that daily logwatch, I would never have
noticed. It would not surprise me if a lot of people are ha
FWIW, this and other recent discussions led to a few PRs and investigative
issues about paths and PIDs and signals - so here's some reading for your
enjoyment:
* https://github.com/networkupstools/nut/pull/1724
* https://github.com/networkupstools/nut/issues/1721
* https://github.com/networkupstool
My thoughts ...
First, this is only a problem in Fedora 37. On Fedora 36 it works.
Second, Fedora 37 has only been out for about three weeks. I bet
adoption is still ramping up.
Third - A good point about many people using laptops and so not needing
a UPS. Even so, there are millions of s
Oops, sorry about missing your test two. I did not read it all the way
through.
That test is done, and nut-server starts successfully. Upsc will give
back information about the device. I did have to run a daemon-reload.
It does complain about not finding the PID file.
On 12/2/22 07:59, Sam Varshavchik wrote:
Roger Price writes:
On Thu, 1 Dec 2022, Sam Varshavchik wrote:
And even now, weeks after a Fedora release, that bug is not blowing
up with everyone, and their uncle, complaining that nut is completely
non-functional? So, what, there are less than a do
On 12/2/22 03:32, Roger Price wrote:
On Thu, 1 Dec 2022, Sam Varshavchik wrote:
Simon Wilson via Nut-upsuser writes:
I'm just looking forward to a set of RH/Fedora packages which are not
borked out of the box.
I'm not sure what's going on with that. Looking through that package,
it was buil
Roger Price writes:
On Thu, 1 Dec 2022, Sam Varshavchik wrote:
And even now, weeks after a Fedora release, that bug is not blowing up with
everyone, and their uncle, complaining that nut is completely non-
functional? So, what, there are less than a dozen people out there who are
using Fed
Hi Bill,
OK your test 1 and 2 line up with my ask for test 1 :)
Have another read of the Test 2 ask please if you can:
2. Second test:- copy the edited
/etc/systemd/system/nut-driver@.service.d/environ.conf to
/etc/systemd/system/nut-server.service.d/environ.conf. So you
should at that po
Test 1 - I moved the environ.conf file to /tmp. I ran systemctl
daemon-reload, then restarted nut-driver@cyberpower.service. Results:
=
[root@mythtv nut-driver@.service.d]# systemctl restart
nut-driver@cyberpower.service
Job for nut-driver@cyberpower.servic
On Thu, 1 Dec 2022, Sam Varshavchik wrote:
Simon Wilson via Nut-upsuser writes:
I'm just looking forward to a set of RH/Fedora packages which are not
borked out of the box.
I'm not sure what's going on with that. Looking through that package, it was
built back in September, long before Fedor
11 matches
Mail list logo
