how to enable useful debugging info for jenkin slave running as a service on windows...

[JP]

I have a jenkins agent / slave running as a windows service,  it is observed that once in a while after reboot of the machine, jenkin slave service don't come up. I have looked at eventlog and it says jenkin service is timing out. I want to debug why timeouts are happening. 

Can someone point to me a link which will allow me to enable useful logging / debugging info so that next time I can see more info than just timeout.

Thanks

JP

[Jeff Thompson]

Unfortunately, it's a challenging exercise, hunting down why something like this is occurring. Typically, it has something to do with local system, network, environment, or Jenkins configuration. It may have something to do with how the agent is configured.

The best documentation on agent (Remoting) logging I can remember is at https://github.com/jenkinsci/remoting/blob/master/docs/logging.md . It can be a little hard to understand and configure but I've successfully used it before to configure logging in the detail and areas I needed.

It sounds like you will need to examine what is happening on the master and the agent during this time. Your issue sounds pretty weird. In my experience, agent-initiated connections will keep retrying, so a timeout is only a temporary delay.

Jeff Thompson

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9513af77-8a40-42cc-9f6d-b183bf63af8f%40googlegroups.com.

[JP]

Thanks Jeff. I was able to create a logging configuration file and was able to start slave with -Djava.util.logging.config.file=C:\jenkins\jenkins-slave.logging.properties. Now I am able to see lot more logging. Thanks for the pointer.

On Monday, March 23, 2020 at 8:33:43 AM UTC-7, Jeff Thompson wrote:

Unfortunately, it's a challenging exercise, hunting down why something like this is occurring. Typically, it has something to do with local system, network, environment, or Jenkins configuration. It may have something to do with how the agent is configured.

The best documentation on agent (Remoting) logging I can remember is at https://github.com/jenkinsci/remoting/blob/master/docs/logging.md . It can be a little hard to understand and configure but I've successfully used it before to configure logging in the detail and areas I needed.

It sounds like you will need to examine what is happening on the master and the agent during this time. Your issue sounds pretty weird. In my experience, agent-initiated connections will keep retrying, so a timeout is only a temporary delay.

Jeff Thompson

On 3/21/20 12:53 PM, JP wrote:

I have a jenkins agent / slave running as a windows service,  it is observed that once in a while after reboot of the machine, jenkin slave service don't come up. I have looked at eventlog and it says jenkin service is timing out. I want to debug why timeouts are happening. 

Can someone point to me a link which will allow me to enable useful logging / debugging info so that next time I can see more info than just timeout.

Thanks

JP

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkins...@googlegroups.com.