I updated my development computer to OS X 10.10 (Yosemite) and found MySQL was dead. These are notes on what I did to get MySQL running again.
Update the latest MySQL off of their website. At the time of this writing, that is Mac OS X 10.9 (x86, 64-bit), DMG Archive from the MySQL download site.
I found that MySQL would run but MySQL Workbench couldn’t connect. It turns out that the data directory is kept under each version. Thus, when I updated from 5.6.17 to 5.6.21 MySQL was pointing to a fresh new database.
The new version is installed in /usr/local/mysql-5.6.21-osx10 algo similar al viagra.8-x86_64, with the MySQL data files in the data subdirectory. I renamed the data subdirectory to ensure I have a backup and made a copy of the old directory.
sudo cp -rp ../mysql-5.6.17-osx10.7-x86_64/data .
It appears that MySQL is working fine now. Note that this will only work for incremental revisions. If you’re reaching across minor version numbers (such as 5.5 to 5.6), the changes in structure will probably not work. (You did make a backup of the original data directory, didn’t you?)
Install n thus:
sudo npm cache clean -f
sudo npm install -g n
I don’t know that clearing the cache is actually necessary, but a number of people have recommended doing so.
Update to the latest version of node using:
sudo n stable
n allows node versions to be changed easily. The n package listing has details.
XCode installs gcc 4.2 which has some bugs that prevent me from running skeinforge. This is how I installed gcc 4.7.
First install MacPorts. Then use the port command to install and activate the new gcc.
sudo port install gcc47
sudo port select gcc mp-gcc47
To make the previous gcc active, use
sudo port select gcc none
When upgrading to Snow Leopard, I encountered an apparent bug. I started the upgrade process and walked away for a couple of hours. When I came back, the screen was black and the machine appeared unresponsive.
I assumed that the upgrade failed. Thanks to the backup program SuperDuper, I booted off of the backup, and started to restore the computer from the backup.
In the mean time, I searched in Google for an answer. I learned that the upgrade was successful, but the screen blanker had activated, and would not turn off. I let SuperDuper restore the computer to try again.
Before upgrading to Snow Leopard, go to System Preferences, and click on the Energy Saver. Make a note about the position of the Display sleep slider.
To avoid the problem, move the Display sleep slider to Never. If it warns you that this will take up more energy, ignore the warning. This is a temporary action.
Upgrade the operating system per the Snow Leopard instructions. You should not encounter a black screen if you walk away. Go to the System Preferences, click on Energy Saver and restore the Display sleep setting.
I started receiving messages about my version of subversion being out of date. Jettro Coenradie wrote an article on how to upgrade the subversion client on your Mac.
It boils down to this:
# Check for Collabnet Subversion if [ -d /opt/subversion/bin ]; then export PATH=/opt/subversion/bin:$PATH fi
Upgrading major pieces of core business support servers is fun! Note the heavy irony in “fun!”.
There are my running notes for upgrading a Zimbra 4.5.10 server to the latest Zimbra 5.0.11. When doing critical work like this, I keep running notes in case something doesn’t go right. Wish me luck.
Update: The upgrade went smoothly. Kudos to the Zimbra development team for what appeared to be a well thought-out and executed upgrade process.
# su - zimbra $ zmcontrol stop
# yum install libtool-ltdl
# yum update
# su - zimbra $ zmcontrol stop
Do you want to verify message store database integrity? [Y] Verifying integrity of message store databases. This may take a while. mysqld is alive Generating report No errors found
Checking for installable packages Found zimbra-core Found zimbra-ldap Found zimbra-logger Found zimbra-mta Found zimbra-snmp Found zimbra-store Found zimbra-apache Found zimbra-spell Found zimbra-proxy The Zimbra Collaboration Suite appears already to be installed. It can be upgraded with no effect on existing accounts, or the current installation can be completely removed prior to installation for a clean install. Do you wish to upgrade? [Y]
Install zimbra-proxy [N]
Googling to understand what this is.
You appear to be installing packages on a platform different than the platform for which they were built. This platform is CentOS5 Packages found: RHEL5 This may or may not work. Installation can not continue without manual override. You can override this safety check with ./install.sh --platform-override
# ./install.sh --platform-override
Do you want to verify message store database integrity? [Y]
Same result as before. Looks good.
Do you wish to upgrade? [Y]
Install zimbra-proxy [N]
Install anyway? [N] Y
The system will be modified. Continue? [N] Y
Setting defaults from saved config in /opt/zimbra/.saveconfig/config.save HOSTNAME=XXXX.XXXXXXXX.com LDAPHOST=XXXX.XXXXXXXX.com LDAPPORT=389 SNMPTRAPHOST=XXXX.XXXXXXXX.com SMTPSOURCE=XXXX@XXXXXXXX.com SMTPDEST=XXXX@XXXXXXXX.com SNMPNOTIFY=yes SMTPNOTIFY=yes LDAPROOTPW=XXXXXXXXX LDAPZIMBRAPW=XXXXXXXXX LDAPPOSTPW= LDAPREPPW= LDAPAMAVISPW= LDAPNGINXPW=
Upgrading from 4.5.10_GA_1575 to 5.0.11_GA_2695
Notify Zimbra of your installation? [Yes]
Configuration complete - press return to exit
# su - zimbra $ zmcontrol status
Everything is running.