El El dom, 16 feb 2020 a las 14:48, Vincent Massol
escribió:
> This is why I've been asking from the beginning if it's normal :) Usually
> when there's a stack trace it's not really normal. But it happens so
> frequently that the only explanation I can think of is that it's the normal
> behavior
Hi Ivan,
> so the only difference is the stack trace of the exception, the log level
> is the same.
Is it possible that you misunderstood the data at
https://up1.xwikisas.com/#vI0VAypIpe_tD9LrQRTdMA ? :)
As is mentioned there, ALL of the lines are the same as the ones at the top
(ie they
> El 16 feb 2020, a las 14:15, Vincent Massol escribió:
>
> In both cases it"ll be reported as INFO in the logs too. Right?
It seems like, I didn’t noticed that the exception is also a INFO messages, so
the only difference is the stack trace of the exception, the log level is the
same.
--
>
> After seen the log I understand you are asking for the INFO messages that
> inform that a Docker agent is disconnected, IIRC those messages are normal
> they only inform about the Docker agent status,
>
>
Thanks for your reply. Let me make sure I understand. So the Docker Cloud
plugin will
After seen the log I understand you are asking for the INFO messages that
inform that a Docker agent is disconnected, IIRC those messages are normal they
only inform about the Docker agent status, you can change the verbose level of
the Java package on logs configuration to omit those type of me
Thanks Ivan. We're not using SHH agents but Docker Cloud (the agents are
provisioned on the fly as docker containers).
I was indeed looking for how to turn on some debugging on the agent side
but I couldn't find anything. Also the agent docker container is removed
once the job is finished so it
Pingthread and some monitoring stuff run every 4 min, I think that the
disconnections happens before that process but because there is not activity on
this agents is not detected until the pingthread passes. So I guess you have
half closed connections, I mean, the agent closes the convention but
I've seen those stack traces with some other Cloud Node providers in
Jenkins.
Not sure if that's an implementation within the Jenkins core or the
docker-plugin itself or some specific design.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
Hi guys.
Is anyone also having problems with "Disconnected computer for node"
happening all the time, resulting in jenkins master killing agent nodes?
We're getting that all the time it seems for https://ci.xwiki.org.
See https://up1.xwikisas.com/#vI0VAypIpe_tD9LrQRTdMA
2020-02-14 09:10:59.0
