indecisive-haunting5956

Hello Gentlemen! The "Fix common Problem"-Plugin ifentified "Out of memory errors detected on your server" (10.11.2024, 04:30) and proposed to setup a support request in this forum. This happened now for the first time. My system has 64GB RAM (2x 32GB) but only 10GB are consumed in average. If I look further in the Glances history, then I see a maximum RAM consumption of only around 15GB. As well since some time I'm facing unexpected Shutdowns without any obvious reason. Sometimes the system is running for 2 days. Sometimes for 2 weeks. The Logs never had any entry for the relevant timeframe (or i'm not clever enough to understand the content). Your support would be much appreciated! Christian This description I was already looking at: tower-diagnostics-20241110-0753.zip

Ok, happy to do that. But what shall I do then? So my server is in general working fine. It just spams the log full with the message I mentioned above.

Any insights from anyone? I still have this issue.

Hello hello! My Log folder size is rapidly increasing. After looking around in /var/log I have identified the phplog to have a size of around 90MB. It keeps repeating the same error every 3 seconds. Message appear since 31-Oct-2023 09:46:11. This is as well the first message in the log. All "dynamix" plugins are up to date. [28-Nov-2023 20:04:33 Europe/Berlin] PHP Fatal error: Uncaught TypeError: date(): Argument #2 ($timestamp) must be of type ?int, string given in /usr/local/emhttp/plugins/dynamix/scripts/notify:236 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/scripts/notify(236): date('d-m-Y H:i', '"enable"') #1 {main} thrown in /usr/local/emhttp/plugins/dynamix/scripts/notify on line 236 [28-Nov-2023 20:04:36 Europe/Berlin] PHP Fatal error: Uncaught TypeError: date(): Argument #2 ($timestamp) must be of type ?int, string given in /usr/local/emhttp/plugins/dynamix/scripts/notify:236 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/scripts/notify(236): date('d-m-Y H:i', '"enable"') #1 {main} thrown in /usr/local/emhttp/plugins/dynamix/scripts/notify on line 236 [28-Nov-2023 20:04:39 Europe/Berlin] PHP Fatal error: Uncaught TypeError: date(): Argument #2 ($timestamp) must be of type ?int, string given in /usr/local/emhttp/plugins/dynamix/scripts/notify:236 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/scripts/notify(236): date('d-m-Y H:i', '"enable"') #1 {main} thrown in /usr/local/emhttp/plugins/dynamix/scripts/notify on line 236 Any valuable ideas? Thanks, Christian tower-diagnostics-20231128-2006.zip

Thanks a lot! I will do as you said.

Hello Hello! Unraid is complaining about read errors on my parity disc. Can anyone advice if I "just" have to replace it or whether there still is a chance keep this disc? Thanks a lot in advance, Christian tower-diagnostics-20231101-1442.zip

Hello Guys, just coming back to this topic. --> It looks like it is solved. Since my last post: I did not had any further unavalability of my system. I did not run MEMTEST. Would be the next step if it is happening again. Cheers, Christian

What I did so far: I was running btrfs scrub without any errors. I was running btrfs check --readonly without errors and then: btrfs check --repair Again, nothing suspicious. Finally I was backing up my appdata folder and have formatted the cache disk. The time will show, whether this has helped, or not.

@macmanluke did you find any solution to your problem? It looks like i'm facing something similar.

Hi guys! It happened again. Since months I'm facing issues with a freezing system. Now finally I was able to catch something in the Syslog. Please see the file attached. I have killed and restarted the system today at 13:32. I think it died today in the night at 03:34. But why and what can I do? Is my file system on the chache corrupt? What can I do? Any advice from you is very much appreciated. Thanks, Christian A fresh diagnostics file is attached as well. syslog_shorted.txt tower-diagnostics-20230909-1347.zip

Ok, this really helped. Thanks a lot! I have just deleted the vdisk and re-created it as described in the documentation. Any view from your side how to identify the root cause for the "freezing system"? Do I need to enable additional logging or something like this?

Hello Everyone! I'm having significant issues with my Unraid Server since weeks now. Coming from 1. Spontanous Shutdowns, going over to 2. a freezing system to 3. Docker being unable to start. Long story short, My recent issues now is that the Docker Service is failing to start. System is running on a brand new NUC12 I5 setup, 64GB RAM, 1TB NVMVE Cache, 2TB Parity disk, 2 data disks. Since I have this hardware in place my "spontaneous shutdowns" disappeared, but I still have a freezing system roughly once per day. Only a hard shutdown is helping here. Since today after the restart the Docker service is not starting anymore. I already made a downgrade from 6.12 to 6.11 as I made the update a couple of days ago and thought this might be linked. But the error is staying the same. I really hope that you might have reasonable insights helping me with my issue(s). --> Impact? My full smart home is currently not working and my wife is getting crazy 😞 Thanks a lot in advance! tower-diagnostics-20230822-1128.zip