Thanks for the suggestions guys. I copied the new agent.jar to the machine when using the new version. I am executing it on demand from the command line.
How would I update the remoting.jar on the slave? As far as I can tell there is only one .jar used on the slave and that is the one you download from the master? On Monday, 15 February 2021 at 19:50:30 UTC [email protected] wrote: > Remember that JNLP agents do not update the remoting jar if are not > configured to do that, on Jenkins Core 2.248 there is a change on the > remoting version, I bet you can bump the version to 2.247 without issues. > To upgrade to 2.248+ you would need to upgrade the remoting jar on the JNLP > agents. > > El lunes, 15 de febrero de 2021 a las 18:21:04 UTC+1, [email protected] > escribió: > >> Hello, >> >> although I found nothing in the LTS upgrade guide... Did you get the >> current slave.jar from the new master ? >> Otherwise you might have a compatibility issue between new master and old >> slaves, >> >> Regards >> >> Martin >> >> Minimos schrieb am Montag, 15. Februar 2021 um 14:30:53 UTC+1: >> >>> So I rolled the version back and the issue has gone away. >>> >>> I will need to do a incremental upgrade of the WAR to find out which >>> version breaks the functionality >>> >>> On Friday, 12 February 2021 at 15:13:30 UTC Minimos wrote: >>> >>>> >>>> Thanks I'll take a look at the information. >>>> >>>> I am using .Net 4.5 so should not be an issue, but there is an >>>> interesting point re JNLP. >>>> >>>> I'll go through the document and double check everything. >>>> >>>> In the meantime do others have any other pointers? >>>> On Friday, 12 February 2021 at 14:55:58 UTC Mark Waite wrote: >>>> >>>>> The Jenkins 2.249.1 upgrade guide notes that Microsot.NET 2.0 support >>>>> has been removed. See >>>>> https://www.jenkins.io/doc/upgrade-guide/2.249/#upgrading-to-jenkins-lts-2-249-1 >>>>> >>>>> in case that affects your installation. >>>>> >>>>> On Fri, Feb 12, 2021 at 7:49 AM 'Minimos' via Jenkins Users < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> We recently updated Jenkins as per the subject line on our Windows >>>>>> boxes >>>>>> >>>>>> All plugins were updated at the same time, however we can no longer >>>>>> get our nods to communicate with the master. >>>>>> >>>>>> A Java Io exception of Connection time Out is displayed. There have >>>>>> been no changes to our firewall or network. >>>>>> >>>>>> I can see that a connecting is established via NetStat with a port >>>>>> being opened on both boxes. >>>>>> >>>>>> Has any one else experienced this problem? >>>>>> >>>>>> Thanks >>>>>> >>>>>> >>>>>> -- >>>>>> 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 [email protected]. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/jenkinsci-users/3f02999b-fbb4-4c82-92a8-e96bc9a05967n%40googlegroups.com >>>>>> >>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/3f02999b-fbb4-4c82-92a8-e96bc9a05967n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7ea8fe7c-dbe4-474c-9e6a-22ba8181e2ben%40googlegroups.com.
