>How close do the EPEL RPM's systemd configuration files look to the
ones in the NUT tree?
The only difference between /lib/systemd/system/nut-driver.service and
the one
atÂ
https://github.com/networkupstools/nut/blob/v2.7.2/scripts/systemd/nut-driver.service.in
(not counting variable
One thing I just noticed, all of the COMBAD and COMOK messages are about
the same UPS, the other two seem to be fine.
nomad
On 12/5/17 08:24 , Lee Damon wrote:
...
> I suspect there's a deeper problem here. This morning I came in to 22
> emails about COMBAD and 22 emails about COMOK from upsmon
On Dec 4, 2017, at 2:43 PM, Lee Damon wrote:
>
> I have it "working" with the following settings changes from the default
> in the RPM. By "working" I mean it starts after reboot and after issuing
> 'sudo systemctl restart nut-driver' but, as expected, it takes quite a
>
I have it "working" with the following settings changes from the default
in the RPM. By "working" I mean it starts after reboot and after issuing
'sudo systemctl restart nut-driver' but, as expected, it takes quite a
while to finish startup.
I've told systemd to wait up to 10 minutes for startup but it's still
failing. Sometimes it fails with "timeout exceeded" and sometimes with
the ASN error previously reported.
I went back to running upsdrvctl -D to see if I could see anything. On
the third run I saw messages about "startup timer
Hi Charles,
Running upsdrvctl -D start on the host with all three configured to
SNMPv3 kicks out 56 different "unhandled ASN 0x81 from ..." lines on all
three but importantly they all start up and keep running.
I'm starting to suspect the startup is taking so long that systemd is
timing out and
On Nov 30, 2017, at 6:31 PM, Lee Damon wrote:
>
> SNMPv3 works fine when I have any one of the three configured in
> ups.conf while the other two are configured with SNMPv1. It doesn't
> matter which _one_ UPS is configured for SNMPv3 in ups.conf, they all
> work
7 matches
Mail list logo