Re: ldap authentication with crawler ui

2017-07-12 Thread Karl Wright 
Have any users out there made use of LDAP crawler-UI authentication?  If
so, can you have a look at Theodor's configuration and setup?

Karl


On Wed, Jul 12, 2017 at 10:07 AM, Theodor Carp 
wrote:

> Hi,
>
> Using the below settings:
>
>  value="org.apache.manifoldcf.core.auth.LdapAuthenticator" />
>  value="LDAP-AUTHENTICATION" />
> ldap://hdp01.local:389; />
>  value="simple" />
>  value="uid=$(userID),ou=Users,dc=local" />
>  value="(uid=$(userID))" />
>  value="uid" />
>
> I'm getting errors like:
>
> ERROR 2017-07-12 15:20:32,951 (qtp1295083508-17) - User not authenticated
> = authenticating_user exception = [LDAP: error code 32 - No Such Object]
> javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object];
> remaining name ''
> at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3161)
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3082)
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2888)
> [...]
> FATAL 2017-07-12 15:20:32,956 (qtp1295083508-17) - Exception logging in:
> User not authenticated: [LDAP: error code 32 - No Such Object]
> org.apache.manifoldcf.core.interfaces.ManifoldCFException: User not
> authenticated: [LDAP: error code 32 - No Such Object]
> at org.apache.manifoldcf.core.auth.LdapAuthenticator.
> verifyLogin(LdapAuthenticator.java:162)
> at org.apache.manifoldcf.core.auth.LdapAuthenticator.verifyUILogin(
> LdapAuthenticator.java:107)
> at org.apache.manifoldcf.ui.beans.AdminProfile.login(
> AdminProfile.java:103)
> [...]
> Caused by: javax.naming.NameNotFoundException: [LDAP: error code 32 - No
> Such Object]; remaining name ''
> at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3161)
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3082)
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2888)
>
> But if do maual ldapsearch basicaly using the same settings: e.g.:
>
> ldapsearch -x -H ldap://hdp01.local -b "dc=local" -s sub
> '(uid=authenticating_user)'
>
> Or
>
> ldapsearch -x -D "uid=authenticating_user1,ou=Users,dc=local" -W -H
> ldap://hdp01.local -b "dc=local" -s sub 'uid=authenticating_user'
>
> It basically works ok.
>
> for reference i'm running manifold 2.7, on tomcat, using postgresql for
> database and zookeeper as config repo and orchestrator.
>
> Any ideas?
>
> Best,
> T
>

ldap authentication with crawler ui

2017-07-12 Thread Theodor Carp 
Hi,
Using the below settings:


ldap://hdp01.local:389 " />




I'm getting errors like: 
ERROR 2017-07-12 15:20:32,951 (qtp1295083508-17) - User not authenticated = 
authenticating_user exception = [LDAP: error code 32 - No Such Object]
javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; 
remaining name ''
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3161)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3082)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2888)
[...]
FATAL 2017-07-12 15:20:32,956 (qtp1295083508-17) - Exception logging in: User 
not authenticated: [LDAP: error code 32 - No Such Object]
org.apache.manifoldcf.core.interfaces.ManifoldCFException: User not 
authenticated: [LDAP: error code 32 - No Such Object]
at 
org.apache.manifoldcf.core.auth.LdapAuthenticator.verifyLogin(LdapAuthenticator.java:162)
at 
org.apache.manifoldcf.core.auth.LdapAuthenticator.verifyUILogin(LdapAuthenticator.java:107)
at org.apache.manifoldcf.ui.beans.AdminProfile.login(AdminProfile.java:103)
[...]
Caused by: javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such 
Object]; remaining name ''
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3161)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3082)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2888)
But if do maual ldapsearch basicaly using the same settings: e.g.:
ldapsearch -x -H ldap://hdp01.local  -b "dc=local" -s sub 
'(uid=authenticating_user)'
Or 
ldapsearch -x -D "uid=authenticating_user1,ou=Users,dc=local" -W -H 
ldap://hdp01.local  -b "dc=local" -s sub 
'uid=authenticating_user'
It basically works ok.
for reference i'm running manifold 2.7, on tomcat, using postgresql for 
database and zookeeper as config repo and orchestrator.
Any ideas?
Best,
T

