MariaDB issues on startup

[braddevans]

implemented fixes to broken docker images and the database spews out an error from small fixes done to make the docker images run

Successfully tagged docker_worldserver:latest 
Starting docker_mariadb_1 ...  
Starting docker_mariadb_1 ... done
Starting docker_tcjsonapi_1 ...  
Starting docker_authserver_1 ...
Starting docker_worldserver_1 ...
Starting docker_tcjsonapi_1
Starting docker_authserver_1 
Starting docker_tcjsonapi_1 ... done
Starting docker_keira2_1 ...  
Starting docker_keira2_1 ... done
Attaching to docker_mariadb_1, docker_authserver_1, docker_worldserver_1, docker_tcjsonapi_1, docker_keira2_1 
mariadb_1      | 2019-04-18 22:32:18 139843018065856 [Note] mysqld (mysqld 10.1.26-MariaDB-1~jessie) starting as process 1 ... 
mariadb_1      | 2019-04-18 22:32:18 139843018065856 [Note] Using unique option prefix 'myisam_recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.
mariadb_1      | 2019-04-18 22:32:18 139843018065856 [Note] InnoDB: Using mutexes to ref count buffer pool pages
mariadb_1      | 2019-04-18 22:32:18 139843018065856 [Note] InnoDB: The InnoDB memory heap is disabled
mariadb_1      | 2019-04-18 22:32:18 139843018065856 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mariadb_1      | 2019-04-18 22:32:18 139843018065856 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
mariadb_1      | 2019-04-18 22:32:18 139843018065856 [Note] InnoDB: Compressed tables use zlib 1.2.8
mariadb_1      | 2019-04-18 22:32:18 139843018065856 [Note] InnoDB: Using Linux native AIO
mariadb_1      | 2019-04-18 22:32:18 139843018065856 [Note] InnoDB: Using generic crc32 instructions
mariadb_1      | 2019-04-18 22:32:18 139843018065856 [Note] InnoDB: Initializing buffer pool, size = 256.0M
mariadb_1      | 2019-04-18 22:32:18 139843018065856 [Note] InnoDB: Completed initialization of buffer pool
mariadb_1      | 2019-04-18 22:32:18 139843018065856 [Note] InnoDB: Highest supported file format is Barracuda.
mariadb_1      | 2019-04-18 22:32:18 139843018065856 [Note] InnoDB: The log sequence number 5132263 in ibdata file do not match the log sequence number 5132300 in the ib_logfiles!
mariadb_1      | 2019-04-18 22:32:18 139843018065856 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
mariadb_1      | InnoDB: wrong number of columns in SYS_INDEXES record
mariadb_1      | InnoDB: wrong number of columns in SYS_INDEXES record
mariadb_1      | InnoDB: wrong number of columns in SYS_INDEXES record
mariadb_1      | InnoDB: wrong number of columns in SYS_INDEXES record
mariadb_1      | InnoDB: wrong number of columns in SYS_INDEXES record
mariadb_1      | InnoDB: wrong number of columns in SYS_INDEXES record
mariadb_1      | 2019-04-18 22:32:18 139843018065856 [Note] InnoDB: Creating tablespace and datafile system tables.
mariadb_1      | 2019-04-18 22:32:18 139843018065856 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18.  Tablespace is full. Dropping incompletely created tables.
mariadb_1      | 2019-04-18 22:32:18 7f2fbd6a87c0  InnoDB: Assertion failure in thread 139843018065856 in file dict0crea.cc line 1903
authserver_1   | wait-for-it.sh: waiting for mariadb:3306 without a timeout
mariadb_1      | InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS
mariadb_1      | InnoDB: We intentionally generate a memory trap.
mariadb_1      | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
mariadb_1      | InnoDB: If you get repeated assertion failures or crashes, even
mariadb_1      | InnoDB: immediately after the mysqld startup, there may be
mariadb_1      | InnoDB: corruption in the InnoDB tablespace. Please refer to
mariadb_1      | InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
mariadb_1      | InnoDB: about forcing recovery.
mariadb_1      | 190418 22:32:18 [ERROR] mysqld got signal 6 ;
mariadb_1      | This could be because you hit a bug. It is also possible that this binary
mariadb_1      | or one of the libraries it was linked against is corrupt, improperly built,
mariadb_1      | or misconfigured. This error can also be caused by malfunctioning hardware.
worldserver_1  | wait-for-it.sh: waiting for mariadb:3306 without a timeout
mariadb_1      |
mariadb_1      | To report this bug, see https://mariadb.com/kb/en/reporting-bugs
mariadb_1      |
mariadb_1      | We will try our best to scrape up some info that will hopefully help
mariadb_1      | diagnose the problem, but since we have already crashed,
mariadb_1      | something is definitely wrong and this may fail.
mariadb_1      |
mariadb_1      | Server version: 10.1.26-MariaDB-1~jessie
mariadb_1      | key_buffer_size=134217728
mariadb_1      | read_buffer_size=2097152
mariadb_1      | max_used_connections=0
mariadb_1      | max_threads=102
mariadb_1      | thread_count=0
mariadb_1      | It is possible that mysqld could use up to
mariadb_1      | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759842 K  bytes of memory
mariadb_1      | Hope that's ok; if not, decrease some variables in the equation.
mariadb_1      |
mariadb_1      | Thread pointer: 0x0
mariadb_1      | Attempting backtrace. You can use the following information to find out
mariadb_1      | where mysqld died. If you see no messages after this, something went
mariadb_1      | terribly wrong...
mariadb_1      | stack_bottom = 0x0 thread_stack 0x30000
mariadb_1      | mysqld(my_print_stacktrace+0x2e)[0x559b056b6e2e]
mariadb_1      | mysqld(handle_fatal_signal+0x2fd)[0x559b051edaed]
mariadb_1      | /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f2fbd28a890]
mariadb_1      | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f2fbb37a067]
mariadb_1      | /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f2fbb37b448]
mariadb_1      | mysqld(+0x8942ab)[0x559b054d22ab]
mariadb_1      | mysqld(+0x7fe688)[0x559b0543c688]
mariadb_1      | mysqld(+0x71e367)[0x559b0535c367]
tcjsonapi_1    | wait-for-it.sh: waiting for mariadb:3306 without a timeout
mariadb_1      | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x559b051efd84]
mariadb_1      | mysqld(+0x4322f5)[0x559b050702f5]
mariadb_1      | mysqld(_Z11plugin_initPiPPci+0x8aa)[0x559b050719ca]
mariadb_1      | mysqld(+0x38c03e)[0x559b04fca03e]
mariadb_1      | mysqld(_Z11mysqld_mainiPPc+0x1b11)[0x559b04fcd9b1]
mariadb_1      | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f2fbb366b45]
mariadb_1      | mysqld(+0x38374d)[0x559b04fc174d]
mariadb_1      | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
mariadb_1      | information that should help you find out what is causing the crash.
mariadb_1      | Fatal signal 11 while backtracing
keira2_1       | AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 172.18.0.6. Set the 'ServerName' directive globally to suppress this message
keira2_1       | AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 172.18.0.6. Set the 'ServerName' directive globally to suppress this message
keira2_1       | [Thu Apr 18 22:32:24.210915 2019] [mpm_event:notice] [pid 1:tid 139888616684392] AH00489: Apache/2.4.39 (Unix) configured -- resuming normal operations
keira2_1       | [Thu Apr 18 22:32:24.212511 2019] [core:notice] [pid 1:tid 139888616684392] AH00094: Command line: 'httpd -D FOREGROUND'
docker_mariadb_1 exited with code 139
keira2_1       | 127.0.0.1 - - [18/Apr/2019:22:33:24 +0000] "HEAD /Keira2/index.html HTTP/1.1" 200 - 
keira2_1       | 127.0.0.1 - - [18/Apr/2019:22:34:24 +0000] "HEAD /Keira2/index.html HTTP/1.1" 200 - 
keira2_1       | 127.0.0.1 - - [18/Apr/2019:22:35:24 +0000] "HEAD /Keira2/index.html HTTP/1.1" 200 - 
keira2_1       | 127.0.0.1 - - [18/Apr/2019:22:36:25 +0000] "HEAD /Keira2/index.html HTTP/1.1" 200 - 
keira2_1       | 127.0.0.1 - - [18/Apr/2019:22:37:25 +0000] "HEAD /Keira2/index.html HTTP/1.1" 200 - 
keira2_1       | 127.0.0.1 - - [18/Apr/2019:22:38:25 +0000] "HEAD /Keira2/index.html HTTP/1.1" 200 - ```

[braddevans]

fixes from current pull requests merged in https://github.com/braddevans/trinitycore