Bug 776 - The Unbound DNS validator service terminated unexpectedly.
The Unbound DNS validator service terminated unexpectedly.
Status: ASSIGNED
Product: unbound
Classification: Unclassified
Component: server
1.5.9
x86_64 Windows
: P5 blocker
Assigned To: unbound team
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-06-10 08:05 CEST by drahnier
Modified: 2016-07-09 01:29 CEST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description drahnier 2016-06-10 08:05:56 CEST
Unbound service 1.5.9 apparently wants to run under a 'Network Service' account but fails on Windows 10 build 14361. The service runs just fine if reconfiguring it to run under a 'Local System' account (as was the case in previous versions).

It would be nice to have it running as a 'Network Service', though.

Error log:

Log Name:      System
Source:        Service Control Manager
Date:          06/10/16 12:47:09
Event ID:      7034
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DD-608G12
Description:
The Unbound DNS validator service terminated unexpectedly.  It has done this 2 time(s).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="49152">7034</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2016-06-10T05:47:09.820952900Z" />
    <EventRecordID>1906</EventRecordID>
    <Correlation />
    <Execution ProcessID="752" ThreadID="1040" />
    <Channel>System</Channel>
    <Computer>DD-608G12</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">Unbound DNS validator</Data>
    <Data Name="param2">2</Data>
    <Binary>75006E0062006F0075006E0064000000</Binary>
  </EventData>
</Event>
Comment 1 Wouter Wijngaards 2016-06-10 09:03:15 CEST
Hi Drahnier,

Yes these executables use localsystem:

http://www.nlnetlabs.nl/~wouter/unbound_setup_1.5.10rc61.exe
http://www.nlnetlabs.nl/~wouter/unbound-1.5.10rc61.zip

You can also grant permission to use the networkservice with (Thanks to Ray Griffith):

icacls "C:\Program Files (x86)\unbound" /grant "NT Authority\Network
Service:(CI)(OI)M"

Best regards, Wouter
Comment 2 drahnier 2016-06-10 09:19:09 CEST
Now, your reply leaves me confused. In the upcoming 1.5.10 release, the unbound service will run as 'local system' (as was the case prior to release 1.5.9)? Or will 1.5.10 include a fix to allow the unbound service to run as 'network service' (as is the default for release 1.5.9) without crashing?

Mh, my question here is perhaps: What exactly is release 1.9.10 supposed to fix?
Comment 3 Karl 2016-07-08 22:32:55 CEST
Hi...

I also noticed a second startup problem for 1.5.9.

I am using Unbound on Windows 8.1. By default it installs to C:\Program Files (x86)\Unbound, but is looking for a config file in C:\Program Files\Unbound.

Thanks,

Karl
Comment 4 drahnier 2016-07-09 01:29:09 CEST
(In reply to Karl from comment #3)
> Hi...
> 
> I also noticed a second startup problem for 1.5.9.
> 
> I am using Unbound on Windows 8.1. By default it installs to C:\Program
> Files (x86)\Unbound, but is looking for a config file in C:\Program
> Files\Unbound.
> 
> Thanks,
> 
> Karl

Yes, indeed. I've made it my habit to install unbound to "Program Files\Unbound" a long time ago. - I wish someone would take the extra step to compile a 64bit version for Windows ...