First, make a manifest change to put Apache2.2 in debug mode.
# svccfg -s apache22 setprop 'httpd/startup_options=("-e" "Debug")'
# svccfg refresh apache22
That should hopefully get you some additional logging, but I suspect there are
a few error conditions during startup that Apache doesn't properly report.
I've been running Apache 2.2 on b134 for a few months now, and I've noticed
startup failures every time I upgraded.
One trick is to make sure that if you build a custom configuration that might
need to write to a directory (like a pidfile dir or a logdir), and if you
change the apache server to run under a different userid, avoid using any of
the paths that come included with the Apache2.2 package, otherwise their
ownership and permissions will be updated during the next package upgrade.
I think I also had to disable the proxy module once, but I forgot the reasoning
behind it.
--
This message posted from opensolaris.org
_______________________________________________
opensolaris-help mailing list
opensolaris-help@opensolaris.org
