It crashes every time shortly after I click on the "install" button. Does it in both IE7, FF3, and Google Chrome.
This is all I get in the Apache error log each time:
[Wed Jan 14 21:03:56 2009] [notice] Server built: Jun 14 2008 19:02:12
[Wed Jan 14 21:03:56 2009] [notice] Parent: Created child process 2800
[Wed Jan 14 21:03:57 2009] [notice] Child 2800: Child process is running
[Wed Jan 14 21:03:57 2009] [notice] Child 2800: Acquired the start mutex.
[Wed Jan 14 21:03:57 2009] [notice] Child 2800: Starting 250 worker threads.
[Wed Jan 14 21:03:57 2009] [notice] Child 2800: Starting thread to listen on port 443.
[Wed Jan 14 21:03:57 2009] [notice] Child 2800: Starting thread to listen on port 80.
[Wed Jan 14 21:04:06 2009] [notice] Parent: child process exited with status 255 -- Restarting.
[Wed Jan 14 21:04:07 2009] [notice] Apache/2.2.9 (Win32) DAV/2 mod_ssl/2.2.9 OpenSSL/0.9.8i mod_autoindex_color PHP/5.2.6 configured -- resuming normal operations
The MODx error log shows this error over and over -- many times per second:
[2009-01-14 21:09:19] (ERROR @ /addons/manager/index.php) Error 42S22 executing statement:
Array
(
[0] => 42S22
[1] => 1054
[2] => Unknown column 'description' in 'field list'
)
-
MODX Staff
- 10,725 Posts
I had this for a second before I ran an upgrade with a fresh transport package. Did you rebuild the core package?
Quote from: OpenGeek at Jan 14, 2009, 10:12 PM
I had this for a second before I ran an upgrade with a fresh transport package. Did you rebuild the core package?
Yes, but it took an unusually long time. ( > 400 sec.).
I’m probably on a slower machine. The builds normally take about 120-180 seconds for me, but I’m doing them from inside my editor which launches its own php engine and debugger. Still, from the error logs, it looks like there may be an infinite loop in the install under some circumstances.
