Thank you for taking the time to file a bug report. I don't have a remote UPS readily available to test, so I did my best to set up nut locally (using its dummy.dev interface) inside a Focal container, and then set MODE=netclient in the nut.conf file. I could not reproduce the bug you reported. nut-driver.service did not start:
Oct 28 20:06:03 bla systemd[1]: Stopping Network UPS Tools - power device driver controller... Oct 28 20:06:03 bla upsdrvctl[13898]: Network UPS Tools - UPS driver controller 2.7.4 Oct 28 20:06:03 bla dummy-ups[13896]: Signal 15: exiting Oct 28 20:06:03 bla systemd[1]: nut-driver.service: Succeeded. Oct 28 20:06:03 bla systemd[1]: Stopped Network UPS Tools - power device driver controller. I thought it was because the dummy.dev trick was interfering with the test, so I fired up a Groovy container, and configured it to connect to the Focal container by editing /etc/nut/upsmon.conf like: MONITOR dummy-dev1@10.101.133.205 1 monuser pass master Then, I configured the Focal container with MODE=standalone (so that the server would start and accept connections), and the Groovy container as MODE=netclient. This time, nut-driver simply failed to start, but that's because I did not configure anything else other than /etc/nut/upsmon.conf: Oct 28 20:09:59 nut-bug1901659 upsdrvctl[1543]: Error: no UPS definitions found in ups.conf Oct 28 20:09:59 nut-bug1901659 upsdrvctl[1543]: Network UPS Tools - UPS driver controller 2.7.4 Oct 28 20:09:59 nut-bug1901659 systemd[1]: Starting Network UPS Tools - power device driver controller... Oct 28 20:09:59 nut-bug1901659 systemd[1]: nut-driver.service: Control process exited, code=exited, status=1/FAILURE Oct 28 20:09:59 nut-bug1901659 systemd[1]: nut-driver.service: Failed with result 'exit-code'. Oct 28 20:09:59 nut-bug1901659 systemd[1]: Failed to start Network UPS Tools - power device driver controller. Which seems OK-ish to me. In other words, I could not replicate the 90-second timeout you mentioned in the report by doing these local tests. For the reasons I explained above, I am marking this bug as Incomplete. I would also like to request more information from you: your configuration files (without the passwords, of course) would be helpful in trying to understand your setup and what might be causing this timeout. Since there is not enough information in your report to begin triage or to differentiate between a local configuration problem and a bug in Ubuntu, I am marking this bug as "Incomplete". We would be grateful if you would: provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: nut (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901659 Title: nut-driver attempts to start when mode=netclient in nut.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1901659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
