Re: [Condor-users] Quill not saving historical job data (Condor 7.0.1)?

["Justin Ottley" <justin.ottley@xxxxxxxxx>]

Hi Daniel, Steven,
thanks for the replies - 

 > I assume from what you've said that "condor_history" (with no args)
 > produces no output (the historical database is empty)?
 >

That's correct - it produces no output, and i checked the database tables manually for entries, and there are none.
If
its just condor_history that's the problem, I should be able to
see the history in the database by manually querying (using, for
example, the postgres
interpreter). Ill keep scouring the docs for potential configuration,
but as far as I can tell, between QUILL_USE_SQL_LOG and
SCHEDD.QUILL_USE_SQL_LOG, the job history should be working but isnt
(im further convinced that this doesnt seem like a configuration
problem because manual queries show the other history tables like
machine_history are being populated..).

As for the query bug that Steve has already reported, is there a known
timeline as to when that might be fixed? (Maybe I should be posing that
question to condor-admin instead..)

Thanks,
-justin

On 8/21/08, Steven Timm <timm@xxxxxxxx> wrote:

This is a bug that I also reported a couple of weeks ago to condor-admin,
have heard nothing from them yet.  At one point in 6.9.5 they had
everything working and then they started breaking stuff again.
Doesn't anyone in the condor team ever execute a condor_history command
against quill before they release a release?  There are so many different
ways the quill has been broken and they just can't keep it working.

Steve


------------------------------------------------------------------
Steven C. Timm, Ph.D  (630) 840-8525
timm@xxxxxxxx  http://home.fnal.gov/~timm/
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.


On Thu, 21 Aug 2008, Daniel Forrest wrote:

> Justin,
>
>> When i run condor_history [owner] (on the machine running quill) i get:
>>
>> Error while opening the history cursors: ERROR:  column reference
>> "scheddname" is ambiguous at character 314
>>
>> and the postgres log contains:
>>
>> ERROR:  column reference "scheddname" is ambiguous at character 314
>> STATEMENT:  DECLARE HISTORY_OWNER_VER_CUR CURSOR FOR SELECT
>> hv.cluster_id,hv.proc_id,hv.attr,hv.val FROM Jobs_Horizontal_History hh,
>> Jobs_Vertical_History hv WHERE hh.cluster_id=hv.cluster_id AND
>> hh.proc_id=hv.proc_id AND hh.owner='[owner]' AND hh.scheddname =
>> '[quill_host]' AND hh.scheddbirthdate = 1219245801  ORDER BY scheddname,
>> cluster_id,proc_id;
>
> This is a bug in the database query, the final clause needs to be:
>
> "... ORDER BY hh.scheddname, hh.cluster_id,hh.proc_id"
>
> I have a patch for this, but I haven't pushed it to the Condor team
> yet.  It does not affect how the history is stored in the database.
>
> I assume from what you've said that "condor_history" (with no args)
> produces no output (the historical database is empty)?
>
> We are running Condor 7.1.1 now (even though it was pulled), but the
> same problem exists in 7.1.0.  Quill has worked fine for us with both
> versions, both for job queue and historical entries.
>
> --
> Daniel K. Forrest     Laboratory for Molecular and
> forrest@xxxxxxxxxxxxx Computational Genomics
> (608) 262 - 9479      University of Wisconsin, Madison
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/
>
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/condor-users/