On 02/24/2012 11:15 AM, Feyza Eryol wrote:
> Dear all,
>
> After the last update of the CREAM CE we have the same problem in one of
> our sites. The cream database does not except any status information
> after it has lots of SET_JOB_STATUS records in its command table. So,
> the jobs status could not be changed since the job had been successfully
> ended in the site CE.
>
> Do you have any new comment on this issue?
Please open a ggus ticket
Cheers, Massimo
>
> The versions of the CREAM CE is as follows:
> glite-CREAM-3.2.14-1.sl5
> glite-TORQUE_server-3.2.5-1
> glite-TORQUE_utils-3.2.5-1
>
> Thanks,
>
> --feyza
>
> On 11/25/2011 05:52 PM, Christos Triantafyllidis wrote:
>> Is this the definition of "BINGO!"?
>>
>> Database changed
>> +----------+---------------------------+
>> | count(*) | name |
>> +----------+---------------------------+
>> | 2 | DELETE_PROXY_FROM_SANDBOX | | 2 | JOB_PURGE | | 151603 |
>> SET_JOB_STATUS | +----------+---------------------------+
>> 3 rows in set (48.21 sec)
>>
>> I guess i should not just delete these records, right?
>>
>> Many thanks,
>> Christos
>>
>> On Nov 25, 2011, at 5:44 PM, Mario Kadastik wrote:
>>
>>>> Can i check backlog of commands somehow?
>>> Example from my CREAM CE:
>>>
>>> mysql> use creamdb; select count(*), name from command group by name;
>>> Database changed
>>> +----------+---------------------------+
>>> | count(*) | name |
>>> +----------+---------------------------+
>>> | 1 | COPY_NEW_PROXY_TO_SANDBOX | | 1 | JOB_CANCEL | | 163 |
>>> JOB_PURGE | | 15 | JOB_START | | 32 | SET_JOB_STATUS |
>>> +----------+---------------------------+
>>> 5 rows in set (0.01 sec)
>>>
>>>
>>> Mario Kadastik, PhD
>>> Researcher
>>>
>>> ---
>>> "Physics is like sex, sure it may have practical reasons, but that's
>>> not why we do it" -- Richard P. Feynman
>>>
>>
>
>
|