alex
March 24, 2017, 3:39pm
83
Sure. No problem.
When you do, run docker-compose down
That will destroy the instance you have, leaving all your data secure.
Then delete everything in the db
folder in shared
, and then have another go at the import, ensuring your database export is in the right place, right name etc.
Then you can run docker-compose up -d
to bring it up and import
Are there any specua commands for the import apart from the normal one. I did docker-compose up -d.
I exported my dm from phpmyadmin and made the folders as per the instructions, copied the sql file into the required place and copied thd media into the correct folder.
Also is it possible to change the ip of the virtual instance as at ghe moment its given itself a 192 address which is not on out subnet so the clients will not ba able to see it.
Thanks
I tried that and no change, then I realised that there is no db folder in shared folder, the only things that are there are the folders I created during setup with my media copied and my import.sql.
Iâve been over the instruction again and again and cant see where im going wrong.
I also added apicture as some new media to the install and still no db folder or file appeared and the media I uploaded is not located in the media folder I created with my media from the old version.
Hello Alex,
Any ideas what might be going wrong now?
Thanks
alex
March 27, 2017, 11:27am
87
Sounds like the files arenât being correctly mapped in to the container.
Whatâs the output of docker-compose config
Can i email you that as theres obviously passwords in there and stuff
As far as I can tell, the instructions say modify that file but but you donât need to do anything in it if you dont want to use email?
Hi Alex,
Iâve ditched Docker toolbox and downloaded docker for windows and seem to be getting somewhere. Im up to the bot when I should be typing in localhost but am getting this error in the browser
Fatal Error - sorry this shouldnât happen. SQLSTATE[28000] [1045] Access denied for user âcmsâ@â172.18.0.4â (using password: NO)
Things are looking more promising though as I have the db folder created now.
alex
March 27, 2017, 3:46pm
91
Youâve not put a password in the config.env file for the new MySQL account to use.
You need to do docker-compose down
, edit config.env
, put in a password, then bring the containers up.
Hello Alex,
Thanks for that, slightly different error now though
Fatal Error - sorry this shouldnât happen. SQLSTATE[28000] [1045] Access denied for user âcmsâ@â172.18.0.4â (using password: YES)
alex
March 28, 2017, 8:38am
93
I missed a step in my previous response.
Basically, when you run the containers for the first time, if you specify the password for the cms account, the MySQL container creates the database we need and a user with the password you specified.
If you leave that blank, then when it runs, it writes the empty database and then youâve missed your chance for it to create the user automatically.
What you therefore need to do is:
docker-compose down
Delete the shared/db
folder
docker-compose up -d
That way the MySQL container is created fresh with no data and the thing will provision correctly.
Ok, So do i need to rename my sql file back to import.sql again so it all gets put in or will it stay there?
alex
March 28, 2017, 8:47am
95
You will need to rename it back to import.sql so it is picked up and imported.
Well weâre getting somewhere but fix one error and another one comes.
All iâm getting when I browse to localhost now isâŚ
alex
March 28, 2017, 9:00am
97
Did your import file get renamed?
What does the docker-compose log
show - redacted for any passwords etc?
Yeah its been renamed back to import.sql.done and all the folders are back.
Attaching to xibodocker_cms-web_1, xibodocker_cms-xmr_1, xibodocker_cms-db_1
cms-web_1 | Waiting for MySQL to start - max 300 seconds
cms-web_1 | MySQL started
cms-web_1 | Attempting to import database
cms-web_1 | Importing Database
cms-web_1 | Configuring Database Settings
cms-web_1 | Setting up Maintenance
cms-web_1 | ERROR 1146 (42S02) at line 1: Table âcms.versionâ doesnât exist
cms-web_1 | New install
cms-web_1 | Provisioning Database
cms-web_1 | ERROR 1054 (42S22) at line 4 in file: â/var/www/cms/install/master/data.sqlâ: Unknown column âisSystemNotificationâ in 'field listâ
cms-web_1 | ERROR 1452 (23000) at line 11 in file: â/var/www/cms/install/master/constraints.sqlâ: Cannot add or update a child row: a foreign key constraint fails (cms
.#sql-1_d
, CONSTRAINT campaign_ibfk_1
FOREIGN KEY (UserID
) REFERENCES user
(UserID
))
cms-web_1 | Configuring Database Settings
cms-web_1 | Setting up Maintenance
cms-web_1 | Updating settings.php
cms-web_1 | Configuring Backups
cms-web_1 | Configuring Maintenance
cms-web_1 | Running maintenance
cms-web_1 | Not FoundStarting cron
cms-web_1 | Starting webserver
cms-web_1 | AH00558: apache2: Could not reliably determine the serverâs fully qualified domain name, using 172.18.0.4. Set the âServerNameâ directive globally to suppress this message
cms-db_1 | Initializing database
cms-db_1 | 2017-03-28 08:51:54 0 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap.
cms-db_1 | 2017-03-28 08:51:54 0 [Note] /usr/sbin/mysqld (mysqld 5.6.35) starting as process 33 âŚ
cms-db_1 | 2017-03-28 08:51:54 33 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2017-03-28 08:51:54 33 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2017-03-28 08:51:54 33 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2017-03-28 08:51:54 33 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2017-03-28 08:51:54 33 [Note] InnoDB: Compressed tables use zlib 1.2.8
cms-db_1 | 2017-03-28 08:51:54 33 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2017-03-28 08:51:54 33 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2017-03-28 08:51:54 33 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2017-03-28 08:51:54 33 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2017-03-28 08:51:54 33 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
cms-db_1 | 2017-03-28 08:51:54 33 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
cms-db_1 | 2017-03-28 08:51:54 33 [Note] InnoDB: Database physically writes the file full: waitâŚ
cms-db_1 | 2017-03-28 08:51:55 33 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
cms-db_1 | 2017-03-28 08:51:55 33 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
cms-db_1 | 2017-03-28 08:51:56 33 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
cms-db_1 | 2017-03-28 08:51:56 33 [Warning] InnoDB: New log files created, LSN=45781
cms-db_1 | 2017-03-28 08:51:56 33 [Note] InnoDB: Doublewrite buffer not found: creating new
cms-db_1 | 2017-03-28 08:51:56 33 [Note] InnoDB: Doublewrite buffer created
cms-db_1 | 2017-03-28 08:51:56 33 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2017-03-28 08:51:56 33 [Warning] InnoDB: Creating foreign key constraint system tables.
cms-db_1 | 2017-03-28 08:51:56 33 [Note] InnoDB: Foreign key constraint system tables created
cms-db_1 | 2017-03-28 08:51:56 33 [Note] InnoDB: Creating tablespace and datafile system tables.
cms-db_1 | 2017-03-28 08:51:56 33 [Note] InnoDB: Tablespace and datafile system tables created.
cms-db_1 | 2017-03-28 08:51:56 33 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2017-03-28 08:51:56 33 [Note] InnoDB: 5.6.35 started; log sequence number 0
cms-db_1 | 2017-03-28 08:51:57 33 [Note] Binlog end
cms-db_1 | 2017-03-28 08:51:57 33 [Note] InnoDB: FTS optimize thread exiting.
cms-db_1 | 2017-03-28 08:51:57 33 [Note] InnoDB: Starting shutdownâŚ
cms-db_1 | 2017-03-28 08:51:59 33 [Note] InnoDB: Shutdown completed; log sequence number 1625977
cms-db_1 |
cms-db_1 |
cms-db_1 | 2017-03-28 08:51:59 0 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap.
cms-db_1 | 2017-03-28 08:51:59 0 [Note] /usr/sbin/mysqld (mysqld 5.6.35) starting as process 56 âŚ
cms-db_1 | 2017-03-28 08:51:59 56 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2017-03-28 08:51:59 56 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2017-03-28 08:51:59 56 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2017-03-28 08:51:59 56 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2017-03-28 08:51:59 56 [Note] InnoDB: Compressed tables use zlib 1.2.8
cms-db_1 | 2017-03-28 08:51:59 56 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2017-03-28 08:51:59 56 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2017-03-28 08:51:59 56 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2017-03-28 08:51:59 56 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2017-03-28 08:51:59 56 [Note] InnoDB: Highest supported file format is Barracuda.
cms-db_1 | 2017-03-28 08:51:59 56 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2017-03-28 08:51:59 56 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2017-03-28 08:51:59 56 [Note] InnoDB: 5.6.35 started; log sequence number 1625977
cms-db_1 | 2017-03-28 08:51:59 56 [Note] Binlog end
cms-db_1 | 2017-03-28 08:51:59 56 [Note] InnoDB: FTS optimize thread exiting.
cms-db_1 | 2017-03-28 08:51:59 56 [Note] InnoDB: Starting shutdownâŚ
cms-db_1 | 2017-03-28 08:52:01 56 [Note] InnoDB: Shutdown completed; log sequence number 1625987
cms-db_1 |
cms-db_1 |
cms-db_1 |
cms-db_1 |
cms-db_1 | PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
cms-db_1 | To do so, start the server, then issue the following commands:
cms-db_1 |
cms-db_1 | /usr/bin/mysqladmin -u root password 'new-passwordâ
cms-db_1 | /usr/bin/mysqladmin -u root -h cd7b030e2702 password 'new-passwordâ
cms-db_1 |
cms-db_1 | Alternatively you can run:
cms-db_1 |
cms-db_1 | /usr/bin/mysql_secure_installation
cms-db_1 |
cms-db_1 | which will also give you the option of removing the test
cms-db_1 | databases and anonymous user created by default. This is
cms-db_1 | strongly recommended for production servers.
cms-db_1 |
cms-db_1 | See the manual for more instructions.
cms-db_1 |
cms-db_1 | Please report any problems at http://bugs.mysql.com/
cms-db_1 |
cms-db_1 | The latest information about MySQL is available on the web at
cms-db_1 |
cms-db_1 | http://www.mysql.com
cms-db_1 |
cms-db_1 | Support MySQL by buying support/licenses at http://shop.mysql.com
cms-db_1 |
cms-db_1 | Note: new default config file not created.
cms-db_1 | Please make sure your config file is current
cms-db_1 |
cms-db_1 | WARNING: Default config file /etc/mysql/my.cnf exists on the system
cms-db_1 | This file will be read by default by the MySQL server
cms-db_1 | If you do not want to use this, either remove it, or use the
cms-db_1 | --defaults-file argument to mysqld_safe when starting the server
cms-db_1 |
cms-db_1 | Database initialized
cms-db_1 | MySQL init process in progressâŚ
cms-db_1 | 2017-03-28 08:52:01 0 [Note] mysqld (mysqld 5.6.35) starting as process 79 âŚ
cms-db_1 | 2017-03-28 08:52:01 79 [Note] Plugin âFEDERATEDâ is disabled.
cms-db_1 | 2017-03-28 08:52:01 79 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2017-03-28 08:52:01 79 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2017-03-28 08:52:01 79 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2017-03-28 08:52:01 79 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2017-03-28 08:52:01 79 [Note] InnoDB: Compressed tables use zlib 1.2.8
cms-db_1 | 2017-03-28 08:52:01 79 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2017-03-28 08:52:01 79 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2017-03-28 08:52:01 79 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2017-03-28 08:52:01 79 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2017-03-28 08:52:01 79 [Note] InnoDB: Highest supported file format is Barracuda.
cms-db_1 | 2017-03-28 08:52:01 79 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2017-03-28 08:52:01 79 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2017-03-28 08:52:01 79 [Note] InnoDB: 5.6.35 started; log sequence number 1625987
cms-db_1 | 2017-03-28 08:52:01 79 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: cf439d4e-1393-11e7-97da-0242ac120002.
cms-db_1 | 2017-03-28 08:52:01 79 [Warning] âuserâ entry âroot@cd7b030e2702â ignored in --skip-name-resolve mode.
cms-db_1 | 2017-03-28 08:52:01 79 [Warning] âuserâ entry â@cd7b030e2702 â ignored in --skip-name-resolve mode.
cms-db_1 | 2017-03-28 08:52:01 79 [Warning] âproxies_privâ entry â@ root@cd7b030e2702â ignored in --skip-name-resolve mode.
cms-db_1 | 2017-03-28 08:52:01 79 [Note] Event Scheduler: Loaded 0 events
cms-db_1 | 2017-03-28 08:52:01 79 [Note] mysqld: ready for connections.
cms-db_1 | Version: â5.6.35â socket: â/var/run/mysqld/mysqld.sockâ port: 0 MySQL Community Server (GPL)
cms-db_1 | Warning: Unable to load â/usr/share/zoneinfo/iso3166.tabâ as time zone. Skipping it.
cms-db_1 | Warning: Unable to load â/usr/share/zoneinfo/leap-seconds.listâ as time zone. Skipping it.
cms-db_1 | Warning: Unable to load â/usr/share/zoneinfo/zone.tabâ as time zone. Skipping it.
cms-db_1 | GENERATED ROOT PASSWORD: jo4quoopuchang1Mai6yiu5eeth7boaw
cms-db_1 | 2017-03-28 08:52:03 79 [Warning] âproxies_privâ entry â@ root@cd7b030e2702â ignored in --skip-name-resolve mode.
cms-db_1 | Warning: Using a password on the command line interface can be insecure.
cms-db_1 | Warning: Using a password on the command line interface can be insecure.
cms-db_1 | Warning: Using a password on the command line interface can be insecure.
cms-db_1 | Warning: Using a password on the command line interface can be insecure.
cms-db_1 | 2017-03-28 08:52:03 79 [Warning] âproxies_privâ entry â@ root@cd7b030e2702â ignored in --skip-name-resolve mode.
cms-db_1 |
cms-db_1 | 2017-03-28 08:52:03 79 [Note] mysqld: Normal shutdown
cms-db_1 |
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Giving 0 client threads a chance to die gracefully
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Event Scheduler: Purging the queue. 0 events
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down slave threads
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Forcefully disconnecting 0 remaining clients
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Binlog end
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'partitionâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_SYS_DATAFILESâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACESâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLSâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_SYS_FOREIGNâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_SYS_FIELDSâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_SYS_COLUMNSâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_SYS_INDEXESâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATSâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_SYS_TABLESâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLEâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHEâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_FT_CONFIGâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETEDâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_FT_DELETEDâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORDâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_METRICSâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATSâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRUâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_BUFFER_PAGEâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESETâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEXâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_CMPMEM_RESETâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_CMPMEMâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_CMP_RESETâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_CMPâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_LOCK_WAITSâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_LOCKSâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'INNODB_TRXâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] Shutting down plugin 'InnoDBâ
cms-db_1 | 2017-03-28 08:52:03 79 [Note] InnoDB: FTS optimize thread exiting.
cms-db_1 | 2017-03-28 08:52:03 79 [Note] InnoDB: Starting shutdownâŚ
cms-db_1 | 2017-03-28 08:52:05 79 [Note] InnoDB: Shutdown completed; log sequence number 1625997
cms-db_1 | 2017-03-28 08:52:05 79 [Note] Shutting down plugin 'BLACKHOLEâ
cms-db_1 | 2017-03-28 08:52:05 79 [Note] Shutting down plugin 'ARCHIVEâ
cms-db_1 | 2017-03-28 08:52:05 79 [Note] Shutting down plugin 'PERFORMANCE_SCHEMAâ
cms-db_1 | 2017-03-28 08:52:05 79 [Note] Shutting down plugin 'MRG_MYISAMâ
cms-db_1 | 2017-03-28 08:52:05 79 [Note] Shutting down plugin 'MyISAMâ
cms-db_1 | 2017-03-28 08:52:05 79 [Note] Shutting down plugin 'CSVâ
cms-db_1 | 2017-03-28 08:52:05 79 [Note] Shutting down plugin 'MEMORYâ
cms-db_1 | 2017-03-28 08:52:05 79 [Note] Shutting down plugin 'sha256_passwordâ
cms-db_1 | 2017-03-28 08:52:05 79 [Note] Shutting down plugin 'mysql_old_passwordâ
cms-db_1 | 2017-03-28 08:52:05 79 [Note] Shutting down plugin 'mysql_native_passwordâ
cms-db_1 | 2017-03-28 08:52:05 79 [Note] Shutting down plugin 'binlogâ
cms-db_1 | 2017-03-28 08:52:05 79 [Note] mysqld: Shutdown complete
cms-db_1 |
cms-db_1 |
cms-db_1 | MySQL init process done. Ready for start up.
cms-db_1 |
cms-db_1 | 2017-03-28 08:52:05 0 [Note] mysqld (mysqld 5.6.35) starting as process 1 âŚ
cms-db_1 | 2017-03-28 08:52:05 1 [Note] Plugin âFEDERATEDâ is disabled.
cms-db_1 | 2017-03-28 08:52:05 1 [Note] InnoDB: Using atomics to ref count buffer pool pages
cms-db_1 | 2017-03-28 08:52:05 1 [Note] InnoDB: The InnoDB memory heap is disabled
cms-db_1 | 2017-03-28 08:52:05 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
cms-db_1 | 2017-03-28 08:52:05 1 [Note] InnoDB: Memory barrier is not used
cms-db_1 | 2017-03-28 08:52:05 1 [Note] InnoDB: Compressed tables use zlib 1.2.8
cms-db_1 | 2017-03-28 08:52:05 1 [Note] InnoDB: Using Linux native AIO
cms-db_1 | 2017-03-28 08:52:05 1 [Note] InnoDB: Using CPU crc32 instructions
cms-db_1 | 2017-03-28 08:52:05 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M
cms-db_1 | 2017-03-28 08:52:05 1 [Note] InnoDB: Completed initialization of buffer pool
cms-db_1 | 2017-03-28 08:52:05 1 [Note] InnoDB: Highest supported file format is Barracuda.
cms-db_1 | 2017-03-28 08:52:05 1 [Note] InnoDB: 128 rollback segment(s) are active.
cms-db_1 | 2017-03-28 08:52:05 1 [Note] InnoDB: Waiting for purge to start
cms-db_1 | 2017-03-28 08:52:05 1 [Note] InnoDB: 5.6.35 started; log sequence number 1625997
cms-db_1 | 2017-03-28 08:52:05 1 [Note] Server hostname (bind-address): â*â; port: 3306
cms-db_1 | 2017-03-28 08:52:05 1 [Note] IPv6 is available.
cms-db_1 | 2017-03-28 08:52:05 1 [Note] - â::â resolves to â::â;
cms-db_1 | 2017-03-28 08:52:05 1 [Note] Server socket created on IP: â::â.
cms-db_1 | 2017-03-28 08:52:05 1 [Warning] âproxies_privâ entry â@ root@cd7b030e2702â ignored in --skip-name-resolve mode.
cms-db_1 | 2017-03-28 08:52:06 1 [Note] Event Scheduler: Loaded 0 events
cms-db_1 | 2017-03-28 08:52:06 1 [Note] mysqld: ready for connections.
cms-db_1 | Version: â5.6.35â socket: â/var/run/mysqld/mysqld.sockâ port: 3306 MySQL Community Server (GPL)
alex
March 28, 2017, 9:09am
99
Your database export is incomplete.
See it imports your existing database, and then tests to see if thereâs a version table.
If youâre exporting the database with PHPMyAdmin then it will fail silently if the database is too large for it to export. You need to use mysqldump to get a complete valid backup.
Once you have that, youâll need to down the containers, delete the DB folder, put your import.sql in the right place, and then bring the containers up again.
Ok Iâll have a go at that, thanks
More progress but more errors, Got everything imorted and started to run teh upgrade and it has stopped on this -
alex
March 28, 2017, 10:50am
102
I expect thereâs something in one of your existing datasets that it isnât able to convert.
Itâs possible itâs related to this:
Do you have datasets with select from list content?