CHBMB

FWIW I know it'll work as I was the one that added sudo to the container to allow us to run commands as the specified user from the command line so it would be possible to run occ as the same user that Nextcloud runs under. Sent from my Mi A1 using Tapatalk

Do you mind? I've written the solution and he's hitting a forum bug, not an issue with the code I've written. I do kind of know what I'm doing here..... Test for yourself TYPE sudo -u abc touch /config/test In the container and guarantee it'll work. Sent from my Mi A1 using Tapatalk

I know that sudo -u abc works the issue is the damned forum sometimes adds invisible characters to text copied and pasted from it. Sent from my Mi A1 using Tapatalk

I wouldn't do that as Nextcloud runs as abc Sent from my Mi A1 using Tapatalk

Type the command in manually, don't copy/paste I think this is probably the forum bug causing an issue.

What is your nextcloud container called? By default it's nextcloud Linux is case sensitive so have you changed anything to caps or renamed it in any way? Sent from my Mi A1 using Tapatalk

Right now run these commands: docker exec -it nextcloud bash sudo -u abc touch /config/log/nextcloud.log chmod 777 /config/log/nextcloud.log then edit config.php in /mnt/cache/appdata/nextcloud/www/config/config.php and include these two lines 'loglevel' => 1, 'logfile' => '/config/log/nextcloud.log', and restart your container. Now as /config is really /mnt/cache/appdata/nextcloud and remember that /mnt/user/ = array disks and cache disk and /mnt/user0 = array disks without cache disk your log file for nextcloud will be in /mnt/user/appdata/nextcloud/log/ and called nextcloud.log Because you had the log directory partially on the array there was every chance that if that was where the nextcloud.log file was it would continue to write to the array even with just the config.php changes. By removing that rogue /mnt/user0/appdata/nextcloud directory and setting use cache disk to prefer it will stop that from happening again

Then the container is working and on the right version. You tested the settings in Sonarr/Radarr?

And @OOmatrixOO stop trying to do two fixes synchronously, you'll complicate matters more and you're making changes to things you don't understand. As I said change Use cache disk to prefer.

Well for whatever reason you DO have the logs directory on your array as /mnt/user0/ is the array minus the cache disk. Apologies, typo in that command rm -rf /mnt/user0/appdata/nextcloud

Actually that shows there is part of you log file on the array. rm -rm /mnt/user0/appdata/nextcloud Will remove it. Probably need to check your appdata share to ensure it's set to prefer cache disk.

v6.7.0rc1-swarm.zip Here's a version of v6.7.0rc1 with the swarm patch applied. The check config script will still show it as missing the above two modules but they are included, but the script checks the contents of /usr/src/linux-4.19.43-Unraid/.config which I haven't changed as that would require unpacking bzroot. Instead I applied the patch above and just recreated bzmodules and bzfirmware The proof will be if it works or not. v6.7.0rc1-swarm.zip

There are two parameters that need changing IP_VS NETFILTER_XT_MATCH_IPVS

