This error:

WARN 2017-10-09 08:23:56,284 (Idle cleanup thread) -
to set file lock 'mcf/mcf_home/./syncharea/551/442/lock-_POOLTARGET__
REPOSITORYCONNECTORPOOL_SmbFileShare.lock' failed: No such file or directory No such file or directory
at Method)
at org.apache.manifoldcf.core.lockmanager.FileLockObject.
at org.apache.manifoldcf.core.lockmanager.FileLockObject.
at org.apache.manifoldcf.core.lockmanager.LockObject.obtainGlobalWriteLock(
at org.apache.manifoldcf.core.lockmanager.LockObject.
at org.apache.manifoldcf.core.lockmanager.LockGate.
at org.apache.manifoldcf.core.lockmanager.BaseLockManager.
at org.apache.manifoldcf.core.lockmanager.BaseLockManager.enterWriteLock(
at org.apache.manifoldcf.core.lockmanager.LockManager.
at org.apache.manifoldcf.core.connectorpool.ConnectorPool$
at org.apache.manifoldcf.core.connectorpool.ConnectorPool.pollAllConnectors(
at org.apache.manifoldcf.crawler.repositoryconnectorpool.
at org.apache.manifoldcf.crawlerui.IdleCleanupThread.
And the error was repeated indefinitely in the log.

is due to somebody erasing the file-based syncharea while ManifoldCF
processes were active.  We strongly suggest using Zookeeper rather than
file-based synch, in any case.


On Wed, Oct 11, 2017 at 6:05 AM, Luis Cabaceira <[EMAIL PROTECTED]> wrote:

> From the look of it, this can be coming from a limitation on the number
> file handles. You process can be creating too many file handles and not
> closing those in time, eventually preventing further file operations.
> I suggest you check this, in Linux run : cat /proc/sys/fs/file-max
> To see the hard and soft values :
> # ulimit -Hn
> # ulimit -Sn
> P.S. - Change into the user that is running Manifold first
> On 11 October 2017 at 13:54, Olivier Tavard <[EMAIL PROTECTED]
> > wrote:
>> Hi,
>> Thanks for your answer.
>> Yes I could reach the samba server from the MCF server. Indeed, the first
>> hours after the MCF job was launched, thousands of documents were correctly
>> accessed and processed by MCF. The mentioned errors appeared only after few
>> hours. Before that, the indexation was done correctly.
>> Best regards,
>> Olivier TAVARD
>> Le 11 oct. 2017 à 11:21, Cihad Guzel <[EMAIL PROTECTED]> a écrit :
>> Hi Olivier,
>> Did you try to connect to samba server with any samba client app? Check
>> Iptables on your server. Can you stop iptables on ubuntu server? Maybe, you
>> can configure iptables.
>> Regards,
>> Cihad Guzel
>> 2017-10-11 12:02 GMT+03:00 Olivier Tavard <[EMAIL PROTECTED]>
>> :
>>> Hi,
>>> I had this error during crawling a Samba hosted on Ubuntu Server :
>>> ERROR 2017-10-05 00:00:14,109 (Idle cleanup thread) -
>>> MCF|MCF-agent|apache.manifoldcf.crawlerthreads|Exception tossed:
>>> Service '_ANON_0' of type '_REPOSITORYCONNECTORPOOL_SmbFileShare' is
>>> not active
>>> org.apache.manifoldcf.core.interfaces.ManifoldCFException: Service
>>> '_ANON_0' of type '_REPOSITORYCONNECTORPOOL_SmbFileShare' is not active
>>> at org.apache.manifoldcf.core.lockmanager.BaseLockManager.updat
>>> eServiceData(
>>> at org.apache.manifoldcf.core.lockmanager.LockManager.updateSer
>>> viceData(
>>> at org.apache.manifoldcf.core.connectorpool.ConnectorPool$Pool.
>>> pollAll(
>>> at org.apache.manifoldcf.core.connectorpool.ConnectorPool.pollA
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB