giusemr

Hey guys, I use the idrive container for some time but I experience a growing number of Dumps inside the user folder on my cache driver under appdata. The folder is called "CDPDBDUMP" and is after 12 weeks at roughly 60 GB. Can you explain what these dump-files are and if one can delete them without breaking the backup? Maybe @taverty can help with this one? Thanks in advance.

I have the same issue. Does anyone of you have a download link for the v10 version? I want to create a fork from flubster/gsdock with a specific version tag for v10.

The error appears everytime a container tries to create or write a file. For example my plex container from plexinc throws following error: unable to create '/usr/lib/plexmediaserver/Resources/Tuner/Shared/scanners/dvbc/transponders/5244.ini.dpkg-new' (while processing './usr/lib/plexmediaserver/Resources/Tuner/Shared/scanners/dvbc/transponders/5244.ini'): No space left on device [Errno 28] No space left on device: '/etc/letsencrypt/.certbot.lock' This morning, at the moment when I wrote this post, the problem was there. After leaving the system untouched until now, everything works as expected after a test. From this morning until now, nothing has changed in the system. Even in the logs where no entries that would indicate any change. Now I started all containers and the problem seems resolved. I don't know what could cause this problem. But thank you @Squid for looking into this.

Hello everybody, I already read multiple topics here in the forums and over on reddit about this error, but no solution for me. Since yesterday evening I noticed my cpu utilization went up to 100% because the influxdb container could not write any data. After checking the other containers I noticed similar errors in the logs. I also checked if any container writes directly to the image, like a downloader or something but the containers and volumes sizes looks fine. Down below you find some outputs from my system and my diagnostics output. I wonder if the devices /dev/loop0 and /dev/loop1 cause these issues because they are at 100% utilization. I also increased the docker image size to 80G. Previously it was on 40G. Currently I stopped all containers. df -h Filesystem Size Used Avail Use% Mounted on rootfs 5.8G 959M 4.9G 17% / tmpfs 32M 232K 32M 1% /run devtmpfs 5.8G 0 5.8G 0% /dev tmpfs 5.9G 0 5.9G 0% /dev/shm cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup tmpfs 128M 476K 128M 1% /var/log /dev/sda1 15G 323M 15G 3% /boot /dev/loop0 12M 12M 0 100% /lib/modules /dev/loop1 12M 12M 0 100% /lib/firmware /dev/md2 5.5T 4.5T 983G 83% /mnt/disk2 /dev/md3 932G 415G 517G 45% /mnt/disk3 /dev/sde1 224G 52G 171G 24% /mnt/cache shfs 6.4T 5.0T 1.5T 78% /mnt/user0 shfs 6.6T 5.0T 1.7T 76% /mnt/user /dev/loop2 80G 13G 67G 16% /var/lib/docker /dev/loop3 1.0G 17M 905M 2% /etc/libvirt shm 64M 0 64M 0% /var/lib/docker/containers/e5c05fd2bc13be950a7ddc7cc47dfd7025fa0c857534982c437639239c2e45ce/mounts/shm shm 64M 0 64M 0% /var/lib/docker/containers/27d86e87953d222b315ef03bb583941df32f3904d360d3ee8169dce5cd431638/mounts/shm shm 64M 0 64M 0% /var/lib/docker/containers/72bfc085261798d287e7e55d3f3f2d45791c687cfc562f916f8b5d6be0d18cd0/mounts/shm shm 64M 0 64M 0% /var/lib/docker/containers/b3e9c142f3cafbd16e4de3b68898cf496fe0b88b1d20c888b46c2ec85d51dd26/mounts/shm shm 64M 0 64M 0% /var/lib/docker/containers/717477a8dc3f79e64532727d1e054ce20eb7e9e19d293dd7d176082d52262f5d/mounts/shm shm 64M 0 64M 0% /var/lib/docker/containers/c27fe5a357e6d77fe59d5d89eb84c82625d4188cf8047f7be70e2fea61a5785c/mounts/shm shm 64M 0 64M 0% /var/lib/docker/containers/928f5b9ff7ee9cbeead0bf207640ed5213c97bb542fc44eedcee9c7b539e6077/mounts/shm docker system df TYPE TOTAL ACTIVE SIZE RECLAIMABLE Images 28 28 8.434GB 87.06MB (1%) Containers 32 7 350.7MB 350.7MB (99%) Local Volumes 5 1 49.65MB 49.65MB (100%) Build Cache 0 0 0B 0B Docker Volume Info: btrfs filesystem show: Label: none uuid: b5a7631a-65ec-4867-a43d-19009f3496a2 Total devices 1 FS bytes used 11.62GiB devid 1 size 80.00GiB used 20.07GiB path /dev/loop2 I hope someone can help me with this. Thanks in advance. server-diagnostics-20190929-0857.zip

I fixed this issue, inside the proxy config from the letsencrypt container I had changed the redirect port to 444 ( My host port) this lead to infinite redirects between the proxy and nextcloud.

No one with a similar problem or who can point me in the right direction? I desperately try to solve this problem.

Hello everyone, I tried to give my nextcloud setup a fresh install: fresh mariadb, fresh nextcloud docker and also removed everything (even hidden files) from the shares (appdata/nextcloud & Datashare). Following the guides from spaceinvaderone and linuxserver.io, the DB setup and first installation from nextcloud works. But then nextcloud tries to redirect me to my files page and I get a 302 redirect to /apps/files/ page that doesn't end. It doesn't matter if I take the stock config.php file an try to access directly or through the proxy with modified config.php. The result is the error "Too many redirects". On some issue discussion on github someone said there might be a permission issue with the files but I checked the config folder and the share folder and it's all set to "nobody:users". I also found an issue on github which describes exactly my issue (https://github.com/nextcloud/server/issues/11203). My nginx logs inside the nextcloud container are also filled with this output. GET /apps/files/ HTTP/1.1" 302 Has anyone an idea if this is related to the linuxserver image or to the nextcloud software? I appreciate your help. Thanks in advance.