I used yesterday to recompile Postfix, Courier-Auth, Apache and PHP with the 5.0.24a MySQL libraries. I just used my own instructions to compile everything.
I first did Postfix and Courier-auth as they would cause the least problems when it would go wrong. My backup mailserver would still receuve all mail and forward it to me when the mailserver is back online. It all went without a hitch, just did a restart of the programs and all was running as expected.
Apache posed an issue, how to compile and install, followed by compiling PHP without disturbing all the people looking at my sites. In the end it was simple. Compile and install Apache2, don’t restart Apache so the old version keeps running but the new software is available on disk. Then compile and install PHP using the new Apache installation files and when that is done restart Apache and all would be fine. Well that’s what I thought…
There was a small error in the modules that I included in the httpd.conf. Some of them, all concerning authentication, where rewritten and given different names. I was still trying to load the old ones as I didn’t update my httpd.conf to reflect these changes. So Apache2 wouldn’t start. I just commented out the old modules and added the new ones in my httpd.conf and presto, Apache 2.2.3 and PHP 5.1.6 are now running on my server, together with Postfix 2.2.3.
They’ve been running for almost a day now and I haven’t gotten any complaints yet.
If you are still running “ISP in a box” version 1 and want to upgrade but are still a bit afraid on how to do this let me know and I’ll help out.
Update:
Just found out there was an error, got a call on the phone from some of my friends that they couldn’t email anymore. When checking the logfiles I foud out I forgot a step after compiling and installing Courier auth:
sudo chmod o+x /usr/local/var/spool/authdaemon
In the logfile there was the error:
SASL authentication failure: cannot connect to Courier
authdaemond: Permission denied
Which means I didn’t follow my own instructions !
- No related posts
January 12th, 2007 at 8:31 pm
Hi,
I’m having a bit of a problem here man, I’ve noticed that you said you have Apache 2.2.3 running successfully on your server now. Well see the problem I’m having is updating from Apache 2.0.52 which I initially installed from server logistics to Apache 2.2.3 which I’ve taken advise from your post. The problem is I’m not able to start my server due to the following error…
API module structure `access_module’ in file /Library/Apache2/modules/mod_access.so is garbled – perhaps this is not an Apache module DSO?
If I comment out that module in my httpd.conf file then it just throws me another error on the next module…
Any suggestions please???
oh btw Im running Mac OS X 10.4.8
thanks
Sal
January 13th, 2007 at 11:01 am
To solve your problem take the following steps:
- put your httpd.conf in a safe place for later reference
- delete the entire /Library/Apache2 directory, but if you need to keep apache running whilst upgrading, just delete the conf, lib and modules dir.
- perform the “sudo make install” again, or start from the beginning.
- update the new httpd.conf with your settings (except the modules) from the original!
Hope this helps
February 4th, 2007 at 10:15 pm
I just compiled and installed PHP 5 (upgraded from the previous server logistics version) and Apache 2.2.4 and I seem to have lost Unicode support; no Japanese fonts are displaying properly on my site.
Also, in the wordpress admin panel I get the following error at the top of the page:
Warning: fopen(/Library/Apache2/htdocs/snozle_wp/wp-content/cache/wp_cache_mutex.lock) [function.fopen]: failed to open stream: Permission denied in /Library/Apache2/htdocs/snozle_wp/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 96
February 4th, 2007 at 10:19 pm
ah, had to change the priviledges to 777 on the wp_content directory and it’s enclosed items, fixed both of the problems