I see.
Starting another process somehow it turns out to the same point
DEBUG 2018-08-10T10:31:08,336 (Thread-38685) - Cancelling request execution
No one is pushing the button through the Web User Interface, so I guess I
have to look at the source code.
El vie., 10 ago. 2018 a las 10:55,
There is no configuration I know of that is related to this.
The connection manager being shut down occurs when the agents process is
being shut down or killed. This is not something that MCF will do except
when told to.
Karl
On Fri, Aug 10, 2018 at 4:28 AM Gustavo Beneitez
wrote:
> Hi
Hi again Karl,
I've been further investigating this issue since today it happened again. I
was able to capture the instant when jobs stopped, It seems they receive an
abort command.
I then investigate the logs (they are centralised with Kibana) and the most
strange thing I can see is this log:
Yes, you are right, maybe I can execute OPTIMIZE queries if job fails
again, let's just cross fingers.
El jue., 9 ago. 2018 a las 12:28, Karl Wright ()
escribió:
> There is no autovacuum for MySQL. MySQL apparently does dead tuple
> cleanup as it goes.
>
> Karl
>
> On Thu, Aug 9, 2018 at 6:13
There is no autovacuum for MySQL. MySQL apparently does dead tuple cleanup
as it goes.
Karl
On Thu, Aug 9, 2018 at 6:13 AM Gustavo Beneitez
wrote:
> Hi,
>
> looking at the manifoldCF pom I can see
>
> 1.0.4-SNAPSHOT
>
> I'm not aware of any change in database, in fact ours is MySQL, I don't
>
Hi,
looking at the manifoldCF pom I can see
1.0.4-SNAPSHOT
I'm not aware of any change in database, in fact ours is MySQL, I don't
know if "auto_vacuum" property is present in MySQL installation.
Thanks!
El jue., 9 ago. 2018 a las 11:19, msaunier () escribió:
> Hi Gustavo,
>
>
>
> What is
Hi Gustavo,
What is your ManifoldCF version?
Do you have disabled auto_vacuum on your SQL configuration?
Maxence,
De : Gustavo Beneitez [mailto:gustavo.benei...@gmail.com]
Envoyé : jeudi 9 août 2018 11:17
À : user@manifoldcf.apache.org
Objet : crawl interrupted
Hi all,
