Folks,
I just upgraded from v1.11.1 to v1.11.3 (via make upgrade), but it hasn’t worked out very well. The problem appears to be with Apache 2, not Bricolage, but I’m not certain of that. The upgrade itself went just fine, concluding with "Bricolage Upgrade Complete,” no errors or anything. (At least not once I was done hacking my way around the mod_apreq2 problem...) But when firing up Bricolage, it goes a little like this:
----cut----
# /usr/local/bricolage/bin/bric_apachectl start
bric_apachectl start: starting httpd
bric_apachectl start: httpd could not be started
----cut----
Given the lack of verbosity, I figured I’d cut Bricolage out of the loop and fire up Apache using the httpd.conf within Bricolage.
----cut----
# /usr/sbin/httpd -f /usr/local/bricolage/conf/httpd.conf -e debug
[Tue Feb 02 11:48:10 2010] [debug] mod_so.c(246): loaded module perl_module
[Tue Feb 02 11:48:10 2010] [debug] mod_so.c(246): loaded module expires_module
[Tue Feb 02 11:48:10 2010] [debug] mod_so.c(246): loaded module apreq_module
[Tue Feb 02 11:48:10 2010] [debug] mod_so.c(246): loaded module log_config_module
[Tue Feb 02 11:48:10 2010] [debug] mod_so.c(246): loaded module mime_module
[Tue Feb 02 11:48:10 2010] [debug] mod_so.c(246): loaded module alias_module
[Tue Feb 02 11:48:10 2010] [debug] mod_so.c(246): loaded module ssl_module
----cut----
No errors, but Apache still doesn’t fire up. I tried shutting down the main site—leaving no instances of httpd running—and then starting only the Bricolage instance of Apache, but the result was the same. As I was with v1.11.1, I’m using this same Apache 2 binary to run the live (non-Bricolage) site on this same box, and nothing has changed on that front this morning.
Any ideas?
Best,
Waldo
---
Virginia Quarterly Review
One West Range, Box 400223
University of Virginia
Charlottesville, VA 22904-4223
434-243-4995
I just upgraded from v1.11.1 to v1.11.3 (via make upgrade), but it hasn’t worked out very well. The problem appears to be with Apache 2, not Bricolage, but I’m not certain of that. The upgrade itself went just fine, concluding with "Bricolage Upgrade Complete,” no errors or anything. (At least not once I was done hacking my way around the mod_apreq2 problem...) But when firing up Bricolage, it goes a little like this:
----cut----
# /usr/local/bricolage/bin/bric_apachectl start
bric_apachectl start: starting httpd
bric_apachectl start: httpd could not be started
----cut----
Given the lack of verbosity, I figured I’d cut Bricolage out of the loop and fire up Apache using the httpd.conf within Bricolage.
----cut----
# /usr/sbin/httpd -f /usr/local/bricolage/conf/httpd.conf -e debug
[Tue Feb 02 11:48:10 2010] [debug] mod_so.c(246): loaded module perl_module
[Tue Feb 02 11:48:10 2010] [debug] mod_so.c(246): loaded module expires_module
[Tue Feb 02 11:48:10 2010] [debug] mod_so.c(246): loaded module apreq_module
[Tue Feb 02 11:48:10 2010] [debug] mod_so.c(246): loaded module log_config_module
[Tue Feb 02 11:48:10 2010] [debug] mod_so.c(246): loaded module mime_module
[Tue Feb 02 11:48:10 2010] [debug] mod_so.c(246): loaded module alias_module
[Tue Feb 02 11:48:10 2010] [debug] mod_so.c(246): loaded module ssl_module
----cut----
No errors, but Apache still doesn’t fire up. I tried shutting down the main site—leaving no instances of httpd running—and then starting only the Bricolage instance of Apache, but the result was the same. As I was with v1.11.1, I’m using this same Apache 2 binary to run the live (non-Bricolage) site on this same box, and nothing has changed on that front this morning.
Any ideas?
Best,
Waldo
---
Virginia Quarterly Review
One West Range, Box 400223
University of Virginia
Charlottesville, VA 22904-4223
434-243-4995