So you could not resist getting yourself that free upgrade to OS X 10.9 Mavericks and now your local development environment went south? Or you are thinking of upgrading, but first want to know what problems you will have to face? So here is a short list of problems i ran into, what their causes are and how to fix them:
What’s not working (for me)
After upgrading these things were not working anymore:
- no virtual hosts
- no php
- no mysql
- no mcrypt
- Zend generating timeouts in various modules
Detecting the first two was quite obvious, but why Zend framework resulted in timeouts was somewhat of a mystery in the first place. Mysql server worked nicely, as i checked that with Sequel Pro – contecting worked fine, all the data was there. So here are the reasons why stuff did not work on my machine:
Reasons for not working
- no virtual hosts because the upgrade moved my vhost-file to a backup file and did not replicate the already created ones
- no php because similar happened to the httpd.conf file where by default php module is commented out
- no mysql (via php) because the default connection sockets are not set in the php.ini, where the previous version also got backup-ed
- no mcyrpt because it is not completed in the new version coming with OS X 10.9 Mavericks, which is PHP 5.4.17 (at the moment)
- the Zend timeout occurred because of the missing mysql socket of php
How to fix these problems
So, know that we know the reasons for the errors here are the links and ways to get your development mac up and running again:
- Go to /private/etc/apache2/extra and check your httpd-vhosts.conf file or another where you have stored your virtual hosts. Usually it simply requires copying the old version indicated by ~orig at the end and renaming it the desired .conf file.
- Check your httpd.conf (/private/etc/apache2) and enable php5 by uncommenting the line starting with LoadModule php5_module.
- Reenabling Mysql: there are various websites on the net explaining how to enable mysql on php5 on a mac – so follow that or simply compare your /private/etc/php.ini.default (currently used) with your original from before the upgrade (/private/etc/php.ini-5.2-previous~orig, or similar). Especially watch out for instructions like „mysqli.default_socket = “ where the new version is empty.
- Ok, installing mcrypt is a longer process. I followed the instructions from Neil Gee and it just worked – many thanks!
- After your mysql socket is working properly Zend should also be humming again…
Hope this helps everybody who is keen to do the step to Mavericks – it really paid of for me. Just one simple fact to undermine my excitement: 10 GB extra space on my hard drive!!
Leave a Reply