unbound did not start automatically after reboot
FritzS - gmx
fritzs at gmx.net
Wed Sep 30 10:36:01 PDT 2015
The resolution:
Before I used in unbound.conf
interface: 127.0.0.1
interface: <ethernet - local IP address>
Now I use
# listen on all interfaces, answer queries from the local subnet.
interface: 0.0.0.0
interface: ::0
and it works well now, probably with specific IP and Little Snitch firewall unbound runs in a timeout and hangs in undefined state.
With the ‚joker‘ IP this timeout is not effective.
> Am 08.09.2015 um 17:03 schrieb FritzS - gmx <fritzs at gmx.net>:
>
>
>> Am 08.09.2015 um 03:40 schrieb Ryan Schmidt <ryandesign at macports.org>:
>>
>>
>> On Sep 6, 2015, at 7:56 AM, FritzS wrote:
>>
>>> David, Ryan,
>>> who is the unbound specialist?
>>
>> I've never used unbound.
>>
>>> My in MacPorts installed unbound did not start automatically after reboot.
>>> But it seems to run, but not listed in the process list
>>> If I want to start
>>> $ sudo port load unbound
>>> /opt/local/etc/LaunchDaemons/org.macports.unbound/org.macports.unbound.plist: Operation already in progress
>>>
>>> So I must
>>> $ sudo port unload unbound
>>> $ sudo port load unbound
>>>
>>> Seldom it starts after reboot. My guess, the start command for unbound comes to early in the OS X startup.
>>>
>>> Why I could set a waiting time in the
>>> org.macports.unbound.plist
>>
>> I'm not aware of a way to set a waiting time in a plist.
>>
>> I believe you can set dependencies on some things, like indicating that a plist requires the network be up, or that it should be restarted if the network connection changes?
>
> I must search for this code or code samples.
>
>>
>> One reason why a launchd plist might not work at startup is if your ports are actually installed on a second volume, not on the startup disk. Is that the case?
>>
>
> I use only one volume. My guess the startup of the ethernet port coming to late or the application firewall Little Snitch unblocking the DNS ports to late at startup.
>
> My suggestion - unbound should start after network connection is OK and Little Snitch is running up.
>
> Fritz
>
More information about the macports-users
mailing list