SOLVED Xenon Rocketlauncher install fails /InnoDB vs MyIsam problem
-
-
- Walt
- Newbie
- Posts: 18
- Thanks: 0
-
The topic has been renamed and the initial post has been replaced here since it was in error. The final resolution is now copied to here, since it can easily be missed on page 2 of this series. It reads as follows:
I did as Reggie suggested (set display_errors=On) and IT WORKED! Thank you both so much.
Kat05 had suggested doing that earlier but I didn't think it was relevant, given that I had previously (on an older version of xampp) installed many rocketlaunchers with display_errors=On (and output_buffering=On/4096) and had no problem.
I am left wondering why these settings could cause the installation to fail when they seem to have no direct relationship to the process. It seems totally irrational, but there must be a reason, e.g. too many errors being generated (?). Anyway, no answer necessary on that.
Thanks again,
Walt - Last Edit: 7 years 5 months ago by Walt.
-
-
-
- Damir
- Preeminent Rocketeer
- Posts: 22450
- Thanks: 2679
- Web Developer
- What do you mean by this?
- Available for CUSTOM WORK with Joomla, WordPress and Grav Templates and Gantry Framework!
-
-
-
- Kat05
- Preeminent Rocketeer
- Posts: 25898
- Thanks: 334
-
Hi Walt,
I saw in our logs that Interstellar was the last template you have downloaded, so I've checked the current RocketLauncher and made a fresh install locally (using MAMP). All database tables use InnoDB except for #_finder_tokens and #_finder_tokens_aggregate which use MEMORY. I get the exact same result when I install a core Joomla 3.7.2 package as well as the previous core Joomla 3.6.5 package. Please could you be more specific about what the actual issue is that you're having with our RocketLaunchers and on which specific platforms you're seeing them? - Last Edit: 7 years 5 months ago by Kat05.
- Kat05 / QA Lead & Support / Germany
-
-
-
- Walt
- Newbie
- Posts: 18
- Thanks: 0
-
Kat05: I've completed more testing and it appears that I owe you (all) an apology.
In the past, when the xenon Rocketlauncher install would run forever, there was a "fix" [available from www.balbooa.com/knowledgebase/32-documen...ating-database-table ]. The fix required a change to the installation\sql\mysql\joomla.sql file, replacing"ENGINE=InnoDB" with "ENGINE=MyIsam".
But that was on an earlier release of xampp and Joomla back in February. Now I'm using xampp 7.1.1 and xenon (Kat05, not wamp & interstellar) on an up-to-date Windows10. I have just tested 4 combinations: InnoDB+MySQLi (the defaults), then InnoDB+MySQL(PDO), then MyIsam+MySQLi, then MyIsam+MySQL(PDO). They all fail in the same way.
It appears that the configuration.php file is not being created. In the forum it's suggested by Matt, Preeminent Rocketeer, (2 years ago) that "It's gotta be a server setting... permissions or owner/group issue on your server isn't allow that file to written on install... Make sure you FTP up the package from the account created for the webspace specifically and NOT with a reseller/root account."
There are no "permissions or owner/group issue" as Matt suggests. I'm working on my desktop, moving files directly, so no FTP/reseller issues either.
Does anyone have any further thoughts / insights?
-
-
-
- Walt
- Newbie
- Posts: 18
- Thanks: 0
-
Kat05: Further to my previous message to you:
Given the current status, the title of this topic should be something else, such as "Xenon Rocketlauncher installation fails".
To better define the problem I downloaded the latest xampp 7.1.4 (using xampp-win32-7.1.4-0-VC14-installer) and a fresh copy of xenon 1.3.0 Rocketlauncher. I installed xampp, and restored an Akeeba backup of my work to htdocs (it's called fjdp12 and is based on xenon) . The restored website works as it did before on xampp 7.1.1 (as it has in past upgrades of xampp). Then I installed the xenon Rocketlauncher and it fails to finish, (as stated earlier, apparently it cannot create the configuration.php file). Can you reproduce a Windows10 / xampp 7.1.4 / xenon 1.3.0 install? Or, suggest how I might proceed? Thanks...
-
-
-
- Walt
- Newbie
- Posts: 18
- Thanks: 0
-
Further to the previous messages:
I reproduced what your message suggests, by downloading a new copy of Joomla and installing it. So to summarize, we have current releases of everything: Windows10 (up-to-date), xampp 7.1.4, Joomla 3.7.2, all of which works, but xenon Rocketlauncher 1.3.0 fails. I have 2 screenshots attached showing the Rocketlauncher install.
The failing xenon Rocketlauncher install seems have a problem installing the sample data, then restarts the entire install again, then has the same problem, and repeats and repeats.
Thanks once again for your help.
-
-
-
- Kat05
- Preeminent Rocketeer
- Posts: 25898
- Thanks: 334
-
Hi Walt,
thanks a lot for the additional info!
Before I get to rechecking the Xenon RocketLauncher you've mentioned... I saw in one of your screenshots showing that pre-installation system check that 'Error reporting' is set to ON. I remember some users being able to resolve their RocketLauncher installation issues after they have changed that to OFF (which is recommended by Joomla).
Not sure if changing the setting 'Output Buffering' would have any effect, but it's possible too. Please note that a Joomla core install (especially when no sample data is selected) runs through much quicker than our RocketLauncher installations. Our RocketLaunchers do contain a lot more data than a regular core Joomla install. - Kat05 / QA Lead & Support / Germany
-
-
-
- Kat05
- Preeminent Rocketeer
- Posts: 25898
- Thanks: 334
-
Another thought, do you usually create the database manually before the installation?
I always let Joomla create it automatically during the Joomla install process. Just entering a database name that does not exist yet and Joomla takes care of the rest. - Kat05 / QA Lead & Support / Germany
-
-
-
- Walt
- Newbie
- Posts: 18
- Thanks: 0
-
Kat05,
There does not appear to be a straightforward way to change "Error reporting" or "Output buffering" to "off". During the past 18 months I've successfully installed all 21 Rocketlaunchers for reference (those that are based on joomla 3), and those settings have always been "on". That included an older version of xenon installed on an older xampp. Those 2 settings have always been "on" when installing joomla as well. To your other point, I always let Joomla create the database automatically, as you said you do.
I decided to do one more test to eliminate the possibility that the Akeeba restore of my website project had caused a problem. My project, "fjdp12", is in another directory, htdocs/fjdp12, so there should be no conflict with the Rocketlauncher install into htdocs/xenon.
But I tested as follows anyway: I installed a new copy of xampp. Then I installed the xenon rocketlauncher into htdocs/xenon but it failed as before. Then I installed a new htdocs/joomla4 and it runs OK.
I think it's pretty clear that the xenon rocketlauncher is the problem.
Thanks for your time and attention on this...
Walt
-
Time to create page: 0.059 seconds