We recently installed a version of Sun’s CoolStack software bundle on a SunFire T2000 server running Solaris 10 so that we could use its CoolThreads-optimised version of Apache instead of the regular Apache that came pre-installed on the box (highly recommended by Sun).
However, when we ran the new version of Apache against our configuration, we discovered that it does not include a number of key modules that we require (namely Proxy Balancer). Sun does not provide these in binary format so we had to build them by hand. Fortunately, Apache does provide a convenient tool (apxs) for building modules but unfortunately this requires you to install a Sun compiler, Sun Studio (now free though) which added some extra time to the process.
Anyway, I appreciate that this may not be rocket science to many of you but, despite the many articles already published on this topic, there were still some issues that we hit which were not documented. So, here is how we did it.
- Ensure that you have installed the latest version of the CoolStack software (installs to /opt/coolstack)
- Download, unpack and install Sun Studio 11 (installs to /opt/SUNWspro)
- Be patient, very patient … 600MB download, followed by a long unzip to 1.1GB followed by a long install …
- Download, unpack and install the CoolStack Source (installs to /opt/coolstack/src)
- Now, as a root user, follow the commands below
# export PATH=/opt/SUNWspro/bin:$PATH
# cd /opt/coolstack/src/httpd-2.2.3/modules/proxy
# /opt/coolstack/apache2/bin/apxs -i -a -c mod_proxy.c proxy_util.c
This will compile the module, copy it to the appropriate directory and update the Apache configuration file for you.
If you leave out the proxy_util.c you will get "proxy_lb_worker: symbol not found" errors when you start Apache
# /opt/coolstack/apache2/bin/apxs -i -a -c mod_proxy_balancer.c
Once again, this will compile, copy and deploy the module for you
# /opt/coolstack/apache2/bin/apxs -i -a -c mod_proxy_http.c
If you forget to install this module, Apache will start, but the site will be inaccessible (saying you do not have permissions to view this page). You will also see errors like "proxy: No protocol handler was valid for the URL /" in the Apache error log file for your product.
Best of luck!