Nw.js: Failed to read DnsConfig

[alexandrethsilva]

On OS X I have an alert that's triggered on every node-webkit project that I run (including the sample apps), where the terminal throws the following:

[38459:0409/121155:WARNING:dns_config_service_posix.cc(289)] Failed to read DnsConfig.

The apps seem to run normally despite the issue and while investigating the warning all I could find was the part of Chromium's source code that contains this trigger, but nothing else.

My question is if that's an actual error of node-webkit and how it could be solved.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[sholladay]

I also experience this. Same behavior. I'm guessing it has something to do with network connectivity issues.

[matthew-dean]

Yeah, what's this about? I get this error all the time. It doesn't seem to cause any fatal problems with the app, but it pollutes the console.

I also get now:

[37399:0427/092538:FATAL:child_shared_bitmap_manager.cc(112)] Check failed: false. 

[Nedudi]

Hi, I have the same issue on OS X

[26837:0430/214650:WARNING:dns_config_service_posix.cc(293)] Failed to read DnsConfig.

[xixixao]

Backdoor to Chromium? This happens when I'm offline.

[angelxmoreno]

any word on this? Does anyone know how this affects the apps built?

[matthew-dean]

Any ETA on when this will be fixed?

[mayeaux]

Same thing on OS X
[15576:0306/162600:WARNING:dns_config_service_posix.cc(293)] Failed to read DnsConfig.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[miry]

Nice. I have the same issue, but it was resolved by bot :)

[sholladay]

When bugs go unfixed for a long time, they fix themselves!

[rogerwang]

CC @Christywl please follow up.

[rogerwang]

@miry @sholladay
In 0.13 and later versions we changed to an optimized architecture so more features can be supported, see http://nwjs.io/blog/whats-new-in-0.13/ and it's good for keeping up with Chromium upstream -- we released with new Chromium versions within 1 day after upstream release.
The new version would fixed many issues reported here and we're scrubbing them. We'll see if this issue still reproduce.

[Christywl]

I try some simple tests on Mac with nwjs v0.27.3 and don't see this error . @miry , could you please provide a sample to reproduce this issue?

[miry]

@Christywl the issue/warning related with Alpine docker image and Chromium in my case:

Sample Dockerfile:

FROM gradle:jdk8-alpine

USER root
RUN apk -U --no-cache --allow-untrusted add \
   zlib-dev \
   chromium \
   wait4ports \
   dbus \
   ttf-freefont \
   chromium-chromedriver \
   grep

After built you can run:

$ docker run -it imagename  /usr/bin/chromium-browser --disable-web-security --headless --disable-gpu --no-sandbox --dump-dom  https://www.chromestatus.com | head -n 1

[rogerwang]

If it reproduces with the latest Chromium browser, please report it to the Chromium upstream: https://crbug.com/new

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[etheaven]

I still need help with this.