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

    Unbound server will not start

    Scheduled Pinned Locked Moved DHCP and DNS
    15 Posts 6 Posters 5.7k 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.
    • P Offline
      phil.davis
      last edited by

      Forum: https://forum.pfsense.org/index.php?topic=89925.0
      This was a regression in Unbound 1.5.2
      I am surprised you saw the problem in 2.2-RELEASE - I thought it was only in some 2.2.1-DEVELOPMENT snapshots.

      It is fixed with Unbound 1.5.3 which is in pfSense 2.2.1-RELEASE - upgrade to 2.2.1-RELEASE and all your problems go away :)

      As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
      If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

      1 Reply Last reply Reply Quote 0
      • R Offline
        RomanHelmet
        last edited by

        @hypnoticpancake:

        the first one is basically saying the service isn't running, the pid file gets created when it starts up.

        The second error is saying you dont have an unbound user which is what should be running the unbound daemon.

        can you verify that you have the following files:
        /usr/local/sbin/unbound
        /var/unbound/unbound.conf

        and then check /etc/passwd for your unbound user should look like this:

        unbound:*:59:59:Unbound DNS Resolver:/var/unbound:/usr/sbin/nologin

        Both of those files exist.  In my passwd file there is no unbound user.

        @phil.davis:

        Forum: https://forum.pfsense.org/index.php?topic=89925.0
        This was a regression in Unbound 1.5.2
        I am surprised you saw the problem in 2.2-RELEASE - I thought it was only in some 2.2.1-DEVELOPMENT snapshots.

        It is fixed with Unbound 1.5.3 which is in pfSense 2.2.1-RELEASE - upgrade to 2.2.1-RELEASE and all your problems go away :)

        I updated to 2.2.1 yesterday before I made this post. It still didn't work after the upgrade which is what prompted me to post here.

        1 Reply Last reply Reply Quote 0
        • V Offline
          vsilgalis
          last edited by

          you might want to try opening a bug report around it.  It looks like unbound is all there but the user wasn't created sometime in the past, so you could try creating the user (no guarantee it will work and run it at your own risk):
          pw adduser unbound -g unbound -d /var/unbound -s /usr/sbin/nologin -c "Unbound DNS Resolver"

          1 Reply Last reply Reply Quote 0
          • D Offline
            doktornotor Banned
            last edited by

            Is this a full install? Any fsck log entries in system log?

            1 Reply Last reply Reply Quote 0
            • R Offline
              RomanHelmet
              last edited by

              Yes, full x86 install.

              You'll have to forgive me, I'm very green with bsd. Can you explain what I should be looking for with fsck? Or should I run fsck?

              1 Reply Last reply Reply Quote 0
              • D Offline
                doktornotor Banned
                last edited by

                Look at the system logs. Search for fsck entries.

                1 Reply Last reply Reply Quote 0
                • M Offline
                  Melphiz
                  last edited by

                  @hypnoticpancake:

                  you might want to try opening a bug report around it.  It looks like unbound is all there but the user wasn't created sometime in the past, so you could try creating the user (no guarantee it will work and run it at your own risk):
                  pw adduser unbound -g unbound -d /var/unbound -s /usr/sbin/nologin -c "Unbound DNS Resolver"

                  As I have the same problem with unbound on 2.2.1 atm. I tried yours but pfsense gives back that the group 'unbound' does not exist

                  1 Reply Last reply Reply Quote 0
                  • D Offline
                    doktornotor Banned
                    last edited by

                    @hypnoticpancake:

                    As I have the same problem with unbound on 2.2.1 atm. I tried yours but pfsense gives back that the group 'unbound' does not exist

                    You really need to read the whole thread and answer what's asked there, instead of posting "me too".

                    1 Reply Last reply Reply Quote 0
                    • M Offline
                      Melphiz
                      last edited by

                      So, when there is no fsck entry in neither of the the logs what shall I search for?

                      1 Reply Last reply Reply Quote 0
                      • R Offline
                        RomanHelmet
                        last edited by

                        @doktornotor:

                        Look at the system logs. Search for fsck entries.

                        I don't have any fsck entries.

                        1 Reply Last reply Reply Quote 0
                        • V Offline
                          vsilgalis
                          last edited by

                          @Melphiz:

                          @hypnoticpancake:

                          you might want to try opening a bug report around it.  It looks like unbound is all there but the user wasn't created sometime in the past, so you could try creating the user (no guarantee it will work and run it at your own risk):
                          pw adduser unbound -g unbound -d /var/unbound -s /usr/sbin/nologin -c "Unbound DNS Resolver"

                          As I have the same problem with unbound on 2.2.1 atm. I tried yours but pfsense gives back that the group 'unbound' does not exist

                          did you verify all the other settings?

                          if you did you will need to add the group before hand, again this is really just hand jamming stuff, i'd recommend a bug report and no guarantee that this will work:
                          pw groupadd unbound
                          pw adduser unbound -g unbound -d /var/unbound -s /usr/sbin/nologin -c "Unbound DNS Resolver"

                          1 Reply Last reply Reply Quote 0
                          • M Offline
                            Melphiz
                            last edited by

                            @hypnoticpancake:

                            did you verify all the other settings?

                            if you did you will need to add the group before hand, again this is really just hand jamming stuff, i'd recommend a bug report and no guarantee that this will work:
                            pw groupadd unbound
                            pw adduser unbound -g unbound -d /var/unbound -s /usr/sbin/nologin -c "Unbound DNS Resolver"

                            Yes,
                            /usr/local/sbin/unbound
                            /var/unbound/unbound.conf
                            exist but there is no entry in the passwd file.

                            Well, finally it's weekend now for me, so no access to the firewall anyway, I might open such a bug report tomorrow.

                            Have a nice weekend =)

                            1 Reply Last reply Reply Quote 0
                            • S Offline
                              Supermule Banned
                              last edited by

                              Still not working in the 2.2.2 upgrade file.

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