I finally got this fixed by removing ruby-runtime plugin. I think that got installed during the update and was left in the system even after the downgrade. I found out the issue by copying all the configs and plugins to a test Jenkins instance, and one by one disabling plugins until the SSH connections started even printing something in Jenkins logs.
After the real culprit was found, I asked for maintenance break in our production Jenkins and removed the plugin - SSH started working there too! -Pasi On Tuesday, February 12, 2013 10:18:59 AM UTC+2, Pasi wrote: > > Nobody has any ideas about this? What logs to check, increase debug prints > somehow? > > Yesterday I once more did Jenkins update from 1.451 to 1.466.2 and SSH > slaves are still not working. There is nothing related to SSH connections > in any logs I checked, and monitoring IP packets with tcpdump doesn't show > any SSH action between the master and the SSH slave. > > I'm getting quite frustrated as SSH slave handling was working really well > before we did the catastrophic update from 1.451 to 1.499, and it was much > easier to do than with JNLP :( > > -Pasi > > On Monday, January 28, 2013 10:27:45 AM UTC+2, Pasi wrote: >> >> I think this is not the same issue, I have no trouble connecting Windows >> and Linux slaves via JNLP. SSH slave connection was not the only issue >> with the new Jenkins version, it also didn't start any jobs even though >> there were slaves available. >> >> I created a blocker ticket for my issue: >> https://issues.jenkins-ci.org/browse/JENKINS-16482 >> >> -Pasi >> >>> -- 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. For more options, visit https://groups.google.com/groups/opt_out.
