Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    unbound fatal error

    Scheduled Pinned Locked Moved DHCP and DNS
    3 Posts 2 Posters 473 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      reggie14
      last edited by

      I've been running into intermittent internet drop outs since upgrading to 2.4.5. Looking through the logs, it looks like it is unbound failing. I see this line in my logs when it drops out:

      fatal error: Could not read config file: /unbound.conf. Maybe try unbound -dd, it stays on the commandline to see more errors, or unbound-checkconf
      

      Is this related to all the other unbound problems I'm seeing here? I have a custom setting for the Plex rebinding issue. And while I have pfBlockerNG installed, DNSBL is disabled. DHCP leases were getting registered in unbound, but I just disabled that based on the other posts I'm seeing around here.

      1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan
        last edited by

        Hi,

        What happens when you to what it suggested ?
        Stop unbound in the GUI (if needed).

        Console -> Oprtion 8, and :

        cd /var/unbound
        

        and

        ls -al
        

        To see what's in the unbound working directory. There must be a "unbound.conf" file, about 21xx bytes size.

        And finally

        unbound -dd -c /var/unbound/unbound.conf
        

        to start unbound manually. It will log important messages.
        Ctrl-C to stop it.

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        1 Reply Last reply Reply Quote 0
        • R
          reggie14
          last edited by

          Thanks!

          To be clear, manually restarting unbound in the pfSense webGUI seems to resolve the problem when this occurs. I looked at the contents of unbound.conf. It seems to be fine.

          Outside the workday I'll try stopping and manually starting unbound with the command above. However, I fully expect it will start up fine with no obvious errors, since that's what usually happens.

          This problem only pops up every week or so. Given that I've had DHCP registration turned on, that means unbound restarts several times per day, almost always successfully. I don't know what's going on in these rare cases where it doesn't.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.