Error in Manifoldcf, what's the first step?

2013-10-29 Thread Ronny Heylen
Hi, Solr is 4.4, manifoldcf 1.3. We are indexing a shared windows network drive, filtering on *.doc*, *.xls*, *.pdf ... with about 650,000 files to index, giving a SOLR index 35GB in size. The result is great except that the manifoldcf job crashes before the end. Note that: -

Re: Error in Manifoldcf, what's the first step?

2013-10-29 Thread Ronny Heylen
Sent from my Windows Phone -- From: Ronny Heylen Sent: 10/29/2013 6:52 AM To: user@manifoldcf.apache.org Subject: Error in Manifoldcf, what's the first step? Hi, Solr is 4.4, manifoldcf 1.3. We are indexing a shared windows network drive, filtering on *.doc

Re: Error in Manifoldcf, what's the first step?

2013-10-29 Thread Ronny Heylen
) at java.lang.ClassLoader.loadClass(Unknown Source) ... 30 more On Tue, Oct 29, 2013 at 1:25 PM, Ronny Heylen securaqbere...@gmail.comwrote: That was a very good suggestion! Setting the max size has solved the problem for the first subfolder on which we test. Now we wil retry on the full drive

Error: Repeated service interruptions - failure processing document: Read timed out

2013-11-06 Thread Ronny Heylen
Hi, We use Manifoldcf 1.3 and Solr 4.4 to index a shared network drive with several hundred thousands documents. Doing only one manifoldcf job to index all the drive was always giving some kind of error, therefore to better understand where the problem can be, we made one job to index all *.doc*,

Re: Error: Repeated service interruptions - failure processing document: Read timed out

2013-11-06 Thread Ronny Heylen
can't tell. You could, however, create a null output connection, and create a similar job the sends its output there, and see if it completes. Can you do this and get back to me? Thanks, Karl On Wed, Nov 6, 2013 at 3:17 PM, Ronny Heylen securaqbere...@gmail.comwrote: Hi, We use

Re: Error: Repeated service interruptions - failure processing document: Read timed out

2013-11-07 Thread Ronny Heylen
there, and see if it completes. Can you do this and get back to me? Thanks, Karl On Wed, Nov 6, 2013 at 3:17 PM, Ronny Heylen securaqbere...@gmail.comwrote: Hi, We use Manifoldcf 1.3 and Solr 4.4 to index a shared network drive with several hundred thousands documents. Doing only one

Re: Error: Repeated service interruptions - failure processing document: Read timed out

2013-11-07 Thread Ronny Heylen
to excessive load on the Solr instance. My suggestion is to increase the socket timeout on your solr connection to at least 30 minutes or more to see if this resolves. Thanks, Karl On Thu, Nov 7, 2013 at 9:30 AM, Ronny Heylen securaqbere...@gmail.comwrote: Hi, We have reset thottling

How to index files, not folders

2013-11-09 Thread Ronny Heylen
Hi, Indexing all indexable files on our Windows drive fails with different problems. Several of these problems were solved by the list, thanks for that, now we still have (at least) the missing class in common-compress problem. Using jar from common-compress 1.6 did not help. Anyway, this

autovacuum

2013-11-09 Thread Ronny Heylen
Turning autovacuum off as recommended in the manifoldcf optimization guide, I receive the message here after. Postgresql is version 9.3. Is it still applicable that we should vacuum ourselve everyday? Running autovacuum recommended Introduced in PostgreSQL 8.1, the autovacuum process which was

Useful tip?

2013-11-09 Thread Ronny Heylen
We are not used (yet ;-) ) to read the logging we can get from the manifoldcf UI, but it seemed to us that manifoldcf was loosing some time on ~-...doc files (the hidden files MS-Word is using while you are editing and left on the disk when MS-Word crashes). We have +/- 8 doc files and had +/-

Re: Scheduler not working as we expected

2018-09-25 Thread Ronny Heylen
Hi, We have been using SOLR for a few years and now the server has been transferred to the VM's in out HQ ( and reinstalled ), We ara having the the following issue now : orcing SOLR indexation by curl works, as we can see from: *curl "*

Unscribe

2022-10-21 Thread Ronny Heylen
Hi, Please unscribe me from these emails, I don't work anymore. Regards, Ronny