You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by Sahil Shah <sa...@gmail.com> on 2015/06/18 03:01:38 UTC

Re: [jira] [Created] (NUTCH-2000) Link inversion fails with .locked already exists.

unsubscribe

-Sahil

On Thu, Apr 23, 2015 at 4:03 AM, Julien Nioche (JIRA) <ji...@apache.org>
wrote:

> Julien Nioche created NUTCH-2000:
> ------------------------------------
>
>              Summary: Link inversion fails with .locked already exists.
>                  Key: NUTCH-2000
>                  URL: https://issues.apache.org/jira/browse/NUTCH-2000
>              Project: Nutch
>           Issue Type: Bug
>     Affects Versions: 1.9
>             Reporter: Julien Nioche
>              Fix For: 1.10
>
>
> using standard crawl script with a brand new test dir in local mode I am
> getting
>
> Link inversion
> /data/BLABLABLA/runtime/local/bin/nutch invertlinks
> /data/BLABLABLA/testCrawl2//linkdb
> /data/BLABLABLA/testCrawl2//segments/20150423114335
> LinkDb: java.io.IOException: lock file
> /data/BLABLABLA/testCrawl2/linkdb/.locked already exists.
>
> PS: 2000!
>
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Re: [jira] [Created] (NUTCH-2000) Link inversion fails with .locked already exists.

Posted by Sahil Shah <sa...@gmail.com>.
Where is the unsubscribe link?

-Sahil

On Wed, Jun 17, 2015 at 6:44 PM, Mattmann, Chris A (3980) <
chris.a.mattmann@jpl.nasa.gov> wrote:

>  Please follow the instructions on the website to unsubscribe.
>
>  ------------------------------
> *From:* Sahil Shah [sahilshah2650@gmail.com]
> *Sent:* Wednesday, June 17, 2015 6:01 PM
> *To:* dev@nutch.apache.org
> *Subject:* Re: [jira] [Created] (NUTCH-2000) Link inversion fails with
> .locked already exists.
>
>   unsubscribe
>
>  -Sahil
>
> On Thu, Apr 23, 2015 at 4:03 AM, Julien Nioche (JIRA) <ji...@apache.org>
> wrote:
>
>> Julien Nioche created NUTCH-2000:
>> ------------------------------------
>>
>>              Summary: Link inversion fails with .locked already exists.
>>                  Key: NUTCH-2000
>>                  URL: https://issues.apache.org/jira/browse/NUTCH-2000
>>              Project: Nutch
>>           Issue Type: Bug
>>     Affects Versions: 1.9
>>             Reporter: Julien Nioche
>>              Fix For: 1.10
>>
>>
>> using standard crawl script with a brand new test dir in local mode I am
>> getting
>>
>> Link inversion
>> /data/BLABLABLA/runtime/local/bin/nutch invertlinks
>> /data/BLABLABLA/testCrawl2//linkdb
>> /data/BLABLABLA/testCrawl2//segments/20150423114335
>> LinkDb: java.io.IOException: lock file
>> /data/BLABLABLA/testCrawl2/linkdb/.locked already exists.
>>
>> PS: 2000!
>>
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.3.4#6332)
>>
>
>

RE: [jira] [Created] (NUTCH-2000) Link inversion fails with .locked already exists.

Posted by "Mattmann, Chris A (3980)" <ch...@jpl.nasa.gov>.
Please follow the instructions on the website to unsubscribe.

________________________________
From: Sahil Shah [sahilshah2650@gmail.com]
Sent: Wednesday, June 17, 2015 6:01 PM
To: dev@nutch.apache.org
Subject: Re: [jira] [Created] (NUTCH-2000) Link inversion fails with .locked already exists.

unsubscribe

-Sahil

On Thu, Apr 23, 2015 at 4:03 AM, Julien Nioche (JIRA) <ji...@apache.org>> wrote:
Julien Nioche created NUTCH-2000:
------------------------------------

             Summary: Link inversion fails with .locked already exists.
                 Key: NUTCH-2000
                 URL: https://issues.apache.org/jira/browse/NUTCH-2000
             Project: Nutch
          Issue Type: Bug
    Affects Versions: 1.9
            Reporter: Julien Nioche
             Fix For: 1.10


using standard crawl script with a brand new test dir in local mode I am getting

Link inversion
/data/BLABLABLA/runtime/local/bin/nutch invertlinks /data/BLABLABLA/testCrawl2//linkdb /data/BLABLABLA/testCrawl2//segments/20150423114335
LinkDb: java.io.IOException: lock file /data/BLABLABLA/testCrawl2/linkdb/.locked already exists.

PS: 2000!




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)