Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

Minimos
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3f02999b-fbb4-4c82-92a8-e96bc9a05967n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

Mark Waite-2
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 <[hidden email]> 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3f02999b-fbb4-4c82-92a8-e96bc9a05967n%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFP0Q8Cx2okoJT%2Bp4dE-RTPy29eOzyVts0qOaySM4Sdkw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

Minimos

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 <[hidden email]> 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3f02999b-fbb4-4c82-92a8-e96bc9a05967n%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/058dc8e8-f145-4901-aa4a-76e586df2862n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

Minimos
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 <[hidden email]> 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3f02999b-fbb4-4c82-92a8-e96bc9a05967n%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8ff9007a-2977-4efb-8569-3489ea5437d1n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

mj1414...@gmail.com
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 <[hidden email]> 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3f02999b-fbb4-4c82-92a8-e96bc9a05967n%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5b085879-5d46-47d5-ae04-d5a92da462f1n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

Ivan Fernandez Calvo
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, [hidden email] 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 <[hidden email]> 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3f02999b-fbb4-4c82-92a8-e96bc9a05967n%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/518c8893-c3e8-4d79-ba87-67c888ff7002n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

Minimos
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 [hidden email] 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, [hidden email] 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 <[hidden email]> 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3f02999b-fbb4-4c82-92a8-e96bc9a05967n%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7ea8fe7c-dbe4-474c-9e6a-22ba8181e2ben%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

Ivan Fernandez Calvo
Yes, there is only one file to update the remoting.jar. If you install the remoting process as a service the update is done by the service see 
https://github.com/jenkinsci/windows-slave-installer-module and 

If you have updated the remoting jar before you connect your agents and they fails to connect, it means is not related to the remoting version. you could check which JNLP versions you have enabled on “manage Jenkins/security”, also check if you see something on the Jenkins logs related to those agents, if not try to enable verbose log for remoting 


El El mié, 17 feb 2021 a las 17:28, 'Minimos' via Jenkins Users <[hidden email]> escribió:
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 [hidden email] 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, [hidden email] 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 <[hidden email]> 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3f02999b-fbb4-4c82-92a8-e96bc9a05967n%40googlegroups.com.

--
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/fAFN1E3n9zs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7ea8fe7c-dbe4-474c-9e6a-22ba8181e2ben%40googlegroups.com.
--

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAKo5QrpvhorSb5f29ZMqieZ3Jics5Y3bam8kNS1scJTiBKOhOA%40mail.gmail.com.