[Support] Linuxserver.io - MariaDB


Recommended Posts

Removed the appdata folder, put it on a different disk, deleting the docker from the webgui and selecting delete image as well each time,

repulled, waited for it to stop creating databases then stopped docker, ssh into unraid server and used nano to make changes, saved then exited out and started docker

Sent from my HTC One M9 using Tapatalk

Link to comment
On 22/03/2017 at 4:25 PM, jaybird2203 said:

Removed the appdata folder, put it on a different disk, deleting the docker from the webgui and selecting delete image as well each time,

repulled, waited for it to stop creating databases then stopped docker, ssh into unraid server and used nano to make changes, saved then exited out and started docker

Sent from my HTC One M9 using Tapatalk
 

 

Right I tried this tonight, removed all instances I have of MariaDB before this test.

 

First pulled the container.

docker run -d --name="mariadb-test" --net="bridge" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -e "MYSQL_ROOT_PASSWORD"="testing" -p 3305:3305/tcp -v "/mnt/cache/.appdata/mariadb-testing":"/config":rw linuxserver/mariadb

Docker Logs from setup

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...

-------------------------------------
_ _ _
| |___| (_) ___
| / __| | |/ _ \
| \__ \ | | (_) |
|_|___/ |_|\___/
|_|

Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donations/
-------------------------------------
GID/UID
-------------------------------------
User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30_config: executing...
[cont-init.d] 30_config: exited 0.
[cont-init.d] 40-initialise-db: executing...
Setting Up Initial Databases
Installing MariaDB/MySQL system tables in '/config/databases' ...
2017-03-23 21:06:17 47049871650560 [Note] /usr/sbin/mysqld (mysqld 10.1.22-MariaDB-1~xenial) starting as process 248 ...
2017-03-23 21:06:17 47049871650560 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-03-23 21:06:17 47049871650560 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-23 21:06:17 47049871650560 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-23 21:06:17 47049871650560 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-03-23 21:06:17 47049871650560 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-03-23 21:06:17 47049871650560 [Note] InnoDB: Using Linux native AIO
2017-03-23 21:06:17 47049871650560 [Note] InnoDB: Using SSE crc32 instructions
2017-03-23 21:06:17 47049871650560 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2017-03-23 21:06:17 47049871650560 [Note] InnoDB: Completed initialization of buffer pool
2017-03-23 21:06:18 47049871650560 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2017-03-23 21:06:18 47049871650560 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2017-03-23 21:06:18 47049871650560 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2017-03-23 21:06:19 47049871650560 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2017-03-23 21:06:20 47049871650560 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2017-03-23 21:06:20 47049871650560 [Warning] InnoDB: New log files created, LSN=45883

2017-03-23 21:06:20 47049871650560 [Note] InnoDB: Doublewrite buffer not found: creating new
2017-03-23 21:06:20 47049871650560 [Note] InnoDB: Doublewrite buffer created
2017-03-23 21:06:20 47049871650560 [Note] InnoDB: 128 rollback segment(s) are active.
2017-03-23 21:06:20 47049871650560 [Warning] InnoDB: Creating foreign key constraint system tables.

2017-03-23 21:06:20 47049871650560 [Note] InnoDB: Foreign key constraint system tables created
2017-03-23 21:06:20 47049871650560 [Note] InnoDB: Creating tablespace and datafile system tables.
2017-03-23 21:06:20 47049871650560 [Note] InnoDB: Tablespace and datafile system tables created.
2017-03-23 21:06:20 47049871650560 [Note] InnoDB: Waiting for purge to start
2017-03-23 21:06:20 47049871650560 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 0
2017-03-23 21:06:21 47050676766464 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-03-23 21:06:21 47049872165632 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist

