tidwall
The arm64 environment is not running properly
Describe the bug I run tile38 in an arm64 environment, and after running for a few hours each time, tile38 will exit. Is there any way to obtain detailed error information?
To Reproduce run command: nohup ./tile38-server -vv --appendonly no --dev &
Using 1 million GPS per minute, continuously executing three caches set wyc1 plate_no POINT lat lon set wyc2 plate_no POINT lat lon set wyc3 plate_no POINT lat lon
Expected behavior system is running normally
Logs 2024/06/03 10:50:28 [DEBU] Opened connection: [::1]:35616 2024/06/03 10:50:28 [DEBU] Opened connection: [::1]:35628 2024/06/03 10:50:28 [DEBU] Opened connection: [::1]:35640 2024/06/03 10:52:41 [DEBU] Opened connection: [::1]:52388 2024/06/03 10:52:41 [DEBU] Opened connection: [::1]:52400 2024/06/03 10:52:41 [DEBU] Opened connection: [::1]:52426 2024/06/03 10:52:41 [DEBU] Opened connection: [::1]:52414 2024/06/03 10:52:41 [DEBU] Opened connection: [::1]:52420 2024/06/03 11:07:55 [DEBU] Opened connection: [::1]:38892 2024/06/03 11:07:55 [DEBU] Opened connection: [::1]:38904 2024/06/03 11:07:55 [DEBU] Opened connection: [::1]:38920 2024/06/03 11:07:55 [DEBU] Opened connection: [::1]:38924 2024/06/03 11:07:55 [DEBU] Opened connection: [::1]:38936 2024/06/03 12:11:48 [DEBU] Closed connection: [::1]:60922 2024/06/03 12:11:48 [DEBU] Closed connection: [::1]:57262 2024/06/03 12:11:48 [DEBU] Closed connection: [::1]:57914 2024/06/03 12:11:48 [DEBU] Closed connection: [::1]:57922 2024/06/03 12:11:48 [DEBU] Opened connection: [::1]:34062 2024/06/03 12:11:48 [DEBU] Opened connection: [::1]:34068 2024/06/03 12:11:48 [DEBU] Opened connection: [::1]:34080 2024/06/03 12:14:02 [DEBU] Closed connection: [::1]:57778 2024/06/03 12:14:02 [DEBU] Closed connection: [::1]:39836 2024/06/03 12:14:02 [DEBU] Closed connection: [::1]:57564 2024/06/03 12:14:02 [DEBU] Closed connection: [::1]:57818 2024/06/03 12:14:02 [DEBU] Closed connection: [::1]:57206 2024/06/03 12:14:02 [DEBU] Closed connection: [::1]:38924 2024/06/03 12:14:02 [DEBU] Closed connection: [::1]:57408 2024/06/03 12:14:02 [DEBU] Opened connection: [::1]:46258 2024/06/03 12:14:02 [DEBU] Closed connection: [::1]:57768 2024/06/03 12:26:18 [DEBU] Opened connection: [::1]:51184 2024/06/03 12:37:45 [DEBU] Opened connection: [::1]:41688 2024/06/03 13:14:18 [WARN] signal: hangup
Operating System (please complete the following information):
- OS: [e.g. Linux / Windows / Mac OS] linux
- CPU: [e.g. amd64 / arm64 / Apple Silicon / Intel] arm64
- Version: [e.g. 1.19.0] 1.29.2 与 1.32.2
- Container: [e.g. Docker / None] None
Additional context
That's strange indeed. nohup should be immune to hangups. The 'signal: hangup' message indicates that Tile38 received a SIGHUP, which should not happen unless the shell closes and nohup is not used.
Which shell are using. Bash or something else?
Thanks, after I brought the nohop parameter, nohup ./tile38-server -vv --appendonly no --nohup & there was no more hangup.