Unbound server will not start
-
I upgraded to 2.2 when it came out and experienced the following.
I have been using dnsmasq for forwarding, etc. Wanted to try the newly bundled unbound. Disabled masq, enabled unbound, and found that that service appears in the list of services with a stopped status. Attempting to manually start it does nothing. I just upgraded to 2.2.1 in hopes of it fixing itself, but it behaves the same.
The system logs show the following message repeatedly while trying to start the service.
dhcpleases: Could not deliver signal HUP to process because its pidfile (/var/run/unbound.pid) does not exist, No such file or directory.I also get this one, not as many times though.
php-fpm[56832]: /services_unbound.php: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '139', the output was '[1426790319] unbound[58749:0] error: user 'unbound' does not exist.'I looked at trying to reinstall the package, but it looks like that's not possible now since it's bundled. Can anyone help me decipher these log entries? Or advise on how to reinstall unbound?
PS - I wasn't sure if this was the right sub, or packages (or another), but packages didn't feel like the right place.
-
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.confand then check /etc/passwd for your unbound user should look like this:
unbound:*:59:59:Unbound DNS Resolver:/var/unbound:/usr/sbin/nologin -
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 :)
-
@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.confand then check /etc/passwd for your unbound user should look like this:
unbound:*:59:59:Unbound DNS Resolver:/var/unbound:/usr/sbin/nologinBoth of those files exist. In my passwd file there is no unbound user.
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.
-
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" -
Is this a full install? Any fsck log entries in system log?
-
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?
-
Look at the system logs. Search for fsck entries.
-
@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
-
@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".
-
So, when there is no fsck entry in neither of the the logs what shall I search for?
-
-
@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" -
@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 =)
-
Still not working in the 2.2.2 upgrade file.