OK
Filling help tables...
2017-03-23 21:06:28 47287637774080 [Note] /usr/sbin/mysqld (mysqld 10.1.22-MariaDB-1~xenial) starting as process 277 ...
2017-03-23 21:06:28 47287637774080 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-03-23 21:06:28 47287637774080 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-23 21:06:28 47287637774080 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-23 21:06:28 47287637774080 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-03-23 21:06:28 47287637774080 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-03-23 21:06:28 47287637774080 [Note] InnoDB: Using Linux native AIO
2017-03-23 21:06:28 47287637774080 [Note] InnoDB: Using SSE crc32 instructions
2017-03-23 21:06:28 47287637774080 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2017-03-23 21:06:28 47287637774080 [Note] InnoDB: Completed initialization of buffer pool
2017-03-23 21:06:28 47287637774080 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-23 21:06:29 47287637774080 [Note] InnoDB: 128 rollback segment(s) are active.
2017-03-23 21:06:29 47287637774080 [Note] InnoDB: Waiting for purge to start
2017-03-23 21:06:29 47287637774080 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 1616799
2017-03-23 21:06:30 47288437208832 [Note] InnoDB: Dumping buffer pool(s) not yet started
OK
Creating OpenGIS required SP-s...
2017-03-23 21:06:32 47487587241728 [Note] /usr/sbin/mysqld (mysqld 10.1.22-MariaDB-1~xenial) starting as process 307 ...
2017-03-23 21:06:32 47487587241728 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-03-23 21:06:32 47487587241728 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-23 21:06:32 47487587241728 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-23 21:06:32 47487587241728 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-03-23 21:06:32 47487587241728 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-03-23 21:06:32 47487587241728 [Note] InnoDB: Using Linux native AIO
2017-03-23 21:06:32 47487587241728 [Note] InnoDB: Using SSE crc32 instructions
2017-03-23 21:06:32 47487587241728 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2017-03-23 21:06:32 47487587241728 [Note] InnoDB: Completed initialization of buffer pool
2017-03-23 21:06:32 47487587241728 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-23 21:06:33 47487587241728 [Note] InnoDB: 128 rollback segment(s) are active.
2017-03-23 21:06:33 47487587241728 [Note] InnoDB: Waiting for purge to start
2017-03-23 21:06:33 47487587241728 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 1616809
2017-03-23 21:06:33 47488388069120 [Note] InnoDB: Dumping buffer pool(s) not yet started
OK

To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
To do so, start the server, then issue the following commands:

'/usr/bin/mysqladmin' -u root password 'new-password'
'/usr/bin/mysqladmin' -u root -h 38662e24f054 password 'new-password'

Alternatively you can run:
'/usr/bin/mysql_secure_installation'

which will also give you the option of removing the test
databases and anonymous user created by default. This is
strongly recommended for production servers.

See the MariaDB Knowledgebase at http://mariadb.com/kb or the
MySQL manual for more instructions.

You can start the MariaDB daemon with:
cd '/usr' ; /usr/bin/mysqld_safe --datadir='/config/databases'

You can test the MariaDB daemon with mysql-test-run.pl
cd '/usr/mysql-test' ; perl mysql-test-run.pl

Please report any problems at http://mariadb.org/jira

The latest information about MariaDB is available at http://mariadb.org/.
You can find additional information about the MySQL part at:
http://dev.mysql.com
Consider joining MariaDB's strong and vibrant community:
https://mariadb.org/get-involved/

2017-03-23 21:06:36 47387721457408 [Note] mysqld (mysqld 10.1.22-MariaDB-1~xenial) starting as process 335 ...
2017-03-23 21:06:36 47387721457408 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-03-23 21:06:36 47387721457408 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-23 21:06:36 47387721457408 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-23 21:06:36 47387721457408 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-03-23 21:06:36 47387721457408 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-03-23 21:06:36 47387721457408 [Note] InnoDB: Using Linux native AIO
2017-03-23 21:06:36 47387721457408 [Note] InnoDB: Using SSE crc32 instructions
2017-03-23 21:06:36 47387721457408 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2017-03-23 21:06:36 47387721457408 [Note] InnoDB: Completed initialization of buffer pool
2017-03-23 21:06:36 47387721457408 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-23 21:06:36 47387721457408 [Note] InnoDB: 128 rollback segment(s) are active.
2017-03-23 21:06:36 47387721457408 [Note] InnoDB: Waiting for purge to start
2017-03-23 21:06:36 47387721457408 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 1616819
2017-03-23 21:06:36 47388521690880 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-03-23 21:06:36 47387721457408 [Note] Plugin 'FEEDBACK' is disabled.
2017-03-23 21:06:36 47387721457408 [Warning] Failed to create a socket for IPv6 '::': errno: 97.