root@matrix:/mnt/disk1/dvb# patch /mnt/disk1/dvb/kernel/.config /mnt/disk1/dvb/swarm.patch patching file /mnt/disk1/dvb/kernel/.config root@matrix:/mnt/disk1/dvb# ./check-config.sh /mnt/disk1/dvb/kernel/.config info: reading kernel config from /mnt/disk1/dvb/kernel/.config ... Generally Necessary: - cgroup hierarchy: properly mounted [/sys/fs/cgroup] - CONFIG_NAMESPACES: enabled - CONFIG_NET_NS: enabled - CONFIG_PID_NS: enabled - CONFIG_IPC_NS: enabled - CONFIG_UTS_NS: enabled - CONFIG_CGROUPS: enabled - CONFIG_CGROUP_CPUACCT: enabled - CONFIG_CGROUP_DEVICE: enabled - CONFIG_CGROUP_FREEZER: enabled - CONFIG_CGROUP_SCHED: enabled - CONFIG_CPUSETS: enabled - CONFIG_MEMCG: enabled - CONFIG_KEYS: enabled - CONFIG_VETH: enabled (as module) - CONFIG_BRIDGE: enabled - CONFIG_BRIDGE_NETFILTER: enabled - CONFIG_NF_NAT_IPV4: enabled (as module) - CONFIG_IP_NF_FILTER: enabled (as module) - CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled - CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled - CONFIG_NETFILTER_XT_MATCH_IPVS: enabled (as module) - CONFIG_IP_NF_NAT: enabled (as module) - CONFIG_NF_NAT: enabled (as module) - CONFIG_NF_NAT_NEEDED: enabled - CONFIG_POSIX_MQUEUE: enabled Optional Features: - CONFIG_USER_NS: enabled - CONFIG_SECCOMP: enabled - CONFIG_CGROUP_PIDS: enabled - CONFIG_MEMCG_SWAP: enabled - CONFIG_MEMCG_SWAP_ENABLED: enabled (cgroup swap accounting is currently enabled) - CONFIG_LEGACY_VSYSCALL_EMULATE: enabled - CONFIG_BLK_CGROUP: enabled - CONFIG_BLK_DEV_THROTTLING: enabled - CONFIG_IOSCHED_CFQ: enabled - CONFIG_CFQ_GROUP_IOSCHED: enabled - CONFIG_CGROUP_PERF: enabled - CONFIG_CGROUP_HUGETLB: missing - CONFIG_NET_CLS_CGROUP: missing - CONFIG_CGROUP_NET_PRIO: missing - CONFIG_CFS_BANDWIDTH: enabled - CONFIG_FAIR_GROUP_SCHED: enabled - CONFIG_RT_GROUP_SCHED: enabled - CONFIG_IP_NF_TARGET_REDIRECT: enabled (as module) - CONFIG_IP_VS: enabled (as module) - CONFIG_IP_VS_NFCT: missing - CONFIG_IP_VS_PROTO_TCP: missing - CONFIG_IP_VS_PROTO_UDP: missing - CONFIG_IP_VS_RR: missing - CONFIG_EXT4_FS: enabled (as module) - CONFIG_EXT4_FS_POSIX_ACL: enabled - CONFIG_EXT4_FS_SECURITY: missing enable these ext4 configs if you are using ext3 or ext4 as backing filesystem - Network Drivers: - "overlay": - CONFIG_VXLAN: enabled (as module) Optional (for encrypted networks): - CONFIG_CRYPTO: enabled - CONFIG_CRYPTO_AEAD: enabled - CONFIG_CRYPTO_GCM: enabled (as module) - CONFIG_CRYPTO_SEQIV: enabled - CONFIG_CRYPTO_GHASH: enabled (as module) - CONFIG_XFRM: enabled - CONFIG_XFRM_USER: enabled - CONFIG_XFRM_ALGO: enabled - CONFIG_INET_ESP: enabled - CONFIG_INET_XFRM_MODE_TRANSPORT: enabled - "ipvlan": - CONFIG_IPVLAN: missing - "macvlan": - CONFIG_MACVLAN: enabled (as module) - CONFIG_DUMMY: missing - "ftp,tftp client in container": - CONFIG_NF_NAT_FTP: missing - CONFIG_NF_CONNTRACK_FTP: missing - CONFIG_NF_NAT_TFTP: enabled (as module) - CONFIG_NF_CONNTRACK_TFTP: enabled - Storage Drivers: - "aufs": - CONFIG_AUFS_FS: missing - "btrfs": - CONFIG_BTRFS_FS: enabled - CONFIG_BTRFS_FS_POSIX_ACL: enabled - "devicemapper": - CONFIG_BLK_DEV_DM: enabled (as module) - CONFIG_DM_THIN_PROVISIONING: enabled (as module) - "overlay": - CONFIG_OVERLAY_FS: enabled - "zfs": - /dev/zfs: missing - zfs command: missing - zpool command: missing Limits: - /proc/sys/kernel/keys/root_maxkeys: 1000000 And here's a patch file for v6.7.0rc1 1139a1140 > CONFIG_NETFILTER_XT_MATCH_IPVS=m 1165c1166,1210 < # CONFIG_IP_VS is not set --- > CONFIG_IP_VS=m > # CONFIG_IP_VS_IPV6 is not set > # CONFIG_IP_VS_DEBUG is not set > CONFIG_IP_VS_TAB_BITS=12 > > # > # IPVS transport protocol load balancing support > # > # CONFIG_IP_VS_PROTO_TCP is not set > # CONFIG_IP_VS_PROTO_UDP is not set > # CONFIG_IP_VS_PROTO_ESP is not set > # CONFIG_IP_VS_PROTO_AH is not set > # CONFIG_IP_VS_PROTO_SCTP is not set > > # > # IPVS scheduler > # > # CONFIG_IP_VS_RR is not set > # CONFIG_IP_VS_WRR is not set > # CONFIG_IP_VS_LC is not set > # CONFIG_IP_VS_WLC is not set > # CONFIG_IP_VS_FO is not set > # CONFIG_IP_VS_OVF is not set > # CONFIG_IP_VS_LBLC is not set > # CONFIG_IP_VS_LBLCR is not set > # CONFIG_IP_VS_DH is not set > # CONFIG_IP_VS_SH is not set > # CONFIG_IP_VS_MH is not set > # CONFIG_IP_VS_SED is not set > # CONFIG_IP_VS_NQ is not set > > # > # IPVS SH scheduler > # > CONFIG_IP_VS_SH_TAB_BITS=8 > > # > # IPVS MH scheduler > # > CONFIG_IP_VS_MH_TAB_INDEX=12 > > # > # IPVS application helper > # > # CONFIG_IP_VS_NFCT is not set I haven't tested as I have no interest in swarm, but it can now be put to @limetech if they wish to update things upstreamswarm.patch

