jaybird2203

Members
  • Posts

    56
  • Joined

  • Last visited

Everything posted by jaybird2203

  1. Yeah, that sorted the issue on my setup - thanks for the direction! Always get cautious about a plugin that manages a driver and the direction given is to remove the driver lol
  2. @ich777 Had to go back awhile but did this step and driver has updated. Still seeing the same web error about trying to download the last listed version in the pop up as well as the php error on the left side. Guessing I'd need to remove the plugin, reboot, reinstall the plugin yeah? Don't see any steps on removing the driver itself.
  3. Nope, doesn't bother me in the slightest. Was simply thinking if other users were looking for that instant gratification of deleting and getting an immediate update on size they could use that approach of navigating to the share tab until both had the same functionality implemented. Sent from my SM-G975W using Tapatalk
  4. I have the update recycle bin in the background set as yes and noticed that if you manually navigate to the shares tab then delete the files from there instead of the main settings page the size is still updated almost instantly. I'm guessing the two locations to empty the recycle bin are handled differently in regards to the listed size? Any intention to bring the shares tab into that same approach?
  5. Thanks for the quick response Squid, I've moved the flash drive to another port on the motherboard. This time its specifically a USB2 port. I'll continue to monitor. Is there any validation/test that can be done on the flash drive to ensure its not in early stages of dying? Drive itself is less than a year old since being replaced from a previous flash drive I was using for unraid.
  6. I've been running 6.8.0 rc-9 with only one issue that's happened twice. First time I wasn't able to capture it but this time I did. Last time the server had ~30 days of run time, this time its 21 days. It appears that when the server gets into this state it's no longer detected on the network yet you can access it directly (if you use the network location \\Tower) to view folder structure and use Dockers (webpages direct like tower:8080) but as soon as you attempt to copy a file the connection will drop and the client PC will report 0x8007003B. Has happened on two different PC's. I've attached the diagnostics while its in this state as well as provided a few screenshots of the webpage (that should be dark) yet its clearly white. Any assistance is greatly appreciated. tower-diagnostics-20191229-1218.zip
  7. I've been running 6.8.0 rc-9 with only one issue that's happened twice. First time I wasn't able to capture it but this time I did. Last time the server had ~30 days of run time, this time its 21 days. It appears that when the server gets into this state it's no longer detected on the network yet you can access it directly (if you use the network location \\Tower) to view folder structure and use Dockers (webpages direct like tower:8080) but as soon as you attempt to copy a file the connection will drop and the client PC will report 0x8007003B. Has happened on two different PC's. I've attached the diagnostics while its in this state as well as provided a few screenshots of the webpage (that should be dark) yet its clearly white. Any assistance is greatly appreciated. tower-diagnostics-20191229-1218.zip
  8. Appreciate the quick response. OK, so the scenario is to be expected then. I swear I used to recall there was a time recently where you could trigger the mover and remain on that page at which point once the mover was finished the page/button would revert back to being able to trigger again (not that you would)
  9. Was running rc7 for ~40 days (upgraded to rc7 shortly after its release) until I had an issue with my system recently where the main web page background was completely white with the text being slightly grey despite my theme being set to black along with an inability to restart some dockers after a power outage running on UPS. Hard reboot of the system brought that back but ever since then things have been "off" from normal operations. Attached diagnostics are from ~20 mins prior to this post while running rc9 and reverting the majority of the issues I could correct easily. Core System specs: Asus Crosshair 6 w/3900x (7501 bios), 32 GB DDR4 ram. Now I may have other underlying issues that may be influencing this (and I'd love some assistance pointing out potential ones) but I just noticed that with both Chrome and Edge web browsers there are pages that are not updating automatically. One such page is when starting the Mover manually. It does not revert back to the Orange Move now but but stay with the greyed out Move Now button and "Disabled - Mover is running." message being shown. CPU dashboard is showing that its appears to be updating dynamically there but I'm at a loss for where to check/test next to address this. The file share functionality and the Dockers are still operating normally as best I can tell and a quick revert to rc7 didn't change this behavior. Any thoughts? (marking this as Minor to rule out other potential issues first but if its only webpage related then should be annoyance) tower-diagnostics-20191208-1547.zip
  10. Quick question that I may have missed so apologies in advance. Looking for the proper way to setup Radarr to use the standard unraid recycle bin plug-in by dlandon rather than pointing to a empty folder then manually deleting from there. Any assistance with this is greatly appreciated.
  11. Upgraded directly from 6.6.6 with no issues. Been running ~4 days no issues, Ryzen 1700 + Asus Crosshair mobo.
  12. Appreciate the quick turn around. Can report that the details do remain after the upgrade so that portion was addressed. Sent from my SM-T700 using Tapatalk
  13. Hi All, Having an issue with the recent linuxserver/openvpn-as repo build of Openvpn-as that I hope someone can shed some light. Running 6.7.0-rc-7 right now, haven't updated openVPN in ages (can't recall prior build but already did the network type = bridge and removal of "interface=eth0" modifications which all worked until I tried to change the network settings the clients could access) but decided to nuke the full install and start from scratch. As it stands now I'm able to install the docker, get into the GUI and add a new user although every time I attempt to stop/start the docker it appears the install reverts back to defaults. I mean my users details, as.conf settings and not sure what else all revert back to the defaults as if the file has been completely wiped. I've tried using the same app folder location and new app folder location but nothing appears to be retained. File permissions look correct (nobody/users) and the cache drive works for the other dockers just not this one. Any assistance is greatly appreciated. App run is as follows: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='OpenVPN' --net='bridge' --log-opt max-size='10m' --log-opt max-file='3' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'PGID'='100' -e 'PUID'='99' -p '943:943/tcp' -p '9443:9443/tcp' -p '1194:1194/udp' -v '/mnt/user/Dockers/openvpn':'/config':'rw' 'linuxserver/openvpn-as' 566e0951ece71323f6fa1a567f02a72ba1301036be09ca43ccd155914931f7b6 logs when the docker starts (up to EULA) are as follows: [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/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-time: executing... Current default time zone: 'America/New_York' Local time is now: Sat Apr 6 22:45:22 EDT 2019. Universal Time is now: Sun Apr 7 02:45:22 UTC 2019. [cont-init.d] 20-time: exited 0. [cont-init.d] 30-config: executing... existing data found, reinstalling openvpn-as backing up certs.db backing up cluster.db backing up config.db backing up config_local.db backing up log.db backing up notification.db backing up userprop.db backing up as.conf Selecting previously unselected package openvpn-as. (Reading database ... 11947 files and directories currently installed.) Preparing to unpack /openvpn/openvpn.deb ... Unpacking openvpn-as (2.7.3-05bc07c0-Ubuntu16) ... Setting up openvpn-as (2.7.3-05bc07c0-Ubuntu16) ... Automatic configuration failed, see /usr/local/openvpn_as/init.log You can configure manually using the /usr/local/openvpn_as/bin/ovpn-init tool. Automatic configuration failed, see /usr/local/openvpn_as/init.log You can configure manually using the /usr/local/openvpn_as/bin/ovpn-init tool. Beginning with OpenVPN AS 2.6.0 compression is disabled by default and on upgrades as security patch. restoring certs.db restoring cluster.db restoring config.db restoring config_local.db restoring log.db restoring certs.db restoring cluster.db restoring config.db restoring config_local.db restoring log.db restoring notification.db restoring userprop.db restoring as.conf [cont-init.d] 30-config: exited 0. [cont-init.d] 40-openvpn-init: executing... Detected an existing OpenVPN-AS configuration. Continuing will delete this configuration and restart from scratch. Please enter 'DELETE' to delete existing configuration: OpenVPN Access Server Initial Configuration Tool ------------------------------------------------------ OpenVPN Access Server End User License Agreement (OpenVPN-AS EULA)
  14. Sweet, just did the steps and looks like the cache drives are back to the pool. Just copying the files back. Here's the diagnostics for ref.
  15. Ok so ran the check disk filesystems using the scrub option given the btrfs and cache pool and it couldn't repair the error, specifically "error details: csum=1" Once that was completed I stopped array, unassigned the cache drives and restarted the array. Immediately got a message from the "fix common errors" about detecting hardware errors, so installed mcelog plugin via nerdpack then restarted complete tower. Didn't see the same error but pulled diagnostics and attached. Since then I've backup the contents of the cache drive and I'm open to completely destroying the pool and starting from scratch although I can't seem to find the location where I can reformat from the gui. I have the preclear plugin installed but didn't think that'd be the proper way to format the drives and start from scratch.
  16. ok cool. I'll look into the overheating on the CPU shortly, I've recently moved and the CPU/MOBO combo has been installed for ages so wouldn't be surprised if it shifted slightly recently.
  17. should I back up my dockers from the cache only share first?
  18. Hi All, Been using unraid for awhile now, since 6.0b13 if memory serves and the system has been decent until today. I've had 6.3.3 installed since the day it was made available and upgraded from 6.3.2 with no issues. Just today though all of a sudden my shares are completely blank, all drives were still online and when browsing them through the main -> array devices I could see all the folder structure of the original shares, although the shares were completely blank. I've pulled diagnostics and attached for pre and post reboot to see if there's anything outstanding. I've removed the name of the files that were moved from the syslog but that's it. One thing I noticed is that the shares themselves are gone from within the shares folder from the diagnostics yet after the reboot they're all there..... Any assistance will be greatly appreciated.
  19. 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
  20. 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
  21. Yep, no change when using nano from within Unraid itself either. Edit: only changes are taken when I use nano from within the docker (after I manually installed it) and modifying the my.cnf file. obviously that's not the best path but at this point that is allows the changes to be taken.
  22. @CHBMB Unless I'm missing something, the only *.cnf file in the appdata folder ( /config ) is the custom.cnf which is the file that by default is the one that is world writable. This is why I'm having a hard time trying to nail down why I'm not able to make changes to the config by default with the default settings on the docker. That said, I've had to install nano using the deb package manually to edit the my.cnf in /etc/mysql/ stop then start the container for the changes to actually stick when using the remote mysqlclient. At this point if that doesn't work for my needs I'll have to revert back to using mariaDB within the VM itself which I was trying to avoid.
  23. I previously tried stopping the docker prior to editing or moving the appdata folder, ensuring the appdata folder is fresh and not changed from defaults..default my.cnf settings are used..... I looked into the ownership on the custom.cnf file and it's the same root:root from a default install to after being edited once the docker is stopped. All I've tried to confirm that the custom.cnf file is being used is changing the max_connections from 100 to 200. details from the unraid gui logs for mariadb followed from the logs in the same location but just after the fresh install. I'm looking at the lines below specifically Warning: World-writable config file '/etc/mysql/conf.d/custom.cnf' is ignored ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| 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. Warning: World-writable config file '/etc/mysql/conf.d/custom.cnf' is ignored Warning: World-writable config file '/etc/mysql/conf.d/custom.cnf' is ignored 170321 08:03:56 mysqld_safe Logging to syslog. 170321 08:03:56 mysqld_safe Starting mysqld daemon with databases from /config/databases That's the same as the log after a fresh install. [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 Warning: World-writable config file '/etc/mysql/conf.d/custom.cnf' is ignored Installing MariaDB/MySQL system tables in '/config/databases' ... Warning: World-writable config file '/etc/mysql/conf.d/custom.cnf' is ignored 2017-03-21 7:59:38 47847027015424 [Note] /usr/sbin/mysqld (mysqld 10.1.22-MariaDB-1~xenial) starting as process 248 ... 2017-03-21 7:59:38 47847027015424 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2017-03-21 7:59:38 47847027015424 [Note] InnoDB: The InnoDB memory heap is disabled 2017-03-21 7:59:38 47847027015424 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2017-03-21 7:59:38 47847027015424 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2017-03-21 7:59:38 47847027015424 [Note] InnoDB: Compressed tables use zlib 1.2.8 2017-03-21 7:59:38 47847027015424 [Note] InnoDB: Using Linux native AIO 2017-03-21 7:59:38 47847027015424 [Note] InnoDB: Using SSE crc32 instructions 2017-03-21 7:59:38 47847027015424 [Note] InnoDB: Initializing buffer pool, size = 256.0M 2017-03-21 7:59:38 47847027015424 [Note] InnoDB: Completed initialization of buffer pool 2017-03-21 7:59:38 47847027015424 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created! 2017-03-21 7:59:38 47847027015424 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB 2017-03-21 7:59:38 47847027015424 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB 2017-03-21 7:59:39 47847027015424 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB 2017-03-21 7:59:39 47847027015424 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 2017-03-21 7:59:39 47847027015424 [Warning] InnoDB: New log files created, LSN=45883 2017-03-21 7:59:39 47847027015424 [Note] InnoDB: Doublewrite buffer not found: creating new 2017-03-21 7:59:39 47847027015424 [Note] InnoDB: Doublewrite buffer created 2017-03-21 7:59:39 47847027015424 [Note] InnoDB: 128 rollback segment(s) are active. 2017-03-21 7:59:39 47847027015424 [Warning] InnoDB: Creating foreign key constraint system tables. 2017-03-21 7:59:39 47847027015424 [Note] InnoDB: Foreign key constraint system tables created 2017-03-21 7:59:39 47847027015424 [Note] InnoDB: Creating tablespace and datafile system tables. 2017-03-21 7:59:39 47847027015424 [Note] InnoDB: Tablespace and datafile system tables created. 2017-03-21 7:59:39 47847027015424 [Note] InnoDB: Waiting for purge to start 2017-03-21 7:59:39 47847027015424 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 0 2017-03-21 7:59:39 47847833601792 [Note] InnoDB: Dumping buffer pool(s) not yet started 2017-03-21 7:59:39 47847027530496 [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... Warning: World-writable config file '/etc/mysql/conf.d/custom.cnf' is ignored 2017-03-21 7:59:42 47067448139520 [Note] /usr/sbin/mysqld (mysqld 10.1.22-MariaDB-1~xenial) starting as process 278 ... 2017-03-21 7:59:42 47067448139520 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2017-03-21 7:59:42 47067448139520 [Note] InnoDB: The InnoDB memory heap is disabled 2017-03-21 7:59:42 47067448139520 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2017-03-21 7:59:42 47067448139520 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2017-03-21 7:59:42 47067448139520 [Note] InnoDB: Compressed tables use zlib 1.2.8 2017-03-21 7:59:42 47067448139520 [Note] InnoDB: Using Linux native AIO 2017-03-21 7:59:42 47067448139520 [Note] InnoDB: Using SSE crc32 instructions 2017-03-21 7:59:42 47067448139520 [Note] InnoDB: Initializing buffer pool, size = 256.0M 2017-03-21 7:59:42 47067448139520 [Note] InnoDB: Completed initialization of buffer pool 2017-03-21 7:59:42 47067448139520 [Note] InnoDB: Highest supported file format is Barracuda. 2017-03-21 7:59:42 47067448139520 [Note] InnoDB: 128 rollback segment(s) are active. 2017-03-21 7:59:42 47067448139520 [Note] InnoDB: Waiting for purge to start 2017-03-21 7:59:42 47067448139520 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 1616799 2017-03-21 7:59:42 47068248831744 [Note] InnoDB: Dumping buffer pool(s) not yet started OK Creating OpenGIS required SP-s... Warning: World-writable config file '/etc/mysql/conf.d/custom.cnf' is ignored 2017-03-21 7:59:45 46988664037120 [Note] /usr/sbin/mysqld (mysqld 10.1.22-MariaDB-1~xenial) starting as process 308 ... 2017-03-21 7:59:45 46988664037120 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2017-03-21 7:59:45 46988664037120 [Note] InnoDB: The InnoDB memory heap is disabled 2017-03-21 7:59:45 46988664037120 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2017-03-21 7:59:45 46988664037120 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2017-03-21 7:59:45 46988664037120 [Note] InnoDB: Compressed tables use zlib 1.2.8 2017-03-21 7:59:45 46988664037120 [Note] InnoDB: Using Linux native AIO 2017-03-21 7:59:45 46988664037120 [Note] InnoDB: Using SSE crc32 instructions 2017-03-21 7:59:45 46988664037120 [Note] InnoDB: Initializing buffer pool, size = 256.0M 2017-03-21 7:59:45 46988664037120 [Note] InnoDB: Completed initialization of buffer pool 2017-03-21 7:59:45 46988664037120 [Note] InnoDB: Highest supported file format is Barracuda. 2017-03-21 7:59:45 46988664037120 [Note] InnoDB: 128 rollback segment(s) are active. 2017-03-21 7:59:45 46988664037120 [Note] InnoDB: Waiting for purge to start 2017-03-21 7:59:45 46988664037120 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 1616809 2017-03-21 7:59:45 46989463025408 [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 e796d217e613 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/ Warning: World-writable config file '/etc/mysql/conf.d/custom.cnf' is ignored 2017-03-21 7:59:48 47292679749376 [Note] mysqld (mysqld 10.1.22-MariaDB-1~xenial) starting as process 336 ... 2017-03-21 7:59:48 47292679749376 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2017-03-21 7:59:48 47292679749376 [Note] InnoDB: The InnoDB memory heap is disabled 2017-03-21 7:59:48 47292679749376 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2017-03-21 7:59:48 47292679749376 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2017-03-21 7:59:48 47292679749376 [Note] InnoDB: Compressed tables use zlib 1.2.8 2017-03-21 7:59:48 47292679749376 [Note] InnoDB: Using Linux native AIO 2017-03-21 7:59:48 47292679749376 [Note] InnoDB: Using SSE crc32 instructions 2017-03-21 7:59:48 47292679749376 [Note] InnoDB: Initializing buffer pool, size = 256.0M 2017-03-21 7:59:48 47292679749376 [Note] InnoDB: Completed initialization of buffer pool 2017-03-21 7:59:48 47292679749376 [Note] InnoDB: Highest supported file format is Barracuda. 2017-03-21 7:59:48 47292679749376 [Note] InnoDB: 128 rollback segment(s) are active. 2017-03-21 7:59:48 47292679749376 [Note] InnoDB: Waiting for purge to start 2017-03-21 7:59:48 47292679749376 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 1616819 2017-03-21 7:59:48 47293478762240 [Note] InnoDB: Dumping buffer pool(s) not yet started 2017-03-21 7:59:48 47292679749376 [Note] Plugin 'FEEDBACK' is disabled. 2017-03-21 7:59:48 47292679749376 [Warning] Failed to create a socket for IPv6 '::': errno: 97. 2017-03-21 7:59:48 47292679749376 [Note] Server socket created on IP: '0.0.0.0'. 2017-03-21 7:59:48 47292679749376 [Note] Reading of all Master_info entries succeded 2017-03-21 7:59:48 47292679749376 [Note] Added new Master_info '' to hash table 2017-03-21 7:59:48 47292679749376 [Note] mysqld: ready for connections. Version: '10.1.22-MariaDB-1~xenial' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution Warning: World-writable config file '/etc/mysql/conf.d/custom.cnf' is ignored 2017-03-21 7:59:50 47292731407104 [Note] mysqld: Normal shutdown 2017-03-21 7:59:50 47292731407104 [Note] Event Scheduler: Purging the queue. 0 events 2017-03-21 7:59:50 47293482964736 [Note] InnoDB: FTS optimize thread exiting. 2017-03-21 7:59:50 47292731407104 [Note] InnoDB: Starting shutdown... 2017-03-21 7:59:50 47292731407104 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool 2017-03-21 7:59:52 47292731407104 [Note] InnoDB: Shutdown completed; log sequence number 1616829 2017-03-21 7:59:52 47292731407104 [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. Warning: World-writable config file '/etc/mysql/conf.d/custom.cnf' is ignored Warning: World-writable config file '/etc/mysql/conf.d/custom.cnf' is ignored 170321 07:59:52 mysqld_safe Logging to syslog. 170321 07:59:52 mysqld_safe Starting mysqld daemon with databases from /config/databases [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [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... usermod: no changes
  24. I've got an interesting situation, just tried to install this docker the other day on 6.3.2, installed beside all other dockers no issues. can run and create databases no issue. My issue comes in when attempting to make any changes to the custom.cnf file, they're not being taken. I've verified this by going into a fresh install, fresh appdata folder then using mysqlclient install on a remote pc to log into the mysql port then running show variables like 'xxxxxx'; which returns the default settings. Same thing goes for the default install location, same thing, make changes in custom.cnf and they're ignored. Any thoughts? my initial thought is the the /etc/mysql/my.cnf is being used over this custom file.
  25. If it works for you let me know and I'll try the same but back to the drive mounted outside my array using unassigned devices.