You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read the documentation and understand the meaning of all configuration items I have written, avoiding a large number of seemingly useful options or default values.
I have not reviewed the documentation and resolve this issue.
I have not searched the Issue Tracker for the problem I am going to raise.
I have tested with the latest Alpha branch version, and the issue still persists.
I have provided server and client configuration files and processes that can reproduce the issue locally, rather than a desensitized complex client configuration file.
I have provided the simplest configuration that can reproduce the error I reported, rather than relying on remote servers, TUN, graphical client interfaces, or other closed-source software.
I have provided complete configuration files and logs, rather than providing only parts that I believe are useful due to confidence in my own intelligence.
Using provided config file and letting the core run, OS would auto reboot after random duration or just hang with no response and 25% CPU usage, no ICMP, SSH or even VNC (black screen) response. This is the first time I capture the fail log. Have not tested with latest Alpha branch cuz it's kind random to reproduce the failure.
Logs
Exceeded the max characters, click this link to see the journalctl log
https://codefile.io/f/Sts26x5eIt
Append
Here is the Out-Of-Memory journalctl log from the last crash. Have enabled the debug and will upload the memory dump file after next crash.
Maybe you can try to switch to the amd64-compatible version, or an older golang compiled version such as one containing the go120 or go122 tags.
This problem is more likely to be a CPU instruction set incompatibility problem caused by virtualization, or even caused by hardware failure (such as memory errors).
Maybe you can try to switch to the amd64-compatible version, or an older golang compiled version such as one containing the go120 or go122 tags.
This problem is more likely to be a CPU instruction set incompatibility problem caused by virtualization, or even caused by hardware failure (such as memory errors).
Yes it is the compatible version now, I'll try using the older golang compile and report back. Thanks for your help :)
Verify steps
Operating System
Linux
System Version
Linux portal-gateway 6.1.0-25-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.106-3 (2024-08-26) x86_64 GNU/Linux
Mihomo Version
Configuration File
Description
This core is running on a proxmox Debian guest with CPU passthrough
Reproduction Steps
Using provided config file and letting the core run, OS would auto reboot after random duration or just hang with no response and 25% CPU usage, no ICMP, SSH or even VNC (black screen) response. This is the first time I capture the fail log. Have not tested with latest Alpha branch cuz it's kind random to reproduce the failure.
Logs
Append
Here is the Out-Of-Memory journalctl log from the last crash. Have enabled the
debug
and will upload the memory dump file after next crash.https://codefile.io/f/5EJnfbU3C6
The text was updated successfully, but these errors were encountered: