Windows 8.1, AMPPS 2.4, php 5.4.28, MySQL 5.6.17
I tried a Joomla installation from AMPPS backend, 3.3.6, no problem
Labels |
Added:
?
|
I tested it with mysql and postgresql both worked as expected
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
My first attempts were with test data. Now I tried again with no data - stuck again, but the progress bar went a bit further, to about 30%. I now also checked the error logs - nothing.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
Same here on WINDOWS 8.1, XAMPP 1.8.3, php 5.5.15, mysql 5.6.20
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
When you are installing are you selecting mysql or mysqli?
Can you try with the other one
On 17 October 2014 22:32, Nymphea Studio notifications@github.com wrote:
[image: screen shot 2014-10-17 at 16 26 13]
https://camo.githubusercontent.com/04df5f11aa855e421400d577ee6f0718f6281460/687474703a2f2f6973737565732e6a6f6f6d6c612e6f72672f75706c6f6164732f312f39393430636539396666336266336434333631346238386462343937656338342eSame here on WINDOWS 8.1, XAMPP 1.8.3, php 5.5.15, mysql 5.6.20
This comment was created with the J!Tracker Application
https://github.com/joomla/jissues at issues.joomla.org/joomla-cms/4813
http://issues.joomla.org/tracker/joomla-cms/4813.—
Reply to this email directly or view it on GitHub
#4813 (comment).
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/
OK, seems to be my system: I now downloaded 3.3.6 from joomla.org - same issue. (Note: previous installation of 3.3.6 - which worked - was from AMPPS backend)
So the question is, what's wrong with my system? And: if this happens here, it can happen elsewhere. This issue could turn into a feature request: check + error message ...
BTW: in phpMyAdmin I see that 62 tables have been created.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
was mysqli, same without the i
@nympheastudio - thanks for confirmation. Can't see screenshot.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
Can you check your server error logs and see if there's anything in there?
No - it eventually worked! Both staging with mysql, and 3.3.6 with mysqli - just took a very long time
Will try with staging + mysqli now, and watch some YouTube while it installs ...
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
First i got the bug with "mysqli" and now i try with "mysql".
Sorry for the pic, it was just the "installation" page stuck at almost 30 %
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
@ninicksavov - yes, I have checked the error logs - nothing.
Seems to work now - less than two minutes, including test data. I don't know what changed. Not aware of anything that could have slowed down the PC. (no I did not watch YouTube on the side ...)
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
i ll try on a distant debian, to be sure it s not linked to XAMP in my case.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
It s finish on the online server, it worked fine with "mysqli", but still stuck on XAMP with "mysql" choice.
So it looks like a XAMP problem for me, i ll retry on XAMP this WE.
now i go to the bed ;), good luck to everyone
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
Xampp 1.8.3 seems to be the problem on windows, download 1.8.1 and it will work
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
I have xampp 1.8.3 on Windows 7 and it works perfectly.
There have been two posts in the forum where the update has halted during the populating of the #_content_types Table. It appears to create the table, populate it then tries to populate it again and throws a Duplicate ID error on the first record. Both sites have several 3rd party extensions and to my knowledge has not happened with the update of a clean 2.5 Joomla.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
Tried again just now. Differences, as far as I can tell: re-pulled staging files and restarted the laptop - Windows updated itself. No problem today, installation went smoothly.
So I don't know what it was, just my system, a small change in one of the files, or solar flares. Sorry about the trouble - thanks for your testing etc.
@nympheastudio - how are your installations going?
As far as I'm concerned, this issue can be closed.
Remark on the side: As part of my test I copied a database with phpMyAdmin - failed a couple of times, max_execution_time in php.ini had to be increased to 180 (was 30). These failures caused timeout entries in the error log. Install failures yesterday caused no log entries.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
Closing as requested
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
Set to "closed" on behalf of @brianteeman by The JTracker Application at issues.joomla.org/joomla-cms/4813
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2014-10-18 08:24:52 |
the same for me , this morning i try a new install from joomla-cms-staging.zip (that failed last night on XAMP, but was ok online).
this morning the install was successfull on XAMP !
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
The issue still exists http://forum.joomla.org/viewtopic.php?f=710&t=861708#p3228461 It is undoubtable cause with an interaction with a 3rd party extension but something can trigger it.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
How can a third party extension effect the installation of joomla. You have not installed joomla yet so you cant have any third party extensions
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
Agree with Brian - it's not an installation of a backup like in the linked forum thread. Clean clone from Github.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
OK so because the problem in the forum relates to a working 2.5 site with extensions then the database error during update is not related to this tracker ?
So should a new tracker be created or is it not considered a bug because the error only occurs on working sites ?
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
Create a new tracker please as it is clearly a different issue to this one
as it is for a different version of Joomla
On 18 Oct 2014 13:03, "Webdongle" notifications@github.com wrote:
OK so because the problem in the forum relates to a working 2.5 site with
extensions then the database error during update is not related to this
tracker ?So should a new tracker be created or is it not considered a bug because
the error only occurs on working sites ?This comment was created with the J!Tracker Application
https://github.com/joomla/jissues at issues.joomla.org/joomla-cms/4813
http://issues.joomla.org/tracker/joomla-cms/4813.—
Reply to this email directly or view it on GitHub
#4813 (comment).
Just want to confirm that I got the same issue myself as well (install fresh version Joomla version 3.3.6). The information of my system:
PHP Built On Windows NT IT 6.3 build 9200 (Windows 8.1 Business Edition) i586
Database Version 5.6.21
Database Collation utf8_general_ci
PHP Version 5.5.17
Web Server Apache/2.4.10 (Win32) PHP/5.5.17
WebServer to PHP Interface apache2handler
Joomla! Version Joomla! 3.3.6 Stable [ Ember ] 01-October-2014 02:00 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
In my case, I solved the issue by increasing max execute time and memory limit via php.ini. Maybe you can try to do the same if you get this issue. (I got that issue both when I was using XAMP and the same later when I tried to install Apache, PHP, Mysql manually)
@joomdonation Did you have a look at your error logs? If it was a timeout or memory issue, it should show in there.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.
Hi !
Same here with XAMPP 3.2.1 and an empty DB install... Stucked while creating DB tables.
After trying to update from 2.5.8 to 3.3.6 which fails after several tryies, cleaning, etc.. i finaly tried to install a fresh 3.3.6 to see if i could import datas from my 2.5.8 site. But this fails also !
Really boring !
Thanks zero-24, but this did not help ...
I even tried with another WAMP server (UWamp) but same result !
Both Wamp are working fine with a full Akeeba backup of my 2.5.8 site.. Problem must be somewhere else..
What i noticed is that there are 59 tables in the DB that has been created. So ,something happens, but does not complete.
Answer to this problem here: (Open the following file mentioned in Notepad). THIS WORKS EVERYTIME.
https://www.youtube.com/watch?v=zPeFWwPMj_A
Published on Jun 9, 2014
This problem occurring most usually at Joomla 3.x. To solve this go to
D:\xampp\htdocs\joomla\installation\sql\mysql
and open Joomla.sql file find the term
"ENGINE=InnoDB"
and replace ALL with
"ENGINE=MyIsam"
While that may work, Joomla's technical requirements call for MySQL servers to support InnoDB.
If you have that problem (and it is solved by making this change) then the
problem is NOT with the latest versions of Joomla. The problem is that you
are using an old outdated version of xampp.
On 3 January 2015 at 01:23, Michael Babker notifications@github.com wrote:
While that may work, Joomla's technical requirements
https://www.joomla.org/technical-requirements.html call for MySQL
servers to support InnoDB.—
Reply to this email directly or view it on GitHub
#4813 (comment).
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/
It is hard to tell from the apachefriends exactly what version of xampp
changed from myisam to innodb but assuming they made the change at the
latest when they upgraded to use mysql 5.5 where innodb became the default
engine would be logical.
They switched to mysql 5.5 with version 1.7.4 which was released 2011-01-22
0 thats 4 YEARS AGO
On 3 January 2015 at 02:01, Brian Teeman brian@teeman.net wrote:
If you have that problem (and it is solved by making this change) then the
problem is NOT with the latest versions of Joomla. The problem is that you
are using an old outdated version of xampp.On 3 January 2015 at 01:23, Michael Babker notifications@github.com
wrote:While that may work, Joomla's technical requirements
https://www.joomla.org/technical-requirements.html call for MySQL
servers to support InnoDB.—
Reply to this email directly or view it on GitHub
#4813 (comment).Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/
No @brianteeman I'm using the latest xampp 3.2.1 and I'm facing the issue of bar stuck at about 30%, after I read @Maria9uk solution and it worked with me perfectly, thank you @Maria9uk
@yabasha There is no such thing as XAMPP 3.2.1, you probably refer to XAMPP Control Panel 3.2.1. Despite being the most recent control panel that information is pretty useless. It can be used with any version of XAMPP. The versions of XAMPP are 1.7.7, 1.8.1-x, 1.8.2-x, 1.8.3-x, 5.5.19, 5.6.3.
5.5.19 and 5.6.3 being the latest, named after the version of php it includes.
I had this happen on my laptop but not on my computer. Raising the max_execution time solved the problem.
It's basically just the machine or software being to slow.
With windows 8 there is some kind of problem between Apache and IPv6 that slows page loads etc. http://go.microsoft.com/?linkid=9728869 of http://support.microsoft.com/kb/929852/en-gb disables IPv6. If you wish to check if your ISP supports IPv6 see http://test-ipv6.com/
If you find disabling IPv6 causes problems then http://go.microsoft.com/?linkid=9732129 re-enables it.
@Webdongle XAMPP 5.6.3 has MySQL 5.6.21
@Webdongle Anything is possible. That means checking XAMPP Control Panel ->Config is the only way to find out the version. Assuming no mess was created with failed updates or any other manipulation with the installation!
@Webdongle This issue is already closed since October last year.
@Webdongle No I didn't update from an older version, I downloaded it directly from the official site for xampp: https://www.apachefriends.org/index.html I clicked on "XAMPP for Windows"
Labels |
Added:
?
|
I too faced the same issue of hanging of the installation of joomla 3.4.5 on my windows machine.
OS: Win 8.1 x64
XAMPP v3.2.1
Joomla: 3.4.5
I tried to perform the same 5-6 times. Then, after googling a lot came to conclusion that it can be resolved just my modifying 2 parameters in the php.ini config file usually located inside the
/php/php.ini
memory_limit = 512M
max_execution_time = 200
It worked. So, there is no need to modify the InnoDB engine to MyIsam. Base installation works well. Just the issue with our default settings of the php configuration.
Installed staging with no problem using test and brochure sample data sets
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4813.