Start mysql as a daemon on OS X Mavericks on boot

I’ve been doing some work with WordPress and Joomla recently, which led to the need to have mysql up and running on my dev server; it’s a mac mini running OS X Mavericks Server.

I’d like the mysqld process to run as a daemon in the background after the server boots; that way I don’t have to log in and start the process after each server reboot.  I couldn’t find a recent, up-to-date faq for doing this, so I thought I would write what I did.

I’m a big fan of homebrew, so I used it to install mysql.

homebrew is a unix-style package manager for OS X; it’s awesome!

If you don’t have homebrew installed on your mac, you can get it by opening the terminal app and using this command:

ruby -e "$(curl -fsSL https://raw.github.com/Homebrew/homebrew/go/install)"

Then to install mysql…

brew install mysql

Read the output of the above command carefully, as there are a few more steps that won’t be covered here today that are required to initialize and setup your new mysql database.

The homebrew mysql package comes with some info for automatically launching mysql on login. You can access the info with the following command:

brew info mysql

This is the last part of the output of the above command:

...
To have launchd start mysql at login:
ln -sfv /usr/local/opt/mysql/*.plist ~/Library/LaunchAgents
Then to load mysql now:
launchctl load ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist
Or, if you don't want/need launchctl, you can just run:
mysql.server start

Remember, I want to have mysql run as a daemon even when there is no user actively logged into the dev server…

This can easily be accomplished by copying the homebrew.mxcl.mysql.plist file that is provided with the homebrew mysql package to the /Library/LaunchDaemons/ folder and then making some edits to the file in it’s new location.

Here is the contents of the included plist file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>KeepAlive</key>
<true/>
<key>Label</key>
<string>homebrew.mxcl.mysql</string>
<key>ProgramArguments</key>
<array>
<string>/usr/local/opt/mysql/bin/mysqld_safe</string>
<string>--bind-address=127.0.0.1</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>WorkingDirectory</key>
<string>/usr/local/var</string>
</dict>
</plist>

There are a couple of issues that need to be addressed with the default plist file if you want to run mysql as a daemon.

  1. You’ll want to call the mysqld executable directly instead of invoking the mysqld_safe script.
  2. You need to provide the user account that you would like to have run the mysqld process.
  3. You need to provide the complete path to the WorkingDirectory; which on my system is /usr/local/var/mysql

Before getting started with any changes to the included plist file, make a copy in the /Library/LaunchDaemons/ folder:

sudo cp /usr/local/opt/mysql/homebrew.mxcl.mysql.plist /Library/LaunchDaemons/homebrew.mxcl.mysql.plist

Then open your favorite unix text editor (vim in my case):

sudo vim /Library/LaunchDaemons/homebrew.mxcl.mysql.plist

Then make the following edits…

To call mysqld directly edit the line:

<string>/usr/local/opt/mysql/bin/mysqld_safe</string>

and change it to:

<string>/usr/local/opt/mysql/bin/mysqld</string>

To add the user account that you would like to have run the mysqld process, add the following line under the <key>ProgramArguments</key> line:

<string>--user=mysqlusergoeshere</string>

where mysqlusergoeshere is the unix name of the account you want to run the mysql process.

After

<key>RunAtLoad</key>
<true/>

Add the following two lines:

<key>UserName</key>
<string>mysqlusergoeshere</string>

Make sure the path for your WorkingDirectory leads to folder where your mysql data is located; in my case this was /usr/local/var/mysql :

<key>WorkingDirectory</key>
<string>/usr/local/var/mysql</string>

Here is the contents of the complete plist file with all the necessary modifications:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>KeepAlive</key>
<true/>
<key>Label</key>
<string>homebrew.mxcl.mysql</string>
<key>ProgramArguments</key>
<array>
<string>/usr/local/opt/mysql/bin/mysqld</string>
<string>--bind-address=127.0.0.1</string>
<string>--user=mysqlusergoeshere</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>UserName</key>
<string>mysqlusergoeshere</string>
<key>WorkingDirectory</key>
<string>/usr/local/var/mysql</string>
</dict>
</plist>

Once you have all the changes made to the plist file, you’ll want to change ownership and permissions of the file so that it will work with the launchctl process.

If it isn’t already, change the owner to root and the group to wheel.

sudo chown root:wheel /Library/LaunchDaemons/homebrew.mxcl.mysql.plist

Set the appropriate permission by changing the file mode to 644:

sudo chmod 644 /Library/LaunchDaemons/homebrew.mxcl.mysql.plist

The last step is to load the plist with launchctl:

sudo launchctl load -w /Library/LaunchDaemons/homebrew.mxcl.mysql.plist

mysqld should load immediately after this last command is run. It should also now load each time the system boots.

If you make changes to the plist file and need to reload it with launchctl, make sure you first unload the file:

sudo launchctl unload -w /Library/LaunchDaemons/homebrew.mxcl.mysql.plist

I hope this guide helps anyone out who would like to have their homebrew mysql run as a daemon on OS X Mavericks.

Apple Training Site Still Down

Update (8/8/2011): The Apple Training site has been back up for a couple of days. They are now offering the following certifications:

  • Apple Certified Associate: Mac Integration 10.7
  • Apple Certified Support Professional 10.7
  • Apple Certified Technical Coordinator 10.7

It appears that they have either discontinued or have not yet updated the Apple Certified System Administrator (ACSA) certification.

Training, course books, and certification for OS X Lion will be available later this fall.

–original post–

I’ve read that there are some pretty big changes in the works for Apple’s certification exams and training. I’m planning on taking some of the certifications, and have been checking training.apple.com every couple of days since OS X Lion was released.

Screen shot 2011-08-01 at 3.53.47 PM

It has surprised me that the site is still down!

Seems like a pretty big oversight to not have your training program ready to go with the launch of your new OS. Makes me wonder what Apple has in store for us?

OS X Lion Drops Rosetta and PowerPC Architecture Support For Intel Macs

Anyone who still uses any applications that were written for the PowerPC architecture should know that with the release of OS X v10.7 Lion, Apple has officially dropped Rosetta and support for older apps written for PowerPC.

What does this mean?

Your old PowerPC apps will not run on OS X Lion.

Is there a way to add Rosetta to OS X Lion?

No.

What can you do?

Helpful hint! Before upgrading, use the Finder’s Get Info feature to find out if any of your apps require Rosetta.

Apps that are written for the PowerPC architecture and require Rosetta to run on an Intel Mac will say:

Kind: Application(PowerPC)

PowerPC App

Apps that don’t require Rosetta will either say:

Kind: Application (Intel)
Kind: Application (Universal)

If you have PowerPC architecture apps, check to see if new, updated, Intel or Universal versions of your apps are available from the software developer.

If not, see if there is an alternative app that will substitute for your outdated PowerPC app.

Alternatively, if your app is mission critical and/or you have an extra Mac laying around, you can choose to keep OS X Leopard (v10.5) or Snow Leopard (v10.6) running on at least one Mac.

Then…

If you’re really itching to try OS X Lion, purchase one of the fantastic new MacBook Airs!

Mac OS X v10.7 Lion and Lion Server Review

There is an excellent review of Apple’s latest OS offerings, OS X Lion and OS X Lion Server on www.thetechscoop.net. The review is fairly comprehensive, hits most of the new features, and is relatively unbiased.

You can read the review here: http://www.thetechscoop.net/2011/07/20/mac-osx-10-lion-complete-review/

Although I have not downloaded and installed OS X Lion or Lion Server, from what I have read, it appears that the Server version is improved in some areas. However, the interface is significantly dumbed down and stripped down to make server administration easier for non-admins.

I mentioned in an earlier post that several key components have been removed, such as, MySQL and Tomcat. It also appears that many of the advanced server controls have either been eliminated from the GUI, or completely eliminated altogether.

These changes are great for server novices who want to try their hat at server admin.

However, I don’t think that this will bode well with many server admins in enterprise and research environments with complicated OS X Server deployments. I think many will choose not to upgrade.

I understand that Apple is going after with masses to capitalize on the overwhelming popularity of iOS. They are building iOS features into the core OS and are bringing server administration within the reaches of the common user.

I just don’t understand why they would choose to eliminate or severely hamstring many of the advanced server controls for more experienced admins. There is no reason that you can’t have both interfaces; Server made easy and Server on steroids. It seems that now we’ll have to hack at the command line more often to maintain the more advanced functionality of OS X Server.

This move along with the recent overhaul of Final Cut Pro X, seems to suggest that Apple has lost touch with it’s core devoted user base, that has historically helped sustain their market share in key markets (creative pros, science, academics) for so many years.

It appears that the mass-consumer market is now driving OS feature development. I can understand that for the core OS, but why for the Server version and Pro Apps?

Apple, please don’t try to turn my Mac into an iPhone, I already have one of those…

Some Significant changes under the hood in OS X v10.7 Lion Server

For anyone considering upgrading to Lion Server, check out this pdf from Apple titled, “Lion Server Upgrading and Migrating.” There are some significant changes under the hood to some of the core features included in Snow Leopard Server.

http://images.apple.com/macosx/server/docs/Upgrading_and_Migrating_v10.7.pdf

Check out page 5, “What’s new in Lion Server.”

Lion Server has major changes in several key areas:

  • Lateral Migrations: The migration of Lion Server to Lion Server is supported.
  • Server app Services are administrated by the new Server app.
  • PostgreSQL: MySQL is replaced with PostgreSQL.
  • Tomcat: Support for Tomcat is removed from Lion Server.
  • Axis: Support for Axis is removed from Lion Server.
  • Mobile Access: Support for Mobile Access is removed from Lion Server.
  • Print service: Print service is replaced with CUPS.
  • QuickTime Streaming Server (QTSS): Support for QTSS is removed from Lion Server.

As with any server upgrade or migration, make sure there isn’t any mission critical service(s) that will be broken or missing by migrating to Lion Server.

The replacement of MySQL with PostgreSQL and the removal of Tomcat will probably affect a lot of folks.

Text Your Lost Phone

I recently wrote a post about using the Find My iPhone app to locate and recover my wife’s missing iPhone.

The experience got me thinking…

What can you do if you don’t have an iPhone or other smartphone with location based tracking (GPS, Wifi)?

Well, if your phone supports text messaging, you can simply send your phone a text message with a note to whoever finds it. Give them a phone number you can be reached at and you may be pleasantly surprised with a returned call!

Don’t forget that you can also try the time honored approach of calling your lost phone from another phone. Someone might actually pick up on the other end!

Find My iPhone

find-my-iphone

Anyone who owns an Apple iPhone needs to install and configure this app!

When I first configured the Find My iPhone app, my initial thoughts were…this is sort of neat, but mostly a gimmick.

Ok, so it lets me see the current location of my iDevices (iPhones, iPads, etc…). Is it really going to help me locate a lost or stolen iPhone?

Well, the short answer is: YES!

Over the past several months I’ve used this app to successfully locate several misplaced iPhones.

A few weeks ago my wife couldn’t find her iPhone. We tried calling it, hoping to hear it ring, but after several tries…nothing. So I opened the find my iPhone app on my iPhone and voila, in about 15 seconds it told me that the phone was located in our driveway approximately where our minivan was sitting. The initial response was, “I’ve already looked in the minivan.” However, upon closer inspection, the missing iPhone was found under the center console.

The real test came this last week, as we flew home from a short family vacation in Missouri. Our flight had a connection through Newark, NJ, and just before landing at our final destination in Boston, my wife realized she did not have her iPhone. Unknowingly to us, it had fallen out of her purse on the first flight. To complicate matters it was on airplane mode, so the cell phone radio was off.

The first thing I did was open the Find My iPhone app on my iPhone and set the alert for her phone. I told the app to have her phone display a message as soon as it was found saying that it was lost and to call my iPhone’s number. I also told it to notify me via email as soon as her phone was located.

We reported the phone lost with the airline and went home. I checked the app a few times that evening and the phone could not be located.

Then at 11 PM that night, I received an email while sitting at my computer that said that her iPhone had been located. Before I could even launch the find my iPhone webpage, my phone rang. It was a cleaning lady on the plane in Indianapolis who had found the phone. She said as soon as she turned it on, it started making all sorts of noise and displaying the message that she needed to call me. She keep me on the phone as she walked to the Continental office to turn the phone in. While talking to her, I loaded the Find My iPhone webpage on my computer and watch as the phones location was updated every 30 secs or so.

Continental made arrangements to have the phone on a flight to Boston the next day, where I picked it up at the airport. Overall a resounding success for the Find My iPhone app!

To get the Find My iPhone app installed and working on your iPhone, iPad, or 4th gen iPod Touch there are a few things you need to do:

  1. Visit the App Store on your iPhone, iPad, or iPod Touch and download the Find My iPhone app.
  2. Use your Apple ID to sign in and register your device with the service.
  3. Use the same Apple ID to turn on the app on your other iDevices.

Now if one of your devices goes missing, you can use the app to attempt to locate it. For the location services to work, the device has to be turned on and connected to the internet either via Wifi or the cellular network. If it cannot be located, you can have it send you an email the next time it connects to the internet.

There are also options to lock the device or to remotely wipe the device. These options may be handy if you are having trouble recovering a lost or stolen device from it’s new owner.

Overall, I highly recommend this app based on personal experience. Download and configure it today!

Mac mini with Snow Leopard Server–Setup Tips

Macminisnowleopardserver

I recently decided to purchase an Apple Mac mini with Snow Leopard Server so that I could have a fully featured server providing services for my home network and some business interests.

The primary goals being:

  1. To eventually reduce the cost of maintaining calendar, email, and contact management services that push info to our mobile devices (iPhones, iPad, etc…). My goal here is to ditch mobile me.
  2. Establish a central file server to manage our growing collection of digital assets (photos, music, movies, documents, etc.).
  3. Facilitate server based Time Machine backups of all local mac computers on our home network.
  4. Manage user and computer accounts to control the level of service provided to the various household users.
  5. Establish a VPN to remotely access files and services on the home network.

A secondary goal being an overall refresh and improvement of my server management skills.

The features that attracted me to the Mac mini server were:

  • It’s small footprint
  • Extremely energy efficient design
  • Unlimited client license
  • Low cost
  • Ability to support and manage Mac, Windows, and linux clients.

The marketing info from Apple is very suggestive that a non IT person can easily setup and manage a Mac mini server. By using their included setup assistant, anyone familiar with Mac OS X is supposed to be able to quickly and easily have a fully functioning email, file, and directory server. I can confidently say that this is not the case. I have a substantial amount of experience with OS X, some OS X Server experience, and some linux admin experience. I thought I would give the setup assistant a try and see how easy it really can be to setup a Snow Leopard Server. Here is a brief summary of my results:

First try (setup assistant) = EPIC FAIL

Second try  (manual configuration) = SUCCESS

After reading a substantial amount of the server admin guides from Apple, and researching much info on the web, I now have a properly functioning Snow Leopard Server with the following services enabled:

  • DNS (Domain Name Server)
  • Open Directory
  • AFP (Apple Filing Protocol)
  • SMB (Windows file sharing)
  • NFS (Unix file sharing)

 I have migrated my user account from local accounts on the various macs, to a network account on the server. This was a challenging task to do correctly and there is virtually no documentation from Apple which provides an approach or framework to migrate local accounts to server accounts. A full write-up will be forthcoming…but in the mean time, a few things to consider:

  • Have a full admin account on your server that does not have the same long or short name as the account you plan on using as your everyday network account.
  •  Network accounts should have different long/short names than the local accounts on your Macs.
  • It is helpful to have a local admin account (backdoor account) for each mac in your network.
  • Back up all of your files on your local machines before you begin messing with the accounts!

 In the future, I plan on incrementally adding the following services to my server:

  • iCal Server
  • Address Book Server
  • VPN
  • Mail

The key to success was not allowing the setup assistant to configure any services. Just start with a minimal server install and configuration. Then, starting with the DNS service, incrementally added services by configuring them manually with the Server Admin application.

Setting up your DNS service is the most important step and requires forethought and planning to avoid having to reconfigure your server in the future; this is where I screwed up the first time (DNS config), and then the server assistant took it from there and hosed the rest of the services. I tried to repair manually using Server Admin and at the command line, but in the end, it was just easier to start over.

I think if I had a more complete understanding of DNS during the first attempt with the setup assistant, it is very likely that I would have been successful configuring my server. So I don’t think that there is any problem with Apple’s setup assistant per se, it’s just that the setup assistant assumes that you have at least a baseline knowledge of DNS service settings. It is very easy to quickly get of course with the setup assistant despite the fact that it was designed to make server setup a breeze.

When setting up DNS service on your server, keep these things in mind:

  • Make sure you understand what constitutes a fully qualified domain name (FQDN).
  • Example: myserver.mydomain.com
  • Do not use .local or .private in your FQDN.
  • Register a unique domain name for your server, even if you intend on having a private network behind a firewall.
  • Use Google’s DNS servers, 8.8.8.8 and 8.8.4.4, as your “Forwarder IP addresses.” You will get fast and accurate domain name resolution without ending up at your ISP’s search page when they can’t resolve the domain your looking for.
  • Double check your DNS server and ensure that it is working before moving on to setting up other services.

In the near future, I plan on writing a comprehensive online guide to setting up a functioning Snow Leopard Server that the average Mac OS X user can follow and have a higher likelihood of success than relying on the setup assistant alone. Update (3/12/2011): Since writing this post I have discovered several very good online resources for Snow Leopard Server setup and configuration. So rather than re-invent the wheel, I am just going to post some links to these excellent resources:

wazmacdotcom OSX 10.6 Server setup

DNS Tips: Establishing a DNS Server on Snow Leopard | Hoffmanlabs

Bringing up a Mac mini Server

I do think that OS X Server is easier to setup and manage than say a Windows 2003 server or a linux server. However, it is definitely not as easy as Apple makes it sound on their Mac mini Server webpage.

Don’t let that discourage you from taking the leap!

  • If you’re growing a small business around the mac platform (or Windows),
  • and you’d like to provide email, calendar, and address book services while keeping overall IT costs low.
  • Or you have a large technology investment at home (multiple Macs/iPhones/iPads, multiple users, and lots of files), need centrally managed file storage, and would like to provide your own services. 

Then you can definitely benefit from leveraging a Mac OS X unlimited client license server to meet your evolving needs.

Also, setting up and running your own Snow Leopard Server = MAXIMUM COOLNESS FACTOR!

 

Setting Up A Charging Station

One of the quickest paths to BDH (bad digital hygiene), is not charging your devices. Devices are useless if they don’t have an adequate charge.

If you have multiple devices that need to be charged each day, I recommend setting up a charging station.

In it’s simplest form, a charging station can be nothing more than a power strip with your device’s chargers attached, located in a convenient place.

No one likes the clutter associated with a bunch of loose power cords. So often it is desirable to find a way to disguise your charging station. One option is to hide your charging station in a closet or on a shelf. Here’s an example on the top of a cabinet (the powerstrip is behind the cabinet out of view).

Charging Station On Cabinet

Use inexpensive cable ties to organize and band together all of the loose cables for a neat and tidy look.

Cable Ties

Alternatively, you can also buy a dedicated charging station (a.k.a. charging valet) like the one pictured below. These usually have an opening on the back for a small power strip that you can plug your power cords into. The cords then feed through the charging station to a few holders for your devices so that you can neatly charge them without all of the clutter. An added bonus is that most also have a few drawers that can be used to store other personal items or accessories for your devices. Dedicated charging stations have become very popular and now you can find many different styles and manufacturers. Search online for the most variety.

Charging Station

Recently, I’ve noticed these wireless charging mats at Best Buy.

PowerMat

They are supposed to be the one solution to all of your charging needs. However, if you jump on Amazon.com, you’ll find mostly negative to luke-warm reviews of these types of products (Duracell makes one too). The most consistent complaints being the lack of device compatibility and the bulky sleeves which enable the wireless charging feature. I haven’t tested any, but my recommendation at this point is to stay away from them.

If you’re a road warrior who commutes to work each day, or if you’re on the road a lot for your job, you can also setup a charging station in your car via the 12 volt cigarette lighter or dedicated power port. Some newer vehicles, including many minivans ans SUVs, also come with optional factory installed power inverters which you can plug your power cord into directly without the need to buy a new 12 volt vehicle charging cord.

As with all digital hygiene, the most important consideration is to find something that works for you consistently. Try not to get too complicated, remember the adage keep it super simple (k.i.s.s.). If the recommendations above seem like too much effort, just find a consistent place to plug in your device everyday and you’ll be fine.