sparklyballs

you can change whatever you like, the shared folder is the place to put things. it's tricky, the best way is to use a surrogate system to install things and tweak the settings then copy over the whole userdata folder. i'm not installing things there by default.

FTR , i'm running the latest CP update and am not experiencing any issues

dr who fan eh ? anyways, i think we're closing in on what's going on. docker exec back into the container and once inside the container run... chown -R abc:abc /config then exit out and restart the container. i changed those two folders to be owned by mysql:users and my mariad instance didn't start. the good news is the only things affected are two folders and none of the files within them. the bad news is i don't why it would have happened, the only thing i can think of is running unraid newperms script.

abc is the user we (linuxserver) create to run services etc inside of the docker. it's transparent to unraid users because it's preset in the template but for other systems it allows people to set uid and gid to match their host user. anyways, long and short, for some reason that folder has changed ownership. from the unraid terminal run this docker exec -it mariadb find /config/databases \! -user abc -print there shouldn't be any output normally....

-rw-r----- 1 abc abc 998K Nov 15 02:24 Docker-Server.err -rw-rw---- 1 abc abc 16K Nov 15 02:15 aria_log.00000001 -rw-rw---- 1 abc abc 52 Nov 15 02:15 aria_log_control -rw-rw---- 1 abc abc 48M Nov 15 02:24 ib_logfile0 -rw-rw---- 1 abc abc 48M Nov 15 02:14 ib_logfile1 -rw-rw---- 1 abc abc 12M Nov 15 02:15 ibdata1 -rw-rw---- 1 abc abc 0 Nov 15 02:14 multi-master.info drwx------ 2 abc abc 4.0K Nov 15 02:14 mysql drwx------ 2 abc abc 4.0K Nov 14 20:16 performance_schema your mysql folder has different ownership to mine.

i forcefully deleted all the files in the mysql folder and now docker log is full of this 151115 02:17:33 mysqld_safe Starting mysqld daemon with databases from /config/databases 151115 02:17:33 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended over and over. but the .err file is written and tells me i don't have any tables in databases

meanwhile i'm trying to bust a test copy of mariadb to see if it logs the error....

