I’ve just finished updating all my servers with Security update 2009-001. Experience from the last updates made me check the postfix config for changes and yes there was the usual change to the config, luckily postfix itself wasn’t affected. To correct it comment out or delete the following line:
from ‘/etc/postifx/main.cf‘. Restart postfix (reloading config does not work) with:
sudo postfix start
On my production server sqlgrey didn’t start after a first reboot but I think that was a temporary glitch as it did work on my other servers and was easily started manually.
If you want to read more on what is affected in the updates I would suggest reading the Apple support site for the 2009-001 security update.
In case of doubt, please make a full bootable disk image backup with Cabon Copy Cloner before you start.
Comments
10:07 pm
Richard: I’ve had the same issue on restart of the server with sqlgrey not starting itself.
I don’t know how often of why this happens, but in my case it happens consistently and it turns out after some digging through the system logs that mysql hasn’t started fully yet, sqlgrey can’t find the mysql server and dies.
I suspect there are some simple fixes for making sure mysql is started first, but given that it’s simple to manually start sqlgrey and server restarts are not all that frequent, it has not been an issue worth my time to solve.
I post it here just in case anyone else is seeing this, wanting to know a possible cause, or has solved it in some simple way.
Hope it helps…
8:48 am
Richard: Well, I finally bit the bullet and upgraded. Not a happy time.
I’m posting this for any of your readers who use Perl-based stuff like Amavisd. I know it’s not on your list of items, but I’ve got it running (plus a DKIM checker) and it helps.
If you have Perl anything, and you’ve installed or udpated modules (as required with Amavisd), this update will break Perl.
You can find the solution here:
http://bulknews.typepad.com/blog/2009/02/mac-os-x-security-update-2009001-breaks-perl-cpan.html
The three installs should work. If not, scroll down the comments and there’s a list of files affected by the update. Restore all of them from your backup (you did backup before you upgraded, right?) and all will be fine. (at least it was for me).
I hope that helps someone…
9:33 am
Jeff, sorry to hear about your problems. I had read about the perl problems and was afraid that the sqlgey (perl based) stuff would be affected but that wasn’t the case, therefore I didn’t report it.
But I will have a closer look…