Installation SummaryBut no errors/results are actually listed below? Nothing is output to /core/cache/logs/ either, so I’m at a loss. Any ideas or suggestions? (Same issue on alpha 6 standard, advanced, and SVN builds).
Errors were encountered during core installation. Please review the installation results below, correct the problems and proceed as directed.
I’ve just enabled XCache and have yet to get a seg fault (sure does decrease the cached processing times nicely though, trimming it to a third of the normal response times on my MAMP installation). Can you provide any additional details on configurations and/or actions that cause this to occur for you? Also environment details would help immensely in your case.
In case anybody else runs into this: XCache will give a segmentation fault as well (at least in my testing).
Disabling XCache corrects the problem.
Again, I think we need more information on the versions and configurations in your environment.
Also, while I’m talking, is anybody else having an issue where it’s reporting back:
Installation SummaryBut no errors/results are actually listed below? Nothing is output to /core/cache/logs/ either, so I’m at a loss. Any ideas or suggestions? (Same issue on alpha 6 standard, advanced, and SVN builds).
Errors were encountered during core installation. Please review the installation results below, correct the problems and proceed as directed.
Why such ancient MySQL with cutting edge PHP (< 30 days old)? That is likely the problem, depending on the mysql client API libraries it was compiled with.
Sorry, should have included that before. Relatively standard LAMP box (LiquidWeb VPS):
CentOS 4.7
Apache/2.0.63
PHP/5.2.8
MySQL 4.1.22
(details a la phpinfo())
I’m getting the same issues using both the latest from the SVN and alpha 6.
Yeah, I took a closer look at the phpinfo and everything seemed kosher. I also searched for any version specific bug reports, and couldn’t really find any, but I am noticing a few segfaults after running XCache on my config for a while (PHP 5.2.5/Apache 2.0.59/MySQL 5.0.41); however, I can’t seem to identify a request that is causing it specifically.
Will be upgrading tonight. I’ll report back with updates. It should still be reporting some sort of error back though, I’d imagine, no?