You can configure logging in the Agent when you launch it. The issue you describe used to be an OOM. If you can install something to monitor the memory usage of the Agents and send that data to somewhere you can review it, you will probably catch the problem.
https://github.com/jenkinsci/remoting/blob/master/docs/logging.md https://docs.cloudbees.com/docs/cloudbees-ci-kb/latest/client-and-managed-controllers/configure-loggers-for-jenkins-agents On Tuesday, November 12, 2024 at 11:48:46 PM UTC+1 jgl...@cloudbees.com wrote: > On Tue, Nov 12, 2024 at 10:14 AM Michael Carter <mikeyca...@gmail.com> > wrote: > >> What class or how would I send info to the remoting.jar log on the remote >> agent? >> > > Do you mean the system error of the agent process? (As opposed to the > “agent launch log”, which is collected on the controller.) You could just > write a `MasterToSlaveCallable` which does something with > `java.util.logging`. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/3a620756-968a-4912-850c-a3da8caa703en%40googlegroups.com.