Also examining the current v6.7.1rc1 kernel Show that the module is enabled. I'll have a bit more of a poke around now as I'm just a bit curious.

In my experience, @limetech are far more likely to respond to a request which clearly states the requirement, which, in this case is a kernel module, than just a plain "Can we get docker swarm?" Problem with the second question is it's an unknown quantity of what needs to be done and why this is important? Just remember Unraid can't be everything to everyone, and whilst some decisions might seem arbitrary, there may be good reasons why stuff isn't changed upstream. For instance if adding that kernel module breaks something else, it's a no go. As some useful information, here's the output of the above script. root@server:~# wget https://raw.githubusercontent.com/moby/moby/master/contrib/check-config.sh --2019-05-25 12:00:31-- https://raw.githubusercontent.com/moby/moby/master/contrib/check-config.sh Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.16.133 Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.16.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 10314 (10K) [text/plain] Saving to: ‘check-config.sh’ check-config.sh 100%[===================>] 10.07K --.-KB/s in 0s 2019-05-25 12:00:31 (208 MB/s) - ‘check-config.sh’ saved [10314/10314] root@server:~# chmod +x check-config.sh root@server:~# ./check-config.sh warning: /proc/config.gz does not exist, searching other paths for kernel config ... info: reading kernel config from /usr/src/linux-4.19.41-Unraid/.config ... Generally Necessary: - cgroup hierarchy: properly mounted [/sys/fs/cgroup] - CONFIG_NAMESPACES: enabled - CONFIG_NET_NS: enabled - CONFIG_PID_NS: enabled - CONFIG_IPC_NS: enabled - CONFIG_UTS_NS: enabled - CONFIG_CGROUPS: enabled - CONFIG_CGROUP_CPUACCT: enabled - CONFIG_CGROUP_DEVICE: enabled - CONFIG_CGROUP_FREEZER: enabled - CONFIG_CGROUP_SCHED: enabled - CONFIG_CPUSETS: enabled - CONFIG_MEMCG: enabled - CONFIG_KEYS: enabled - CONFIG_VETH: enabled (as module) - CONFIG_BRIDGE: enabled - CONFIG_BRIDGE_NETFILTER: enabled - CONFIG_NF_NAT_IPV4: enabled (as module) - CONFIG_IP_NF_FILTER: enabled (as module) - CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled - CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled - CONFIG_NETFILTER_XT_MATCH_IPVS: missing - CONFIG_IP_NF_NAT: enabled (as module) - CONFIG_NF_NAT: enabled (as module) - CONFIG_NF_NAT_NEEDED: enabled - CONFIG_POSIX_MQUEUE: enabled Optional Features: - CONFIG_USER_NS: enabled - CONFIG_SECCOMP: enabled - CONFIG_CGROUP_PIDS: enabled - CONFIG_MEMCG_SWAP: enabled - CONFIG_MEMCG_SWAP_ENABLED: enabled (cgroup swap accounting is currently enabled) - CONFIG_LEGACY_VSYSCALL_EMULATE: enabled - CONFIG_BLK_CGROUP: enabled - CONFIG_BLK_DEV_THROTTLING: enabled - CONFIG_IOSCHED_CFQ: enabled - CONFIG_CFQ_GROUP_IOSCHED: enabled - CONFIG_CGROUP_PERF: enabled - CONFIG_CGROUP_HUGETLB: missing - CONFIG_NET_CLS_CGROUP: missing - CONFIG_CGROUP_NET_PRIO: missing - CONFIG_CFS_BANDWIDTH: enabled - CONFIG_FAIR_GROUP_SCHED: enabled - CONFIG_RT_GROUP_SCHED: enabled - CONFIG_IP_NF_TARGET_REDIRECT: enabled (as module) - CONFIG_IP_VS: missing - CONFIG_IP_VS_NFCT: missing - CONFIG_IP_VS_PROTO_TCP: missing - CONFIG_IP_VS_PROTO_UDP: missing - CONFIG_IP_VS_RR: missing - CONFIG_EXT4_FS: enabled (as module) - CONFIG_EXT4_FS_POSIX_ACL: enabled - CONFIG_EXT4_FS_SECURITY: missing enable these ext4 configs if you are using ext3 or ext4 as backing filesystem - Network Drivers: - "overlay": - CONFIG_VXLAN: enabled (as module) Optional (for encrypted networks): - CONFIG_CRYPTO: enabled - CONFIG_CRYPTO_AEAD: enabled - CONFIG_CRYPTO_GCM: enabled (as module) - CONFIG_CRYPTO_SEQIV: enabled - CONFIG_CRYPTO_GHASH: enabled (as module) - CONFIG_XFRM: enabled - CONFIG_XFRM_USER: enabled - CONFIG_XFRM_ALGO: enabled - CONFIG_INET_ESP: enabled - CONFIG_INET_XFRM_MODE_TRANSPORT: enabled - "ipvlan": - CONFIG_IPVLAN: missing - "macvlan": - CONFIG_MACVLAN: enabled (as module) - CONFIG_DUMMY: missing - "ftp,tftp client in container": - CONFIG_NF_NAT_FTP: missing - CONFIG_NF_CONNTRACK_FTP: missing - CONFIG_NF_NAT_TFTP: enabled (as module) - CONFIG_NF_CONNTRACK_TFTP: enabled - Storage Drivers: - "aufs": - CONFIG_AUFS_FS: missing - "btrfs": - CONFIG_BTRFS_FS: enabled - CONFIG_BTRFS_FS_POSIX_ACL: enabled - "devicemapper": - CONFIG_BLK_DEV_DM: enabled (as module) - CONFIG_DM_THIN_PROVISIONING: enabled (as module) - "overlay": - CONFIG_OVERLAY_FS: enabled - "zfs": - /dev/zfs: missing - zfs command: missing - zpool command: missing Limits: - /proc/sys/kernel/keys/root_maxkeys: 1000000 root@server:~#

