https://www.freebsd.org/cgi/man.cgi?sshd_config(5)
https://www.freebsd.org/cgi/man.cgi?ssh_config(5)
Also, check you follow the best practices to configure your SSH agents and enable SSH verbose log output in your service (see https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/TROUBLESHOOTING.md)
When I saw something like this in the past, it was because the process was running out of resources. Specifically when running SpotBugs, I got out-of-memory errors. I had to modify the pom to allocate more memory.
I recommend ensuring your build runs normally on the agent without the additional complexities of the Jenkins environment. This might show where additional resources are needed. If that all passes, then continue on to the additional troubleshooting steps involving the Jenkins controller and agent.
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/030aced0-ba6e-4012-a60a-58208d350544n%40googlegroups.com.
When I saw something like this in the past, it was because the process was running out of resources. Specifically when running SpotBugs, I got out-of-memory errors. I had to modify the pom to allocate more memory.
>I have 2 different kind of jenkins agents.>1. java web start>2. ssh>If the memory was issue then wouldn't it fail on both cases?Not necessarily, starting by the point that are different ways to establish the connection, the JNLP agents could not update the remoting jar file (depends on your configurations), so you can be running different versions of remoting. I agree with Jeff looks like an OOM issue, review my comments at https://groups.google.com/g/jenkinsci-users/c/nD3s06hSUXE/m/BQKk5GSYBwAJ my recommendation is to fix the mem for the remoting process to 1024M (-Xmx1024m -Xms1024m) see if the issue disappear or change, if disappear, you would have to adjust the remoting process memory to the right one between 256M-1024M, to use 512M usually is safe a not too much (but depends on your agents' memory we do not know how much they have)
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/nD3s06hSUXE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/615a4333-587c-4ea2-a11f-fea45fe38a56n%40googlegroups.com.
ERROR: Step ‘[Deprecated] Scan workspace for open tasks’ aborted due to exception: java.io.StreamCorruptedException: invalid type code: 6D ... at hudson.plugins.tasks.TasksPublisher.perform(TasksPublisher.java:182) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:69) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:298) at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:112) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1919) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428)
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/32d22541-1143-4c96-be3b-23c10bb5619cn%40googlegroups.com.
I agree with Ivan. There are differences, sometimes subtle, between how different agents behave for various reasons. The basic operations of the plugins and the protocol should be the same. There are can be differences in resource usage, platforms, etc. Sometimes plugins will behave differently on different one.
Try out some of Ivan's suggests or other troubleshooting like that and figure out how to isolate the problem.
Jeff Thompson
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/099267e4-36f2-4b1e-adf1-4ed6f6d5bf90n%40googlegroups.com.
I see some serialization fails and this breaks the channel, the plugin that causes the exception seems https://github.com/jenkinsci/tasks-plugin, and the `[Deprecated] Scan workspace for open tasks` I think matters, this plugins has been integrated into https://github.com/jenkinsci/warnings-ng-plugin and https://github.com/jenkinsci/analysis-modelERROR: Step ‘[Deprecated] Scan workspace for open tasks’ aborted due to exception: java.io.StreamCorruptedException: invalid type code: 6D ... at hudson.plugins.tasks.TasksPublisher.perform(TasksPublisher.java:182) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:69) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:298) at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:112) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1919) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428)
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAKo5Qrr7zpoT__4EeG-oXzPeW-518g56oPphTV0989yLgyr9wQ%40mail.gmail.com.
On Thu, Feb 4, 2021 at 9:29 AM kuisathaverat <kuisat...@gmail.com> wrote:I see some serialization fails and this breaks the channel, the plugin that causes the exception seems https://github.com/jenkinsci/tasks-plugin, and the `[Deprecated] Scan workspace for open tasks` I think matters, this plugins has been integrated into https://github.com/jenkinsci/warnings-ng-plugin and https://github.com/jenkinsci/analysis-modelERROR: Step ‘[Deprecated] Scan workspace for open tasks’ aborted due to exception: java.io.StreamCorruptedException: invalid type code: 6D ... at hudson.plugins.tasks.TasksPublisher.perform(TasksPublisher.java:182) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:69) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:298) at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:112) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1919) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428)Thanks for this information. I will move to use warning-ng plugin & see if it breaks this or not.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c23aa67c-49e3-4a81-ad6e-5e3b4c81b762n%40googlegroups.com.
you attached the Jenkins build log and the Agent log, should be also an exception in the Jenkins log, Is the same you posted before `invalid type code: 6D`?
El 12 feb 2021, a las 17:32, Jigar R <jigarra...@gmail.com> escribió:
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1ed964b4-e619-4680-a1b0-fc93765bd01cn%40googlegroups.com.
On Feb 12, 2021, at 1:09 PM, Iván Fernández Calvo <kuisat...@gmail.com> wrote:
Looks like an abrupt disconnect, this point to the resources you give to the remote process and the resources you have in the agent. The resource management on a JVM is tricky, the JDK gives a 75% of the memory resources if you do not pass Xmx and Xms settings. So I wonder how much memory you have on those agents and if you set those limits. Based on my experience less than 4GB for sunfire tasks use to be tight.
Un SaludoIvan Fernandez Calvo
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3E29DA25-7732-4BA6-9C29-47544088D8D7%40gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/22ACBD5A-0D12-4BCD-BCFE-AFC490606099%40gmail.com.
I configured my jenkins agent with over 16GB of memory now. I use Apache ivy & Apache Ant to build the project. I still get resource temporarily unavailable.On the other hand, It works like a charm with Java Web start agent that I have. I haven't configured any JVM options for it and it just works smoothly. This is nerve wrecking.On Saturday, February 13, 2021 at 8:35:07 AM UTC-5 kuisat...@gmail.com wrote:the memory for the remoting process is not the issue, it is the free memory you left for the builds and the systems. I dunno what memory have your agents, but let's said they have 4GB if you give 2GB to the remoting process you only have 2GB for your builds and the system tasks so probably if you run a maven build that generates reports, it will need more than 4GB but only have 2GB so the maven process will die and because it grabs all the memory probably tear down another system process so the agent will disconnect the SSH connection.The remoting process usually not need more than 512MB (-Xms512m -Xms512m), I use to keep 1-2 GB for the system (ssh, Docker, and other services) so if you maven build need 4GB the agent will need at least 6-8GB. But all this is a guess because I dunno how much memory your build needs (maven or whatever) and I dunno which services you have running on your agents, and so on.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/428b6c62-61b4-4e3c-be64-10f9b3de7794n%40googlegroups.com.