Category: Geek Bits

Just a quick note on how upgrading to yesterday’s 10.5.3 release broke iCal, what didn’t fix it, and what did.

I upgraded yesterday, and everything seemed fine. It wasn’t until this morning that I tried to access my iCal, and I received an error dialog letting me know that iCal could not move the Calendar Cache due to a permissions problem.

I manually checked permissions on ~/Library/Calendars/Calendar\ Cache and the file was owned and writable by me, as well as the containing directory.

smeg:~ merlin$ cd ~/Library/Calendars
smeg:Calendars merlin$ ls -al Calendar\ Cache*
-rwxr–r–+ 1 merlin staff 532480 May 28 17:39 Calendar Cache
-rwxr–r–+ 1 merlin staff 311296 Feb 11 15:33 Calendar Cache~1

Running Permissions Repair inside of DIsk Utility did not help.

Moving the old Calendar Cache files out of the way did fix the problem, and the new iCal was able to upgrade and rebuld its databases:

smeg:~ merlin$ cd ~/Library/Calendars
smeg:Calendars merlin$ mv Calendar\ Cache Calendar\ Cache.bak
smeg:Calendars merlin$ mv Calendar\ Cache~1 Calendar\ Cache~1.bak

If you found this page because you have hit this problem, then I hope this helps.

-Chris

[ad#adsense-horizontal]

I’ll flesh this out later, but if you are having problems with the check_snmp_cisco_ifstatus plugin for nagios, and you are getting errors like the one below, you need to make a couple of tweaks.

**ePN failed to compile /usr/lib64/nagios/plugins/check_snmp_cisco_ifstatus: Global symbol script requires explicit package name at (eval 7) line 30,

Right after the line that reads use Getopt::Std; you need to add the following three statements:

my ($oid_sysDescr,$community,$s,$e,$oid_temp,
$temp_interface_descr,$errorstring,$temp,$index,
$configfilepath,$hostname,$script,$script_version,
$critical,$ifadminstatus,$ifdescr,$ifinerrors,$iflastchange,
$ifmtu,$ifoperstatus,$ifoutbitssec,$ifouterrors,$ifoutqlen,
$ifphysaddress,$ifspeed,$iftype,$number_of_interfaces,
$oid_ifadminstatus,$oid_ifdescr,$oid_ifinerrors,
$oid_iflastchange,$oid_ifmtu,$oid_ifnumber,
$oid_ifoperstatus,$oid_ifouterrors,$oid_ifoutqlen,
$oid_ifphysaddress,$oid_ifspeed,$oid_iftype,
$oid_locIfIntBitsSec,$oid_locIfOutBitsSec,$oid_sysdescr,
$returnstring,$status,$target_interface,
$target_interface_index,$timeout,$version,$warning);

our ($opt_c,$opt_C,$opt_h,$opt_H,$opt_w,$opt_i);

$status=0;

The short story is that Nagios has moved to used re-compiled perl, and as a security feature they insert several strictness policies regarding variable handling. You can disable this via nagios.cfg in version 3.0, but config template for 2.0 doesn’t have this option and I haven’t had a chance to try the setting anyways just to see what happens.

Verbose documentation regarding how this affects your plugins can be found here:

Nagios 2.x
Nagios 3.x

[ad#adsense-horizontal]