You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@manifoldcf.apache.org by "Sivakoti, Nikhilesh" <ni...@capgemini.com> on 2018/11/24 12:45:01 UTC
Manifold fails with alfresco | pipeline exception
Hi Team,
We have been trying to use ManifoldCF with our Alfresco. We have customized the manifold alfresco connector and manifold elastic search connector as per our needs.
We have added the authentication mechanism in elastic search connector to connect to the QA servers. But when we try to execute a job we are getting the below errors.
HTTP code = 400, Response = {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"pipeline with id [null] does not exist"}],"type":"illegal_argument_exception","reason":"pipeline with id [null] does not exist"},"status":400}
Could you please provide any support on thiss?
Thanks,
Nikhilesh
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: Manifold fails with alfresco | pipeline exception
Posted by Karl Wright <da...@gmail.com>.
Hi Nikhilesh,
What you see is perfectly normal. Until the job is fully aborted, you
won't have any action buttons you can click.
As for why it takes a while: all documents must be updated so that aren't
able to be queued, and if there are a lot of documents in a job, that can
take a while. Alternatively, you might have shut the agents process down;
without the agents process running, documents are not updated in any manner.
Thanks,
Karl
On Sat, Nov 24, 2018 at 12:33 PM Sivakoti, Nikhilesh <
nikhilesh.sivakoti@capgemini.com> wrote:
> Thank you Karl.
>
>
>
> Could you please guide me on the below issue? Aborting the job results in
> missing the action buttons.
>
> This issue persists even after restarting the server.
>
>
>
>
>
>
>
> _______________________________________________________________________
>
> [image: Email_CBE.gif]*Nikhilesh Sivakoti*
>
> Senior Consultant | I&D ECM
>
>
>
> Capgemini India | Bangalore
>
> Tel.: +8099062 – Mob.: + 91 81236 25125
>
> www.capgemini.com
>
>
>
> *People matter, results count.*
>
> _______________________________________________________________________
>
> [image: 50years]
>
>
>
> *Connect with Capgemini:*
> [image: Picto_Blog]
> <http://www.capgemini.com/insights-and-resources/blogs>[image:
> Picto_Twitter] <http://www.twitter.com/capgemini>[image: Picto_Facebook]
> <http://www.facebook.com/capgemini>[image: Picto_LinkedIn]
> <http://www.linkedin.com/company/capgemini>[image: Picto_Slideshare]
> <http://www.slideshare.net/capgemini>[image: Picto_YouTube]
> <http://www.youtube.com/capgeminimedia>
>
>
>
>
>
>
>
>
>
> P Please consider the environment and do not print this email unless
> absolutely necessary.
>
> Capgemini encourages environmental awareness.
>
>
>
> *From:* Karl Wright [mailto:daddywri@gmail.com]
> *Sent:* Saturday, November 24, 2018 7:11 PM
> *To:* user@manifoldcf.apache.org
> *Cc:* Steph van Schalkwyk
> *Subject:* Re: Manifold fails with alfresco | pipeline exception
>
>
>
> Here's the list of all ES connector tickets. Note that some of these have
> been resolved.
>
>
>
>
> https://issues.apache.org/jira/browse/CONNECTORS-1488?jql=project%20%3D%20CONNECTORS%20AND%20text%20~%20elasticsearch
>
>
>
> Karl
>
>
>
>
>
> On Sat, Nov 24, 2018 at 8:00 AM Sivakoti, Nikhilesh <
> nikhilesh.sivakoti@capgemini.com> wrote:
>
> Hi Karl,
>
>
>
> I have found this error in the manifold crawler UI under simple history
> report. Please find screenshot below.
>
>
>
> We are using elastic search version 5.6.0.
>
>
>
> Could you please provide the JIRA link for these kind of issues?
>
> _______________________________________________________________________
>
> [image: Email_CBE.gif]*Nikhilesh Sivakoti*
>
> Senior Consultant | I&D ECM
>
>
>
> Capgemini India | Bangalore
>
> Tel.: +8099062 – Mob.: + 91 81236 25125
>
> www.capgemini.com
>
>
>
> *People matter, results count.*
>
> _______________________________________________________________________
>
> [image: 50years]
>
>
>
> *Connect with Capgemini:*
> [image: Picto_Blog]
> <http://www.capgemini.com/insights-and-resources/blogs>[image:
> Picto_Twitter] <http://www.twitter.com/capgemini>[image: Picto_Facebook]
> <http://www.facebook.com/capgemini>[image: Picto_LinkedIn]
> <http://www.linkedin.com/company/capgemini>[image: Picto_Slideshare]
> <http://www.slideshare.net/capgemini>[image: Picto_YouTube]
> <http://www.youtube.com/capgeminimedia>
>
>
>
>
>
>
>
>
>
> P Please consider the environment and do not print this email unless
> absolutely necessary.
>
> Capgemini encourages environmental awareness.
>
>
>
> *From:* Karl Wright [mailto:daddywri@gmail.com]
> *Sent:* Saturday, November 24, 2018 6:21 PM
> *To:* user@manifoldcf.apache.org
> *Cc:* Steph van Schalkwyk
> *Subject:* Re: Manifold fails with alfresco | pipeline exception
>
>
>
> Hi Nikhilesh,
>
>
>
> Where are you seeing these errors? They sound like ElasticSearch errors
> to me; it is complaining that an null or empty-string pipeline name is
> being specified somehow. Can you tell me what version of ElasticSearch you
> are using?
>
> We have outstanding tickets for updating the ElasticSearch connector,
> because the public API for ElasticSearch changes very rapidly and therefore
> it may be out of date. Please check the JIRA queue to find the status of
> issues like this.
>
>
>
> Thanks,
>
> Karl
>
>
>
>
>
>
>
> On Sat, Nov 24, 2018 at 7:45 AM Sivakoti, Nikhilesh <
> nikhilesh.sivakoti@capgemini.com> wrote:
>
> Hi Team,
>
>
>
> We have been trying to use ManifoldCF with our Alfresco. We have
> customized the manifold alfresco connector and manifold elastic search
> connector as per our needs.
>
> We have added the authentication mechanism in elastic search connector to
> connect to the QA servers. But when we try to execute a job we are getting
> the below errors.
>
>
>
> HTTP code = 400, Response =
> {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"pipeline
> with id [null] does not
> exist"}],"type":"illegal_argument_exception","reason":"pipeline with id
> [null] does not exist"},"status":400}
>
>
>
> Could you please provide any support on thiss?
>
>
>
>
>
> Thanks,
>
> Nikhilesh
>
> This message contains information that may be privileged or confidential
> and is the property of the Capgemini Group. It is intended only for the
> person to whom it is addressed. If you are not the intended recipient, you
> are not authorized to read, print, retain, copy, disseminate, distribute,
> or use this message or any part thereof. If you receive this message in
> error, please notify the sender immediately and delete all copies of this
> message.
>
>
RE: Manifold fails with alfresco | pipeline exception
Posted by "Sivakoti, Nikhilesh" <ni...@capgemini.com>.
Thank you Karl.
Could you please guide me on the below issue? Aborting the job results in missing the action buttons.
This issue persists even after restarting the server.
[cid:image001.png@01D48449.E83BCFE0]
_______________________________________________________________________
[Email_CBE.gif]Nikhilesh Sivakoti
Senior Consultant | I&D ECM
Capgemini India | Bangalore
Tel.: +8099062 – Mob.: + 91 81236 25125
www.capgemini.com<http://www.capgemini.com/>
People matter, results count.
_______________________________________________________________________
[50years]
Connect with Capgemini:
[Picto_Blog]<http://www.capgemini.com/insights-and-resources/blogs>[Picto_Twitter]<http://www.twitter.com/capgemini>[Picto_Facebook]<http://www.facebook.com/capgemini>[Picto_LinkedIn]<http://www.linkedin.com/company/capgemini>[Picto_Slideshare]<http://www.slideshare.net/capgemini>[Picto_YouTube]<http://www.youtube.com/capgeminimedia>
P Please consider the environment and do not print this email unless absolutely necessary.
Capgemini encourages environmental awareness.
From: Karl Wright [mailto:daddywri@gmail.com]
Sent: Saturday, November 24, 2018 7:11 PM
To: user@manifoldcf.apache.org
Cc: Steph van Schalkwyk
Subject: Re: Manifold fails with alfresco | pipeline exception
Here's the list of all ES connector tickets. Note that some of these have been resolved.
https://issues.apache.org/jira/browse/CONNECTORS-1488?jql=project%20%3D%20CONNECTORS%20AND%20text%20~%20elasticsearch
Karl
On Sat, Nov 24, 2018 at 8:00 AM Sivakoti, Nikhilesh <ni...@capgemini.com>> wrote:
Hi Karl,
I have found this error in the manifold crawler UI under simple history report. Please find screenshot below.
[cid:image011.jpg@01D48423.AD114920]
We are using elastic search version 5.6.0.
Could you please provide the JIRA link for these kind of issues?
_______________________________________________________________________
[Email_CBE.gif]Nikhilesh Sivakoti
Senior Consultant | I&D ECM
Capgemini India | Bangalore
Tel.: +8099062 – Mob.: + 91 81236 25125
www.capgemini.com<http://www.capgemini.com/>
People matter, results count.
_______________________________________________________________________
[50years]
Connect with Capgemini:
[Picto_Blog]<http://www.capgemini.com/insights-and-resources/blogs>[Picto_Twitter]<http://www.twitter.com/capgemini>[Picto_Facebook]<http://www.facebook.com/capgemini>[Picto_LinkedIn]<http://www.linkedin.com/company/capgemini>[Picto_Slideshare]<http://www.slideshare.net/capgemini>[Picto_YouTube]<http://www.youtube.com/capgeminimedia>
P Please consider the environment and do not print this email unless absolutely necessary.
Capgemini encourages environmental awareness.
From: Karl Wright [mailto:daddywri@gmail.com<ma...@gmail.com>]
Sent: Saturday, November 24, 2018 6:21 PM
To: user@manifoldcf.apache.org<ma...@manifoldcf.apache.org>
Cc: Steph van Schalkwyk
Subject: Re: Manifold fails with alfresco | pipeline exception
Hi Nikhilesh,
Where are you seeing these errors? They sound like ElasticSearch errors to me; it is complaining that an null or empty-string pipeline name is being specified somehow. Can you tell me what version of ElasticSearch you are using?
We have outstanding tickets for updating the ElasticSearch connector, because the public API for ElasticSearch changes very rapidly and therefore it may be out of date. Please check the JIRA queue to find the status of issues like this.
Thanks,
Karl
On Sat, Nov 24, 2018 at 7:45 AM Sivakoti, Nikhilesh <ni...@capgemini.com>> wrote:
Hi Team,
We have been trying to use ManifoldCF with our Alfresco. We have customized the manifold alfresco connector and manifold elastic search connector as per our needs.
We have added the authentication mechanism in elastic search connector to connect to the QA servers. But when we try to execute a job we are getting the below errors.
HTTP code = 400, Response = {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"pipeline with id [null] does not exist"}],"type":"illegal_argument_exception","reason":"pipeline with id [null] does not exist"},"status":400}
Could you please provide any support on thiss?
Thanks,
Nikhilesh
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: Manifold fails with alfresco | pipeline exception
Posted by Karl Wright <da...@gmail.com>.
Here's the list of all ES connector tickets. Note that some of these have
been resolved.
https://issues.apache.org/jira/browse/CONNECTORS-1488?jql=project%20%3D%20CONNECTORS%20AND%20text%20~%20elasticsearch
Karl
On Sat, Nov 24, 2018 at 8:00 AM Sivakoti, Nikhilesh <
nikhilesh.sivakoti@capgemini.com> wrote:
> Hi Karl,
>
>
>
> I have found this error in the manifold crawler UI under simple history
> report. Please find screenshot below.
>
>
>
> We are using elastic search version 5.6.0.
>
>
>
> Could you please provide the JIRA link for these kind of issues?
>
> _______________________________________________________________________
>
> [image: Email_CBE.gif]*Nikhilesh Sivakoti*
>
> Senior Consultant | I&D ECM
>
>
>
> Capgemini India | Bangalore
>
> Tel.: +8099062 – Mob.: + 91 81236 25125
>
> www.capgemini.com
>
>
>
> *People matter, results count.*
>
> _______________________________________________________________________
>
> [image: 50years]
>
>
>
> *Connect with Capgemini:*
> [image: Picto_Blog]
> <http://www.capgemini.com/insights-and-resources/blogs>[image:
> Picto_Twitter] <http://www.twitter.com/capgemini>[image: Picto_Facebook]
> <http://www.facebook.com/capgemini>[image: Picto_LinkedIn]
> <http://www.linkedin.com/company/capgemini>[image: Picto_Slideshare]
> <http://www.slideshare.net/capgemini>[image: Picto_YouTube]
> <http://www.youtube.com/capgeminimedia>
>
>
>
>
>
>
>
>
>
> P Please consider the environment and do not print this email unless
> absolutely necessary.
>
> Capgemini encourages environmental awareness.
>
>
>
> *From:* Karl Wright [mailto:daddywri@gmail.com]
> *Sent:* Saturday, November 24, 2018 6:21 PM
> *To:* user@manifoldcf.apache.org
> *Cc:* Steph van Schalkwyk
> *Subject:* Re: Manifold fails with alfresco | pipeline exception
>
>
>
> Hi Nikhilesh,
>
>
>
> Where are you seeing these errors? They sound like ElasticSearch errors
> to me; it is complaining that an null or empty-string pipeline name is
> being specified somehow. Can you tell me what version of ElasticSearch you
> are using?
>
> We have outstanding tickets for updating the ElasticSearch connector,
> because the public API for ElasticSearch changes very rapidly and therefore
> it may be out of date. Please check the JIRA queue to find the status of
> issues like this.
>
>
>
> Thanks,
>
> Karl
>
>
>
>
>
>
>
> On Sat, Nov 24, 2018 at 7:45 AM Sivakoti, Nikhilesh <
> nikhilesh.sivakoti@capgemini.com> wrote:
>
> Hi Team,
>
>
>
> We have been trying to use ManifoldCF with our Alfresco. We have
> customized the manifold alfresco connector and manifold elastic search
> connector as per our needs.
>
> We have added the authentication mechanism in elastic search connector to
> connect to the QA servers. But when we try to execute a job we are getting
> the below errors.
>
>
>
> HTTP code = 400, Response =
> {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"pipeline
> with id [null] does not
> exist"}],"type":"illegal_argument_exception","reason":"pipeline with id
> [null] does not exist"},"status":400}
>
>
>
> Could you please provide any support on thiss?
>
>
>
>
>
> Thanks,
>
> Nikhilesh
>
> This message contains information that may be privileged or confidential
> and is the property of the Capgemini Group. It is intended only for the
> person to whom it is addressed. If you are not the intended recipient, you
> are not authorized to read, print, retain, copy, disseminate, distribute,
> or use this message or any part thereof. If you receive this message in
> error, please notify the sender immediately and delete all copies of this
> message.
>
>
RE: Manifold fails with alfresco | pipeline exception
Posted by "Sivakoti, Nikhilesh" <ni...@capgemini.com>.
Hi Karl,
I have found this error in the manifold crawler UI under simple history report. Please find screenshot below.
[cid:image011.jpg@01D48423.AD114920]
We are using elastic search version 5.6.0.
Could you please provide the JIRA link for these kind of issues?
_______________________________________________________________________
[Email_CBE.gif]Nikhilesh Sivakoti
Senior Consultant | I&D ECM
Capgemini India | Bangalore
Tel.: +8099062 – Mob.: + 91 81236 25125
www.capgemini.com<http://www.capgemini.com/>
People matter, results count.
_______________________________________________________________________
[50years]
Connect with Capgemini:
[Picto_Blog]<http://www.capgemini.com/insights-and-resources/blogs>[Picto_Twitter]<http://www.twitter.com/capgemini>[Picto_Facebook]<http://www.facebook.com/capgemini>[Picto_LinkedIn]<http://www.linkedin.com/company/capgemini>[Picto_Slideshare]<http://www.slideshare.net/capgemini>[Picto_YouTube]<http://www.youtube.com/capgeminimedia>
P Please consider the environment and do not print this email unless absolutely necessary.
Capgemini encourages environmental awareness.
From: Karl Wright [mailto:daddywri@gmail.com]
Sent: Saturday, November 24, 2018 6:21 PM
To: user@manifoldcf.apache.org
Cc: Steph van Schalkwyk
Subject: Re: Manifold fails with alfresco | pipeline exception
Hi Nikhilesh,
Where are you seeing these errors? They sound like ElasticSearch errors to me; it is complaining that an null or empty-string pipeline name is being specified somehow. Can you tell me what version of ElasticSearch you are using?
We have outstanding tickets for updating the ElasticSearch connector, because the public API for ElasticSearch changes very rapidly and therefore it may be out of date. Please check the JIRA queue to find the status of issues like this.
Thanks,
Karl
On Sat, Nov 24, 2018 at 7:45 AM Sivakoti, Nikhilesh <ni...@capgemini.com>> wrote:
Hi Team,
We have been trying to use ManifoldCF with our Alfresco. We have customized the manifold alfresco connector and manifold elastic search connector as per our needs.
We have added the authentication mechanism in elastic search connector to connect to the QA servers. But when we try to execute a job we are getting the below errors.
HTTP code = 400, Response = {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"pipeline with id [null] does not exist"}],"type":"illegal_argument_exception","reason":"pipeline with id [null] does not exist"},"status":400}
Could you please provide any support on thiss?
Thanks,
Nikhilesh
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: Manifold fails with alfresco | pipeline exception
Posted by Karl Wright <da...@gmail.com>.
Hi Nikhilesh,
Where are you seeing these errors? They sound like ElasticSearch errors to
me; it is complaining that an null or empty-string pipeline name is being
specified somehow. Can you tell me what version of ElasticSearch you are
using?
We have outstanding tickets for updating the ElasticSearch connector,
because the public API for ElasticSearch changes very rapidly and therefore
it may be out of date. Please check the JIRA queue to find the status of
issues like this.
Thanks,
Karl
On Sat, Nov 24, 2018 at 7:45 AM Sivakoti, Nikhilesh <
nikhilesh.sivakoti@capgemini.com> wrote:
> Hi Team,
>
>
>
> We have been trying to use ManifoldCF with our Alfresco. We have
> customized the manifold alfresco connector and manifold elastic search
> connector as per our needs.
>
> We have added the authentication mechanism in elastic search connector to
> connect to the QA servers. But when we try to execute a job we are getting
> the below errors.
>
>
>
> HTTP code = 400, Response =
> {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"pipeline
> with id [null] does not
> exist"}],"type":"illegal_argument_exception","reason":"pipeline with id
> [null] does not exist"},"status":400}
>
>
>
> Could you please provide any support on thiss?
>
>
>
>
>
> Thanks,
>
> Nikhilesh
>
> This message contains information that may be privileged or confidential
> and is the property of the Capgemini Group. It is intended only for the
> person to whom it is addressed. If you are not the intended recipient, you
> are not authorized to read, print, retain, copy, disseminate, distribute,
> or use this message or any part thereof. If you receive this message in
> error, please notify the sender immediately and delete all copies of this
> message.
>