2017-03-23 21:06:36 47387721457408 [Note] Server socket created on IP: '0.0.0.0'.
2017-03-23 21:06:36 47387721457408 [Note] Reading of all Master_info entries succeded
2017-03-23 21:06:36 47387721457408 [Note] Added new Master_info '' to hash table
2017-03-23 21:06:36 47387721457408 [Note] mysqld: ready for connections.
Version: '10.1.22-MariaDB-1~xenial' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution

2017-03-23 21:06:37 47387790277376 [Note] mysqld: Normal shutdown

2017-03-23 21:06:37 47387790277376 [Note] Event Scheduler: Purging the queue. 0 events
2017-03-23 21:06:38 47388525893376 [Note] InnoDB: FTS optimize thread exiting.
2017-03-23 21:06:38 47387790277376 [Note] InnoDB: Starting shutdown...
2017-03-23 21:06:38 47387790277376 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
2017-03-23 21:06:40 47387790277376 [Note] InnoDB: Shutdown completed; log sequence number 1616829
2017-03-23 21:06:40 47387790277376 [Note] mysqld: Shutdown complete

Database Setup Completed

[cont-init.d] 40-initialise-db: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
170323 21:06:41 mysqld_safe Logging to syslog.
170323 21:06:41 mysqld_safe Starting mysqld daemon with databases from /config/databases

Then shutdown the container

 

