[Spacewalk-list] taskomatic issues

Jan Pazdziora jpazdziora at redhat.com
Mon May 7 13:10:02 UTC 2012


On Tue, May 01, 2012 at 12:13:27AM -0400, Christopher J Petrolino wrote:
> Hello List,
> 
> I am having a problem with tascomatic where repodata is never being created.
> 
> Here is the log file entry that seems to be relevant -
> 
>   spacewalk1 wrapper[1873]: Failure occured during job
> recovery.#012com.redhat.rhn.taskomatic.core.TaskomaticException:
> Failure occured during job recovery.#012#011at
> com.redhat.rhn.taskomatic.core.SchedulerKernel.startup(SchedulerKernel.java:177)#012#011at
> com.redhat.rhn.taskomatic.core.TaskomaticDaemon$1.run(TaskomaticDaemon.java:102)#012#011at
> java.lang.Thread.run(Thread.java:679)#012Caused by:
> org.quartz.SchedulerConfigException: Failure occured during job
> recovery. [See nested exception: org.quartz.JobPersistenceException:
> Couldn't recover jobs: End time cannot be before start time [See
> nested exception: java.lang.IllegalArgumentException: End time cannot
> be before start time]]#012#011at
> org.quartz.impl.jdbcjobstore.JobStoreSupport.schedulerStarted(JobStoreSupport.java:512)#012#011at
> org.quartz.core.QuartzScheduler.start(QuartzScheduler.java:396)#012#011at
> org.quartz.impl.StdScheduler.start(StdScheduler.java:147)#012#011at
> com.redhat.rhn.taskomatic.core.SchedulerKernel.startup(SchedulerKernel.java:165)#012#011...
> 2 more
> 
> Whats interesting is that the log is being written with a date stamp
> that is about 10 minutes or so behind my actual system time...
> 
> Anyone seen this? Any advice?

Is this perhaps an installation with external database, where the time
on the Spacewalk server and the database server would be out of sync?

-- 
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat




More information about the Spacewalk-list mailing list