February 4Feb 4 hi all,I for a couple of days now experience freezes when I am trying to interact with maybe radarr or overseer.. I also had this when I was starting a VM. Just before the Windows boot logo disappeared, the Server and UI froze.I am unable to SSH into the server if that happens, so I painfully have to hard kill the server. I tried to close tabs and wait for a while, but it didn't came back.Is my rig dying or just the stick having hickups?II found these lines interesting.Feb 4 19:04:53 NASty move: Action ended at: 19:04:53 Feb 4 19:04:53 NASty move: Elapsed time: 0 sec Feb 4 19:04:53 NASty move: ****************************************************************** WE ARE DONE ! **************************************************************** Feb 4 19:10:16 NASty emhttpd: read SMART /dev/sdh Feb 4 19:10:16 NASty emhttpd: read SMART /dev/sdg Feb 4 19:10:16 NASty emhttpd: read SMART /dev/sdd Feb 4 19:10:16 NASty emhttpd: read SMART /dev/sdf Feb 4 19:18:13 NASty winbindd[2704]: [2026/02/04 19:18:11.659256, 0, traceid=6164] ../../source3/winbindd/winbindd_samr.c:71(open_internal_samr_conn) Feb 4 19:18:13 NASty winbindd[2704]: open_internal_samr_conn: Could not connect to samr pipe: NT_STATUS_CONNECTION_DISCONNECTED Feb 4 19:31:45 NASty emhttpd: spinning down /dev/sdh Feb 4 19:33:35 NASty emhttpd: spinning down /dev/sdg Feb 4 19:35:08 NASty winbindd[2704]: [2026/02/04 19:35:08.248834, 0, traceid=6200] ../../source3/winbindd/winbindd_samr.c:71(open_internal_samr_conn) Feb 4 19:35:08 NASty winbindd[2704]: open_internal_samr_conn: Could not connect to samr pipe: NT_STATUS_CONNECTION_DISCONNECTED Feb 4 19:35:42 NASty emhttpd: spinning down /dev/sdd Feb 4 19:42:24 NASty sshd-session[3014530]: Connection from 192.168.1.100 port 38368 on 192.168.200.2 port 8908 rdomain "" Feb 4 19:42:48 NASty init: Switching to runlevel: 0 Feb 4 19:42:49 NASty shutdown[3014738]: shutting down for system haltU can check the full log here:nasty-diagnostics-20260204-2105.zip Edited February 8Feb 8 by W0nderW0lf
February 5Feb 5 Author It is and I thought it would have been added to the diagnostics. Where is it usually being stored?I have also set 'write to flash: true'
February 5Feb 5 Community Expert 11 minutes ago, W0nderW0lf said:Where is it usually being stored?To the share where you set it in the options, assuming that part is enabled, that will save a continuous log, unlike the flash drive, which will only have the previous boot.
February 5Feb 5 Author Hmm... well... seems like something not rly working.I had to take the syslog server offline a couple of days ago, but that should nethertheless write it locally if enabled, right?
February 5Feb 5 Community Expert 5 hours ago, W0nderW0lf said:It is and I thought it would have been added to the diagnostics.It is when the “mirror to flash” option is set (which you have done).
February 5Feb 5 Author I've set remote syslog server to 127.0.0.1... now it created a file. Gonna have to bring back that old server in the near future.I will reply back if another crash happen.
February 7Feb 7 Author So over an hour ago, the server randomly disappeared again. We noticed this while playing hytale and got thrown out of the server.WebUI, HDMI, and power button where not responding.After I killed the server, the log doesn't seem to trace anything useful.Is there a way add a debugging log level?The Server crashed at 18:20.Feb 7 17:52:51 NASty emhttpd: spinning down /dev/sdb Feb 7 17:54:50 NASty winbindd[2703]: [2026/02/07 17:54:49.500070, 0, traceid=21888] ../../source3/winbindd/winbindd_samr.c:71(open_internal_samr_conn) Feb 7 17:54:50 NASty winbindd[2703]: open_internal_samr_conn: Could not connect to samr pipe: NT_STATUS_CONNECTION_DISCONNECTED Feb 7 18:09:17 NASty emhttpd: read SMART /dev/sdd Feb 7 18:34:29 NASty rc.rsyslogd: Syslog server daemon... Started. Feb 7 18:34:29 NASty enhanced.log: Enabling Syslog filter...edit:just checked the syslog-previous log at /boot/logs/syslog-previous and found this interesting:Feb 7 18:09:17 NASty emhttpd: read SMART /dev/sdd Feb 7 18:20:01 NASty webgui: curl error: Recv failure: Connection reset by peer endpoint: wlan0 Feb 7 18:24:37 NASty init: Switching to runlevel: 0 Edited February 7Feb 7 by W0nderW0lf added more info
February 8Feb 8 Author It happened again.This is all I could find, but its more than yesterday.I also noticed that the WebUI becomes slower over time.Feb 8 09:00:20 NASty move: Elapsed time: 0 sec Feb 8 09:00:20 NASty move: ****************************************************************** WE ARE DONE ! **************************************************************** Feb 8 09:04:01 NASty emhttpd: read SMART /dev/sdc Feb 8 09:06:47 NASty ntpd[2516]: RATE KoD from 62.108.36.235 poll 1024 Feb 8 09:10:59 NASty winbindd[120300]: [2026/02/08 09:10:58.481800, 0, traceid=1919] ../../source3/winbindd/winbindd_samr.c:71(open_internal_samr_conn) Feb 8 09:10:59 NASty winbindd[120300]: open_internal_samr_conn: Could not connect to samr pipe: NT_STATUS_CONNECTION_DISCONNECTED Feb 8 09:11:12 NASty winbindd[120298]: [2026/02/08 09:11:02.461850, 0, traceid=1919] ../../source3/winbindd/winbindd.c:820(winbind_client_processed) Feb 8 09:11:12 NASty winbindd[120298]: winbind_client_processed: request took 60.391927 seconds Feb 8 09:11:14 NASty winbindd[120298]: [struct process_request_state] ../../source3/winbindd/winbindd.c:439 [2026/02/08 09:10:01.507533] ../../source3/winbindd/winbindd.c:620 [2026/02/08 09:11:01.899460] [60.391927] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct winbindd_getgroups_state] ../../source3/winbindd/winbindd_getgroups.c:55 [2026/02/08 09:10:01.507540] ../../source3/winbindd/winbindd_getgroups.c:172 [2026/02/08 09:11:01.899340] [60.391800] -> TEVENT_REQ_USER_ERROR (3 10483072397370982924)) Feb 8 09:11:14 NASty winbindd[120298]: [struct wb_parent_idmap_setup_state] ../../source3/winbindd/winbindd_idmap.c:163 [2026/02/08 09:10:01.507542] ../../source3/winbindd/winbindd_idmap.c:175 [2026/02/08 09:10:01.507542] [0.000000] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct dcerpc_wbint_NormalizeNameUnmap_state] librpc/gen_ndr/ndr_winbind_c.c:6696 [2026/02/08 09:10:01.535567] librpc/gen_ndr/ndr_winbind_c.c:6759 [2026/02/08 09:10:02.135655] [0.600088] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct dcerpc_wbint_NormalizeNameUnmap_r_state] librpc/gen_ndr/ndr_winbind_c.c:6611 [2026/02/08 09:10:01.583392] librpc/gen_ndr/ndr_winbind_c.c:6646 [2026/02/08 09:10:02.135653] [0.552261] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct dcerpc_binding_handle_call_state] ../../librpc/rpc/binding_handle.c:414 [2026/02/08 09:10:01.631425] ../../librpc/rpc/binding_handle.c:564 [2026/02/08 09:10:02.135645] [0.504220] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct dcerpc_binding_handle_raw_call_state] ../../librpc/rpc/binding_handle.c:192 [2026/02/08 09:10:01.796834] ../../librpc/rpc/binding_handle.c:247 [2026/02/08 09:10:02.135640] [0.338806] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct wbint_bh_raw_call_state] ../../source3/winbindd/winbindd_dual_ndr.c:102 [2026/02/08 09:10:01.796840] ../../source3/winbindd/winbindd_dual_ndr.c:179 [2026/02/08 09:10:02.135630] [0.338790] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct wb_child_request_state] ../../source3/winbindd/winbindd_dual.c:203 [2026/02/08 09:10:01.796855] ../../source3/winbindd/winbindd_dual.c:306 [2026/02/08 09:10:02.135627] [0.338772] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct tevent_queue_wait_state] ../../tevent_queue.c:408 [2026/02/08 09:10:01.796859] ../../tevent_queue.c:429 [2026/02/08 09:10:01.796877] [0.000018] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct wb_simple_trans_state] ../../nsswitch/wb_reqtrans.c:375 [2026/02/08 09:10:01.796892] ../../nsswitch/wb_reqtrans.c:432 [2026/02/08 09:10:02.135621] [0.338729] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct req_write_state] ../../nsswitch/wb_reqtrans.c:158 [2026/02/08 09:10:01.796893] ../../nsswitch/wb_reqtrans.c:194 [2026/02/08 09:10:01.797089] [0.000196] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct writev_state] ../../lib/async_req/async_sock.c:361 [2026/02/08 09:10:01.796895] ../../lib/async_req/async_sock.c:483 [2026/02/08 09:10:01.797087] [0.000192] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct resp_read_state] ../../nsswitch/wb_reqtrans.c:222 [2026/02/08 09:10:01.797091] ../../nsswitch/wb_reqtrans.c:275 [2026/02/08 09:10:02.135620] [0.338529] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct read_packet_state] ../../lib/async_req/async_sock.c:578 [2026/02/08 09:10:01.797092] ../../lib/async_req/async_sock.c:713 [2026/02/08 09:10:02.135616] [0.338524] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct wb_lookupname_state] ../../source3/winbindd/wb_lookupname.c:47 [2026/02/08 09:10:02.165638] ../../source3/winbindd/wb_lookupname.c:99 [2026/02/08 09:11:01.899336] [59.733698] -> TEVENT_REQ_USER_ERROR (3 10483072397370982924)) Feb 8 09:11:14 NASty winbindd[120298]: [struct dcerpc_wbint_LookupName_state] librpc/gen_ndr/ndr_winbind_c.c:795 [2026/02/08 09:10:02.247415] librpc/gen_ndr/ndr_winbind_c.c:862 [2026/02/08 09:11:01.899300] [59.651885] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct dcerpc_wbint_LookupName_r_state] librpc/gen_ndr/ndr_winbind_c.c:707 [2026/02/08 09:10:02.247422] librpc/gen_ndr/ndr_winbind_c.c:742 [2026/02/08 09:11:01.899294] [59.651872] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct dcerpc_binding_handle_call_state] ../../librpc/rpc/binding_handle.c:414 [2026/02/08 09:10:02.247424] ../../librpc/rpc/binding_handle.c:564 [2026/02/08 09:11:01.427627] [59.180203] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct dcerpc_binding_handle_raw_call_state] ../../librpc/rpc/binding_handle.c:192 [2026/02/08 09:10:02.247438] ../../librpc/rpc/binding_handle.c:247 [2026/02/08 09:11:01.358035] [59.110597] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct wbint_bh_raw_call_state] ../../source3/winbindd/winbindd_dual_ndr.c:102 [2026/02/08 09:10:02.247441] ../../source3/winbindd/winbindd_dual_ndr.c:223 [2026/02/08 09:11:01.057226] [58.809785] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct wb_domain_request_state] ../../source3/winbindd/winbindd_dual.c:523 [2026/02/08 09:10:02.293029] ../../source3/winbindd/winbindd_dual.c:769 [2026/02/08 09:11:01.015370] [58.722341] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct wb_child_request_state] ../../source3/winbindd/winbindd_dual.c:203 [2026/02/08 09:10:02.293058] ../../source3/winbindd/winbindd_dual.c:306 [2026/02/08 09:11:01.015367] [58.722309] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct tevent_queue_wait_state] ../../tevent_queue.c:408 [2026/02/08 09:10:02.293059] ../../tevent_queue.c:429 [2026/02/08 09:10:02.293060] [0.000001] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct wb_simple_trans_state] ../../nsswitch/wb_reqtrans.c:375 [2026/02/08 09:10:02.293062] ../../nsswitch/wb_reqtrans.c:432 [2026/02/08 09:11:01.015358] [58.722296] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct req_write_state] ../../nsswitch/wb_reqtrans.c:158 [2026/02/08 09:10:02.293062] ../../nsswitch/wb_reqtrans.c:194 [2026/02/08 09:10:02.293086] [0.000024] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct writev_state] ../../lib/async_req/async_sock.c:361 [2026/02/08 09:10:02.293062] ../../lib/async_req/async_sock.c:483 [2026/02/08 09:10:02.293086] [0.000024] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct resp_read_state] ../../nsswitch/wb_reqtrans.c:222 [2026/02/08 09:10:02.293087] ../../nsswitch/wb_reqtrans.c:275 [2026/02/08 09:11:01.015357] [58.722270] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct read_packet_state] ../../lib/async_req/async_sock.c:578 [2026/02/08 09:10:02.293087] ../../lib/async_req/async_sock.c:713 [2026/02/08 09:11:01.015346] [58.722259] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct resp_write_state] ../../nsswitch/wb_reqtrans.c:307 [2026/02/08 09:11:01.899377] ../../nsswitch/wb_reqtrans.c:344 [2026/02/08 09:11:01.899457] [0.000080] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:14 NASty winbindd[120298]: [struct writev_state] ../../lib/async_req/async_sock.c:361 [2026/02/08 09:11:01.899380] ../../lib/async_req/async_sock.c:483 [2026/02/08 09:11:01.899421] [0.000041] -> TEVENT_REQ_DONE (2 0)) Feb 8 09:11:49 NASty emhttpd: read SMART /dev/sdd Edited February 8Feb 8 by W0nderW0lf
February 8Feb 8 Community Expert 14 hours ago, W0nderW0lf said:After I killed the server, the log doesn't seem to trace anything useful.This typically suggests a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one, including the individual docker containers. Additionally, look in the BIOS for a "Global C-States" or similar setting and disable that to retest, it's been known to be a problem with some boards, with both Intel and AMD CPUs.
February 8Feb 8 Author I am not sure, but I have the suspicion that it could be the CPU. Might it be possible to stress test the CPU with cpufreq?The RAM recently passed the test.
February 9Feb 9 Author okay... I think the CPU is not faulty.CPU stress passedswitched cpu - same problems with unraid.But today I encountered a different behaviour. While playing with my son, we got thrown out of our hytale server again. Unraid wasn't responding for maybe 4 minutes and came back. Couple of minutes later we got thrown out again.If that happens I am unable to connect to the server, but I might be able to use JetKVM to access the console. Unfortunately as soon as I enter the username and hit enter, I receive a timeout after 60 seconds, but I can repeat it over and over..Just like here:When I pressed the power button, the server shutdown as if nothing happened.Today after being thrown out of my server again, the Server struggled to end processes. Like if something held unraid up and didn't wanted to stop its job.This is the log I captured from the first timeout encounter to the last before I pressed the power button.Feb 9 16:00:11 NASty move: No new files will be moved/synced from primary to secondary Feb 9 16:00:11 NASty move: No new files will be moved/synced from secondary to primary Feb 9 16:00:11 NASty move: Action started at: 16:00:11 Feb 9 16:00:11 NASty move: Cleaning lock and stop files Feb 9 16:00:11 NASty move: Action ended at: 16:00:11 Feb 9 16:00:11 NASty move: Elapsed time: 0 sec Feb 9 16:00:11 NASty move: ****************************************************************** WE ARE DONE ! **************************************************************** Feb 9 16:00:19 NASty php-fpm[11243]: [WARNING] [pool www] server reached max_children setting (50), consider raising it Feb 9 16:05:07 NASty php-fpm[11243]: [WARNING] [pool www] child 1123945 exited on signal 9 (SIGKILL) after 288.839758 seconds from start Feb 9 16:06:04 NASty php-fpm[11243]: [WARNING] [pool www] child 1123946 exited on signal 9 (SIGKILL) after 312.984302 seconds from start Feb 9 16:08:57 NASty php-fpm[11243]: [WARNING] [pool www] child 1123947 exited on signal 9 (SIGKILL) after 391.020086 seconds from start Feb 9 16:08:58 NASty sshd-session[1138551]: Connection from 192.168.1.100 port 47624 on 192.168.200.2 port 8908 rdomain "" Feb 9 16:08:59 NASty php-fpm[11243]: [WARNING] [pool www] child 1123948 exited on signal 9 (SIGKILL) after 520.342596 seconds from start Feb 9 16:09:05 NASty emhttpd: spinning down /dev/sdd Feb 9 16:09:08 NASty emhttpd: read SMART /dev/sdd Feb 9 16:09:14 NASty php-fpm[11243]: [WARNING] [pool www] child 1123959 exited on signal 9 (SIGKILL) after 535.502147 seconds from start Feb 9 16:09:16 NASty sshd-session[1138551]: Postponed keyboard-interactive for root from 192.168.1.100 port 47624 ssh2 [preauth] Feb 9 16:09:16 NASty sshd-session[1138551]: Postponed keyboard-interactive/pam for root from 192.168.1.100 port 47624 ssh2 [preauth] Feb 9 16:09:16 NASty sshd-session[1138551]: Accepted keyboard-interactive/pam for root from 192.168.1.100 port 47624 ssh2 Feb 9 16:09:16 NASty sshd-session[1138551]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0) Feb 9 16:09:16 NASty sshd-session[1138551]: User child is on pid 1139417 Feb 9 16:09:16 NASty sshd-session[1139417]: Starting session: shell on pts/0 for root from 192.168.1.100 port 47624 id 0 Feb 9 16:24:10 NASty emhttpd: spinning down /dev/sdh Feb 9 16:24:10 NASty emhttpd: spinning down /dev/sdg Feb 9 16:24:11 NASty emhttpd: spinning down /dev/sdd Feb 9 16:24:11 NASty emhttpd: spinning down /dev/sdf Feb 9 16:24:19 NASty emhttpd: spinning down /dev/sdc Feb 9 16:31:53 NASty emhttpd: read SMART /dev/sdf Feb 9 16:47:00 NASty emhttpd: spinning down /dev/sdf Feb 9 16:48:29 NASty php-fpm[11243]: [WARNING] [pool www] child 1123954 exited on signal 9 (SIGKILL) after 2890.598371 seconds from start Feb 9 16:48:29 NASty emhttpd: read SMART /dev/sdg Feb 9 16:48:29 NASty emhttpd: read SMART /dev/sdc Feb 9 16:48:36 NASty emhttpd: read SMART /dev/sdh Feb 9 16:48:43 NASty emhttpd: read SMART /dev/sdf Feb 9 16:52:33 NASty php-fpm[11243]: [WARNING] [pool www] child 1123955 exited on signal 9 (SIGKILL) after 3133.934713 seconds from start Feb 9 16:52:34 NASty php-fpm[11243]: [WARNING] [pool www] child 1123957 exited on signal 9 (SIGKILL) after 3135.573704 seconds from start Feb 9 16:53:34 NASty php-fpm[11243]: [WARNING] [pool www] child 1123956 exited on signal 9 (SIGKILL) after 3195.051690 seconds from start Feb 9 16:54:12 NASty emhttpd: read SMART /dev/sdd Feb 9 16:54:54 NASty php-fpm[11243]: [WARNING] [pool www] child 1123960 exited on signal 9 (SIGKILL) after 3274.926191 seconds from start Feb 9 16:54:55 NASty php-fpm[11243]: [WARNING] [pool www] child 1123961 exited on signal 9 (SIGKILL) after 3276.808240 seconds from start Feb 9 16:55:09 NASty php-fpm[11243]: [WARNING] [pool www] child 1123962 exited on signal 9 (SIGKILL) after 3289.948800 seconds from start Feb 9 16:55:22 NASty php-fpm[11243]: [WARNING] [pool www] child 1124182 exited on signal 9 (SIGKILL) after 3287.654819 seconds from start Feb 9 16:55:28 NASty php-fpm[11243]: [WARNING] [pool www] child 1138320 exited on signal 9 (SIGKILL) after 2949.016911 seconds from start Feb 9 16:55:32 NASty php-fpm[11243]: [WARNING] [pool www] child 1139340 exited on signal 9 (SIGKILL) after 2777.326532 seconds from start Feb 9 16:55:39 NASty php-fpm[11243]: [WARNING] [pool www] child 1139405 exited on signal 9 (SIGKILL) after 2779.985190 seconds from startAfter pressing the power button:I am currently trying to run the server in safe mode with my containers on but plugins off. One of both might be interfering.
February 10Feb 10 Community Expert 11 hours ago, W0nderW0lf said:Feb 9 16:55:28 NASty php-fpm[11243]: [WARNING] [pool www] child 1138320 exited on signal 9 (SIGKILL) after 2949.016911 seconds from start Feb 9 16:55:32 NASty php-fpm[11243]: [WARNING] [pool www] child 1139340 exited on signal 9 (SIGKILL) after 2777.326532 seconds from start Feb 9 16:55:39 NASty php-fpm[11243]: [WARNING] [pool www] child 1139405 exited on signal 9 (SIGKILL) after 2779.985190 seconds from startIn my experience, these errors can be the result of the server being close to exhausting the memory, GUI can become extremely slow, like 1 minute to open the dashboard, try limiting the memory for VMs/docker services, or adding a little more RAM.It could also be one or more containers hogging the CPU, try pinning only some cores to them, and leave cores 0/1 available for Unraid.Also, recommend trying a couple of other things, go to Settings - Global share settings and set the Number of fuse File Descriptors to the max, and enable this:https://docs.unraid.net/unraid-os/release-notes/7.0.0/#excessive-flash-drive-activity-slows-the-system-down
February 10Feb 10 Author I think I found my suspect. Seems like hytale server is pretty resource hungry and causes memory leaks. I don't experience lags or performance issues when we play on the server and it just recently started to "crash", but never made it to check the logs if that happens.I now lowered the maxrendering distance.I discovered this because I wondered why my Fan's randomly start to spin faster in safe mode. But only when the hytale server runs. I have 16GB of RAM, because I only have 2 slots available and DDR4 prices are insane rn. Looking at the processes I saw that the hytale java process consumed almost 50% RAM in idle.For now I will observe that and will try to fine tune things to prevent further crashes. Edited February 10Feb 10 by W0nderW0lf
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.