Hi Appu,

Then it means that OpenGrok doesn't recognize that it's ClearCase
repository.
Source code for the check is -
http://src.opensolaris.org/source/xref/opengrok/trunk/src/org/opensolaris/opengrok/history/ClearCaseRepository.java#332

For snapshot view it should match first check (if file view.dat exists in
main directory).
That can be source of problem if your snapshot view is on Unix/Linux as
there it's called '*.*view.dat'.
Try to create empty file called view.dat on same place as .view.dat is and
re-run indexer.

-- 
Cheers,
Petr Sobotka aka Pietro

2012/10/3 Appu Mathew <deans...@gmail.com>

> Hi Vladimir
>
> No,  i cannot see any lshistory in the logs.
>
> Regards
> Appu
>
>
> On Tue, Oct 2, 2012 at 8:56 PM, Vladimir Kotal 
> <vladimir.ko...@oracle.com>wrote:
>
>> On 10/01/12 19:07, Appu Mathew wrote:
>>
>>> Hi
>>>
>>> I checked for the Executor log. Pasted below are the logs. Why is it
>>> saying
>>> directory null? Could this be the issue?
>>>
>>> 2012-09-25 10:27:03.926+0530 FINE t10 Executor.exec: Executing command
>>> [/usr/atria/bin/cleartool, –version] in directory null
>>> 2012-09-25 10:27:04.076+0530 FINE t10 Executor.exec: Executing command
>>> [p4,
>>> help] in directory null
>>>
>>
>> I've been told these are harmless:
>>
>>   http://defect.opensolaris.org/bz/show_bug.cgi?id=19165
>>
>> Anyway, please add yourself to the interest list of that bug.
>>
>> The first command is part of the check if clearcase command is available.
>> The second command 'p4 help' command most probably belongs to the same
>> check but in another repository (Perforce).
>>
>> Are there any entries in the log of running clearcase command with
>> 'lshistory' argument ?
>>
>>
>> v.
>>
>>
>>> Regards
>>> Appu
>>>
>>>
>>>
>>>
>>> On Mon, Sep 24, 2012 at 9:01 PM, Vladimir Kotal
>>> <vladimir.ko...@oracle.com>wrote:
>>>
>>>  On 09/21/12 14:52, Appu Mathew wrote:
>>>>
>>>>  Yes.. the cleartool is setting the cleartool path automatically. And
>>>>> yet i
>>>>> am not able to see any historycache folder in my data directory.
>>>>>
>>>>>
>>>> Check opengrok logs (by default in /var/opengrok/log/), there should be
>>>> entries (from the Executor class) about the history commands being run.
>>>>
>>>> Alternatively, you can truss/strace/dtrace the web container process for
>>>> signs of exec() done by getHistoryLogExecutor():
>>>>
>>>> http://src.opensolaris.org/**source/xref/opengrok/trunk/**
>>>> src/org/opensolaris/opengrok/**history/ClearCaseRepository.**java#83<
>>>> http://src.opensolaris.org/source/xref/opengrok/trunk/src/org/opensolaris/opengrok/history/ClearCaseRepository.java#83
>>>> >
>>>>
>>>>
>>>> v.
>>>>
>>>>
>>>>  On Fri, Sep 21, 2012 at 6:16 PM, Vladimir Kotal
>>>>> <vladimir.ko...@oracle.com>**wrote:
>>>>>
>>>>>
>>>>>   On 09/21/12 08:52, Petr Sobotka wrote:
>>>>>
>>>>>>
>>>>>>   Hello Appu,
>>>>>>
>>>>>>>
>>>>>>> I think there is necessary (or used to be ;-) to provide path to
>>>>>>> cleartool
>>>>>>> binary via following property, when you run indexer:
>>>>>>> -Dorg.opensolaris.opengrok.****history.ClearCase=/opt/**
>>>>>>> rational/clearcase/linux_x86/****bin/cleartool
>>>>>>>
>>>>>>>
>>>>>>>  It is sufficient to run the OpenGrok shell script from environment
>>>>>> where
>>>>>> 'cleartool' is available in PATH. The script will then set up the
>>>>>> property
>>>>>> automatically.
>>>>>>
>>>>>>
>>>>>> v.
>>>>>>
>>>>>>
>>>>>>   As well following options should be used for running indexer '-H -S
>>>>>> -r
>>>>>>
>>>>>>> on'.
>>>>>>>
>>>>>>> Then you should check if user which is running web server can use
>>>>>>> clearcase.
>>>>>>> You can check if historycache directory is created in your index dir
>>>>>>> (or
>>>>>>> project dir).
>>>>>>>
>>>>>>> Good luck with ClearCase.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ______________________________****_________________
>>>>>>> opengrok-discuss mailing list
>>>>>>> opengrok-discuss@opensolaris.****org<opengrok-discuss@**
>>>>>>> opensolaris.org<opengrok-discuss@opensolaris.org>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> http://mail.opensolaris.org/****mailman/listinfo/opengrok-****discuss
>>>>>>> <http://mail.opensolaris.org/**mailman/listinfo/opengrok-**discuss>
>>>>>>> <http://mail.**opensolaris.org/mailman/**listinfo/opengrok-discuss<
>>>>>>> http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>  ______________________________****_________________
>>>>>> opengrok-discuss mailing list
>>>>>> opengrok-discuss@opensolaris.****org<opengrok-discuss@**
>>>>>> opensolaris.org<opengrok-discuss@opensolaris.org>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>> http://mail.opensolaris.org/****mailman/listinfo/opengrok-****discuss
>>>>>> <http://mail.opensolaris.org/**mailman/listinfo/opengrok-**discuss>
>>>>>> <http://mail.**opensolaris.org/mailman/**listinfo/opengrok-discuss<
>>>>>> http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>  ______________________________**_________________
>>>> opengrok-discuss mailing list
>>>> opengrok-discuss@opensolaris.**org<opengrok-discuss@opensolaris.org>
>>>> http://mail.opensolaris.org/**mailman/listinfo/opengrok-**discuss<
>>>> http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss>
>>>>
>>>>
>>>
>> _______________________________________________
>> opengrok-discuss mailing list
>> opengrok-discuss@opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss
>>
>
>
> _______________________________________________
> opengrok-discuss mailing list
> opengrok-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss
>
>
_______________________________________________
opengrok-discuss mailing list
opengrok-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss

Reply via email to