Installation Woes - Time out when Adding Block Types
Permalink
Hi Folks
Total newbie here doing first install of version 5.7.5.9
All goes well until it gets to Adding Block Types and then says "Connection Timed Out - Please try again". When you hit the Back button to try again you get told that the database needs to be empty! I look at the database and it is nicely populated with tables, so I delete the database and start again. I get the same timeout. Have tried this several times and it always times out when "Adding Block Types".
Where do I start?
Is there someway to try again without having to delete/empty the database?
Is there someway to extend the timeout period?
FYI the site is being hosted on Laughing Squid. All the requirements get the tick
Cheers
Tim
Total newbie here doing first install of version 5.7.5.9
All goes well until it gets to Adding Block Types and then says "Connection Timed Out - Please try again". When you hit the Back button to try again you get told that the database needs to be empty! I look at the database and it is nicely populated with tables, so I delete the database and start again. I get the same timeout. Have tried this several times and it always times out when "Adding Block Types".
Where do I start?
Is there someway to try again without having to delete/empty the database?
Is there someway to extend the timeout period?
FYI the site is being hosted on Laughing Squid. All the requirements get the tick
Cheers
Tim
Maybe the database connection is timing out? Can you post any screenshots?
After starting "Adding Block Types" as attached I get the time out as attached after 30 seconds.
I don't get anything in my PHP error log and have set the following php values in the.htaccess file
php_value mysql.connect_timeout 60
php_value max_execution_time 60
I cant see anything in phpinfo() that is set to 30 seconds
I don't get anything in my PHP error log and have set the following php values in the.htaccess file
php_value mysql.connect_timeout 60
php_value max_execution_time 60
I cant see anything in phpinfo() that is set to 30 seconds
Gotcha. You should change the title of your post to something like "Install Timing Out at Adding Block Types". I thought you where getting this error after trying to add a block to your page, meaning it would have already been installed.
I thought that setting the category would take care of that, but the category doesn't show! Changed it now
Which one of the plans are you on with laughing squid?
Sorry didn't notice it was in Installation section at first. You could change the title again to something like 'Hosting Provider Woes'...
Just kidding!
Do you have access to server error logs? How are you doing the install, are you uploading the files yourself or is it some kind of included installer from Liquid Squid?
You'll have to keep clearing the database when it fails because its being populated before the crash, so starting over means needing a fresh database.
I'm not sure what causing it to timeout in exactly 30 seconds each time. Do you know what version of mySQL is running in your web host?
Do you set the database host to localhost or does liquid squid provide you some other URL URL?
Do you happen to have PHP safe mode enabled in your web hosting?
Sorry didn't notice it was in Installation section at first. You could change the title again to something like 'Hosting Provider Woes'...
Just kidding!
Do you have access to server error logs? How are you doing the install, are you uploading the files yourself or is it some kind of included installer from Liquid Squid?
You'll have to keep clearing the database when it fails because its being populated before the crash, so starting over means needing a fresh database.
I'm not sure what causing it to timeout in exactly 30 seconds each time. Do you know what version of mySQL is running in your web host?
Do you set the database host to localhost or does liquid squid provide you some other URL URL?
Do you happen to have PHP safe mode enabled in your web hosting?
Been doing some more research for you:
Concerning Laughing Squid:
"There are many service interruptions, while most of them are caused by constant server errors instead of the facilities of RackSpace. Many of Laughing Squid users have moved away in the past months due to this reason."
"Laughing Squid has been a little bit slow all the time. But the problem has become more severe. About half a year ago, the average server response was approximately 800ms, while the figure is now over 1000ms. During some spikes, the response time is even longer than 3000ms. Loading a simple page can take more than 10 seconds. Below is the recent monitoring."
This could have to do with the timeouts...
Source:https://whatswp.com/laughing-squid-review/...
Concerning Laughing Squid:
"There are many service interruptions, while most of them are caused by constant server errors instead of the facilities of RackSpace. Many of Laughing Squid users have moved away in the past months due to this reason."
"Laughing Squid has been a little bit slow all the time. But the problem has become more severe. About half a year ago, the average server response was approximately 800ms, while the figure is now over 1000ms. During some spikes, the response time is even longer than 3000ms. Loading a simple page can take more than 10 seconds. Below is the recent monitoring."
This could have to do with the timeouts...
Source:https://whatswp.com/laughing-squid-review/...
Which one of the plans are you on with laughing squid? - MicroSquid
Do you have access to server error logs? - not yet,looking for them!
How are you doing the install, are you uploading the files yourself or is it some kind of included installer from Liquid Squid? - FTP upload, that was 3 hours of fun
You'll have to keep clearing the database when it fails because its being populated before the crash, so starting over means needing a fresh database. - That is painful!
Do you know what version of mySQL is running in your web host? - 5.5.49
Do you set the database host to localhost or does liquid squid provide you some other URL URL? - separate URL
Do you happen to have PHP safe mode enabled in your web hosting? - disabled
Do you have access to server error logs? - not yet,looking for them!
How are you doing the install, are you uploading the files yourself or is it some kind of included installer from Liquid Squid? - FTP upload, that was 3 hours of fun
You'll have to keep clearing the database when it fails because its being populated before the crash, so starting over means needing a fresh database. - That is painful!
Do you know what version of mySQL is running in your web host? - 5.5.49
Do you set the database host to localhost or does liquid squid provide you some other URL URL? - separate URL
Do you happen to have PHP safe mode enabled in your web hosting? - disabled
Tim,
I learned something new. The concrete5 command line tool allows you to reset the database so you don't have to do that yourself manually. If you have access to the server command line, you can run from the concrete/bin directory.
I learned something new. The concrete5 command line tool allows you to reset the database so you don't have to do that yourself manually. If you have access to the server command line, you can run
./concrete5 c5:reset
Unfortunately I don't have access to the command line :(
The admins at LaughingSquid had a go at installing it and point the finger back to the Concrete Code
To quote:
I also tried installing the 'full site' version and it timed out after some tables were created. I have increased the timeout to 60 seconds but it is not making it the full amount of time before failing which points to a different issue other than a timeout. It may be beneficial to try a fresh copy of the software.
Stack trace:
#0 /mnt/stor09-wc1-ord1/782565/857499/www.bazingoid.com.au/web/content/concrete/controllers/install.php(284): Whoops\Run->handleError(2, 'require(/mnt/st...', '/mnt/stor09-wc1...', 284, Array)
#1 /mnt/stor09-wc1-ord1/782565/857499/www.bazingoid.com.au/web/content/concrete/controllers/install.php(284): Concrete\Controller\Install::run_routine()
#2 [internal function]: Concrete\Controller\Install->run_routine('elemental_full', 'install_image_e...')
#3 /mnt/stor09-wc1-ord1/782565/857499/www.bazingoid.com.au/web/content/concrete/src/Controller/AbstractController.php(161): call_user_func_array(Array, Array)
#4 /mnt/stor09-wc1-ord1/782565/857499/www.bazingoid.com.au/web in /mnt/stor09-wc1-ord1/782565/857499/www.bazingoid.com.au/web/content/concrete/controllers/install.php on line 284
[22-Sep-2016 15:58:47 America/Chicago] PHP Fatal error: Concrete\Controller\Install::run_routine(): Failed opening required '/mnt/stor09-wc1-ord1/782565/857499/www.bazingoid.com.au/web/content/application/config/site_install.php' (include_path='/mnt/stor09-wc1-ord1/782565/857499/www.bazingoid.com.au/web/content/concrete/vendor:.:/usr/share/php:/usr/share/pear') in /mnt/stor09-wc1-ord1/782565/857499/www.bazingoid.com.au/web/content/concrete/controllers/install.php on line 284
I did find a potential work around where someone created a local install then uploaded the created database and some of the other required files. Further information can be found here:https://www.concrete5.org/developers/bugs/5-7-3-1/installation-fails...
Beyond my skill level to proceed from here without a few pointers
The admins at LaughingSquid had a go at installing it and point the finger back to the Concrete Code
To quote:
I also tried installing the 'full site' version and it timed out after some tables were created. I have increased the timeout to 60 seconds but it is not making it the full amount of time before failing which points to a different issue other than a timeout. It may be beneficial to try a fresh copy of the software.
Stack trace:
#0 /mnt/stor09-wc1-ord1/782565/857499/www.bazingoid.com.au/web/content/concrete/controllers/install.php(284): Whoops\Run->handleError(2, 'require(/mnt/st...', '/mnt/stor09-wc1...', 284, Array)
#1 /mnt/stor09-wc1-ord1/782565/857499/www.bazingoid.com.au/web/content/concrete/controllers/install.php(284): Concrete\Controller\Install::run_routine()
#2 [internal function]: Concrete\Controller\Install->run_routine('elemental_full', 'install_image_e...')
#3 /mnt/stor09-wc1-ord1/782565/857499/www.bazingoid.com.au/web/content/concrete/src/Controller/AbstractController.php(161): call_user_func_array(Array, Array)
#4 /mnt/stor09-wc1-ord1/782565/857499/www.bazingoid.com.au/web in /mnt/stor09-wc1-ord1/782565/857499/www.bazingoid.com.au/web/content/concrete/controllers/install.php on line 284
[22-Sep-2016 15:58:47 America/Chicago] PHP Fatal error: Concrete\Controller\Install::run_routine(): Failed opening required '/mnt/stor09-wc1-ord1/782565/857499/www.bazingoid.com.au/web/content/application/config/site_install.php' (include_path='/mnt/stor09-wc1-ord1/782565/857499/www.bazingoid.com.au/web/content/concrete/vendor:.:/usr/share/php:/usr/share/pear') in /mnt/stor09-wc1-ord1/782565/857499/www.bazingoid.com.au/web/content/concrete/controllers/install.php on line 284
I did find a potential work around where someone created a local install then uploaded the created database and some of the other required files. Further information can be found here:https://www.concrete5.org/developers/bugs/5-7-3-1/installation-fails...
Beyond my skill level to proceed from here without a few pointers
I believe their answer proves it's their servers fault:
"I did find a potential work around where someone created a local install then uploaded the created database and some of the other required files..."
In other words, while the install script is trying to connect to their offsite sql host, it times out. But everything is fine when then manually import an already populate database, made outside their servers.
Which means even with their so called workaround, once you get in and start editing the site, you will most likely encounter more time outs as information tries to make it make to their sql host....
I could be mistaken, but it seems to be a pretty logical conclusion. Nice of them to go through all the trouble of making a local install and manually uploading it though.
EDIT:
The link they sent you is an issue caused by an incompatible server set up, enforcing my conclusion that its the host. I would run this by laughing squid: "Concrete5 5.7.x needs InnoDB rather than MyISAM as database storage engine"... maybe they are also using MyISAM like the folks having issues with host gator?
"I did find a potential work around where someone created a local install then uploaded the created database and some of the other required files..."
In other words, while the install script is trying to connect to their offsite sql host, it times out. But everything is fine when then manually import an already populate database, made outside their servers.
Which means even with their so called workaround, once you get in and start editing the site, you will most likely encounter more time outs as information tries to make it make to their sql host....
I could be mistaken, but it seems to be a pretty logical conclusion. Nice of them to go through all the trouble of making a local install and manually uploading it though.
EDIT:
The link they sent you is an issue caused by an incompatible server set up, enforcing my conclusion that its the host. I would run this by laughing squid: "Concrete5 5.7.x needs InnoDB rather than MyISAM as database storage engine"... maybe they are also using MyISAM like the folks having issues with host gator?
There's a chance that something more insidious could be going on, and the timeout is just a consequence. I vaguely recall installation problems involving incompatible date formats and null values; possibly even database case sensitivity.
I know that probably doesn't help much...
I know that probably doesn't help much...
Are there any solutions found meanwhile for this time out problem?
I have the exact same problem by trying to install version concrete5.7.5.9. The server support already extended the execution time but that doesnt help.
Please help anyone? What can I/the server support do?
I have the exact same problem by trying to install version concrete5.7.5.9. The server support already extended the execution time but that doesnt help.
Please help anyone? What can I/the server support do?
What's the servers database storage engine? There's several:https://en.wikipedia.org/wiki/Comparison_of_MySQL_database_engines...
Who's the hosting provider?
What is the PHP version?
Who's the hosting provider?
What is the PHP version?
Make sure your MySQL installation is up-to-date. The Core requirements on MySQL versions are a bit slack and can result in issues installing on MySQL versions that are older, but within the required versions.
