[Nut-upsuser] nut-server service fails to start at boot

[Daniel Shields]

Thanks Charles,

     Looks like setting LISTEN to 0.0.0.0 did the trick.  I use iptables so no worries on the filtering.

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

From: Charles Lepple<mailto:clepple at gmail.com>
Sent: Sunday, October 22, 2017 8:39 AM
To: Daniel Shields<mailto:GRUNGELIZARD9 at HOTMAIL.COM>
Cc: nut-upsuser at lists.alioth.debian.org<mailto:nut-upsuser at lists.alioth.debian.org>
Subject: Re: [Nut-upsuser] nut-server service fails to start at boot

On Oct 22, 2017, at 2:39 AM, Daniel Shields <grungelizard9 at hotmail.com> wrote:
>
> Oct 22 05:57:37 nut.tklapp.com upsd[341]: not listening on 192.168.213.189 port 3493
> Oct 22 05:57:37 nut.tklapp.com upsd[341]: not listening on 192.168.213.189 port 3493
> Oct 22 05:57:37 nut.tklapp.com upsd[341]: listening on 127.0.0.1 port 3493
> Oct 22 05:57:37 nut.tklapp.com upsd[341]: no listening interface available
>
I think you're hitting this race condition: https://github.com/networkupstools/nut/issues/393

Using the LISTEN directive to selectively ignore certain interfaces worked a lot better when 1) we didn't have to worry about interfaces being removed and added at runtime and 2) when NUT was guaranteed to start after all of the network interfaces were already up.

Can you just use "LISTEN 0.0.0.0"? If there is one particular interface you are excluding, can you handle that with firewall rules?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20171023/ec84b12a/attachment.html>