RE: ManifoldCF slow documentum indexing performance

2017-07-12 Thread Tamizh Kumaran Thamizharasan 
Thanks Karl and Fukran!!!

After pointing to different Documentum instance, the performance issue got 
resolved.
So its look like a Documentum issue.

Regards,
Tamizh Kumaran

From: Furkan KAMACI [mailto:furkankam...@gmail.com]
Sent: Thursday, July 06, 2017 3:22 PM
To: user@manifoldcf.apache.org
Cc: Sharnel Merdeck Pereira; Sundarapandian Arumaidurai Vethasigamani
Subject: Re: ManifoldCF slow documentum indexing performance

Hi Tamizh,

Set Xmx and Xms to same values for a better performance.

Kind Regards,
Furkan KAMACI

On Thu, Jul 6, 2017 at 9:10 AM, Karl Wright 
> wrote:
Hi Tamizh,

The Documentum Server Process is a thin shell around DFC and its dependencies.  
In order to get helpful suggestions, you will need to contact Documentum, I'm 
afraid.

Thanks,
Karl



On Thu, Jul 6, 2017 at 1:57 AM, Tamizh Kumaran Thamizharasan 
> 
wrote:
Thanks Karl!!

After monitoring the CPU usage of Postgresql, the agents process, and the 
documentum server process, mainly the documentum server process consumes most 
of the CPU and the agent process is the second most CPU consumer.

In documentum server run script, java heap is having value as below.
-Xmx512m -Xms32m

Is there any way to speed up the indexing through heap configuration or 
increasing hardware?
If so, Kindly share us the details.

Regards,
Tamizh Kumaran

From: Karl Wright [mailto:daddy...@gmail.com]
Sent: Wednesday, July 05, 2017 6:19 PM
To: user@manifoldcf.apache.org
Cc: Sharnel Merdeck Pereira; Sundarapandian Arumaidurai Vethasigamani
Subject: Re: ManifoldCF slow documentum indexing performance

Hi Tamizh,

The likely culprit is Documentum itself.  In my experience it can be quite 
slow, depending on how it is configured.  But you can confirm that by 
monitoring the CPU usage of Postgresql, the agents process, and the documentum 
server process.  If none of these are CPU bound, then Documentum itself is the 
problem.

Thanks,
Karl


On Wed, Jul 5, 2017 at 8:24 AM, Tamizh Kumaran Thamizharasan 
> 
wrote:
Hi Team,

The postgresql 9.2, solr 5.3.2 and manifoldcf 2.7.1 are installed on the same 
linux box. The documentum server sits on a different linux box. The indexing 
performance is slow(approx 1000 doc per hour) with the documentum crawler. The 
used properties files is as below for reference


  
  
  
  
  http://org.apache.manifoldcf.co>nnectorsconfigurationfile"
 value="../connectors.xml"/>
  
  http://org.apache.manifoldcf.fi>leresources" 
value="../file-resources"/>
  
  
  
  
  
  http://org.apache.manifoldcf.database.name>"
 value="manifoldcf"/>
  
  
  
  http://org.apache.manifoldcf.cr>awler.threads" 
value="15"/>
  http://org.apache.manifoldcf.cr>awler.repository.store_history"
 value="false"/>

  
  

  
  
  
  


Initially the org.apache.manifoldcf.crawler.threads is setup with 45 and the 
observation is it taking a long time gap between each batch of 45 documents 
during processing.
Can you please point out any changes/recommendations that will speed up the 
indexing.

Regards,
Tamizh Kumaran Thamizharasan