Hi Community,
I am trying to boot into our ARIS Connect is down. After trying to restart the runnables in the ACC console.
*The runnable named zoo_m is permanently in FAILED state.
I have already checked some similar issues here in the community but no solution I found has worked, could you please tell me what is causing this problem and how to solve it?
Thank you!
Hello Rosario,
from your screen I take it you are still running Aris 10.0.18 which has a known bug of zookeeper, cf. SAG support knowlegde base article "Zookeeper does not start anymore"
Symptom: after a shutdown of your server or ARIS Agent Service or stopping runnables
work_zoo_m\log\system.out.log shows the following:
Unexpected exception, exiting abnormally
java.io.EOFException: null
Solution:
Reason: In SR18 zookeeper (or a faulty log4j2 ?) create 0 KB logfiles instead of cleanly rotating old logs on shutdown. This can happen any time again, so I recommend updating to a current release.
Regards, Martin
Martin Schröder on
Hello Rosario,
from your screen I take it you are still running Aris 10.0.18 which has a known bug of zookeeper, cf. SAG support knowlegde base article "Zookeeper does not start anymore"
Symptom: after a shutdown of your server or ARIS Agent Service or stopping runnables
work_zoo_m\log\system.out.log shows the following:
Unexpected exception, exiting abnormally
java.io.EOFException: null
Solution:
(stop usually does not work on FAILED runnables)
should invoke startall runnables if they are set to start automatically
Reason: In SR18 zookeeper (or a faulty log4j2 ?) create 0 KB logfiles instead of cleanly rotating old logs on shutdown. This can happen any time again, so I recommend updating to a current release.
Regards, Martin