Everything posted by JetXS
-
Warning: file_put_contents(): Only -1 of 100 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php on line 714
@JorgeB I reinstalled the driver and rebooted multiple times.. let's see if that helps. @Maticks, I added the no-healthcheck flag.
-
Warning: file_put_contents(): Only -1 of 100 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php on line 714
It appears that the issue is quite widespread (with multiple posts referring to it in different ways on these forums...) and sound like it's all following the same pattern... Should we do a template to ask the questions... On my end... Yes, 6.12.2 Yes Yes, 1.32.4.7195-7c8f9d3b6 Yes 535.54.03 Yes Yes No
-
Can't update apps, OS, or containers. Connect broken too
These issues are occuring when the following issue is occuring:
-
Warning: file_put_contents(): Only -1 of 100 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php on line 714
This is still occuring after update.
-
Warning: file_put_contents(): Only -1 of 100 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php on line 714
Hey folks, I've been having the same issue for a 2-3+ months now. I was hoping that updating to 6.12 would help but sadly it's not the case. Every time it's happening, the Plex docker is "unhealthy" and restarting the Plex Docker fix the issue. As reported in previous messages, I am also using the Nvidia hardware acceleration and I am on the latest Nvidia driver. I will update to 6.12.2 (currently at 6.12.1) and report back. I doubt that the change in Docker version introduced in 6.12 and reverted with 6.12.2 will help though, if that's what we are after.
-
Random 500 Internal Server Error
I've setup the syslog server as well as SSH access. Will report back with my findings when / if it occurs again. Thanks
-
Random 500 Internal Server Error
Hello everyone, Unraid (and Linux I guess) beginner here. I hope I post in the correct place. I've been testing Unraid on a custom box for a week or so now. I was resolving requests on Overseerr and moving files around in my shares. I know Plex started to take up some resources to scan some files (intro / outro, I think), but nothing out of the ordinary / that it didn't do before. I tried to log back into the machine through the Web UI at some point, but it was taking forever to load and resulting in 500s. I couldn't SSH in, I think I didn't set this up correctly yet. My only solution was to force reboot the machine. After reboot, a parity-check started and will now get going for the next 8 hours. I generated and went through the diagnostic files and couldn't spot anything odd, but my knowledge is limited. I find that the system logs are very small, why are they no logs from before the force reboot? Can anyone notice anything with those diagnostics ? Did Plex make the whole server crash ? Thanks