Entourage – times off calendar events

2) Times are always off in mail messages and/or calendar events. How can this be fixed?

First, go to the Date & Time preferences, located in:

OS X System Preferences: Date & Time

OS 9 Control Panels -> Date & Time

First, check to make sure the city listed is in the same time zone as your computer. If not, change it to a city that is. You may notice that the time has changed accordingly. Change it back to the local time. Official time can be found at the U.S. Time Service within the U.S. or the World Time Server for non-domestic locations. There is also information there on syncing your computer clock to their time server, to always keep your clock accurate to the official time.

Now, if you have Entourage 2001, you are done. In Entourage X, go back into Entourage and go to Entourage -> General Preferences. Under the Calendar tab, choose the correct time zone.

Script to copy RSA key multiple servers

I recently needed to add my rsa public key to multiple servers where the .ssh directory didn’t already exist nor the .ssh/authorized_keys in addition to the correct permissions for the .ssh directory and authorized_keys file

I found this taken from the below post on how to install it on OS X: http://thesystemisntdown.blogspot.com/2010/03/ssh-copy-id-on-os-x.html

I can’t find an official source for the ssh-copy-id. If you can, please comment a link for me.

Nevertheless, this should get you what you’re looking for:
wget http://blog.christopherpitzer.com/wp-content/uploads/ssh-copy-id -O /usr/bin/ssh-copy-id
sudo chmod +x /usr/bin/ssh-copy-id

Note: ssh-copy-id appends to authorized_keys file

I created this script to run in order to add to multiple servers:

SSH-COPY-ID=$(which ssh-copy-id)
# Array to add .ssh authorized keys to systems for access
Systems=(server1 server2 server3 server4 server 5 …)
for S in “${Systems[@]}”
#echo $S.$DOMAIN
$SSH-COPY-ID -i ~/.ssh/id_rsa.pub username@$S.$DOMAIN

Note: You need to run this script from your home directory and if you have dsa keys instead of rsa keys, make sure to use the correct name.

Resolve OS X folder with question mark

Today I applied security patches to one of my Leopard servers and rebooted only to have the server not come up.  I had to drive all the way into work to discover the folder with a question mark on it signifying that the server didn’t recognize any boot drive.

Found this very helpful post: http://support.apple.com/kb/TS1440?viewlocale=en_US

Fortunately I could see the drive and the software RAID through Disk Utility when booting from CD.

Tried all of those steps and no luck!  I really didn’t want to reformat the drive and re-install the OS and then have to re-install all applications too!

Recognizing that I had a mirror RAID with 2 disks I thought maybe one of the disks might be causing and issue so I removed one of the disks from the RAID set like this.

dlopez$ diskutil checkRAID

Name:                   Mirror
Unique ID:              2CFEC74D-5C0C-49CB-940E-6099AE3C2B97
Type:                   Mirror
Status:                 Online
Device Node:            disk4
Apple RAID Version:     2
 #      Device Node     UUID                                    Status
0       disk1s3         EF3F0D87-0E9A-4ED4-BB2B-F2A7EBFD0306    Online
1       disk3s3         B1EC4F22-9C0D-4CDB-90FE-D49347195834    Online

I wanted to remove disk3s3 from the RAID

dlopez$ sudo diskutil removeFromRAID disk3s3 disk4
AppleRAID Headers removed from disk 'disk3s3'
Changing filesystem size on disk 'disk3s3'...
Attempting to change filesystem size from 14658928640 to 14658936832 bytes
The disk has been removed from the RAID

Then I ran a disk repair on it and rebooted.  Sure enough the server was back!  Now I just need to recreate the mirror RAID again.

Leopard Apache won’t start after reboot

I took the following from this google posting: http://old.nabble.com/-JIRA–Issue-Comment-Edited:-(MAGNOLIA-1959)-Leopard-(osx-10.5)-issues-td21853819.html

Just following up my previous posts and the solution we found to work with the ‘Too Many Open Files’ error, maybe it will help others as well.

The problem seems to be in the way Apple has changed the files/proc settings for Leopard. Using the ‘ulimit’ and ‘sysctl’ options to adjust the settings no longer works.

The option you have to use is the ‘launchctl limit’ command, which also adjusts both the ‘ulimit’ and the ‘sysctl’ settings automatically.

To check your existing settings, you can use the command ‘launchctl limit’, this shows that the server is ridiculously set at a very low maxfiles of 256 files per user/process.

Three columns will be returned, the first column displayed will be the name of the limit setting, you are looking for the ‘maxproc’ and/or ‘maxfiles‘ settings towards the bottom of the list.

To increase the maxfiles you can use the command ‘launchctl limit maxfiles user max system max’, where user max is the maximum files you want to allow for each user/process and likewise for system max.

An example would be (running as super user): launchctl limit maxfiles 2048 unlimited

We first increased this to 2048 unlimited as Apple states in the manual that the Server Admin app is supposed to change the soft process limit from 100 (the default) to 2048 when starting Apache, obviously this is not happening and the default is set to 256, so the manual is out of date or wrong. We did however still find infrequent ‘too many open files’ errors in apache logs so again increased the limit, this time to 4096 unlimited and have not had a problem since.

The same applies to the maxproc setting if you need additional processes.

You can verify the changes by using the ‘ulimit -a’ and/or ‘sysctl -a | grep files’ commands.

To make the changes stick through a restart, you need to add a file (as it doesn’t exist) by using something like ‘sudo pico /etc/launchd.conf’ and add the changes one per line, so in our case, our file looks like this:

limit maxfiles 4096 unlimited

Remember you do not need to add ‘launchctl’ in front of the commands in this file.

Hope this helps others with this problem, we have not upgraded to 10.5.3 yet, now that things are working in 10.5.2 we will have to setup a test environment before applying anymore potential fuel to the fire!

So I increased the maxfiles to 4096 (launchctl limit maxfiles 4096 unlimited) and the maxproc to 2048 (launchctl limit maxproc 2048 unlimited).

After this two instances are starting fine.