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

Re: [Condor-users] understanding condor history file

Thanks Ian. I do understand that batch system log files should be read using the batch system command but I think there some problem with that at the moment.
Does, history file logs every single jobs those were submitted? We have a separate files which logs the jobID (along with some other info) as soon as the job is submitted to the cluster. There is a huge difference in the number of jobs in history file and our own log file. Any idea what am I missing?


On 26/10/2010 16:57, Ian Chesal wrote:
On Tue, Oct 26, 2010 at 11:52 AM, Santanu Das <santanu@xxxxxxxxxxxxxxxxx> wrote:
On 25/10/2010 14:53, Ian Chesal wrote:

When you "looked in to the history file" do you mean the file defined by the HISTORY setting in the configuration file?

Yes, that's what I meant. Like, for us, it's:
[root@serv07 etc]# condor_config_val HISTORY
Dan already explained the discrepancies you're seeing. The duplicates are likely a cluster vs. process level for the attributes.

I'll add that this file is meant to be replayed by the condor_history command to rebulid the classads for the jobs. While it's human-readable, that's not really the best way to understand the information that's stored in the file. The information isn't meant for human consumption. Better would be to use "condor_history -f /home/condorr/spool/history -l" to get the full ad for every job in the file.

- Ian
_______________________________________________ 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/