Gary,
Thanks for the info. I found the problem, which was an off-by-one error. When you set the keep count to 1, it was actually getting set to 0 which freaked out the scheduler.
I've fixed it, but more importantly if the log rotation schedule is out of bounds the scheduler now simply logs it, picks a valid value, and keeps running. I have no idea what possessed me to make that a fatal error.