I think to have those updated settings applied correctly we need to disconnect and launch those agents again instead of just bringing those offline and online, just checking to make sure that we are not missing anything there.
On Wednesday, September 23, 2020 at 12:01:46 PM UTC-5 kuisat...@gmail.com wrote: > How much memory those agents have? you set "-Xmx64g -Xms64g" for the > remoting process (not for builds) you agent has to have more than 64GB of > RAM to run any build on it, you grab 64GB only for the remoting process, > and this RAM should be enough to run you builds. The remoting agent usually > does not need more than 256-512MB, this keeps the rest of your agent memory > for builds, agents rarely need JVM options to tune the memory the default > configuration is enough, the only case I will recommend to pass JVM option > is to limit the memory of the agent process. > > the jvmOptions field should work is tested on unit test, if not is and > issue, Which version of Jenksin and ssh build agents plugin do your use? > > El miércoles, 23 de septiembre de 2020 a las 1:21:28 UTC+2, > timb...@gmail.com escribió: > >> I'm using ssh-slaves-plugin >> <https://github.com/jenkinsci/ssh-slaves-plugin> to configure and launch >> 2 ssh agents, and I've specified several java options in these agents' >> config (see photo and text list below), but when these agents are launched, >> the agents' log still shows empty jvmOptions in the ssh launcher call. >> Agent Log excerpt: >> >> SSHLauncher{host='jenkins-testing-agent-1', port=22, >> credentialsId='jenkins_user_on_linux_agent', *jvmOptions=''*, >> javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', >> launchTimeoutSeconds=30, maxNumRetries=20, retryWaitTime=10, >> sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.NonVerifyingKeyVerificationStrategy, >> >> tcpNoDelay=true, trackCredentials=true} >> [09/22/20 15:56:12] [SSH] Opening SSH connection to >> jenkins-testing-agent-1:22. >> [09/22/20 15:56:16] [SSH] WARNING: SSH Host Keys are not being verified. >> Man-in-the-middle attacks may be possible against this connection. >> [09/22/20 15:56:16] [SSH] Authentication successful. >> [09/22/20 15:56:16] [SSH] The remote user's environment is: >> BASH=/usr/bin/bash >> . >> . >> . >> [SSH] java -version returned 11.0.8. >> [09/22/20 15:56:16] [SSH] Starting sftp client. [09/22/20 15:56:16] [SSH] >> Copying latest remoting.jar... Source agent hash is >> 0146753DA5ED62106734D59722B1FA2C. Installed agent hash is >> 0146753DA5ED62106734D59722B1FA2C Verified agent jar. No update is >> necessary. Expanded the channel window size to 4MB >> [09/22/20 15:56:16] [SSH] Starting agent process: cd >> "/home/jenkins/.jenkins" && java -jar remoting.jar -workDir >> /home/jenkins/.jenkins -jar-cache /home/jenkins/.jenkins/remoting/jarCache >> Sep 22, 2020 3:56:17 PM org.jenkinsci.remoting.engine.WorkDirManager >> initializeWorkDir INFO: Using /home/jenkins/.jenkins/remoting as a remoting >> work directory Sep 22, 2020 3:56:17 PM >> org.jenkinsci.remoting.engine.WorkDirManager setupLogging INFO: Both error >> and output logs will be printed to /home/jenkins/.jenkins/remoting >> <===[JENKINS REMOTING CAPACITY]===>channel started Remoting version: 4.2 >> This is a Unix agent WARNING: An illegal reflective access operation has >> occurred WARNING: Illegal reflective access by >> jenkins.slaves.StandardOutputSwapper$ChannelSwapper to constructor >> java.io.FileDescriptor(int) WARNING: Please consider reporting this to the >> maintainers of jenkins.slaves.StandardOutputSwapper$ChannelSwapper WARNING: >> Use --illegal-access=warn to enable warnings of further illegal reflective >> access operations WARNING: All illegal access operations will be denied in >> a future release Evacuated stdout Agent successfully connected and online >> >> >> [image: jenkins-ssh-agent-config.PNG] >> >> This is the full text in the "JVM Options" field for >> jenkins-testing-agent-1 and 2: >> >> -Dhudson.slaves.WorkspaceList=- >> -Dorg.apache.commons.jelly.tags.fmt.timeZone=America/Vancouver -Xmx64g >> -Xms64g -XX:+AlwaysPreTouch -XX:+HeapDumpOnOutOfMemoryError >> -XX:HeapDumpPath=/home/jenkins/.jenkins/support -XX:+UseG1GC >> -XX:+UseStringDeduplication -XX:+ParallelRefProcEnabled >> -XX:+DisableExplicitGC -XX:+UnlockDiagnosticVMOptions >> -XX:+UnlockExperimentalVMOptions -verbose:gc >> -Xlog:gc:/home/jenkins/.jenkins/support/gc-%t.log -XX:+PrintGC >> -XX:+PrintGCDetails -XX:ErrorFile=/hs_err_%p.log -XX:+LogVMOutput >> -XX:LogFile=/home/jenkins/.jenkins/support/jvm.log >> >> I am having intermittent catastrophic failures of these agent machines >> during builds and am trying to properly configure java settings per >> Cloudbees best practices, but I cannot seem to get off the ground here. >> Another problem in my agents that's probably related is that the agent-side >> (remoting) logs are all zero bytes. >> >> Thanks for your help. >> > -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3e939ac8-38d3-4717-80b8-b7ff9f1caebfn%40googlegroups.com.
