On Jan 8, 2008 3:12 PM, Nate Keegan <[EMAIL PROTECTED]> wrote: > Seeing this from time to time in my roller.log file: > > INFO 2008-01-08 13:01:01,073 > SingleThreadedFeedUpdater:updateSubscriptions - --- DONE --- Updated > subscriptions in 0.596 seconds
That's good news. Subscriptions were updated! That should mean that the rag_entry table is full of data and ready to be displayed via the Planet $pager. > DEBUG 2008-01-08 13:01:01,076 RollerTaskWithLeasing:run - > RefreshRollerPlanetTask: Attempting to release lease > DEBUG 2008-01-08 13:01:01,127 RollerTaskWithLeasing:run - > RefreshRollerPlanetTask: Lease NOT released, some kind of problem > > DEBUG 2008-01-08 13:11:00,322 TaskScheduler:runTasks - > RefreshRollerPlanetTask: next allowed run time = Wed Dec 31 17:05:00 MST > 1969 > DEBUG 2008-01-08 13:11:00,322 TaskScheduler:runTasks - MISSED last run, > checking if waiting is necessary > DEBUG 2008-01-08 13:11:00,323 TaskScheduler:runTasks - WAITING for next > reasonable run time > DEBUG 2008-01-08 13:11:00,344 TaskScheduler:runTasks - SyncWebsitesTask: > next allowed run time = Thu Jan 01 17:00:00 MST 1970 > DEBUG 2008-01-08 13:11:00,345 TaskScheduler:runTasks - MISSED last run, > checking if waiting is necessary > DEBUG 2008-01-08 13:11:00,345 TaskScheduler:runTasks - WAITING for next > reasonable run time > DEBUG 2008-01-08 13:11:00,346 TaskScheduler:runTasks - Finished I'm not sure if that 1969 date is a bad sign or not. I have seen a couple of cases where the task scheduler gets confused and the only way to kick it back into action is to stop Roller, delete all rows from the roller_tasklock table and then restart. - Dave
