[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Spacewalk-list] Task Schedules not running automatically



Thanks Stephen for your email.  I don't see any issues when restarting
taskomatic and firewal is disabled on this server:

--
# grep -i disabled /etc/sysconfig/selinux | grep -v '#'
SELINUX=disabled
# chkconfig --list | grep -i iptab
iptables           0:off    1:off    2:off    3:off    4:off    5:off    6:off
--

taskomatic logs when restarting the service:

--
..snip..
STATUS | wrapper  | 2015/02/05 12:04:20 | TERM trapped.  Shutting down.
STATUS | wrapper  | 2015/02/05 12:04:22 | <-- Wrapper Stopped
STATUS | wrapper  | 2015/02/05 12:04:23 | --> Wrapper Started as Daemon
STATUS | wrapper  | 2015/02/05 12:04:23 | Launching a JVM...
INFO   | jvm 1    | 2015/02/05 12:04:23 | Wrapper (Version 3.2.3)
http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2015/02/05 12:04:23 |   Copyright 1999-2006 Tanuki
Software, Inc.  All Rights Reserved.
INFO   | jvm 1    | 2015/02/05 12:04:23 |
INFO   | jvm 1    | 2015/02/05 12:04:26 | Feb 05, 2015 12:04:26 PM
com.mchange.v2.log.MLog <clinit>
INFO   | jvm 1    | 2015/02/05 12:04:26 | INFO: MLog clients using
java 1.4+ standard logging.
INFO   | jvm 1    | 2015/02/05 12:04:26 | Feb 05, 2015 12:04:26 PM
com.mchange.v2.c3p0.C3P0Registry banner
INFO   | jvm 1    | 2015/02/05 12:04:26 | INFO: Initializing
c3p0-0.9.1.2 [built 06-August-2008 15:35:00; debug? false; trace: 5]
INFO   | jvm 1    | 2015/02/05 12:04:27 | Feb 05, 2015 12:04:26 PM
com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource getPoolManager
INFO   | jvm 1    | 2015/02/05 12:04:27 | INFO: Initializing c3p0
pool... com mchange v2 c3p0 PoolBackedDataSource 5b6d068f [
connectionPoolDataSource ->
com mchange v2 c3p0 WrapperConnectionPoolDataSource dfe42d05 [
acquireIncrement -> 3, acquireRetryAttempts -> 30, acquireRetryDelay
-> 1000, autoCommitOnClose -> false, automaticTestTable -> null,
breakAfterAcquireFailure -> false, checkoutTimeout -> 0,
connectionCustomizerClassName ->
com.redhat.rhn.common.db.RhnConnectionCustomizer,
connectionTesterClassName ->
com.mchange.v2.c3p0.impl.DefaultConnectionTester,
debugUnreturnedConnectionStackTraces -> false, factoryClassLocation ->
null, forceIgnoreUnresolvedTransactions -> false, identityToken ->
k0jcdo97pcem7ws2of8t|36df8f5, idleConnectionTestPeriod -> 300,
initialPoolSize -> 5, maxAdministrativeTaskTime -> 0, maxConnectionAge
-> 0, maxIdleTime -> 300, maxIdleTimeExcessConnections -> 0,
maxPoolSize -> 20, maxStatements -> 0, maxStatementsPerConnection ->
0, minPoolSize -> 5, nestedDataSource ->
com mchange v2 c3p0 DriverManagerDataSource ed8accb8 [ description ->
null, driverClass -> null, factoryClassLocation -> null, identityToken
-> k0jcdo97pcem7ws2of8t|37b9f7e8, jdbcUrl ->
jdbc:postgresql://rwcswalkpg01:5432/spaceschema, properties ->
{user=******, password=******, driver_proto=jdbc:postgresql} ],
preferredTestQuery -> select 'c3p0 ping' from dual, propertyCycle ->
0, testConnectionOnCheckin -> false, testConnectionOnCheckout -> true,
unreturnedConnectionTimeout -> 0, usesTraditionalReflectiveProxies ->
false; userOverrides: {} ], dataSourceName -> null,
factoryClassLocation -> null, identityToken ->
k0jcdo97pcem7ws2of8t|14ad5843, numHelperThreads -> 3 ]
..snip..
--

However, I do see the following in catalina.out which I am not sure
what it means:

