search for: comok

...ries to start multiple drivers). I've even seen it take multiple tries for the very first driver. Even with the extended timeouts it has failed to start on one reboot out of three. 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 the master host and a bunch more such messages from upsmon on my test clients. The time between BAD and OK is almost always 5 seconds (I presume this is the retry timer setting). Oddly enough, the complaint times on the test clients don't always match up with the complaint times...

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 the master > host and a bunch more such...

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. /etc/systemd/system/nut-driver.service.d/nut-driver.conf [Unit] StopWhenUnneeded=no [Service] TimeoutSec=600