-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ignite daemon dead or terracotta process dead #34
Comments
For example, this one: https://dev.azure.com/TerracottaCI/terracotta/_build/results?buildId=3693&view=logs&j=8dbdaf4e-75b0-549d-49ae-570ac1daf5bb&t=da6f2a7a-ce43-5148-4474-fcade0333e00
|
@saurabhagas also: |
The problem comes from Azure: The root cause is displayed in the console (therefore Angela can not know it) and the console output is separated in Azure If you look at the stack trace:
The Terracotta server couldn't start because another one is started using the same port, and it shut down. The STARTED stage couldn't then never be reached and Angela reported it. I've added the expected condition to the Angela exception so next time it helps a bit on understanding what stage should be happening. I've opened 2 tickets to propose some user experience improvement related to this ticket: |
On the tc-platform build (https://github.com/Terracotta-OSS/terracotta-platform/pull/) with Azure, we often run into build failures caused by the ignite process failing (dead), or tc nodes not found by the ignite process.
These are cryptic errors hard to troubleshoot since there is n oeasy way to pick up the logs in Azure.
So I am opeeing an issue here to make you all 3 aware that there are some random build failures because of the angela process handling mechanism.
@akomakom : I don't if it is possible in Azure to "pin" a build that failed and look at the content, logs, etc.
We could put everything in trace mode but it won't help if we do not have access of the workspace of a failed build.
I am unable to reproduce locally... (Azure only issue perhaps... ?)
The text was updated successfully, but these errors were encountered: