Python subprocess调用exe时DNS配置监视失败问题求助

Let's dig into this issue: your Python subprocess workflow to run an .exe and generate images works flawlessly under your account, but throws that [ERROR:dns_config_service_win.cc(755)] DNS config watch failed error for your colleague—even across different machines and when running outside Spyder.

First, a quick context check: that error comes from Chromium's codebase (the dns_config_service_win.cc file is part of Chromium's network stack). Even if your .exe doesn't look like it uses Chrome, some image generation or data processing tools bundle Chromium under the hood, which is why this DNS watcher component is kicking in.

Here are practical steps to fix this:

1. Check User Account Permissions #

The DNS config watcher needs access to Windows' network configuration settings, and your colleague's account might be missing key permissions:

• First, temporarily set their account to Administrator (Control Panel > User Accounts > Manage Accounts > Change account type) to test if permission restrictions are the root cause. If the error goes away, we know it's a permission issue.
• If admin rights aren't a long-term option, grant specific permissions via Local Security Policy:
  1. Open secpol.msc (type it in the Start menu)
  2. Navigate to Local Policies > User Rights Assignment
  3. Find Manage auditing and security log and add your colleague's account
  4. Also check Modify firmware environment variables and include their account if needed

2. Disable the Chromium DNS Watcher (If Relevant) #

If your .exe or its dependencies use Chromium, you can pass a command-line flag to turn off the problematic DNS watcher:

• Update your subprocess call to append --disable-dns-config-watcher to the command string. Here's how your code might look:

  def executeCmd(self, string):
      # Add the flag to disable the DNS config watcher
      cmd_with_flag = f"{string} --disable-dns-config-watcher"
      p = subprocess.Popen(cmd_with_flag, cwd=self.folder, shell=False)
      p.wait()
  

• Note: This only works if the underlying process accepts Chromium-style command-line args. Test this first to see if the error disappears.

3. Reset Network Settings for the User Profile #

Corrupted network settings in your colleague's user profile could be causing the watcher to fail:

• Have them run these commands in an elevated Command Prompt (right-click > Run as administrator):

  ipconfig /release
  ipconfig /renew
  ipconfig /flushdns
  netsh winsock reset
  

• After running these, restart their machine and test the script again.

4. Check for Group Policy Restrictions #

If your company uses Group Policy, there might be rules blocking the DNS config watcher:

• Reach out to your IT team to check if any policies restrict non-admin users from accessing network configuration APIs. Specifically, ask about policies related to DNS client settings or network service permissions.

5. Compare Environment Variables #

Your colleague's environment variables might differ from yours, causing network resolution issues:

• Have them open Command Prompt and run set to list all environment variables. Compare key ones like PATH, SystemRoot, and DNS_SERVERS with yours.
• Ensure their SystemRoot correctly points to C:\Windows and that network-related paths (like C:\Windows\System32) are included in PATH.

内容的提问来源于stack exchange，提问作者vicgarmu