Posts by Random9

I am using zerotier with nextcloud so I don't need to secure it. Thanks for saying about the TZ I totally forgot about that.

Today I was able to fix the problem, I have now gotten into the nextcloud dashboard hub. So the problem has been fixed.

This is the solved compose file:

version: "2.1"

services:

nextcloud:

image: ghcr.io/linuxserver/nextcloud:latest

container_name: nextcloud

environment:

- PUID=997

- PGID=100

- TZ=Europe/Oslo

volumes:

- /srv/dev-disk-by-label-erlendstorageIII/Appdata&Config/Config/NextCloud:/config

- /srv/c57e0988-2559-4f09-8f66-d20da11e999c/NextCloud:/data

depends_on:

- mariadb

ports:

- 450:443

restart: unless-stopped

mariadb:

image: ghcr.io/linuxserver/mariadb:latest

container_name: mariadb

environment:

- PUID=997

- PGID=100

- MYSQL_ROOT_PASSWORD=mariadbpassword

volumes:

- /srv/dev-disk-by-label-erlendstorageIII/Appdata&Config/Config/Mariadb:/config

- TZ=Europe/Oslo

restart: unless-stopped

Quote from KM0201

What hardware are you using?

I am currently running: gigabyte Z170N-WIFI-CF, i5-6600K CPU @ 3.50GHz & 32gb ram. What other hardware specs would be useful?

Quote from KM0201

There's no logical explanation for that.

Delete your folders and containers again and recreate your folders, then deploy the stack again. When you try to go to the webURL, use your browser in Privacy/Incognito mode.... I guess it could be a cache issue.I

I tried doing what you told me multiple times, but I still get the same problem.

I still get the same error.

I will try again tomorrow and then let you know again if I get the same problem.

I am confused by this "the second part 'backed up' is not correct it stored parity information" and that manual is even more confusing. Could you guide me through each step that I need to do.

Quote from KM0201

Ok, dollars to dollars.. Are you reading any of these posts at all?

Your compose file looks fine (you still don't have a mysql password, but I'm assuming you changed that) You're getting that error because you're not setting up your mysql database.. look at the screen shot.

Delete your current nextcloud and nextclouddb config and nextcloud data containers

Recreate all associated folders (unless you want to recreate the docker compose, use the same names)

Run the compose file again

Display More

In the compose file I used "system" for pass. I did set up the mysql database but I still get the same error. I deleted all what you said but I still get the same problem.

I am still a little confused. Currently I have 14.55tb in UFS, and 3.68tb left. Is it the case that I only need 1 parity for the 3 data drives and all data will be backed up onto the 1 parity drive.

This is my current compose now:

version: "2.1"

services:

nextcloud:

image: ghcr.io/linuxserver/nextcloud:latest

container_name: nextcloud

environment:

- PUID=1000

- PGID=100

volumes:

- /srv/dev-disk-by-label-erlendstorageIII/Appdata&Config/Config/NextCloud:/config

- /srv/c57e0988-2559-4f09-8f66-d20da11e999c/NextCloud:/data

- /etc/localtime:/etc/localtime:ro

depends_on:

- mariadb

ports:

- 450:443

restart: unless-stopped

mariadb:

image: ghcr.io/linuxserver/mariadb:latest

container_name: nextclouddb

environment:

- PUID=1000

- PGID=100

- MYSQL_ROOT_PASSWORD=**YOUR_MYSQL_System

volumes:

- /srv/dev-disk-by-label-erlendstorageIII/Appdata&Config/Config/Mariadb:/config

- /etc/localtime:/etc/localtime:ro

restart: unless-stopped

This is what I get now:

Error while trying to create admin user: Failed to connect to the database: An exception occurred in driver: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Name does not resolve

Here is the UFS & Snapraid you asked for, this is how I have set it up.

Hi

I currently have 2 8tb drives in UFS and another 2 8tb drives, as then 14.55tb & 14.55tb. In snapraid I have the 14.55tb for data, then the other 14.55tb for parity. But when I sync this the problem that comes up:

Your data requires more parity than the available space.

Please move the files 'outofparity' to another data disk.

WARNING! Without a usable Parity file, it isn't possible to sync.

I used your compose, but in the compose section where it says this:

- MYSQL_ROOT_PASSWORD=**YOUR_MYSQL_PASSWORD

Should I enter a custom password.

When I enter the nextcloud info in port 450 this is what I get:

Error while trying to create admin user: Failed to connect to the database: An exception occurred in driver: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Name does not resolve

This is my current compose:

version: "2.1"

services:

nextcloud:

image: ghcr.io/linuxserver/nextcloud:latest

container_name: nextcloud

environment:

- PUID=1000

- PGID=100

volumes:

- /srv/dev-disk-by-label-erlendstorageIII/Appdata&Config/Config/NextCloud:/config

- /srv/c57e0988-2559-4f09-8f66-d20da11e999c/NextCloud:/data

- TZ=Europe/Oslo

depends_on:

- mariadb

ports:

- 450:443

restart: unless-stopped

mariadb:

image: ghcr.io/linuxserver/mariadb:latest

container_name: nextclouddb

environment:

- PUID=1000

- PGID=100

- MYSQL_ROOT_PASSWORD=**YOUR_MYSQL_PASSWORD

volumes:

- /srv/dev-disk-by-label-erlendstorageIII/Appdata&Config/Config/Mariadb:/config

- TZ=Europe/Oslo

restart: unless-stopped

I restarted, but I still cant use omv with organizr.

I tried using PUID 1000 and I also deleted the nextcloud folder. I try to use sqlite but now I get this error message:

Error while trying to initialise the database: An exception occurred while executing 'CREATE TABLE oc_migrations (app VARCHAR(255) NOT NULL, version VARCHAR(255) NOT NULL, PRIMARY KEY(app, version))': SQLSTATE[HY000]: General error: 8 attempt to write a readonly database

Hi

I have searched around for a solution, but I found none. Error while trying to create admin user: Failed to connect to the database: An exception occurred in driver: SQLSTATE[HY000] [2002]

I followed this docker: https://hub.docker.com/r/linuxserver/nextcloud

Here is my docker compose:

---

version: "2.1"

services:

nextcloud:

image: ghcr.io/linuxserver/nextcloud

container_name: nextcloud

environment:

- PUID=997

- PGID=100

- TZ=Europe/Oslo

volumes:

- /srv/dev-disk-by-label-erlendstorageIII/Appdata&Config/Appdata/NextCloud:/config

- /srv/c57e0988-2559-4f09-8f66-d20da11e999c/Images:/data

ports:

- 443:443

restart: unless-stopped

Thank you crashtest that worked.

I tried what you said. But I still get the same message: error splicing file no space left on device. I also find this situation very strange because when I use the UFS folder to copy files into this problem should not be happening. I have both erlendstorage I & II together as one where I 15tb in total, when one drive is full it should start copying to the next automatically. I find this UFS situation very confusing.

Yeah it is full. But this is not:

erlendmainstorage:d01012a5-eb7d-4f98-9de1-b17f816bcf4e 15T 8.0T 6.6T 55% /srv/d01012a5-eb7d-4f98-9de1-b17f816bcf4e

Its this location I am copying files to and it says error splicing file no space left on device. When I use UFS then erlendstorageII should start filling up with data.

This is what I get:

Filesystem Size Used Avail Use% Mounted on

sysfs 0 0 0 - /sys

proc 0 0 0 - /proc

udev 16G 0 16G 0% /dev

devpts 0 0 0 - /dev/pts

tmpfs 3.1G 11M 3.1G 1% /run

/dev/sdf1 221G 27G 182G 13% /

securityfs 0 0 0 - /sys/kernel/security

tmpfs 16G 45M 16G 1% /dev/shm

tmpfs 5.0M 4.0K 5.0M 1% /run/lock

tmpfs 16G 0 16G 0% /sys/fs/cgroup

cgroup2 0 0 0 - /sys/fs/cgroup/unified

cgroup 0 0 0 - /sys/fs/cgroup/systemd

pstore 0 0 0 - /sys/fs/pstore

bpf 0 0 0 - /sys/fs/bpf

cgroup 0 0 0 - /sys/fs/cgroup/blkio

cgroup 0 0 0 - /sys/fs/cgroup/cpu,cpuacct

cgroup 0 0 0 - /sys/fs/cgroup/net_cls,net_prio

cgroup 0 0 0 - /sys/fs/cgroup/rdma

cgroup 0 0 0 - /sys/fs/cgroup/memory

cgroup 0 0 0 - /sys/fs/cgroup/cpuset

cgroup 0 0 0 - /sys/fs/cgroup/perf_event

cgroup 0 0 0 - /sys/fs/cgroup/devices

cgroup 0 0 0 - /sys/fs/cgroup/freezer

cgroup 0 0 0 - /sys/fs/cgroup/pids

systemd-1 - - - - /proc/sys/fs/binfmt_misc

mqueue 0 0 0 - /dev/mqueue

hugetlbfs 0 0 0 - /dev/hugepages

debugfs 0 0 0 - /sys/kernel/debug

sunrpc 0 0 0 - /run/rpc_pipefs

nfsd 0 0 0 - /proc/fs/nfsd

/dev/loop1 58M 58M 0 100% /snap/jdownloader2/13

/dev/loop2 65M 65M 0 100% /snap/gtk-common-themes/1514

/dev/loop3 56M 56M 0 100% /snap/core18/1932

/dev/loop0 218M 218M 0 100% /snap/gnome-3-34-1804/60

/dev/loop4 52M 52M 0 100% /snap/snap-store/518

/dev/loop5 98M 98M 0 100% /snap/core/10577

/dev/loop6 52M 52M 0 100% /snap/snap-store/498

/dev/loop7 219M 219M 0 100% /snap/gnome-3-34-1804/66

/dev/loop9 98M 98M 0 100% /snap/core/10583

/dev/loop8 56M 56M 0 100% /snap/core18/1944

tmpfs 16G 16K 16G 1% /tmp

binfmt_misc 0 0 0 - /proc/sys/fs/binfmt_misc

tmpfs 3.1G 4.0K 3.1G 1% /run/user/113

gvfsd-fuse - - - - /run/user/113/gvfs

fusectl 0 0 0 - /sys/fs/fuse/connections

overlay - - - - /var/lib/docker/overlay2/e9b0f01cf00d77bd64b60cde84c700e1bb5dfda1341b719b874fc1b7e68bcbd2/merged

overlay - - - - /var/lib/docker/overlay2/99f2f8ba7b9e593095282305520ea1280c6c78aef7ec3ccf005e11c33ffe8ec9/merged

overlay - - - - /var/lib/docker/overlay2/6882eae904399d50aba13a8a7c4d9dbb3cfc90777c8a6e09254b2df427b8f777/merged

overlay - - - - /var/lib/docker/overlay2/9af81c4da1c27a07fc2ce359e3c3bcb0fc51640fa655e28a61b0398d29ca034d/merged

overlay - - - - /var/lib/docker/overlay2/24517b8ba77f882990a597eb176fba78603d5474999e8cf402cc85561e56addf/merged

overlay - - - - /var/lib/docker/overlay2/e9fbcbc980b36dac6de2b5cb0d42a7982839caea4f01f2648d73c392e7c8dc11/merged

overlay - - - - /var/lib/docker/overlay2/585ae5e136c554b1baf06bdc85e4dbe7a54de8920d393816e08b60f2c508db96/merged

overlay - - - - /var/lib/docker/overlay2/96b96f6827fed38567e4436e7192383a0af328287e6514f166c63949f3638593/merged

shm - - - - /var/lib/docker/containers/19109303a1f64ad86d4ce2f9afaeeb6db23d8597c7bb71c360eae5371efa28aa/mounts/shm

shm - - - - /var/lib/docker/containers/8d4830db4de8c292e69b6817241d21db665f41db8a00a8dc13400e0d96945ef7/mounts/shm

shm - - - - /var/lib/docker/containers/b5c01f1fd69a78715e3b856cb52b8f616b21ae0e4ae7b3e2b7dc9b76c43ea977/mounts/shm

shm - - - - /var/lib/docker/containers/67f7bbc3c7cf8ba6d6dd1f5de964bc33265d45f1e17982389a48df91c9e2df56/mounts/shm

shm - - - - /var/lib/docker/containers/68d9839697c1d54b50a3783684ded35512e2e4a621b03ba8e38703f57b69de77/mounts/shm

shm - - - - /var/lib/docker/containers/e354d39e8fe788418351d0d7adacf08bd8dcdc7440e8e8005837355e789e9d74/mounts/shm

nsfs - - - - /run/docker/netns/9f38de60dd9a

nsfs - - - - /run/docker/netns/9a5aab122c73

nsfs - - - - /run/docker/netns/259c170a0f37

nsfs - - - - /run/docker/netns/9bdd1433bec6

nsfs - - - - /run/docker/netns/0107864296a3

nsfs - - - - /run/docker/netns/f3f91b37d6e3

nsfs - - - - /run/docker/netns/d087941632ff

nsfs - - - - /run/docker/netns/383552d847fd

tmpfs 3.1G 12K 3.1G 1% /run/user/1000

gvfsd-fuse 0 0 0 - /run/user/1000/gvfs

/dev/mapper/sda-crypt 7.3T 7.3T 64K 100% /srv/dev-disk-by-label-erlendstorageI

/dev/mapper/sdb-crypt 7.3T 81M 7.3T 1% /srv/dev-disk-by-label-erlendstoragepI

/dev/mapper/sdc-crypt 7.3T 100G 7.2T 2% /srv/dev-disk-by-label-erlendstoragepII

/dev/mapper/sdd-crypt 7.3T 742G 6.6T 10% /srv/dev-disk-by-label-erlendstorageII

/dev/mapper/sde-crypt 1.9T 413G 1.5T 23% /srv/dev-disk-by-label-erlendstorageIII

erlendmainstorage:d01012a5-eb7d-4f98-9de1-b17f816bcf4e 15T 8.0T 6.6T 55% /srv/d01012a5-eb7d-4f98-9de1-b17f816bcf4e

erlendmainstoragep:e1929b5b-1179-4228-a6ea-16ce178dc576 15T 100G 15T 1% /srv/e1929b5b-1179-4228-a6ea-16ce178dc576