Database errors during writing

I believe this may be related to the database build mode. Are you using mysqlsql dump? If so after generating a package click on the Details of the package, it will be a link like [View NN], then click on the SQL button and see if the SQL file was built. If its mostly blank then there is a bug with writing to mysql via the shell. Let me know what you find.

Thanks

Thanks for your reply.

No, the SQL file is well filled.
After the try of implementation of the database, there’s no tables created in the database, and hundreds of errors for each table, like we can see in installer-log.txt :

--------------------------------------
DATABASE RESULTS
--------------------------------------
**ERROR** database error write 'Unknown collation: 'utf8mb4_unicode_ci'' - [sql=
CREATE TABLE <code>wp_commentmeta</code> (
  <code>meta_id</code> bigint(20) unsigned NOT NULL A...]

(etc...)

Thanks

I’ve finally found what the problem was!

Like I said, after the launching of the installer.php on the new website, another installation of WordPress was needed. And when I did it, the error was like written below for all the creations of tables :
Unknown character set: 'utf8mb4'

So the solution was to edit the SQL (found in the archive) by replacing every utf8mb4 character set with utf8.
The problem was certainly because of the use of an old version of MySQL by the server (5.3.16), and the character set utf8mb4 has been introduced with 5.5.3.

I don’t know if you could change something in your plugin to avoid this kind of problem…

Thanks anyway!

Thanks for the update Alex. I’ll do some research to see if this is something that I can integrate…

Cheers~

Oh thank God for you, alex.mqt!!! I’m using IX Webhosting and I had the exact same problem. I couldn’t figure out why it wasn’t creating my tables!

@alex.mqt thank you very much

still I get One Deploy Error……….please anyone help in this

********************************************************************************
DUPLICATOR INSTALL-LOG
STEP1 START @ 11:22:45
NOTICE: Do NOT post to public sites or forums
********************************************************************************
VERSION: 0.5.22
PHP: 5.4.41 | SAPI: cgi-fcgi
SERVER: Apache Phusion_Passenger/4.0.10 mod_bwlimited/1.4 mod_fcgid/2.3.9
DOC ROOT: /home/kanvipno/public_html/new/skc
DOC ROOT 755: true
LOG FILE 644: true
BUILD NAME: 20150529_skcet_556d8ec5bd8f34236150602110853

********************************************************************************
ARCHIVE SETUP
********************************************************************************
NAME: 20150529_skcet_556d8ec5bd8f34236150602110853_archive.zip
SIZE: 25.44MB
ZIP: Enabled (ZipArchive Support)
EXTRACTING
ZipArchive Object
(
[status] => 0
[statusSys] => 0
[numFiles] => 1895
[filename] => /home/kanvipno/public_html/new/skc/20150529_skcet_556d8ec5bd8f34236150602110853_archive.zip
[comment] =>
)
COMPLETE: true

WEB SERVER CONFIGURATION FILE RESET:
– Backup of .htaccess/web.config made to .orig
– Reset of .htaccess/web.config files

UPDATED FILES:
– SQL FILE: ‘/home/kanvipno/public_html/new/skc/installer-data.sql’
– WP-CONFIG: ‘/home/kanvipno/public_html/new/skc/wp-config.php’

ARCHIVE RUNTIME: 54.5108 sec.

********************************************************************************
DATABASE-ROUTINES
********************************************************************************
————————————–
SERVER ENVIROMENT
————————————–
MYSQL VERSION: 5.1.60-rel13.1-log
TIMEOUT: 300
MAXPACK: 1048576
————————————–
DATABASE RESULTS
————————————–
**ERROR** database error write ‘MySQL server has gone away’ – [sql=/* DUPLICATOR MYSQL SCRIPT CREATED ON : 2015-06-02 11:09:53 */

SET FOREIGN…]
ERRORS FOUND: 1
DROP TABLE: Database already empty. Ready for install.
QUERIES RAN: 782

sk_commentmeta: (0)
sk_comments: (1)
sk_duplicator_packages: (1)
sk_links: (0)
sk_options: (160)
sk_postmeta: (403)
sk_posts: (132)
sk_term_relationships: (41)
sk_term_taxonomy: (5)
sk_terms: (5)
sk_usermeta: (20)
sk_users: (1)
skc_commentmeta: (0)
skc_comments: (2)
skc_duplicator_packages: (0)
skc_links: (0)
skc_options: (121)
skc_postmeta: (406)
skc_posts: (110)
skc_term_relationships: (42)
skc_term_taxonomy: (5)
skc_terms: (5)
skc_usermeta: (22)
skc_users: (1)
Removed ’30’ cache/transient rows

SECTION RUNTIME: 0.8957 sec.

********************************************************************************
STEP1 COMPLETE @ 11:23:41 – TOTAL RUNTIME: 55.4083 sec.
********************************************************************************

********************************************************************************
DUPLICATOR INSTALL-LOG
STEP2 START @ 11:23:49
NOTICE: Do not post to public sites or forums
********************************************************************************
CHARSET SERVER: latin1
CHARSET CLIENT: utf8

————————————–
SERIALIZER ENGINE
[*] scan every column
[~] scan only text columns
[^] no searchable columns
————————————–
sk_commentmeta^ (0)
sk_comments~ (1)
sk_duplicator_packages^ (0)
sk_links^ (0)
sk_options~ (128)
sk_postmeta~ (403)
sk_posts~ (132)
sk_term_relationships~ (41)
sk_term_taxonomy~ (5)
sk_terms~ (5)
sk_usermeta~ (20)
sk_users~ (1)
skc_commentmeta^ (0)
skc_comments~ (2)
skc_duplicator_packages^ (0)
skc_links^ (0)
skc_options~ (121)
skc_postmeta~ (406)
skc_posts~ (110)
skc_term_relationships~ (42)
skc_term_taxonomy~ (5)
skc_terms~ (5)
skc_usermeta~ (22)
skc_users~ (1)
————————————–
SEARCH1: ‘https://localhost/skcet’
REPLACE1: ‘https://kanvismedia.com/new/skc’
SEARCH2: ‘C:/xampp/htdocs/skcet/’
REPLACE2: ‘/home/kanvipno/public_html/new/skc/’
SCANNED: Tables:24 | Rows:1450 | Cells:10380
UPDATED: Tables:1 | Rows:144 |Cells:184
ERRORS: 0
RUNTIME: 1.194300 sec

********************************************************************************
START FINAL CLEANUP: 11:23:51
********************************************************************************
UPDATE sk_blogs SET domain = ‘kanvismedia.com’ WHERE domain = ‘localhost’

————————————–
WARNINGS
————————————–
No Warnings Found

WEB SERVER CONFIGURATION FILE BASIC SETUP:
created basic .htaccess file. If using IIS web.config this process will need to be done manually.
********************************************************************************
STEP 2 COMPLETE @ 11:23:51 – TOTAL RUNTIME: 1.2096 sec.
********************************************************************************

Hey Shrini,

You will need to make sure you remove the package an installer from your system you reference in the log above as it contains sensitive info. As far as your error you may have to try the process again, it looks like mysql somehow lost connection during the process:

**ERROR** database error write ‘MySQL server has gone away’ – [sql=/* DUPLICATOR MYSQL SCRIPT CREATED ON : 2015-06-02 11:09:53 */

Connection lost issues can be difficult to isolate.

Thanks Cory Lamle

Glad to help, hope you get things going…

Thanks alex.mqt for the solution. For me I had a similar situation, The above solution was nearly enough to fix, I then had to go in the wp-config file and update the db charset to utf8

Good to go!

I had the same issue, and the solution provided by alex.mqt worked as well. For what it’s worth, I host with Dreamhost and they provide MySQL version 5.1.56. Would love to see this solution integrated with Duplicator.

I had the same issue and this thread got me fixed. I am very grateful for the support, both by Cory and this community. I had a very different experience with WP Migrate DB. Its author refuses to provide an ounce of support for his free version and his minimum price is more than twice Duplicator Pro’s. So when I go pro, I’ll go Duplicator! Meanwhile, I sent in a donation.

Thanks and good luck to all.

Gary S.

Hey Gary,

Thanks for the contribution! Glad you were able to get your issue worked out…

Cheers~

Hi Cory,
Do you think you could massage that SQL file and change the UTF stuff automatically?
Alex above had mentioned that he hand-edited the SQL file:

So the solution was to edit the SQL (found in the archive) by replacing every utf8mb4 character set with utf8.

I’m running into a problem with CanvasHost where they haven’t bothered to update MySQL to the latest, and this seems to be a big issue. I’m assuming that having “utf8mb4” is not such an important thing, if “utf8” works? So just a search/replace of the SQL automatically before you wrap up the package. Maybe you could have an option for “Make package less compatible” if it IS important to have the mb4 stuff.

BTW I had donated back in December; thanks for the continual updates you’ve been doing for this plugin. We’ve given up on trying to use it over at MediaTemple and are just doing it the hard way, but for other hosts like SiteGround (and until recently CanvasHost) your plugin works like a charm!