OK, I've reviewed your posts, by default nextcloud logs to the appdata share on your cache disk. (/config/nextcloud.log) Which if your appdata is setup correctly shouldn't be on your array, but on your cache disk. So, lets start from first principles, is your nextcloud appdata definitely on your cache disk? As you seem to believe it is on the array. Can you paste the output of ls -la /mnt/cache/appdata/nextcloud and ls -la /mnt/user0/appdata/nextcloud

Leia tag Sent from my Mi A1 using Tapatalk

https://github.com/linuxserver/docker-kodi-headless#tags

That's the correct solution to the issue. As for the performance, lots of factors spring to mind, CPU, RAM, location of gallery (on cache/array HDD/SSD) so not sure what to say about that.

@bonienl This topic has been bumped in three different places this morning, here, here, and here. I would suggest the topic here is the most appropriate one as it actually defines the kernel requirements to run swarm, although I haven't tested (and am not going to as I have zero interest in swarm on Unraid.) From an Unraid-Nvidia plugin I can state that my position is we won't add it. The project was never designed to modify Unraid any more than add drivers and enable the ability to utilise them in containers, and I'm not modifying .config every time I build a new release as I have to do that with the DVB kernel releases and it's a PITA. If @limetech wish to include the module in the kernel then Unraid-Nvidia will naturally follow being downstream.

The only thing I'd caution against that approach is a location inside the container is on your docker.img so a session of error log spamming will fill up your docker image. I'd suggest moving it to somewhere in /config so at least it's on your cache disk.

Yup.... And as far as I'm aware there is no GUI tools for docker compose.

This has been merged now. Should be in CA within an hour or so.

It's not a ls.io issue. It doesn't break anything, it just requires a direct address to disk. As to whether the actual issue is kernel, Unraid, Docker, Sqlite or Sonarr/${Application} I have no idea and to be honest, I don't see it as a significant issue. Why you would want all your appdata for Sonarr spread across an array anyway is beyond me, and I would recommend keeping it all on one disk for that very reason. I think you see this as a bigger deal than it actually is Also, for some reason it doesn't seem to affect everyone, some people get away with it with no problems at all, others don't, hence you could probably throw hardware into the mix as a possible cause. If you wish to go down the rabbit hole to try and get to the bottom of it, feel free. Sent from my Mi A1 using Tapatalk