Windows 9.16.25 fails to start (1067 Terminated unexpectedly)

Danny Mayer mayer at pdmconsulting.net
Thu Feb 17 17:42:35 UTC 2022


You have to run the debug-enabled code as a service otherwise you will 
get nowhere. It's complicated and it's time consuming to set up right.

Danny

On 2/17/22 12:30 PM, Jakob Bohm via bind-users wrote:
> I know this, and I am quite familiar with low level debugging 
> techniques on Windows, though my favorite tool for the job was ruined 
> by unfortunate business decisions to bundle it with irrelevant 
> software that would be needed only in a completely different license 
> count, if at all.
>
> I could probably set up a debugging scenario with a private 
> compilation (to get debug symbols) and an artificial installation of 
> more recent toolchain to work with the official ISC build 
> instructions, though I strongly suspect a clean process exit with a 
> return code of 0 (Depending, how good Windows is at capturing the 
> return code of the exited product).  But I was hoping there was a way 
> to find out directly,
> such as an option to make the entire startup sequence non-parallel and 
> verbose, thus revealing the exact point of failure.
>
> On 2022-02-17 17:15, Danny Mayer wrote:
>> I can short-cut that a little! :) A 1067 error is always the Windows 
>> named service failing to start. The reasons behind it are much harder 
>> to figure out. I've seen these over the years but I don't know off 
>> the top of my head why.
>>
>> Danny
>>
>> On 2/17/22 9:26 AM, Ondřej Surý wrote:
>>> Log isn’t going to help here if named is crashing. Getting a 
>>> backtrace or anything that closely resembles one would help. Running 
>>> debug build under MSVS would help. Or doing git bisect and pinpoint 
>>> the breakage to a commit or at least Merge commit would help.
>>>
>>> This is part of the problem - debugging on Windows is extremely 
>>> painful and requires expertise with extremely high learning curve.
>>>
>>> -- 
>>> Ondřej Surý — ISC (He/Him)
>>>
>>> My working hours and your working hours may be different. Please do 
>>> not feel obligated to reply outside your normal working hours.
>>>
>>>> On 17. 2. 2022, at 15:08, Jakob Bohm via bind-users 
>>>> <bind-users at lists.isc.org> wrote:
>>>>
>>>> 
>>>>
>>>> On 2022-02-12 01:06, Richard T.A. Neal wrote:
>>>>
>>>>> I run BIND on Windows as well but I've been unable to upgrade to 
>>>>> 9.16.25 - I get an error stating "Error Validating Account. Unable 
>>>>> to install service using this account.". So I'm presently running 
>>>>> 9.16.21.
>>>>>
>>>>> What are the last few things in the Application Event Log (Source: 
>>>>> named) before it terminates?
>>>>>
>>>>> Richard.
>>>>>
>>>>> -----Original Message-----
>>>>> From: bind-users<bind-users-bounces at lists.isc.org> On Behalf Of 
>>>>> Jakob Bohm via bind-users
>>>>> Sent: 11 February 2022 12:19 pm
>>>>> To: bind-users<bind-users at lists.isc.org>
>>>>> Subject: Windows 9.16.25 fails to start (1067 Terminated 
>>>>> unexpectedly)
>>>>>
>>>>> Dear list,
>>>>>
>>>>> When recently trying to upgrade some secondary-only authoritative 
>>>>> servers running on Windows machines, I found that Bind 9.16.25 
>>>>> (x86_64) binaries from isc.org failed to completely startup, 
>>>>> causing Windows to report that "1067 The process terminated 
>>>>> unexpectedly.", with 0 process exit code.  Attempting to up the 
>>>>> debug level all the way to "-d 100"
>>>>> failed to log a reason, but downgrading to the 9.16.21 binaries 
>>>>> resumed operation.
>>>>>
>>>>> Is there a known issue and workaround for this, or is there any 
>>>>> additional information to extract?
>>>>>
>>>>> <snip>
>>>> The latest in the log (I directed it to a file, as the Event Viewer 
>>>> wrapping in the port was badly done) were the mentioned fetch of 
>>>> ./NS etc. interspersed with zone loading messages for default zones 
>>>> (I temporarily commented out the real zones to shorten the config, 
>>>> but it still failed).
>>>>
>>>> Enjoy
>>>>
>>>> Jakob
>>>> -- 
>>>> Jakob Bohm, CIO, Partner, WiseMo A/S.https://www.wisemo.com
>>>> Transformervej 29, 2860 Søborg, Denmark.  Direct +45 31 13 16 10
>>>> This public discussion message is non-binding and may contain errors.
>>>> WiseMo - Remote Service Management for PCs, Phones and Embedded
>>>> -- 
>>>> Visit https://lists.isc.org/mailman/listinfo/bind-users to 
>>>> unsubscribe from this list
>>>>
>>>> ISC funds the development of this software with paid support 
>>>> subscriptions. Contact us at https://www.isc.org/contact/ for more 
>>>> information.
>>>>
>>>>
>>>> bind-users mailing list
>>>> bind-users at lists.isc.org
>>>> https://lists.isc.org/mailman/listinfo/bind-users
>>>
>
>
> Enjoy
>
> Jakob


More information about the bind-users mailing list