Re: [Spacewalk-list] no repodata
Finally i figured out problem.
Spacewalk used system-wide java installed, with libs in /usr/share/java
/usr/share/java/postgresql-jdbc.jar was symlinked to 8.1 jdbc driver. I've
downloaded and relinked it to 9.1 jdbc4 driver, and now everything works fine.
08.02.2012, 16:17, "Denis Zinevich" :
> well, that didn't help.
> I've cleaned tables as you sugessted ( with no errors ), and restarted
> services.
> When trying to single schedule run "channel-repodata-bunch" I'm getting same
> error in taskomatic log.
>
> 07.02.2012, 12:06, "Tomas Lestach" :
>
>> On Monday 06 of February 2012 19:09:51 Denis Zinevich wrote:
>>> Description: CentOS release 5.7 (Final)
>>> quartz-1.8.1-3.el5
>>> tascomatic restart didn't help - same erros occurs.
>>> rhn-search daemon is up. i do not see any erros in it's log.
>> You may try to reinitialize quartz configuration:
>>
>> 1. stop spacewalk services
>> 2. run following sql commands:
>>
>> DELETE FROM qrtz_job_details;
>> DELETE FROM qrtz_job_listeners
>> DELETE FROM qrtz_triggers
>> DELETE FROM qrtz_simple_triggers
>> DELETE FROM qrtz_cron_triggers
>> DELETE FROM qrtz_blob_triggers
>> DELETE FROM qrtz_trigger_listeners
>> DELETE FROM qrtz_calendars
>> DELETE FROM qrtz_paused_trigger_grps
>> DELETE FROM qrtz_fired_triggers
>> DELETE FROM qrtz_scheduler_state
>> DELETE FROM qrtz_locks
>>
>> INSERT INTO qrtz_locks values('TRIGGER_ACCESS');
>> INSERT INTO qrtz_locks values('JOB_ACCESS');
>> INSERT INTO qrtz_locks values('CALENDAR_ACCESS');
>> INSERT INTO qrtz_locks values('STATE_ACCESS');
>> INSERT INTO qrtz_locks values('MISFIRE_ACCESS');
>>
>> 3. start spacewalk services
>>
>> By deleting the quartz configuration, it shall be reinitialized.
>>
>> Regards,
>> Tomas
>>
>> --
>> Tomas Lestach
>> RHN Satellite Engineering, Red Hat
>>> 06.02.2012, 15:19, "Tomas Lestach" :
>>>> Hello,
>>>>
>>>> what is your OS? What version of quartz you hvae installed?
>>>> Do you get this error systematically after every taskomatic restart?
>>>>
>>>> Does rhn-search work as exected?
>>>>
>>>> Regards,
>>>>
>>>> --
>>>> Tomas Lestach
>>>> RHN Satellite Engineering, Red Hat
>>>>
>>>> On Tuesday 17 of January 2012 13:00:16 Denis Zinevich wrote:
>>>>> Hi all,
>>>>>
>>>>> just made fresh install. version 1.6
>>>>> There's no repodata being generated. taskomatic produce following log.
>>>>> Tried upgrade to 1.7-nightly. Didn't help.
>>>>> Any ideas how to fix ?
>>>>>
>>>>> INFO | jvm 1 | 2012/01/17 10:56:08 | INFO: Initializing c3p0
>>>>> pool... com.mchange.v2.c3p0.PoolBackedDataSource@869113 [
>>>>> connectionPoolDataSource ->
>>>>> com.mchange.v2.c3p0.WrapperConnectionPoolDataSource@cb07ef [
>>>>> acquireIncrement -> 3, acquireRetryAttempts -> 30, acquireRetryDelay
>>>>> -> 1000, autoCommitOnClose -> false, automaticTestTable -> null,
>>>>> breakAfterAcquireFailure -> false, checkoutTimeout -> 0,
>>>>> connectionTesterClassName ->
>>>>> com.mchange.v2.c3p0.impl.DefaultConnectionTester, factoryClassLocation
>>>>> -> null, forceIgnoreUnresolvedTransactions -> false, identityToken ->
>>>>> cb07ef, idleConnectionTestPeriod -> 300, initialPoolSize -> 5,
>>>>> maxIdleTime -> 300, maxPoolSize -> 20, maxStatements -> 0,
>>>>> maxStatementsPerConnection -> 0, minPoolSize -> 5, nestedDataSource
>>>>> ->
>>>>> com.mchange.v2.c3p0.DriverManagerDataSource@18b1f8f [ description ->
>>>>> null, driverClass -> null, factoryClassLocation -> null,
>>>>> identityToken -> 18b1f8f, jdbcUrl ->
>>>>> jdbc:postgresql://localhost:5432/space, properties -> {user! =**,
>>>>> password=**, driver_proto=jdbc:postgresql} ], preferredTestQuery
>>>>> -> null, propertyCycle -> 300, testConnectionOnCheckin -> false,
>>>>> testConnectionOnCheckout -> true,
>>>>> usesTraditionalReflectiveProxies -> false ], factoryClassLocation ->
>>>>>
[Spacewalk-list] no repodata
Hi all,
just made fresh install. version 1.6
There's no repodata being generated. taskomatic produce following log.
Tried upgrade to 1.7-nightly. Didn't help.
Any ideas how to fix ?
INFO | jvm 1| 2012/01/17 10:56:08 | INFO: Initializing c3p0 pool...
com.mchange.v2.c3p0.PoolBackedDataSource@869113 [ connectionPoolDataSource ->
com.mchange.v2.c3p0.WrapperConnectionPoolDataSource@cb07ef [ acquireIncrement
-> 3, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose
-> false, automaticTestTable -> null, breakAfterAcquireFailure -> false,
checkoutTimeout -> 0, connectionTesterClassName ->
com.mchange.v2.c3p0.impl.DefaultConnectionTester, factoryClassLocation -> null,
forceIgnoreUnresolvedTransactions -> false, identityToken -> cb07ef,
idleConnectionTestPeriod -> 300, initialPoolSize -> 5, maxIdleTime -> 300,
maxPoolSize -> 20, maxStatements -> 0, maxStatementsPerConnection -> 0,
minPoolSize -> 5, nestedDataSource ->
com.mchange.v2.c3p0.DriverManagerDataSource@18b1f8f [ description -> null,
driverClass -> null, factoryClassLocation -> null, identityToken -> 18b1f8f,
jdbcUrl -> jdbc:postgresql://localhost:5432/space, properties -> {user!
=**, password=**, driver_proto=jdbc:postgresql} ], preferredTestQuery
-> null, propertyCycle -> 300, testConnectionOnCheckin -> false,
testConnectionOnCheckout -> true, usesTraditionalReflectiveProxies -> false ],
factoryClassLocation -> null, identityToken -> 869113, numHelperThreads -> 3 ]
FATAL | jvm 1| 2012/01/17 10:56:17 | 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)
... 2 more
Caused by: org.quartz.JobPersistenceException: Couldn't retrieve trigger: 2
[See nested exception: java.lang.ArrayIndexOutOfBoundsException: 2]
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.retrieveTrigger(JobStoreSupport.java:1571)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.recoverMisfiredJobs(JobStoreSupport.java:950)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.recoverJobs(JobStoreSupport.java:834)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport$2.execute(JobStoreSupport.java:806)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport$41.execute(JobStoreSupport.java:3729)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3763)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3725)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.recoverJobs(JobStoreSupport.java:802)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.schedulerStarted(JobStoreSupport.java:625)
... 5 more
Caused by: java.lang.ArrayIndexOutOfBoundsException: 2
at org.postgresql.util.PGbytea.toBytes(PGbytea.java:47)
at
org.postgresql.jdbc2.AbstractJdbc2ResultSet.getBytes(AbstractJdbc2ResultSet.java:2048)
at
org.postgresql.jdbc2.AbstractJdbc2ResultSet.getBytes(AbstractJdbc2ResultSet.java:2233)
at
org.apache.commons.dbcp.DelegatingResultSet.getBytes(DelegatingResultSet.java:252)
at
org.quartz.impl.jdbcjobstore.PostgreSQLDelegate.getObjectFromBlob(PostgreSQLDelegate.java:92)
at
org.quartz.impl.jdbcjobstore.StdJDBCDelegate.selectTrigger(StdJDBCDelegate.java:2132)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.retrieveTrigger(JobStoreSupport.java:1553)
... 13 more
thanks in advance.
--
Denis
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
