install freezes at "Loading Character Set specific data 59%"

[earmsby]

Ok, I restarted this project today. I completely deleted the previous test store directory (in Filezilla) and I completely deleted the database I created yesterday. I even redownloaded the 1.5.5 zip file from SourceForge. Unfortunately, I'm still stalling out in "loading character set specific data." Comparing the database data to the mysql_utf8.sql file in the install folder, I can see that the countries were added except the last one and no zones have been added. Unlike yesterday, this time a DEBUG log file was generated and it has 14 lines that all say:

[13-Apr-2016 10:45:59 America/New_York] PHP Warning:  mysqli_connect(): (HY000/2002): No such file or directory in /homepages/PATH_TO_STORE/includes/classes/db/mysql/query_factory.php on line 102

In case any of this is pertinent to the problem, here is as much information as I can collect about the server and site:

Host: 1&1
PHP version: 5.5.34
MYSQL version: 5.5

Thanks, DrByte for your previous assistance on this. Is there anything else that would shed light on this issue?

[earmsby]

On closer inspection, I'm not sure that debug line is related to the problem of running the [COLOR=#333333]mysql_utf8.sql file. The time stamp on that file is earlier than the last zcInstallLog file that ends with:


Apr 13 2016 10:49 -- General
processing file /homepages/22/d250293540/htdocs/155_store_upgrade/zc_install/sql/install/mysql_utf8.sql

Not knowing exactly how this new installation works, it sure looks to me like the process partially completes the SQL statements in that file but doesn't finish and doesn't do anything further.

Hope there is some way to complete this install on this server. The host is forcing my client to upgrade to php 7 soon (or pay extra money) and I'm aware that only zc 1.5.5 works with php 7.

[DrByte]

On closer inspection, I'm not sure that debug line is related to the problem of running the [COLOR=#333333]mysql_utf8.sql file. The time stamp on that file is earlier than the last zcInstallLog file that ends with:


Apr 13 2016 10:49 -- General
processing file /homepages/22/d250293540/htdocs/155_store_upgrade/zc_install/sql/install/mysql_utf8.sql

Not knowing exactly how this new installation works, it sure looks to me like the process partially completes the SQL statements in that file but doesn't finish and doesn't do anything further.

You are correct in your understanding of the flow.

I'm still puzzled about why it's halting, and at different points each time.

[wilt]

Hi

Can you provide info regarding your server setup

e.g. php version, mysql version etc.

your admin/server_info.php will provide this info

Or put a file on your server like this:
filename: phpinfo.php

<?php echo phpinfo();

and point your browser to that phpinfo.php file, to see the details on-screen.
Delete the file when done.

[earmsby]

Thanks Wilt, I think I did give the php and mysql versions above. :)

[earmsby]

Could it have anything to do with collation? As far as I can tell from everything I can see in phpMyAdmin the database and tables use UTF, but is it possible that something somewhere else is latin-1 and that is causing a problem? I guess if that were the problem none of the UTF-8 data would be written.

Next, I wonder if the issue has something to do with 1&1. I might try to replicate this install on another server just to see if I get a different result or if the same thing happens.

Meanwhile, if you can think of any other possible reason or possible place for me to look for info that would shed light on the problem, I'd be appreciative.

I'm guessing no one else has reported any problem like this?

Thanks for your help!

[DrByte]

[QUOTE=earmsby;1308471]Could it have anything to do with collation? As far as I can tell from everything I can see in phpMyAdmin the database and tables use UTF, but is it possible that something somewhere else is latin-1 and that is causing a problem? I guess if that were the problem none of the UTF-8 data would be written.
[/code]
For a fresh install I don't see how collation matters in this context.

Next, I wonder if the issue has something to do with 1&1. I might try to replicate this install on another server just to see if I get a different result or if the same thing happens.

Perhaps.

I'm guessing no one else has reported any problem like this?

Nobody.
Of the hundreds of installs I've done, I've not encountered it failing like this, at least not without logging a "why" in the logs.

[lat9]

Are you trying to enable HTTPS from the get-go? 1&1 (shared-server accounts) currently has some "issues" like no support for TLS 1.2 that could be getting in the way.

[earmsby]

Are you trying to enable HTTPS from the get-go? 1&1 (shared-server accounts) currently has some "issues" like no support for TLS 1.2 that could be getting in the way.

Yes, I was using HTTPS from the start because the current live site does. I thought you had to use https to even be able to log into the admin section at all. I guess I try the process again without it just to see what happens and if that makes a difference.

[DrByte]

[13-Apr-2016 10:45:59 America/New_York] PHP Warning:  mysqli_connect(): (HY000/2002): No such file or directory

While the wording is strange, that combination of error number and error message usually means it can't connect to the database. And often it's because of mismatches in the way the server's name-resolution is working.
Sometimes changing the DB_SERVER from 'localhost' to '127.0.0.1' is enough to fix it.

It could be that you were getting those errors before zc_install asked you for the db details (and thus the errors are just a byproduct of the system-inspection probing that zc_install does) ... and then those errors stopped after you gave it your real db details. In that case those errors can be ignored.