from cron at a different time than is listed in crontab. Any ideas on why this might have happened?
Most likely if your system clock shifted time, crond is usually reluctant to give up its grip on time differences and can show this behaviour. If the clock time on the server is correct, try restarting crond.
Now, last night, upcp didnt run at all, but it is set to run at 11:30 pm.
The night before it ran at 3:30 am. The system time appears to be correct.
The night before it ran at 3:30 am. The system time appears to be correct.
