SQ528
commented
7 months ago 没事别更新那么新，我前面从0.03更新到0.05然后一开就断网，然后卸载重装了0.03，看到0.06出来了这次我不为所动了！
Closed Aethersailor closed 7 months ago
SQ528
commented
7 months ago 没事别更新那么新，我前面从0.03更新到0.05然后一开就断网，然后卸载重装了0.03，看到0.06出来了这次我不为所动了！
RayWangQvQ
commented
7 months ago 同样bug，内核更新到alpha-g6f0fe85出现，之前一直是好的
github.com/metacubex/mihomo/main.go:109 +0x580
main.main()
github.com/metacubex/mihomo/hub/hub.go:50 +0x210
github.com/metacubex/mihomo/hub.Parse({0x0, 0x0, 0x194d150?})
github.com/metacubex/mihomo/hub/executor/executor.go:103 +0x284
github.com/metacubex/mihomo/hub/executor.ApplyConfig(0x40000ea0c0, 0x1)
github.com/metacubex/mihomo/hub/executor/executor.go:356 +0x88
github.com/metacubex/mihomo/hub/executor.updateTun(0x40000f6008)
github.com/metacubex/mihomo/listener/listener.go:534 +0x194
github.com/metacubex/mihomo/listener.ReCreateTun({0x1, {0x40001115f8, 0x4}, 0x1, {0x4000041f10, 0x1, 0x1}, 0x0, 0x0, {0x1ee3920, ...}, ...}, ...)
github.com/metacubex/mihomo/listener/sing_tun/server.go:256 +0x131c
github.com/metacubex/mihomo/listener/sing_tun.New({0x1, {0x40001115f8, 0x4}, 0x1, {0x4000041f10, 0x1, 0x1}, 0x0, 0x0, {0x1ee3920, ...}, ...}, ...)
github.com/metacubex/mihomo/component/resolver/system.go:14 +0xf4
github.com/metacubex/mihomo/component/resolver.AddSystemDnsBlacklist({0x40006840a0?, 0x4?, 0x400016adc0?})
goroutine 1 [running]:
panic: assignment to entry in nil map
2024-04-13 20:44:07 level=info msg="Mixed(http+socks) proxy listening at: [::]:7893"
2024-04-13 20:44:07 level=info msg="TProxy server listening at: [::]:7895"
2024-04-13 20:44:07 level=info msg="Redirect proxy listening at: [::]:7892"
2024-04-13 20:44:07 level=info msg="SOCKS proxy listening at: [::]:7891"
2024-04-13 20:44:07 level=info msg="HTTP proxy listening at: [::]:7890"
2024-04-13 20:44:07 level=info msg="DNS server listening at: [::]:7874"
2024-04-13 20:44:07 level=info msg="Sniffer is closed"
2024-04-13 20:44:07 level=info msg="Authentication of local server updated"
2024-04-13 20:44:07 level=info msg="RESTful API listening at: [::]:9090"
2024-04-13 20:44:07 level=info msg="Initial configuration complete, total time: 19236ms"手动回退内核版本到alpha-g16fadd2后恢复正常
root@NX:/etc/openclash/core# ./clash_meta -v
Mihomo Meta alpha-g16fadd2 linux arm64 with go1.22.2 Wed Apr 10 20:12:53 UTC 2024
Use tags: with_gvisor
Verify Steps
OpenClash Version
v0.46.006-beta
Bug on Environment
Immortalwrt
OpenWrt Version
SNAPSHOT
Bug on Platform
Linux-amd64(x86-64)
Describe the Bug
2024-04-13 13:32:22 错误：无法获取 General 部分的转发端口设置, OpenClash 使用原始配置文件启动失败 2024-04-13 13:32:22 错误：无法获取 DNS 部分的运行模式设置, OpenClash 使用原始配置文件启动失败 2024-04-13 13:32:22 错误：无法获取 DNS 部分的监听端口设置, OpenClash 使用原始配置文件启动失败 2024-04-13 13:32:22 错误：OpenClash 启动失败，尝试使用原始配置文件启动...
OpenClash在全新编译的6.6内核系统上无法启动，已经确定同样的配置曾经是可以启动的 这和系统内核的版本太高有没有关系？openclash的内核日志中有报错信息
To Reproduce
设置Openclash，更新配置>启动
OpenClash Log
OpenClash Config
No response
Expected Behavior
如以往情况正常启动
Additional Context
OpenClash 调试日志.log