build everything with maven, run all tests, tried to run jetty-runner with maven
everything is running ok. +1 for the release from me 2013/2/12 Karl Wright <[email protected]> > Hmm, I haven't tried the restart functionality in ages. But if there > is a failure, obviously restart won't work, because the job will > terminate first. > > Can you look at simple history and tell us whether the fetches succeed > or fail? If they fail, and get retried, then that is interesting and > you should look there. If the failure is because it can't get the > documents into Solr, then the fetches will be retried too, and you > will see errors on the solr indexing attempts. > > Karl > > On Tue, Feb 12, 2013 at 8:23 AM, Erlend Garåsen <[email protected]> > wrote: > > > > I tried to restart the crawl ten minutes after I started it. The job ends > > after a while and will not start again. This is the status after it > stopped: > > Error: Repeated service interruptions - failure getting document version > > > > If I start it manually, it just fetches and fetches without posting > anything > > to Solr. > > > > The only thing I did while it was running the first time was to edit the > > exclude list once - removed a white space at the end of a reg exp rule. > > > > Then I commented out the regexp line in case it DID affected the > documents > > (it shouldn't) and restarted again. Same problem - the job does not want > to > > start: Error: Repeated service interruptions - failure getting document > > version > > > > Just before the job ends, the result description shows "Interrupted: Job > no > > longer active". This is normal, but why won't MCF start the job again > after > > it stops? > > > > Same problem after I manually starts it - MCF just fetches and fetches > > without posting anything to Solr. > > > > E > > > > > > On 12.02.13 13.38, Erlend Garåsen wrote: > >> > >> > >> I have changed some settings in MCF which will reduce the heavy load on > >> our PG server (changed hop count mode to "Keep unreachable documents, > >> forever"). > >> > >> I will start a new crawl today and make a final vote tomorrow. > >> > >> Erlend > >> > >> On 11.02.13 20.49, Karl Wright wrote: > >>> > >>> I've looked at this enough now to conclude that this problem is > >>> probably not intrinsic to ManifoldCF. It may instead be due to > >>> timeouts present in Erlend's PostgreSQL installation. I am therefore > >>> leaving the vote open until there is some reason to believe that there > >>> is a general problem here. > >>> > >>> Thanks, > >>> Karl > >>> > >>> > >>> On Mon, Feb 11, 2013 at 10:02 AM, Erlend Garåsen > >>> <[email protected]> wrote: > >>>> > >>>> > >>>> The job just stopped working and nothing suspicious in my logs. The > >>>> database > >>>> people are saying that we have connection locks again ("<idle> in > >>>> transaction"). > >>>> > >>>> Karl, you mentioned that in order to use the following parameter: > >>>> <property name="org.apache.manifoldcf.database.connectiontracking" > >>>> value="true"/> > >>>> there was no way back to use an older release due to changes in the > >>>> database. That's ok, but was that just a temporary functionality, > which > >>>> means, I need to clear my database in order to use 1.1.1 RC0? > >>>> > >>>> Erlend > >>>> > >>>> > >>>> On 10.02.13 20.01, Karl Wright wrote: > >>>>> > >>>>> > >>>>> Please vote on whether to release Apache ManifoldCF 1.1.1, RC0. > >>>>> > >>>>> The release artifact can be downloaded from: > >>>>> > >>>>> http://people.apache.org/~kwright/apache-manifoldcf-1.1.1 > >>>>> > >>>>> There is a tag at: > >>>>> > >>>>> https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.1.1-RC0 > >>>>> > >>>>> This release has been made primarily to fix a leak of connection > >>>>> handles, described by CONNECTORS-638. Other major fixes have also > >>>>> been included, specifically: > >>>>> > >>>>> - Fix the maven build (various tickets) > >>>>> - Fix the rather broken Elastic Search connector (also various > tickets) > >>>>> > >>>>> Karl > >>>>> > >>>> > >>>> > >>>> -- > >>>> Erlend Garåsen > >>>> Center for Information Technology Services > >>>> University of Oslo > >>>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway > >>>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: > >>>> 31050 > >> > >> > >> > > > > > > -- > > Erlend Garåsen > > Center for Information Technology Services > > University of Oslo > > P.O. Box 1086 Blindern, N-0317 OSLO, Norway > > Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: > 31050 >