--
# cat /var/log/tomcat6/catalina.out
[Fatal Error] :-1:-1: Premature end of file.
[Fatal Error] :-1:-1: Premature end of file.
[Fatal Error] :-1:-1: Premature end of file.
[Fatal Error] :-1:-1: Premature end of file.
[Fatal Error] :-1:-1: Premature end of file.
[Fatal Error] :-1:-1: Premature end of file.
--

Any thing else I should be checking for?

Thanks again for your help.

On Thu, Feb 5, 2015 at 8:15 AM, Stephen Herr <sherr redhat com> wrote:
> Try 'service taskomatic restart' and then watch
> /var/log/rhn/rhn_taskomatic_deamon.log to see if there are errors reported.
> Also make sure that there aren't weird firewall rules or something that
> would prevent tomcat from calling in to taskomatic's api.
>
> -Stephen
>
>
> On 02/04/2015 01:26 PM, Jagga Soorma wrote:
>>
>> Everything seems to be running fine:
>>
>> # rhn-satellite status
>> router (pid 2851) is running...
>> sm (pid 2861) is running...
>> c2s (pid 2871) is running...
>> s2s (pid 2881) is running...
>> tomcat6 (pid 1915) is running...                           [  OK  ]
>> httpd (pid  1976) is running...
>> osa-dispatcher (pid  2898) is running...
>> rhn-search is running (2139).
>> cobblerd (pid 8187) is running...
>> RHN Taskomatic is running (19902).
>>
>> One thing to point out is that I am using a external postgres db.  Not
>> sure if that is causing any issues here?  Not sure what else to check
>> but things look good from a configuration/service perspective.  What
>> am I missing here?
>>
>> Thanks!
>>
>> On Wed, Feb 4, 2015 at 10:15 AM, Jagga Soorma <jagga13 gmail com> wrote:
>>>
>>> More information, when I click on "Edit Schedule" for that task I get
>>> the following message:
>>>
>>> "The scheduling service appears down. Please contact your Satellite
>>> administrator"
>>>
>>> The taskomatic service is running:
>>> # /etc/init.d/taskomatic status
>>> RHN Taskomatic is running (19902).
>>>
>>> And I see the following message in the rhn_taskomatic.log file:
>>>
>>> INFO   | jvm 1    | 2015/02/04 10:13:32 | 2015-02-04 10:13:32,639
>>> [Thread-19] WARN  com.redhat.rhn.taskomatic.TaskoQuartzHelper - Job
>>> channel-repodata-default failed to schedule.
>>>
>>> Any ideas what I might be missing?
>>>
>>> Thanks
>>>
>>> On Wed, Feb 4, 2015 at 10:14 AM, Jagga Soorma <jagga13 gmail com> wrote:
>>>>
>>>> More information, when I click on "Edit Schedule" for that task I get
>>>> the following message:
>>>>
>>>> "The scheduling service appears down. Please contact your Satellite
>>>> administrator"
>>>>
>>>> The taskomatic service is running:
>>>>
>>>>
>>>> On Wed, Feb 4, 2015 at 10:08 AM, Jagga Soorma <jagga13 gmail com> wrote:
>>>>>
>>>>> Hi All,
>>>>>
>>>>> I have recently deployed spacewalk and just noticed that after
>>>>> uploading new packages the repodata is not being created.  I have to
>>>>> manually go into "Admin->Task Schedules" in spacewalk ui and click on
>>>>> channel-repodata-bunch in order for it to work.  After the manual run
>>>>> everything updates fine and the client starts seeing the new rpm
>>>>> versions.  I have made sure that the taskomatic service is running and
>>>>> even tried restarting it without any luck.  I also see the following
>>>>> schedule that is enabled:
>>>>>
>>>>> channel-repodata-default 0 * * * * ? 2014-09-17 18:04:36 PDT
>>>>> channel-repodata-bunch
>>>>>
>>>>> Am I missing a quartz package or something?  Do I need to do something
>>>>> to make sure these tasks run automatically on a scheduled time?  I am
>>>>> using spacewalk version 2.2 and here is the quartz package I have
>>>>> installed:
>>>>>
>>>>> # rpm -qa | grep -i quartz
>>>>> quartz-1.8.4-5.el6.noarch
>>>>>
>>>>> Any help would be appreciated.
>>>>>
>>>>> Thanks!
>>
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list redhat com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list redhat com
> https://www.redhat.com/mailman/listinfo/spacewalk-list


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]