New NUT install dealing with three APC Smart-UPS 5000s, two of which
have AP9617 and the third has a AP9619 card.
The SNMPv3 configurations on all three are exactly the same. This is
confirmed by snmpget calls that work just fine:
snmpget -Cf -v3 -u [...] -l authPriv -A '[...]' -X '[...]'
The start-up result is done.
Dec 04 10:17:52 [redacted] systemd[1]: Unit nut-driver.service is not
needed anymore. Stopping.
I have a feeling that if I do get this working by setting huge timers
I'm just cargo-culting a "fix".
nomad
On 12/4/17 09:38 , Lee Damon wrote:
> Hi Charles
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.
3/17 14:34 , Charles Lepple wrote:
> On Nov 30, 2017, at 6:31 PM, Lee Damon <no...@ee.washington.edu> 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 _on
>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
6 matches
Mail list logo
