Launchd eating 100% of a CPU, causes machine to permanently hang

Question

Gentleones,
I'm attempting to create and schedule a script that will rotate the apache2 logs in a nice fashion like all the other logs on the machine. (Why Apache can't do logging like everybody else, I don't know, but I guess that's a little off-topic.
So I naively figured I'd just write a script to roll the logs and use launchd to schedule its execution. Far below, you'll find the plist that I created as well as the rolllogs.sh script.
When I manually execute the script (using sudo so it can play with the logfiles and whatnot), it runs fine. Gzip fires up occasionally and awstats updates like it should. The problem comes when I try to use launchctl to get this script going. When I use
launchctl load net.eccles.rolllogs.plist
CPU usage goes immediately to 100% on one CPU (my signature list of "Model" is way out of date) and I can no longer get anything else to run. I can't open a new ssh into the machine, I can't use top unless it's previously running in another ssh, and I never get a command prompt out of the session that is running launchctl. It goes off into la-la land (adjacent to one of the "stans" near the Black Sea, from what I hear).
If I reboot the hard way (5 second power button, because nothing else works), then the machine is back up and running. But when I try to log in again on the machine with the GUI, the machine immediately goes off into la-la land with 100% CPU usage again. The only way around things is to ssh into the machine and remove the plist from /Library/LaunchAgents where I put it in the first place. Then launchd can't find it and it doesn't try to leave the country.
So... I figured it's my script that is causing the problems, right? Well, to sort this one out, I created a simple script, shown way below, called simple.sh which does nothing more than create a line in the system.log file. It, too, works just fine if I call it manually. But when I try to get launchd to run it, same problem as before and nothing appears in the system.log file.
My guess? There's something hokey about my plist file that is really screwing up launchd, but I can't find it.
Anybody got any ideas? Anybody had any success with their own launchd scripts like this one? (Note that I'm trying to get this to run on Sundays at 0315, so I think I have the plist entry correct for that.)
Thanks,
Bill
P.S. I discovered while making this post that square brackets are important somehow to this forum software, but you can escape them with a backslash.)
P.P.S There's lots of whitespace in the plist below, but it gets eaten by aforementioned forum software.
shr-g5:~ admin$ more net.eccles.rolllogs.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>net.eccles.rolllogs</string>
<key>ProgramArguments</key>
<array>
<string>/usr/local/bin/rolllogs.sh</string>
</array>
<key>StartCalendarInterval</key>
<dict>
<key>Day</key>
<integer>0</integer>
<key>Hour</key>
<integer>3</integer>
<key>Minute</key>
<integer>15</integer>
</dict>
</dict>
</plist>
shr-g5:~ admin$ more /usr/local/bin/rolllogs.sh
#!/bin/bash
# Update statistics for AWStats...
cd /Library/WebServer/awstats/wwwroot/cgi-bin
for i in `ls *.conf | sed -e 's/awstats.//' -e 's/.conf//'` ; do
/Library/WebServer/awstats/wwwroot/cgi-bin/awstats.pl -update -config="$i"
done
cd /var/log/apache2/
for i in `ls *_log` ; do
echo "$i";
if \[ -f "${i}" \]; then
echo -n " ${i}"
if \[ -x /usr/bin/gzip \]; then gzext=".gz"; else gzext=""; fi
if \[ -f "${i}.6${gzext}" \]; then mv -f "${i}.6${gzext}" "${i}.7${gzext}"; fi
if \[ -f "${i}.5${gzext}" \]; then mv -f "${i}.5${gzext}" "${i}.6${gzext}"; fi
if \[ -f "${i}.4${gzext}" \]; then mv -f "${i}.4${gzext}" "${i}.5${gzext}"; fi
if \[ -f "${i}.3${gzext}" \]; then mv -f "${i}.3${gzext}" "${i}.4${gzext}"; fi
if \[ -f "${i}.2${gzext}" \]; then mv -f "${i}.2${gzext}" "${i}.3${gzext}"; fi
if \[ -f "${i}.1${gzext}" \]; then mv -f "${i}.1${gzext}" "${i}.2${gzext}"; fi
if \[ -f "${i}.0" \]; then mv -f "${i}.0" "${i}.1" && if \[ -x /usr/bin/gzip \]; then gzip -9 "${i}.1"; fi; fi
if \[ -f "${i}" \]; then mv -f "${i}" "${i}.0"; fi
fi
apachectl graceful
done
shr-g5:~ admin$ more /usr/local/bin/simple.sh
#!/bin/bash
logger TestMessage

Answer 1

Here's the CORRECT plist. There's one subtle difference, "Day" vs "Weekday." It's enough to cause launchctl to go out to lunch as described above.
<?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>Label</key>
<string>net.eccles.rolllogs</string>
<key>ProgramArguments</key>
<array>
<string>/usr/local/bin/rolllogs.sh</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>StartCalendarInterval</key>
<dict>
<key>Hour</key>
<integer>3</integer>
<key>Minute</key>
<integer>15</integer>
<key>Weekday</key>
<integer>0</integer>
</dict>
</dict>
</plist>