kk.. restart the container if it is stopped... docker exec into again , cd to /config/databases and mv any file ending with .err (be very careful and make sure what you're doing) to .old exit out of the exec session, restart the docker exec back and paste the content of any new .err file

one question that may seem odd, but might be relevant. have you at any time recently deleted a docker, deleted the appdata folder and then readded the same docker with the same settings ?

it's just further indication that mysql/mariadb isn't running inside the container. you can't change the password that way if the service isn't running. you haven't been clear if the data was migrated from another installation somewhere.

part of the name of the log file is made up of the name of the system it's running on, in dockers not running as host, that will be an odd number like is being reported in unraid log.

151115 01:34:29 mysqld_safe Logging to '/config/databases/Docker-Server.err'. 151115 01:34:29 mysqld_safe Starting mysqld daemon with databases from /config/databases Nov 15 01:34:30 Docker-Server syslog-ng[70]: syslog-ng starting up; version='3.5.3' sparklyballs@Docker-Server:~$ docker exec -it mariad cat /config/databases/Docker-Server.err 151114 20:16:18 mysqld_safe Starting mysqld daemon with databases from /config/databases 151114 20:16:18 [Note] /usr/sbin/mysqld (mysqld 10.0.22-MariaDB-1~trusty-log) starting as process 424 ... 151114 20:16:19 [Note] InnoDB: Using mutexes to ref count buffer pool pages 151114 20:16:19 [Note] InnoDB: The InnoDB memory heap is disabled 151114 20:16:19 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 151114 20:16:19 [Note] InnoDB: Memory barrier is not used 151114 20:16:19 [Note] InnoDB: Compressed tables use zlib 1.2.8 151114 20:16:19 [Note] InnoDB: Using Linux native AIO 151114 20:16:19 [Note] InnoDB: Using CPU crc32 instructions 151114 20:16:19 [Note] InnoDB: Initializing buffer pool, size = 256.0M 151114 20:16:19 [Note] InnoDB: Completed initialization of buffer pool 151114 20:16:19 [Note] InnoDB: Highest supported file format is Barracuda. 151114 20:16:19 [Note] InnoDB: 128 rollback segment(s) are active. 151114 20:16:19 [Note] InnoDB: Waiting for purge to start 151114 20:16:19 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1616717 151114 20:16:19 [Note] Plugin 'FEEDBACK' is disabled. 151114 20:16:19 [Note] Server socket created on IP: '::'. 151114 20:16:19 [Note] Reading of all Master_info entries succeded 151114 20:16:19 [Note] Added new Master_info '' to hash table 151114 20:16:19 [Note] /usr/sbin/mysqld: ready for connections. Version: '10.0.22-MariaDB-1~trusty-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution 151114 20:34:33 [Note] /usr/sbin/mysqld: Normal shutdown 151114 20:34:33 [Note] Event Scheduler: Purging the queue. 0 events 151114 20:34:33 [Note] InnoDB: FTS optimize thread exiting. 151114 20:34:33 [Note] InnoDB: Starting shutdown... 151114 20:34:35 [Note] InnoDB: Shutdown completed; log sequence number 1616727 151114 20:34:35 [Note] /usr/sbin/mysqld: Shutdown complete 151114 20:34:35 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 151115 01:34:29 mysqld_safe Starting mysqld daemon with databases from /config/databases 151115 1:34:29 [Note] /usr/sbin/mysqld (mysqld 10.0.22-MariaDB-1~trusty-log) starting as process 290 ... 151115 1:34:30 [Note] InnoDB: Using mutexes to ref count buffer pool pages 151115 1:34:30 [Note] InnoDB: The InnoDB memory heap is disabled 151115 1:34:30 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 151115 1:34:30 [Note] InnoDB: Memory barrier is not used 151115 1:34:30 [Note] InnoDB: Compressed tables use zlib 1.2.8 151115 1:34:30 [Note] InnoDB: Using Linux native AIO 151115 1:34:30 [Note] InnoDB: Using CPU crc32 instructions 151115 1:34:30 [Note] InnoDB: Initializing buffer pool, size = 256.0M 151115 1:34:30 [Note] InnoDB: Completed initialization of buffer pool 151115 1:34:30 [Note] InnoDB: Highest supported file format is Barracuda. 151115 1:34:30 [Note] InnoDB: 128 rollback segment(s) are active. 151115 1:34:30 [Note] InnoDB: Waiting for purge to start 151115 1:34:30 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1616727 151115 1:34:30 [Note] Plugin 'FEEDBACK' is disabled. 151115 1:34:30 [Note] Server socket created on IP: '::'. 151115 1:34:30 [Note] Reading of all Master_info entries succeded 151115 1:34:30 [Note] Added new Master_info '' to hash table 151115 1:34:30 [Note] /usr/sbin/mysqld: ready for connections. Version: '10.0.22-MariaDB-1~trusty-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution

your log is full of this message. 151029 6:25:04 [Warning] Access denied for user 'debian-sys-maint'@'localhost' (using password: YES)

can you paste the output from docker exec -it <container-name> cat /config/databases/aab3299b69a3.err

is this a new container, but existing data ?

try it now.. it downgraded to helix on our test server..

you can't fix it..... but i can... when we moved over to the new file host i missed a path to fetch the checksum. pushing a fix to our build server now. I'll let you know when it's run...

the file host is somehow sending the m5d as garbled text and so the script fails the checksum test and reverts to isengard.

we're not passing in settings to the config file,

and now i'll be getting messages from squid about doing mine... thanks a bunch , j/k.

I am having an issue with scheduled tasks not happening at local time. I need to enter scheduled times at GMT. I bet I'll have to go and edit them once we switch to daylight savings time too. Not a big deal, but I didn't have that problem with needo's docker back when I used that. If this is an acknowledged/known issue, please consider listing it in the top post as a known defect. And if you fix this, please make an announcement or update the top post. Thanks! This is an issue with the version of NZBGet in this container. Try going to settings - logging - TimeCorrection I assume this container uses binary from universal linux installer. That binary is compiled using uClibc, which reads time zone information from /etc/TZ or from environment variable TZ. Expected format for TZ: http://pubs.opengroup.org/onlinepubs/007904975/basedefs/xbd_chap08.html Examples: http://lists.uclibc.org/pipermail/uclibc/2002-August/004010.html If you can set the env. variable TZ properly before executing NZBGet it will know correct time and TimeCorrection will not be needed. UNRAID probably uses a different way to configure timezone, which NZBGet (uClibc) doesn't support. It's very unlikely that this issue will be fixed in uClibc (=NZBGet). the container is built from this git repo. https://github.com/linuxserver/docker-nzbget

no worries

https://github.com/linuxserver/docker-ogar

building a version of it now.

Thanks for responding. I still think it would be worthwhile to list as a known defect in the first post. it's not a "defect"