On 09/21/2011 12:01 AM, Dustin Tenney wrote:
What are the values
Last Modified
Last Repo Build
Repo Cache Status
on the channel Details page? In other words, were the repodata
generated properly?
If they were not, you might want to check the taskomatic log file.
The Last Modified has dates, but the repo build and cache are both
(none). I am getting errors in the taskomatic log:
INFO | jvm 1 | 2011/08/29 16:55:26 | 2011-08-29 16:55:26,648
[QuartzScheduler_DefaultQuartzScheduler-NON_CLUSTERED_MisfireHandler]
ERROR org.quartz.impl.jdbcjobstore.JobStoreTX - MisfireHandler: Error
handling misfires: Couldn't retrieve trigger: null
INFO | jvm 1 | 2011/08/29 16:55:26 |
org.quartz.JobPersistenceException: Couldn't retrieve trigger: null [See
nested exception: java.lang.ArrayIndexOutOfBoundsException]
INFO | jvm 1 | 2011/08/29 16:55:26 | at
org.quartz.impl.jdbcjobstore.JobStoreSupport.retrieveTrigger(JobStoreSupport.java:1571)
INFO | jvm 1 | 2011/08/29 16:55:26 | at
org.quartz.impl.jdbcjobstore.JobStoreSupport.recoverMisfiredJobs(JobStoreSupport.java:950)
INFO | jvm 1 | 2011/08/29 16:55:26 | at
org.quartz.impl.jdbcjobstore.JobStoreSupport.doRecoverMisfires(JobStoreSupport.java:3125)
INFO | jvm 1 | 2011/08/29 16:55:26 | at
org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:3896)
INFO | jvm 1 | 2011/08/29 16:55:26 | at
org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.run(JobStoreSupport.java:3916)
INFO | jvm 1 | 2011/08/29 16:55:26 | Caused by:
java.lang.ArrayIndexOutOfBoundsException
STATUS | wrapper | 2011/08/29 16:56:42 | TERM trapped. Shutting down.
FATAL | jvm 1 | 2011/08/29 16:57:25 | Failure occured during job
recovery.
com.redhat.rhn.taskomatic.core.TaskomaticException: Failure occured
during job recovery.
at
com.redhat.rhn.taskomatic.core.SchedulerKernel.startup(SchedulerKernel.java:174)
at
com.redhat.rhn.taskomatic.core.TaskomaticDaemon$1.run(TaskomaticDaemon.java:102)
at java.lang.Thread.run(Thread.java:636)
Caused by: org.quartz.SchedulerConfigException: Failure occured during
job recovery. [See nested exception: org.quartz.JobPersistenceException:
Couldn't retrieve trigger: 2 [See nested exception:
java.lang.ArrayIndexOutOfBoundsException: 2]]
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.schedulerStarted(JobStoreSupport.java:627)
at org.quartz.core.QuartzScheduler.start(QuartzScheduler.java:491)
at org.quartz.impl.StdScheduler.start(StdScheduler.java:143)
at
com.redhat.rhn.taskomatic.core.SchedulerKernel.startup(SchedulerKernel.java:162)
Hey Dustin,
this look like unexpected content in quartz internal tables. How did you
come to this state?
Regards,
Tomas
--
Tomas Lestach
RHN Satellite Engineering, Red Hat
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
