OuticNZ
Members
-
Joined
-
Last visited
Everything posted by OuticNZ
-
Also getting the same error - after a reboot docker containers work fine, but after 3-4 days if stopped I can't start them again. I stopped all docker containers and then stopped the docker service - restarted it and the containers can start again.
-
I have an existing Share which I have turned off Caching. However new files are still being written to the cache for that share. Also If I create a new share and initially set cache to No, and then go back and set it to Yes - new files are not placed on the cache they go to disk. I have not restarted the server, but in the past I've not had to do that when changing cache settings. Steps that I can follow to re-create the issue on New Share 1. Create new Share and set cache to No, click apply 2. Change the cache setting to Yes, click apply 3. Share it out over SMB 4. Copy a new file to the share 5. The new file is on the disk Steps that I can follow to re-create the issue on Existing Share 1. Change the cache setting to No for an existing share that is already set to cache yes, click apply 2. Copy a new file to the share 3. The new file is on the cache or if you have an existing Share with cache already set to Yes, change it back No and the files still go to the cache. This is also affecting dockers as well.
-
I did a have a similar issue where the web console wouldn't load in Chrome. It was working in IE/Brave though. Had me worried for a bit that it was stuffed, but it was just chrome. Closing down chrome completely and re-launching fixed the problem for me.