[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.

Next SSH to my Unraid box and edit custom.cnf

Last login: Tue Mar 21 18:37:51 2017 from 192.168.0.190
Linux 4.9.10-unRAID.
root@server:~# cd /mnt/cache/.appdata/mariadb-testing/
root@server:/mnt/cache/.appdata/mariadb-testing# nano custom.cnf 

And restart container.

[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
usermod: no changes

-------------------------------------
_ _ _
| |___| (_) ___
| / __| | |/ _ \
| \__ \ | | (_) |
|_|___/ |_|\___/
|_|

Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donations/
-------------------------------------
GID/UID
-------------------------------------
User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30_config: executing...
[cont-init.d] 30_config: exited 0.
[cont-init.d] 40-initialise-db: executing...
[cont-init.d] 40-initialise-db: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
170323 21:13:13 mysqld_safe Logging to syslog.
170323 21:13:13 mysqld_safe Starting mysqld daemon with databases from /config/databases

So, no issues with this method that I can detect.....

 

Here's the /config directory showing permission, as @saarg says custom.cnf is owned by nobody:users although mine has permissions of 644

 

root@lantallack:/mnt/cache/.appdata/mariadb-testing# ls -la
total 12
drwxrwxrwx  4 nobody users   65 Mar 23 21:06 ./
drwxrwxrwx 43 nobody users 4096 Mar 23 21:04 ../
-rw-r--r--  1 nobody users 3753 Mar 23 21:13 custom.cnf
drwxr-xr-x  4 nobody users 4096 Mar 23 21:17 databases/
drwxr-xr-x  3 nobody users   26 Mar 23 21:06 log/

 

Edited by CHBMB
Link to comment
13 hours ago, jaybird2203 said:

Thanks for confirming on a separate box. One additional item that I'm doing is storing my appdata folder for Mariadb on a SSD managed by unassigned drive.

I'll continue to test on my setup. Thanks again though

Sent from my HTC One M9 using Tapatalk
 

 

Just tried it with my SSD mounted with unassigned devices.  Still works.

 

docker run -d --name="mariadb-test" --net="bridge" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -e "MYSQL_ROOT_PASSWORD"="testing" -p 3305:3306/tcp -v "/mnt/virtualisation/mariadb/":"/config":rw linuxserver/mariadb
| |___| (_) ___
| / __| | |/ _ \
| \__ \ | | (_) |
|_|___/ |_|\___/
|_|

Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donations/
-------------------------------------
GID/UID
-------------------------------------
User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30_config: executing...
[cont-init.d] 30_config: exited 0.
[cont-init.d] 40-initialise-db: executing...
[cont-init.d] 40-initialise-db: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
170324 15:01:04 mysqld_safe Logging to syslog.
170324 15:01:04 mysqld_safe Starting mysqld daemon with databases from /config/databases
root@server:~# cd /mnt/virtualisation/mariadb/
root@server:/mnt/virtualisation/mariadb# nano custom.cnf 
root@server:/mnt/virtualisation/mariadb# ls -la
total 20
drwxrwxrwx 1 nobody users   44 Mar 24 14:59 ./
drwxrwxrwx 1 nobody users   62 Mar 24 14:59 ../
-rw-r--r-- 1 nobody users 3753 Mar 24 15:00 custom.cnf
drwxr-xr-x 1 nobody users  204 Mar 24 15:01 databases/
drwxr-xr-x 1 nobody users   10 Mar 24 14:59 log/

 

Edited by CHBMB
Link to comment
  • 2 months later...

Anybody having problems getting this docker to start after updating it?

 

I just performed an update earlier today and just noticed that it will not start properly.  In the logs I just see "Starting mysqld daemon with databases from /config/databases"

 

Just checked and it looks like the file permissions are all good.  Am I missing something simple?  Thanks for any assistance.

Link to comment
29 minutes ago, gmythx said:

Anybody having problems getting this docker to start after updating it?

 

I just performed an update earlier today and just noticed that it will not start properly.  In the logs I just see "Starting mysqld daemon with databases from /config/databases"

 

Just checked and it looks like the file permissions are all good.  Am I missing something simple?  Thanks for any assistance.

I've seen this before when the databases become corrupted, restore the appdata from a backup and you'll be good to go,

Link to comment
  • 3 weeks later...
On 6/7/2017 at 1:06 AM, gmythx said:

Anybody having problems getting this docker to start after updating it?

 

I just performed an update earlier today and just noticed that it will not start properly.  In the logs I just see "Starting mysqld daemon with databases from /config/databases"

 

Just checked and it looks like the file permissions are all good.  Am I missing something simple?  Thanks for any assistance.

 

I had this same problem, I seemed to have resolved it by deleting the folder appdata\mariadb\log and starting the docker again.

Link to comment
  • 1 month later...

Since updating to the latest image I'm getting the following in the container log:

 

170801 17:54:53 mysqld_safe Logging to syslog.
170801 17:54:53 mysqld_safe Starting mysqld daemon with databases from /config/databases
170801 17:54:56 mysqld_safe Logging to syslog.
170801 17:54:56 mysqld_safe Starting mysqld daemon with databases from /config/databases
170801 17:55:00 mysqld_safe Logging to syslog.
170801 17:55:00 mysqld_safe Starting mysqld daemon with databases from /config/databases
170801 17:55:03 mysqld_safe Logging to syslog.
170801 17:55:03 mysqld_safe Starting mysqld daemon with databases from /config/databases

Repeated essentially as long as the container is running. I have tried deleting the container and image and re-creating it but I continue to get the same message. I got a bash shell into the container to look at the mysql logs that are in /var/log but they were all empty.

 

Any suggestions?

Link to comment
  • 2 weeks later...
On 8/1/2017 at 11:57 PM, ciarlill said:

Since updating to the latest image I'm getting the following in the container log:

 


170801 17:54:53 mysqld_safe Logging to syslog.
170801 17:54:53 mysqld_safe Starting mysqld daemon with databases from /config/databases
170801 17:54:56 mysqld_safe Logging to syslog.
170801 17:54:56 mysqld_safe Starting mysqld daemon with databases from /config/databases
170801 17:55:00 mysqld_safe Logging to syslog.
170801 17:55:00 mysqld_safe Starting mysqld daemon with databases from /config/databases
170801 17:55:03 mysqld_safe Logging to syslog.
170801 17:55:03 mysqld_safe Starting mysqld daemon with databases from /config/databases

Repeated essentially as long as the container is running. I have tried deleting the container and image and re-creating it but I continue to get the same message. I got a bash shell into the container to look at the mysql logs that are in /var/log but they were all empty.

 

Any suggestions?

Hi I've the same issue I've tried to start a new container and copied from backup the folders inside appdata/mariadb/databases which in my case are nextcloud and MySQL but when I copy the MySQL folder the error persist, any suggestion?

thanks

Link to comment
26 minutes ago, CHBMB said:

I don't mind looking into this a bit more, but I'd need a copy of the database and root password, which is a slight issue.

Hi thank you but seem resolved, i've been digging into the issue these couple of days and I've found helpful an earlier solution that suggested to delete the log inside the container.

I've also checked permissions and I did a logical backup inside the container with this command: 

mysqldump --single-transaction -h localhost -u root -p nextcloud > nextcloud-sqlbkp_`date +"%Y%m%d"`.bak

 

I hope this will prevent future issue and help others solve similar issues

also this morning i've just updated the container and everything seem to work fine

 

 

  • Upvote 1
Link to comment
1 hour ago, byographic said:

Hi thank you but seem resolved, i've been digging into the issue these couple of days and I've found helpful an earlier solution that suggested to delete the log inside the container.

I've also checked permissions and I did a logical backup inside the container with this command: 

mysqldump --single-transaction -h localhost -u root -p nextcloud > nextcloud-sqlbkp_`date +"%Y%m%d"`.bak

 

I hope this will prevent future issue and help others solve similar issues

also this morning i've just updated the container and everything seem to work fine

 

 

Mind telling us exactly what log file you deleted?

Link to comment
2 minutes ago, CHBMB said:

Mind telling us exactly what log file you deleted?

To be precise I didn't delete anything because i was scared to mess with the container.

with the container stopped i've renamed the log folder as so:

custom.cnf  custom.cnf.bak  databases/  log/  log.old/

 

restarted the container and everything was up and running

inside the log.old/mysql/ there are these files:

 

mariadb-bin.000148  mariadb-bin.000151  mariadb-bin.000154  mariadb-bin.index

mariadb-bin.000149  mariadb-bin.000152  mariadb-bin.000155  mariadb-bin.state

mariadb-bin.000150  mariadb-bin.000153  mariadb-bin.000156

 

hope this help

happy to advise with further details if necessary

thanks

 

 

Link to comment

OK, so if you're finding the container not starting up and seeing this in the logs repeatedly, (the cause I believe is an unclean shutdown of the container)

 

170801 17:54:53 mysqld_safe Logging to syslog.
170801 17:54:53 mysqld_safe Starting mysqld daemon with databases from /config/databases
170801 17:54:56 mysqld_safe Logging to syslog.
170801 17:54:56 mysqld_safe Starting mysqld daemon with databases from /config/databases
170801 17:55:00 mysqld_safe Logging to syslog.
170801 17:55:00 mysqld_safe Starting mysqld daemon with databases from /config/databases
170801 17:55:03 mysqld_safe Logging to syslog.
170801 17:55:03 mysqld_safe Starting mysqld daemon with databases from /config/databases

There are two ways to remedy this.  Firstly and my preferred method, is to restore from a backup.  Secondly you can try this by opening a terminal on your Unraid server.

 

docker exec -it mariadb bash
mv /config/log/ /config/log-old/
exit
docker restart mariadb

I can't promise this second method won't result in some loss of data but it may get you out of a fix.

  • Thanks 1
Link to comment

Hello @CHBMB,

Just updated all my docker containers including nextcloud and maria-db but now I get the exact same log as above (CHBMB previous post).

I've tried your 2nd method to get it working but it didn't fix anything and I still have the same problem. I never did any backups of my nextcloud database, do you know how I could use your first method?

Cheers

Link to comment
4 hours ago, jonathansayeb said:

Ok so does it mean that i should completely reinstall maria-db and nextcloud and start from scratch because of the update?

 

If you don't have any backups of your databases I'm not sure I can see any alternative.  You won't lose your Nextcloud data though, just leave documents etc where they are.  First step would be to ensure you have a robust backup strategy, Community Applications has the ability to make regular backups, I personally do a weekly backup of my appdata and keep the last five weeks of backups.

Link to comment

@CHBMB I have a strange issue. I was moving all my dockers from /mnt/cache/docker/appdata to /mnt/user/appdata (and also recreating my docker container from that macvlan issue you helped me with) and for some reason my mariadb container threw a strange error (below). What's weird is, i have two mariadb containers, "mariadb" and "mariadb-nextcloud". My nextcloud one works just fine and reinstalled just fine. But the mariadb one keeps throwing up the error. I've even tried switching the template to the nextcloud and changing the details but it keeps throwing the error. I manually added the docker using "docker run -d ...." but i can't edit anything and it won't update when you guys push an update. Any ideas what I can do to fix this? When i try to update it says no template found. I've removed it and tried creating a new one fresh and it still throws up the error.

 

Warning: DOMDocument::loadXML(): xmlParseEntityRef: no name in Entity, line: 10 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 242 Warning: simplexml_load_string(): Entity: line 2: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 247 Warning: simplexml_load_string(): in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 247 Warning: simplexml_load_string(): ^ in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 247

Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 Warning: strpos(): Empty needle in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 717 

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.