The apache team have released an update to the popular webserver. This updates concerns several security fixes and I would advise you to upgrade your server accordingly. I’ve tested and updated all my server without any problem. Read all about the changes and bugs fixed in the 2.2.15 changelog.
If you’ve forgotten how to upgrade your Apache installation in the least painfull way with a possibility to go back if something goes wrong: Upgrading Apache
Here is a quick update on getting Apache, PHP and MySQL installations working again after the Snow Leopard upgrade.
For Apache I did a recompile and install because the config was completely lost (and I had no backup!) and this was the quickest way for me. The normal 64 bit Leopard instructions did the job for now, will look later at possible enhancements.
MySQL I could just startup with the System Preferences MySQL panel. Will do a recompile later today and will update this post with the findings. This as MySQL is updated to 5.1.38
PHP gave the most issues, but a comment from Nico helped out. This problem is valid for 5.2.9 and 5.3.0 but it should be solved in 5.3.1 as the bug was listed as solved in 5.3.1.dev
To solve the problem, follow the normal instructions on this site but after the configure statement you need to edit the Makefile which is created by ./configure
You need to add ‘-lresolv‘ at the end of the line which starts with ‘EXTRA_LIBS‘ like:
As noted earlier, I will keep updating this blogpost till most issues are resolved or properly documented elsewhere on the site.
Update 1: MySQL compiled without a problem using the 64 bits Leopard instructions.
Update 2: Finished some of the PHP documentation on Snow Leopard:
Update 3: Added Apache install instructions:
Update 4: Made a new page with all related Snow Leopard instructions. MAMP stack documented, mailserver will follow!
Last update: Mailserver instructions.
It’s looking mighty fine from a user perspective, even more now as I use my MBP for work in a Microsoft environment. The Exchange integration with Addressbook and iCal is very welcome. I will find out more next week when I get back in the office.
But as I also use my MBP as the 64 bit test server. I was very dissapointed to find out that a lot was gone aftet the upgrade. All launchdaemon plist files where gone so nothing was started. Postfix binary had been replaced (was to be expected). All the configuration for Apache was gone, Postfix config replaced (but old ones renamed). Still assessing most of the damage at the moment.
But first success was that the Apache installation for Leopard also works for Snow Leopard. Don’t forget to install the XCode package from the Snow Leopard install DVD.
By the way I had to buy a copy today (which was hard because it was sold out at many places) because the family pack was not yet available.
I will post of my findings tomorrow.
Update: If you follow me on Twitter I will give you earlier smaller notifications on my discoveries! Twitter.com/diymacserver
Recently I got some remarks from a user who asked why he was not able to compile 64 bits on the PowerPC platform. My notes and instructions did not mention this and I must confess that I had forgotten this as I could not see a PowerMac or iMac G5 as your basic mailserver.
But I’m wrong, as my basic goal was to provide you with a complete mailserver solution, I have to acknowledge that the most polular pages are on installing Apache, PHP and third MySQL. The popularity of the mailserver instructions comes way lower then these three subjects.
So therefore I’ve updated all the 64 bit instructions with how to compile on a 64 bit PowerPC platform. You have to forgive me for not being able to test this (no G5 at my place!) I’m using the input of someone else who told me this. It was a very simple change as you only need to change the ‘x86_64‘ bit into ‘ppc64‘ and that’s it.
If someone else could verify that this works it would be grand!
I got an email today from the unreliable Apache announcement mailing list (somehow all releases are not emailed out) that a new version was released yesterday. I’ve downloaded this version 2.2.13 and compiled it right away on my test machine as a user had indicated a problem with 2.2.12 earlier last week.
It looks like the option “-enable-layout” does not work as we once expected. There are now 3 different config.layout files which we need to edit to use our own layout:
Each will have the same content. I can’t find out why this change has been made and why we need to do this. I hope someone can explain this to me and how to resolve this.
Beyond this issue I could not find a problem with this new version on my test servers. therefore I even tried it on my production server to see if that would work properly and it did.
This version is a release with a small security problem so please upgrade if you want to. Read all about the changes in the 2.2.13 changelog.
If you’ve forgotten how to upgrade your Apache installation in the least painfull way with a possibility to go back if something goes wrong: Upgrading Apache
I got an email today from the reliable Apache announcement mailing list that a new version was released today. I’ve downloaded version 2.2.11 and compiled it right away on my test machine. I could not find a problem with this new version on my test mini. therefore I even tried it on my production server to see if that would work properly and it did.
This version is a bugfix release and not a security problem in sight so only upgrade if you want to. Read all about the changes in the 2.2.11 changelog.
If you’ve forgotten how to upgrade your Apache installation in the least painfull way with a possibility to go back if something goes wrong: Upgrading Apache
I got an email today from the reliable Apache announcement mailing list that a new version was released today. I’ve downloaded version 2.2.10 and compiled it right away on my test machine. I could not find a problem with this new version on my test mini. therefore I even tried it on my production server to see if that would work properly and it did.
This version has besides several bugfixes one security fix so please upgrade to this version whenever possible. Read all about the changes in the 2.2.10 changelog.
If you’ve forgotten how to upgrade your Apache installation in the least painfull way with a possibility to go back if something goes wrong: Upgrading Apache
It looks my earlier findings were a bit premature. I’ve been given access to a Core2Duo Mac mini by Ceriel of Vakantieland.nl and Crashplan.nl to test the findings I had when compiling the MAMP stack in 64 bits. There are some minor differences in compiling MySQL and PHP as the earlier solution does not work for them.
Apache:
./configure --enable-layout=DIYMacServer \
--enable-mods-shared=all \
--with-ssl=/usr \
--with-mpm=prefork \
--disable-unique-id \
--enable-ssl \
--enable-dav \
--enable-cache \
--enable-proxy \
--enable-logio \
--enable-deflate \
--with-included-apr \
--enable-cgi \
--enable-cgid \
--enable-suexec
MySQL:
CXXFLAGS="-arch x86_64" \
./configure --prefix=/usr/local/mysql \
--localstatedir=/usr/local/mysql/data \
--libexecdir=/usr/local/mysql/bin \
--libdir=/usr/local/mysql/lib \
--with-server-suffix=-standard \
--enable-thread-safe-client \
--enable-local-infile \
--enable-shared \
--with-zlib-dir=bundled \
--with-big-tables \
--with-readline \
--with-archive-storage-engine \
--with-innodb \
--without-docs \
--without-bench
PHP:
CXXFLAGS="-arch x86_64" \
./configure --prefix=/usr/local/php5 \
--mandir=/usr/share/man \
--infodir=/usr/share/info \
--sysconfdir=/etc \
--with-zlib \
--with-zlib-dir=/usr \
--with-openssl \
--without-iconv \
--enable-exif \
--enable-ftp \
--enable-mbstring \
--enable-mbregex \
--enable-sockets \
--with-mysql=/usr/local/mysql \
--with-mysqli=/usr/local/mysql/bin/mysql_config \
--with-apxs2=/usr/local/apache2/bin/apxs
In Leopard there is a problem with the iconv library, somehow that is not 64 bits or something like that. When compiling 32 bits it works. I guess if you really want iconv you will have to recompile the inconv library to get that one working. Currently I’m working to get IMAP working for postfixadmin.
Some of you have the “luxury” of having Macs with Core 2 Duo processors. I’m still working on my Core Duo Mac mini so this post isn’t really for me. But if you have one of those Macs who are capable of running 64 bit software than this post is for you.
To compile MySQL, Apache or PHP you need to add a compiler flag to the ./configure statement and that is it.
./configure etc…
(Note: this is only valid for Intel CPU’s, in case of a PowerPc use ppc_64)
I do not know how this would influence performance as I can’t run 64 bit apps. If someone would test the difference and comment their findings here that would be great.
To find out if you’ve got the capability of running 64 bit applications I found this simple test. Open a Terminal session and execute the following command:
In the output you should find a line with:
if you have got a 64 bit version or
if you have a 32 bits system just like me.
By the way I’m planning for a new Mac before the end of the year. Still need to decide what model but I’ve started saving up for it, care to help ?
I found out that while I was installing the new Apache version that some of the documentation was still outdated or did not properly reflect the state of things on Leopard. For instance, I still referred to a blog post instead of a proper documentation page for compiling Apache on Leopard. The startup script still was done in the old fashioned way instead of using the new launchd daemon.
So I did a small overhaul of the Apache documentation and separated the Tiger and Leopard instructions as I’ve done with all the other stuff. I hope this makes it all a bit clearer.
Leopard:
Tiger:
For both:
Leopard:
Tiger:
RSS feed