Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] 太多的 process not found #613

Open
WangHaonie opened this issue Jun 8, 2023 · 8 comments
Open

[Bug] 太多的 process not found #613

WangHaonie opened this issue Jun 8, 2023 · 8 comments

Comments

@WangHaonie
Copy link

WangHaonie commented Jun 8, 2023

短短 50 秒内刷出了 17000 多行 process not found,就算是同一个软件发出的请求,有时找得到进程,有时就找不到,实在是找不到进程就算了,只需报一行就OK,不然整个日志都是 process not found,影响后续分析,希望可以修复一下。

Clash 版本:alpha-c3ef05b
操作系统:Windows 11 22H2 x64 22631.1830
配置文件:

port: 7890
socks-port: 7891
allow-lan: true
mode: Rule
log-level: info
external-controller: :9090
proxies:
proxy-groups:
rules:
proxy-providers: {}
rule-providers: {}
tun:
  enable: true
  stack: system
  auto-detect-interface: true
  auto-route: true
  dns-hijack:
    - any:53
dns:
  enable: true
  prefer-h3: true
  listen: 0.0.0.0:1053
  ipv6: false
  use-hosts: false
  default-nameserver:
    - 119.29.29.29
  enhanced-mode: fake-ip
  fake-ip-range: 198.18.0.1/16
  fake-ip-filter:
    - "*.lan"
    - localhost.ptlogin2.qq.com
  nameserver-policy:
    geosite:cn: 119.29.29.29
  nameserver:
    - 119.29.29.29
  fallback:
    - 8.8.8.8
  proxy-server-nameserver:
    - 119.29.29.29
  fallback-filter:
    geoip: true
    geoip-code: CN
    geosite:
      - gfw
      - geolocation-!cn
    ipcidr:
      - 240.0.0.0/4
    domain:
      - +.google.com
      - +.facebook.com
      - +.youtube.com
geodata-mode: true
geox-url:
  geoip: https://cdn.jsdelivr.net/gh/Loyalsoldier/v2ray-rules-dat@release/geoip.dat
  geosite: https://cdn.jsdelivr.net/gh/Loyalsoldier/v2ray-rules-dat@release/geosite.dat
  mmdb: https://cdn.jsdelivr.net/gh/Loyalsoldier/geoip@release/Country.mmdb
find-process-mode: always
tcp-concurrent: true
lazy: false
hosts:
  diskgenius.cn: 0.0.0.0
  www.diskgenius.cn: 0.0.0.0
  2.au.download.windowsupdate.com: 23.216.153.159
  3.au.download.windowsupdate.com: 8.251.135.126
  4.au.download.windowsupdate.com: 111.119.27.0
  images-eds-ssl.xboxlive.com: 23.77.214.7

Log

time="2023-06-08T16:13:57.4934699+08:00" level=debug msg="[Rule] use default rules"
time="2023-06-08T16:13:57.4934699+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:13:57.49447+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:13:57.49447+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:13:57.49447+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:13:57.49447+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:13:57.49447+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:13:57.49447+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:13:57.4954692+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:13:57.4954692+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:13:57.4954692+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"

----------- 省略了 17000+ 行日志 -----------

time="2023-06-08T16:14:47.2276317+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:14:47.2281449+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:14:47.230349+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:14:47.2318726+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:14:47.2333783+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:14:47.2349124+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:14:47.2359135+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:14:47.2369125+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:14:47.2369125+08:00" level=debug msg="[DNS] oth.eve.mdt.qq.com --> 119.147.6.84"
time="2023-06-08T16:14:47.2379108+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:14:47.2399646+08:00" level=debug msg="[Process] find process oth.eve.mdt.qq.com: process not found"
time="2023-06-08T16:14:47.2835639+08:00" level=info msg="[TCP] 198.18.0.1:8650 --> oth.eve.mdt.qq.com:8081 match GeoIP(CN) using 🎯 国内直连[DIRECT]"
@WangHaonie
Copy link
Author

刚试了最新的 alpha-cd44901,问题依旧

@xishang0128
Copy link
Contributor

@WangHaonie debug log刷屏不算bug

@vj23456
Copy link

vj23456 commented Jun 8, 2023

@WangHaonie 你别写process规则就没了

@H1JK
Copy link
Collaborator

H1JK commented Jun 8, 2023

This is indeed a problem. In the current implementation, the PROCESS-NAME rule will trigger the process name lookup and cache the result, but if the process name lookup failed (and nothing got cached), the process name will be looked up again every time matching the PROCESS-NAME rules and then the error will be reported repeatedly.

May we only need one such error message per connection, or never do match once failed?

CC @Skyxim

@Skyxim
Copy link
Collaborator

Skyxim commented Jun 8, 2023

This is indeed a problem. In the current implementation, the PROCESS-NAME rule will trigger the process name lookup and cache the result, but if the process name lookup failed (and nothing got cached), the process name will be looked up again every time matching the PROCESS-NAME rules and then the error will be reported repeatedly.

May we only need one such error message per connection, or never do match once failed?

CC @Skyxim

最容易出现的环境其实是路由器或者非本机代理,其实可以对非本机 IP 进行过滤

@Skyxim
Copy link
Collaborator

Skyxim commented Jun 8, 2023

253c1f4
试试在相同配置下,还会重复查询进程么

@WangHaonie
Copy link
Author

WangHaonie commented Jun 8, 2023

253c1f4 数量确实比之前少了不少 @Skyxim
image

之前:
image

c57f17d 也OK

@H1JK
Copy link
Collaborator

H1JK commented Jun 8, 2023

The repeated error in the previous version is mainly because your configuration uses PROCESS-NAME too frequently. Now we no longer retry failed process lookup.

However, it's still not clear why your process lookup was failed (and even not completely failed).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants