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
Hello, I run multiple Muximux instances in Docker with Linuxserver image, data is persisted on a Gluster volume.
Randomly I get error accessing the webpage and I found that the culprit is the file settings.ini.php that become corrupted.
I can understand this if I have modified the settings so Muximux is writing to the file, but it seems that Muximux keeps writing to this file also during normal operation. I tried to deny write access to this file but then Muximux webpage remains stuck loading.
I'm wondering what is the problem, I know Gluster is not ideal for storing data like databases, but a simple text file should not have this kind of problems, and this happens only with Muximux.
The text was updated successfully, but these errors were encountered:
I run Muximux with the linuxserver.io docker image and I've had the same issue for a couple of weeks now. I've deleted the file, even the entire directory, and set it all up from scratch every time but it only runs for a couple of days before it gets corrupted again. Normally it's just been gargled towards the end with random characters added but today the entire file looks like this:
Hello, I run multiple Muximux instances in Docker with Linuxserver image, data is persisted on a Gluster volume.
Randomly I get error accessing the webpage and I found that the culprit is the file settings.ini.php that become corrupted.
I can understand this if I have modified the settings so Muximux is writing to the file, but it seems that Muximux keeps writing to this file also during normal operation. I tried to deny write access to this file but then Muximux webpage remains stuck loading.
I'm wondering what is the problem, I know Gluster is not ideal for storing data like databases, but a simple text file should not have this kind of problems, and this happens only with Muximux.
The text was updated successfully, but these errors were encountered: