BrentBollmeier

Ah, see, it was the triangle on that screen saying that the path didn't exist that concerned me. Sorry for such a bone-headed question. Thanks for your time.

Hello all, I did a fresh, new install on a new Unraid server with blank disks. I did this becuase I had done a lot of fumbbling around to get things the way I wanted, and I wanted to "start over". Doing this seemed to work fine, but I only have one user share: "system". I don't have an "appdata" or anything else. Shouldn't I have 4 shares starting out? (I did the refresh by going onto my flash drive, removing all of the /config folder (except for go and Trial.key) and rebooting off of it. Apparently I screwed something up. I'd be most grateful if someone showed me the error of my ways... Thanks very much Brent Diagnostics attached. gretzky-diagnostics-20231114-1508.zip

Well, I got past this problem. I needed to clear out the database itself despite reinstalling the container. So I had everything working, needed to power down my unraid server to physically move it to its final spot. When I booted back up, I started PostgreSQL just fine, but nextcloud won't start. the only error I see in the log is: /entrypoint.sh: 137: cannot create /var/www/html/nextcloud-init-sync.lock: Permission denied Not much to go on here. Anyone have any ideas?

Hi, is this still current? I'm following it (been trying for three days to get nextcloud to run with any semplance of performance), and when I try to add the nextcloud user to postgres, I get the following: # su - postgres postgres@eb802b1ca5cf:~$ createuser --interactive --pwprompt Enter name of role to add: nextcloud Enter password for new role: Enter it again: Shall the new role be a superuser? (y/n) n Shall the new role be allowed to create databases? (y/n) n Shall the new role be allowed to create more new roles? (y/n) n createuser: could not connect to database template1: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: role "postgres" does not exist Not really sure what's going on. Brnet

These are the settings I used to create the MariaDB container:

Bah, I just noticed the advanced settings switch, and sure enough, there was mysqld_safe --skip-grant-tables in the Post arguments. I'm sorry. Edited the container, still failed, here is the log: 2023-11-06 2:35:47 0 [Warning] Can't create test file /var/lib/mysql/599ca10ebea3.lower-test 2023-11-06 2:35:47 0 [ERROR] mariadbd: Can't create/write to file './ddl_recovery.log' (Errcode: 13 "Permission denied") 2023-11-06 2:35:47 0 [ERROR] DDL_LOG: Failed to create ddl log file: ./ddl_recovery.log 2023-11-06 2:35:47 0 [ERROR] Aborting 2023-11-06 02:35:47-06:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.1.2+maria~ubu2204 started. 2023-11-06 02:35:47-06:00 [Note] [Entrypoint]: Initializing database files Installation of system tables failed! Examine the logs in /var/lib/mysql/ for more information. The problem could be conflicting information in an external my.cnf files. You can ignore these by doing: shell> /usr/bin/mariadb-install-db --defaults-file=~/.my.cnf You can also try to start the mariadbd daemon with: shell> /usr/sbin/mariadbd --skip-grant-tables --general-log & and use the command line tool /usr/bin/mariadb to connect to the mysql database and look at the grant tables: shell> /usr/bin/mariadb -u root mysql MariaDB> show tables; Try '/usr/sbin/mariadbd --help' if you have problems with paths. Using --general-log gives you a log in /var/lib/mysql/ that may be helpful. The latest information about mariadb-install-db is available at https://mariadb.com/kb/en/installing-system-tables-mysql_install_db You can find the latest source at https://downloads.mariadb.org and the maria-discuss email list at https://launchpad.net/~maria-discuss Please check all of the above before submitting a bug report at https://mariadb.org/jira ** Press ANY KEY to close this window **

No. I wouldn' tknow where to add it.

No, the container name is MariaDB-Official, the db name is nextcloud. (That's the command specified in the first post of the thread, with mariadb substituted with nextcloud.) Yes, It's not running. Trying to figure out why. Here is what I have for the log file: /usr/local/bin/docker-entrypoint.sh: line 617: exec: mysqld_safe: not found /usr/local/bin/docker-entrypoint.sh: line 617: exec: mysqld_safe: not found ** Press ANY KEY to close this window ** I've deleted the container and restarted a few times with the same result each time.

Hi -- having a problem that I can't get past. (And I'll freely admit I'm new to both Unraid and MariaDB, so please bear with me. After I create the container as shown, it apparently won't start. It shows as "stopped" in the Docker tab of Unraid. When I go into the terminal and run the docker exec command, I get the following: root@Gretzky:~# docker exec -it MariaDB-Official nextcloud -u root -p******************** Error response from daemon: Container 4dc45333bf5dc460ad0d273f54f3d8d630c6d2853176b1934fa852ac717545a0 is not running Am I missing something? This seems pretty simple, but I'm apparently not getting something right. Thank you for your help. Brent