Re: Pending script approvals - Jenkins

[M.Madhusudana Reddy]

Got it. Thanks Dirk.


Thanks
M.Madhu


On Fri, Dec 9, 2022 at 12:41 AM 'Dirk Heinrichs' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Am Donnerstag, dem 08.12.2022 um 20:31 -0600 schrieb M.Madhusudana Reddy:
>
> I have the list from my old machine and would like to know if I can add
> all those signatures directly under the approved list.
>
>
> Yes, this is possible. You can either use the "Jenkins Configuration as
> Code" (JCasC) plugin to export/import or just copy/paste (parts of) your
> configuration from your old machine to the new one in form of YAML files,
> or simply copy the $JENKINS_HOME/scriptApproval.xml file over.
>
> Third alternative would be the "Permissive Script Security" plugin.
>
> HTH...
>
> Dirk
>
> --
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhein...@opentext.com
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan,
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail sind nicht gestattet.
>
> --
> 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/49e55e0f7d085cdbcc12e49cd39412abe7046c39.camel%40opentext.com
> <https://groups.google.com/d/msgid/jenkinsci-users/49e55e0f7d085cdbcc12e49cd39412abe7046c39.camel%40opentext.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAN%2BS7NrhLGaQPY8rea%2BYUrqosBOcOmaExdDwUQ3zCvuAcsvX5Q%40mail.gmail.com.

Pending script approvals - Jenkins

[M.Madhusudana Reddy]

Hi Team,

I installed Jenkins on a new machine and would like to know if there is any
easy way of adding signatures under the approved list instead of approving
each one after my builds fail?

I have the list from my old machine and would like to know if I can add all
those signatures directly under the approved list.

Thanks in advance.

Regards,
M.Madhu

-- 
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/CAN%2BS7NpzFGSYtQ2nAmMJm%3DsbWfbaNABH6FwiiEpQVkwo9tz7AQ%40mail.gmail.com.

Re: *** buffer overflow detected ***: java terminated

[M.Madhusudana Reddy]

I think I spoke too early.

Even with the newer version of Tomcat, I am seeing the issue.

Thanks
M.Madhu


On Tue, Dec 6, 2022 at 12:29 AM 'Dirk Heinrichs' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Am Montag, dem 05.12.2022 um 11:28 -0600 schrieb M.Madhusudana Reddy:
>
> My java version was jdk-11.0.16+8 and I updated this to the latest one in
> JAVA 11 this morning which is jdk-11.0.17+8 and I still see the same error.
>
> Tomcat is of version 9.0.0.0
>
>
> Ah, I see. We have different conditions, then. We're not running Jenkins
> in Tomcat here. And I checked again what our problem was with Java 11.0.16.
> It was a memory leak which led to Jenkins (or better: its JVM) being
> OOM-killed by the Linux kernel. THAT was fixed with 11.0.17.
>
> Bye...
>
> Dirk
>
> --
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhein...@opentext.com
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan,
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail sind nicht gestattet.
>
> --
> 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/dba5491ad09b0ca4eb8ba76c80ecf6dcb663316d.camel%40opentext.com
> <https://groups.google.com/d/msgid/jenkinsci-users/dba5491ad09b0ca4eb8ba76c80ecf6dcb663316d.camel%40opentext.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAN%2BS7NrLc3naAWOpc2VpyvStXfNLdP5GKrW1dq22zRq36DBS-Q%40mail.gmail.com.

Re: *** buffer overflow detected ***: java terminated

[M.Madhusudana Reddy]

Hi Mark -

Looks like the Tomcat upgrade from 9.0.0 to 9.0.70 fixed the issue. I am no
longer seeing that error/Jenkins controller getting crashed.

Thanks all for all your help.

Regards,
M.Madhu


On Mon, Dec 5, 2022 at 2:14 PM Mark Waite  wrote:

>
>
> On Monday, December 5, 2022 at 1:02:18 PM UTC-7 Madhu Muchukota wrote:
>
>> Thanks Mark
>>
>> All I'm doing is just triggering/running a multi branch pipeline job from
>> the controller UI.
>>
>> I will be happy to share more information needed from my end.
>>
>>
> Unfortunately, somehow you have a failure mode that is different than the
> 100,000+ Jenkins controllers around the world that are running with Java
> 11.  I don't have any suggestions about what could be different.
>
> Things that you could explore:
>
>- Does the same failure happen
>   - on a different computer running the same configuration?
>   - on a different computer running without Tomcat?
>   - on the same computer running without Tomcat?
>   - Were there recent upgrades to any components?
>   - Core upgrade
>   - Plugin upgrades
>   - Operating system upgrades
>- Were there any recent system configuration changes?
>   - Were settings increased on the system make it more secure or to
>   better defend it?
>
>
> --
> 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/7d818b09-f66f-4681-8163-2c1b26070e88n%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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAN%2BS7NoH8%2BRrBagTjFp%3Dz5_HKvoPzdd%2B45bUVb2TX9K-bOeYBQ%40mail.gmail.com.

Re: *** buffer overflow detected ***: java terminated

[M.Madhusudana Reddy]

Thanks Mark

All I'm doing is just triggering/running a multi branch pipeline job from
the controller UI.

I will be happy to share more information needed from my end.

I also looked at the compute resources of my controller node and don't see
any issues over there.

###

*** buffer overflow detected ***: /opt/apps/java/current_java/bin/java
terminated
=== Backtrace: =
/lib64/libc.so.6(__fortify_fail+0x37)[0x7f829c70b7a7]
/lib64/libc.so.6(+0x116922)[0x7f829c709922]
/lib64/libc.so.6(+0x118707)[0x7f829c70b707]
/lib64/libglib-2.0.so.0(g_spawn_sync+0x230)[0x7f821b6ec130]
/lib64/libglib-2.0.so.0(g_spawn_command_line_sync+0x75)[0x7f821b6ec805]
/lib64/libgio-2.0.so.0(+0xb2100)[0x7f821c07e100]
/lib64/libgio-2.0.so.0(g_dbus_address_get_for_bus_sync+0x340)[0x7f821c07fad0]
/lib64/libgio-2.0.so.0(+0xbf2fe)[0x7f821c08b2fe]
/lib64/libgio-2.0.so.0(g_bus_get_sync+0x56)[0x7f821c090c46]
/usr/lib64/gio/modules/libdconfsettings.so(+0x7b00)[0x7f821a512b00]
/usr/lib64/gio/modules/libdconfsettings.so(+0x7bed)[0x7f821a512bed]
/lib64/libglib-2.0.so.0(+0x48d47)[0x7f821b6a1d47]
/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x159)[0x7f821b6a5119]
/lib64/libglib-2.0.so.0(+0x4c478)[0x7f821b6a5478]
/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f821b6a552c]
/usr/lib64/gio/modules/libdconfsettings.so(+0x7d6d)[0x7f821a512d6d]
/lib64/libglib-2.0.so.0(+0x735b0)[0x7f821b6cc5b0]
/lib64/libpthread.so.0(+0x7ea5)[0x7f829cdddea5]
/lib64/libc.so.6(clone+0x6d)[0x7f829c6f1b0d]
=== Memory map: 
68000-80163f000 rw-p  00:00 0
80163f000-84000 ---p  00:00 0
55c431546000-55c431547000 r-xp  fd:04 23498504
/opt/apps/java/jdk-11.0.17+8/bin/java
55c431747000-55c431748000 r--p 1000 fd:04 23498504
/opt/apps/java/jdk-11.0.17+8/bin/java
55c431748000-55c431749000 rw-p 2000 fd:04 23498504
/opt/apps/java/jdk-11.0.17+8/bin/java
55c41000-55c433755000 rw-p  00:00 0
 [heap]
7f8219509000-7f821950a000 ---p  00:00 0
7f821950a000-7f8219d0a000 rw-p  00:00 0
7f8219d0a000-7f8219d0b000 ---p  00:00 0
7f8219d0b000-7f821a50b000 rw-p  00:00 0
7f821a50b000-7f821a517000 r-xp  fd:00 33776740
/usr/lib64/gio/modules/libdconfsettings.so
7f821a517000-7f821a716000 ---p c000 fd:00 33776740
/usr/lib64/gio/modules/libdconfsettings.so
7f821a716000-7f821a717000 r--p b000 fd:00 33776740
/usr/lib64/gio/modules/libdconfsettings.so
7f821a717000-7f821a718000 rw-p c000 fd:00 33776740
/usr/lib64/gio/modules/libdconfsettings.so
7f821a718000-7f821a71c000 r-xp  fd:00 102553411
 /usr/lib64/libuuid.so.1.3.0
7f821a71c000-7f821a91b000 ---p 4000 fd:00 102553411
 /usr/lib64/libuuid.so.1.3.0
7f821a91b000-7f821a91c000 r--p 3000 fd:00 102553411
 /usr/lib64/libuuid.so.1.3.0
7f821a91c000-7f821a91d000 rw-p 4000 fd:00 102553411
 /usr/lib64/libuuid.so.1.3.0
7f821a91d000-7f821a959000 r-xp  fd:00 102553418
 /usr/lib64/libblkid.so.1.1.0
7f821a959000-7f821ab58000 ---p 0003c000 fd:00 102553418
 /usr/lib64/libblkid.so.1.1.0
7f821ab58000-7f821ab5b000 r--p 0003b000 fd:00 102553418
 /usr/lib64/libblkid.so.1.1.0
7f821ab5b000-7f821ab5c000 rw-p 0003e000 fd:00 102553418
 /usr/lib64/libblkid.so.1.1.0
7f821ab5c000-7f821ab5d000 rw-p  00:00 0
7f821ab5d000-7f821ab72000 r-xp  fd:00 103879708
 /usr/lib64/libgcc_s-4.8.5-20150702.so.1
7f821ab72000-7f821ad71000 ---p 00015000 fd:00 103879708
 /usr/lib64/libgcc_s-4.8.5-20150702.so.1
7f821ad71000-7f821ad72000 r--p 00014000 fd:00 103879708
 /usr/lib64/libgcc_s-4.8.5-20150702.so.1
7f821ad72000-7f821ad73000 rw-p 00015000 fd:00 103879708
 /usr/lib64/libgcc_s-4.8.5-20150702.so.1
7f821ad73000-7f821adb3000 r-xp  fd:00 102553420
 /usr/lib64/libmount.so.1.1.0
7f821adb3000-7f821afb3000 ---p 0004 fd:00 102553420
 /usr/lib64/libmount.so.1.1.0
7f821afb3000-7f821afb4000 r--p 0004 fd:00 102553420
 /usr/lib64/libmount.so.1.1.0
7f821afb4000-7f821afb5000 rw-p 00041000 fd:00 102553420
 /usr/lib64/libmount.so.1.1.0
7f821afb5000-7f821afb6000 rw-p  00:00 0
7f821afb6000-7f821afcc000 r-xp  fd:00 103211987
 /usr/lib64/libresolv-2.17.so


#

Thanks
M.Madhu


On Mon, Dec 5, 2022 at 11:41 AM Mark Waite 
wrote:

>
>
> On Monday, December 5, 2022 at 10:29:49 AM UTC-7 Madhu Muchukota wrote:
>
>> Thanks Ivan and Dirk.
>>
>> My java version was jdk-11.0.16+8 and I updated this to the latest one in
>> JAVA 11 this morning which is jdk-11.0.17+8 and I still see the same error.
>>
>> Tomcat is of version 9.0.0.0
>> Jenkins is of version 2.375.1
>>
>>
> The message that you're seeing indicates that the Java process was killed
> by the operating system when the Java process performed an unsafe operation
> (buffer overflow).  The Java virtual machine works very hard to prevent
> Java programs from being able to perform unsafe operations.  There are some
> areas where Java allows unsafe operations (Java Native Interface, Java
> 

Re: *** buffer overflow detected ***: java terminated

[M.Madhusudana Reddy]

Thanks Ivan and Dirk.

My java version was jdk-11.0.16+8 and I updated this to the latest one in
JAVA 11 this morning which is jdk-11.0.17+8 and I still see the same error.

Tomcat is of version 9.0.0.0
Jenkins is of version 2.375.1



Thanks
M.Madhu


On Mon, Dec 5, 2022 at 12:32 AM 'Dirk Heinrichs' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Am Freitag, dem 02.12.2022 um 13:41 -0800 schrieb Madhu Muchukota:
>
> 5568a8c67000-5568a8c68000 r-xp  fd:04 17591637
> /opt/apps/java/jdk-11.0.16+8/bin/java
>
>
> You need to update to 11.0.17, it contains a fix.
>
> HTH...
>
> Dirk
>
> --
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhein...@opentext.com
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan,
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail sind nicht gestattet.
>
> --
> 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/db34e239bf19b96d52f34e4974decbb06dc974ab.camel%40opentext.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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAN%2BS7NoiXNSdKgQ0YxeWuNUGa71pkEawtcB2eiH%3DZQwpoDdhEg%40mail.gmail.com.

Re: GIT plugin - notifyCommit Token

[M.Madhusudana Reddy]

Thanks Mark.

Disabled mode worked.


Thanks
M.Madhu


On Fri, Dec 2, 2022 at 9:58 AM Mark Waite  wrote:

>
>
> On Friday, December 2, 2022 at 8:52:26 AM UTC-7 Madhu Muchukota wrote:
>
>> Hi Team,
>>
>> We recently upgraded Jenkins and as a part of this, plugins too got
>> upgraded.
>>
>> We use Service Hooks in Azure DevOps and after the upgrade, we are seeing
>> GIT notifyCommit is failing with HTTP status code 401.
>>
>> Upon troubleshooting, I came to know that the Jenkins Git Plugin that got
>> upgraded to the latest version needs notifyCommit token and I don't have
>> any option to pass that notifyCommit token on my Azure DevOps service hook
>> subscription page.
>>
>> Did anyone run into the same issue? and is there any property through
>> which I can disable this notifyCommit token option?
>>
>>
> The git plugin documentation
> 
> says
>
> The token parameter is required by default as a security measure, but can
> be disabled by the following system property
> :
> hudson.plugins.git.GitStatus.NOTIFY_COMMIT_ACCESS_CONTROL
>
> It has two modes:
>
>-
>
>disabled-for-polling - Allows unauthenticated requests as long as they
>only request polling of the repository supplied in the url query parameter.
>Prohibits unauthenticated requests that attempt to schedule a build
>immediately by providing a sha1 query parameter.
>-
>
>disabled - Fully disables the access token mechanism and allows all
>requests to notifyCommit to be unauthenticated. *This option is
>insecure and is not recommended.*
>
>
> --
> 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/34f1422f-8df5-48a7-91b8-52a99a96a25fn%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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAN%2BS7NoFq6gt6W8QWsKrm0VydwWvV_rT7DFJ1vfmEcykWs44bg%40mail.gmail.com.

GIT plugin - notifyCommit Token

[M.Madhusudana Reddy]

Hi Team,

We recently upgraded Jenkins and as a part of this, plugins too got
upgraded.

We use Service Hooks in Azure DevOps and after the upgrade, we are seeing
GIT notifyCommit is failing with HTTP status code 401.

Upon troubleshooting, I came to know that the Jenkins Git Plugin that got
upgraded to the latest version needs notifyCommit token and I don't have
any option to pass that notifyCommit token on my Azure DevOps service hook
subscription page.

Did anyone run into the same issue? and is there any property through which
I can disable this notifyCommit token option?

Thanks in advance.

Regards,
M.Madhu

-- 
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/CAN%2BS7Nqfph7HDOzZJXRAdjKNB7Sm6z7Ew159oi8Ptyg9Xpvd9g%40mail.gmail.com.

Re: Multibranch job export/import

[M.Madhusudana Reddy]

Thanks Dirk. I will try those steps.

Thanks
M.Madhu


On Wed, Jan 12, 2022 at 12:53 AM 'Dirk Heinrichs' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Am Dienstag, dem 11.01.2022 um 07:59 -0800 schrieb Madhu Muchukota:
>
> Do we have any documentation on this on how to export multibranch pipeline
> jobs?
>
>
> You can export *any* job's config.xml using the Jenkins CLI (possibly via
> the built-in SSH server on port ), like so:
>
> ssh -p  @ get-job  >config.xml
>
> and re-import like so:
>
> cat config.xml|ssh -p  @ create-job 
>
> or, w/o storing the config.xml anywhere:
>
> ssh -p  @ get-job |ssh -p 
> @ create-job 
>
> You can get help by issuing a "help" command (ssh ... help).
>
> Alternatively, if you want to keep the history and archived artifacts of
> your jobs, just rsync the ${JENKINS_HOME}/jobs folder over. Anyway, you
> might need to create other resources used by your jobs first, like
> credentials and such. In this case, the Jenkins Configuration as Code
> plugin should help.
>
> HTH...
>
> Dirk
> --
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhein...@opentext.com
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan,
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail sind nicht gestattet.
>
> --
> 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/49195e61afabdef9ec733d33e4c467aa8b7e563f.camel%40opentext.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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAN%2BS7NoaLCmhqnDQx1rF65Hn41X3waQzewQc%2BKwMX1Oe8enrgw%40mail.gmail.com.

Re: No of builds ran on a given build node/agent

[M.Madhusudana Reddy]

Thanks Dirk.

Do we have any plugins through which I can achieve equal load distribution?

Thanks
M.Madhu


On Fri, Dec 10, 2021 at 8:58 AM 'Dirk Heinrichs' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Am Freitag, dem 10.12.2021 um 06:51 -0800 schrieb Madhu Muchukota:
>
> Hi Team - Is there a way for me to find out how many number of builds
> executed on each build nodes that we have in a given time period?
>
>
> Yes. You can get the build history for every job (which includes the node
> each build ran on) using some Groovy scripting (-> Manage Jenkins -> Script
> console).
>
> I want to check if the load is equally getting distributed between the
> build nodes.
>
>
> It usually isn't, since Jenkins prefers the same node for subsequent
> builds of the same job. It only uses a different node if the preferred node
> is busy (has no free executors).
>
> Bye...
>
> Dirk
>
> --
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhein...@opentext.com
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan,
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail sind nicht gestattet.
>
> --
> 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/54747614fd7fd833f4e746b50f94399333934496.camel%40opentext.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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAN%2BS7NoZtJ2o7GV2%3DYJMBXK5eNJhnw%3DzToCC8jn_CGXcgPsWbA%40mail.gmail.com.

Re: Jenkins Upgrade

[M.Madhusudana Reddy]

Thanks Devin/Mark.

I will try disabling jqs-monitoring first to see if the issue goes away.

yes, we are using Tomcat and I will try with Jetty too.

Thanks
M.Madhu


On Mon, Mar 30, 2020 at 2:23 PM Devin Nusbaum 
wrote:

> From a quick look at the thread dumps, I think that the main problem is
> that JQSMonitoring (from Job/Queue/Slaves Monitoring Plugin) ends up
> loading builds in its constructor, which is invoked during Jenkins
> startup because it is a RootAction
> <https://github.com/jenkinsci/jenkins/blob/c9550613071ec7ddde5a56a9bbb1fa7754baf06b/core/src/main/java/jenkins/model/Jenkins.java#L3288-L3290>,
>  and
> the because extension loading is gated behind a instance-wide lock, this
> means that no other extensions can be loaded until JQSMonitoring is done
> loading builds.
>
> I would try disabling jqs-monitoring to see if the issue goes away. I
> think the easiest way to fix the issue would be for jqs-monitoring to use
> an `@Initializer` method to do the work that is currently done inside of
> JQSMonitoring’s constructor so that it does not need to load builds while
> the extension-loading lock is held.
>
> Some changes to the internals of Pipeline logging in the last two years or
> so might have made it so that Pipelines need to load extensions during
> startup where they did not do that previously, which could be why you are
> only seeing the problem after the upgrade.
>
> One other thing I noticed from the thread dumps is that you are using
> Tomcat rather than the version of Jetty bundled in Jenkins, which is know
> to cause some weird behavior. I would consider using the bundled version of
> Jetty to run Jenkins instead.
>
> On Mar 30, 2020, at 14:42, M.Madhusudana Reddy 
> wrote:
>
> Thanks Mark. I can definitely try that.
>
> But again as I mentioned early, If I kill the process and start the
> jenkins JVM(with the same JAVA version), I may not see this issue. This is
> intermittent and I need to keep trying with the restarts to reproduce the
> issue.
>
> Thanks
> M.Madhu
>
>
> On Mon, Mar 30, 2020 at 1:37 PM Mark Waite 
> wrote:
>
>> Any chance you can duplicate the same problem on Java 8 update 242 (the
>> current release)?
>>
>> Java 8 u121 was released in Jan 2017.  Significant changes were made to
>> Java 8 in update 161 (WIkipedia says " 21 Security fixes, 3 new features, 9
>> changes and 1 bug fix from 8u152.").  Update 231 (Oct 2019) included 18
>> security fixes.
>>
>> I don't have any hints to offer on the cause of the thread deadlock or
>> possible resolution.
>>
>>
>> On Mon, Mar 30, 2020 at 12:14 PM M.Madhusudana Reddy 
>> wrote:
>>
>>> I dumped the thread dump into one of the thread dump analysis tool and
>>> the tool is reporting on Dead Lock.
>>>
>>> Thread CpsStepContext.isReady [#4] is in deadlock with thread Finalizing
>>> set up
>>>
>>> Thanks
>>> M.Madhu
>>>
>>>
>>> On Mon, Mar 30, 2020 at 12:45 PM M.Madhusudana Reddy <
>>> madhu3...@gmail.com> wrote:
>>>
>>>> Ok. I am able to reproduce the issue even with HotSpot JAVA of versino
>>>> 1.8 update 121
>>>>
>>>> java version "1.8.0_121"
>>>> Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
>>>> Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
>>>>
>>>> ##
>>>>
>>>> Thread CpsStepContext.isReady [#4] is in deadlock with thread Finalizing
>>>> set up
>>>>
>>>> CpsStepContext.isReady [#4]priority:5 - threadId:0x7f843c075000 -
>>>> nativeId:0x4d0f - nativeId (decimal):19727 - state:BLOCKED
>>>> stackTrace:
>>>> java.lang.Thread.State: BLOCKED (on object monitor)
>>>> at hudson.ExtensionList.ensureLoaded(ExtensionList.java:315)
>>>> - waiting to lock <0x0006c191ac60> (a hudson.ExtensionList$Lock)
>>>> at hudson.ExtensionList.iterator(ExtensionList.java:172)
>>>> at org.jenkinsci.plugins.workflow.log.LogStorage.of(LogStorage.java:163
>>>> )
>>>> at org.jenkinsci.plugins.workflow.job.WorkflowRun.getListener(
>>>> WorkflowRun.java:229)
>>>> at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$300(
>>>> WorkflowRun.java:137)
>>>> at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.getListener(
>>>> WorkflowRun.java:974)
>>>> at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$2.onSuccess(
>>>> CpsFlowExecution.java:789)
>>>> at

Re: Jenkins Upgrade

[M.Madhusudana Reddy]

Thanks Mark. I can definitely try that.

But again as I mentioned early, If I kill the process and start the jenkins
JVM(with the same JAVA version), I may not see this issue. This is
intermittent and I need to keep trying with the restarts to reproduce the
issue.

Thanks
M.Madhu


On Mon, Mar 30, 2020 at 1:37 PM Mark Waite 
wrote:

> Any chance you can duplicate the same problem on Java 8 update 242 (the
> current release)?
>
> Java 8 u121 was released in Jan 2017.  Significant changes were made to
> Java 8 in update 161 (WIkipedia says " 21 Security fixes, 3 new features, 9
> changes and 1 bug fix from 8u152.").  Update 231 (Oct 2019) included 18
> security fixes.
>
> I don't have any hints to offer on the cause of the thread deadlock or
> possible resolution.
>
>
> On Mon, Mar 30, 2020 at 12:14 PM M.Madhusudana Reddy 
> wrote:
>
>> I dumped the thread dump into one of the thread dump analysis tool and
>> the tool is reporting on Dead Lock.
>>
>> Thread CpsStepContext.isReady [#4] is in deadlock with thread Finalizing
>> set up
>>
>> Thanks
>> M.Madhu
>>
>>
>> On Mon, Mar 30, 2020 at 12:45 PM M.Madhusudana Reddy 
>> wrote:
>>
>>> Ok. I am able to reproduce the issue even with HotSpot JAVA of versino
>>> 1.8 update 121
>>>
>>> java version "1.8.0_121"
>>> Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
>>> Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
>>>
>>> ##
>>>
>>> Thread CpsStepContext.isReady [#4] is in deadlock with thread Finalizing
>>> set up
>>>
>>> CpsStepContext.isReady [#4]priority:5 - threadId:0x7f843c075000 -
>>> nativeId:0x4d0f - nativeId (decimal):19727 - state:BLOCKED
>>> stackTrace:
>>> java.lang.Thread.State: BLOCKED (on object monitor)
>>> at hudson.ExtensionList.ensureLoaded(ExtensionList.java:315)
>>> - waiting to lock <0x0006c191ac60> (a hudson.ExtensionList$Lock)
>>> at hudson.ExtensionList.iterator(ExtensionList.java:172)
>>> at org.jenkinsci.plugins.workflow.log.LogStorage.of(LogStorage.java:163)
>>> at org.jenkinsci.plugins.workflow.job.WorkflowRun.getListener(
>>> WorkflowRun.java:229)
>>> at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$300(
>>> WorkflowRun.java:137)
>>> at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.getListener(
>>> WorkflowRun.java:974)
>>> at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$2.onSuccess(
>>> CpsFlowExecution.java:789)
>>> at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$2.onSuccess(
>>> CpsFlowExecution.java:776)
>>> at org.jenkinsci.plugins.workflow.support.concurrent.Futures$1.run(
>>> Futures.java:150)
>>> at
>>> com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(
>>> MoreExecutors.java:253)
>>> at
>>> com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(
>>> ExecutionList.java:149)
>>> at com.google.common.util.concurrent.ExecutionList.add(
>>> ExecutionList.java:105)
>>> at com.google.common.util.concurrent.AbstractFuture.addListener(
>>> AbstractFuture.java:155)
>>> at org.jenkinsci.plugins.workflow.support.concurrent.Futures.addCallback(
>>> Futures.java:160)
>>> at org.jenkinsci.plugins.workflow.support.concurrent.Futures.addCallback(
>>> Futures.java:90)
>>> at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.loadProgramAsync(
>>> CpsFlowExecution.java:773)
>>> at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(
>>> CpsFlowExecution.java:740)
>>> at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(
>>> WorkflowRun.java:672)
>>> - locked <0x0006c73dcd98> (a
>>> org.jenkinsci.plugins.workflow.job.WorkflowRun)
>>> at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(
>>> WorkflowRun.java:533)
>>> - locked <0x0006c73dd740> (a java.lang.Object)
>>> at hudson.model.RunMap.retrieve(RunMap.java:225)
>>> at hudson.model.RunMap.retrieve(RunMap.java:57)
>>> at jenkins.model.lazy.AbstractLazyLoadRunMap.load(
>>> AbstractLazyLoadRunMap.java:501)
>>> at jenkins.model.lazy.AbstractLazyLoadRunMap.load(
>>> AbstractLazyLoadRunMap.java:483)
>>> at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(
>>> AbstractLazyLoadRunMap.java:381)
>>> - locked <0x0006c639f178> (a hudson.model.RunMap)
>>> at hudson.model.RunMap

Re: Jenkins Upgrade

[M.Madhusudana Reddy]

I dumped the thread dump into one of the thread dump analysis tool and the
tool is reporting on Dead Lock.

Thread CpsStepContext.isReady [#4] is in deadlock with thread Finalizing
set up

Thanks
M.Madhu


On Mon, Mar 30, 2020 at 12:45 PM M.Madhusudana Reddy 
wrote:

> Ok. I am able to reproduce the issue even with HotSpot JAVA of versino 1.8
> update 121
>
> java version "1.8.0_121"
> Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
>
> ##
>
> Thread CpsStepContext.isReady [#4] is in deadlock with thread Finalizing
> set up
>
> CpsStepContext.isReady [#4]priority:5 - threadId:0x7f843c075000 -
> nativeId:0x4d0f - nativeId (decimal):19727 - state:BLOCKED
> stackTrace:
> java.lang.Thread.State: BLOCKED (on object monitor)
> at hudson.ExtensionList.ensureLoaded(ExtensionList.java:315)
> - waiting to lock <0x0006c191ac60> (a hudson.ExtensionList$Lock)
> at hudson.ExtensionList.iterator(ExtensionList.java:172)
> at org.jenkinsci.plugins.workflow.log.LogStorage.of(LogStorage.java:163)
> at org.jenkinsci.plugins.workflow.job.WorkflowRun.getListener(
> WorkflowRun.java:229)
> at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$300(
> WorkflowRun.java:137)
> at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.getListener(
> WorkflowRun.java:974)
> at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$2.onSuccess(
> CpsFlowExecution.java:789)
> at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$2.onSuccess(
> CpsFlowExecution.java:776)
> at org.jenkinsci.plugins.workflow.support.concurrent.Futures$1.run(
> Futures.java:150)
> at
> com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(
> MoreExecutors.java:253)
> at
> com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(
> ExecutionList.java:149)
> at com.google.common.util.concurrent.ExecutionList.add(
> ExecutionList.java:105)
> at com.google.common.util.concurrent.AbstractFuture.addListener(
> AbstractFuture.java:155)
> at org.jenkinsci.plugins.workflow.support.concurrent.Futures.addCallback(
> Futures.java:160)
> at org.jenkinsci.plugins.workflow.support.concurrent.Futures.addCallback(
> Futures.java:90)
> at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.loadProgramAsync(
> CpsFlowExecution.java:773)
> at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(
> CpsFlowExecution.java:740)
> at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(
> WorkflowRun.java:672)
> - locked <0x0006c73dcd98> (a
> org.jenkinsci.plugins.workflow.job.WorkflowRun)
> at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(
> WorkflowRun.java:533)
> - locked <0x0006c73dd740> (a java.lang.Object)
> at hudson.model.RunMap.retrieve(RunMap.java:225)
> at hudson.model.RunMap.retrieve(RunMap.java:57)
> at jenkins.model.lazy.AbstractLazyLoadRunMap.load(
> AbstractLazyLoadRunMap.java:501)
> at jenkins.model.lazy.AbstractLazyLoadRunMap.load(
> AbstractLazyLoadRunMap.java:483)
> at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(
> AbstractLazyLoadRunMap.java:381)
> - locked <0x0006c639f178> (a hudson.model.RunMap)
> at hudson.model.RunMap.getById(RunMap.java:205)
> at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(
> WorkflowRun.java:921)
> at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(
> WorkflowRun.java:932)
> at org.jenkinsci.plugins.workflow.cps.CpsStepContext.getExecution(
> CpsStepContext.java:217)
> at
> org.jenkinsci.plugins.workflow.cps.CpsStepContext.getThreadGroupSynchronously(
> CpsStepContext.java:242)
> at org.jenkinsci.plugins.workflow.cps.CpsStepContext.access$000(
> CpsStepContext.java:97)
> at org.jenkinsci.plugins.workflow.cps.CpsStepContext$1.call(
> CpsStepContext.java:263)
> at org.jenkinsci.plugins.workflow.cps.CpsStepContext$1.call(
> CpsStepContext.java:261)
> at jenkins.util.ContextResettingExecutorService$2.call(
> ContextResettingExecutorService.java:46)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Locked ownable synchronizers:
> - <0x0006c73dbb00> (a java.util.concurrent.ThreadPoolExecutor$Worker)
>
> Finalizing set uppriority:5 - threadId:0x7f845c00d800 -
> nativeId:0x4ca8 - nativeId (decimal):19624 - state:BLOCKED
> stackTrace:
> java.lang.Thread.State: BLOCKED (on object monitor)
> at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(
> Abstrac

Re: Jenkins Upgrade

[M.Madhusudana Reddy]

Thanks for the update Mark.

I believe we tried with AdoptOpenJDK and ran into same issue but I will
confirm that and let you know.

Thanks
M.Madhu


On Thu, Mar 12, 2020 at 9:15 AM Mark Waite 
wrote:

> FYI IBM openJ9 is not supported by the Jenkins project.  Initial testing
> has found no showstoppers, but IBM OpenJ9 introduces a very significant
> difference between what you're running and what is used and tested by
> people in the Jenkins project.
>
> The Jenkins Platform SIG <https://jenkins.io/sigs/platform/> has started
> the process of evaluating OpenJ9 with the help of Jim Crowley of IBM.
> There are at least 4 open issues
> <https://issues.jenkins-ci.org/issues/?jql=text%20~%20%22OpenJ9%22%20and%20status%20%3D%20Open>
> related to OpenJ9 and another 15 issues
> <https://issues.jenkins-ci.org/issues/?jql=text%20~%20%22J9%22%20%20and%20status%20%3D%20Open>
> related to J9.  Probably best to confirm that the same problem occurs with
> AdoptOpenJDK or with OpenJDK.
>
> Mark Waite
>
> On Wednesday, March 11, 2020 at 3:03:40 PM UTC-6, Madhu Muchukota wrote:
>>
>> Hi Devin, please find the thread dump attached.
>>
>> jfyi, we are using IBM J9.
>>
>> Thanks
>> M.Madhu
>>
>>
>> On Wed, Mar 11, 2020 at 2:05 PM Devin Nusbaum wrote:
>>
>>> Do you have the full thread dump from a tool like jstack? If so, please
>>> attach it to this thread, or paste it somewhere like gist.github.com or
>>> pastebin.com and then paste a link to it here.
>>>
>>> On Mar 11, 2020, at 14:11, M.Madhusudana Reddy wrote:
>>>
>>> Hi Team,
>>>
>>> We upgraded our jenkins instance from 2.107.3 to 2.204.3 and sometimes
>>> we notice that jenkins master is taking lot of time to come up and jenkins
>>> UI/application is unresponsive.
>>>
>>> I took a thread dump while we ran into this issue and noticed that
>>> application is suffering from deadlock.
>>>
>>> Thread jenkins.util.Timer [#1] is in deadlock with thread 
>>> CpsStepContext.isReady
>>> [#6]
>>>
>>> jenkins.util.Timer [#1]priority:0x5 - threadId:0x7F9C4C16EBE0 -
>>> nativeId:0x5AF5 - nativeId (decimal):23285 - state:BLOCKED
>>> stackTrace:
>>> at jenkins/model/lazy/AbstractLazyLoadRunMap.getByNumber(
>>> AbstractLazyLoadRunMap.java:370)
>>> at jenkins/model/lazy/LazyBuildMixIn.getBuildByNumber(
>>> LazyBuildMixIn.java:228)
>>> at org/jenkinsci/plugins/workflow/job/WorkflowJob.getBuildByNumber(
>>> WorkflowJob.java:232)
>>> at org/jenkinsci/plugins/workflow/job/WorkflowJob.getBuildByNumber(
>>> WorkflowJob.java:103)
>>> at hudson/model/Run.fromExternalizableId(Run.java:2446)
>>> at
>>> org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution$PlaceholderTask.runForDisplay(
>>> ExecutorStepExecution.java:445)
>>> at
>>> org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution$PlaceholderTask.getDisplayName(
>>> ExecutorStepExecution.java:461)
>>> at org/jenkinsci/plugins/jqsmonitoring/buildqueue/QueueJob.(
>>> QueueJob.java:50)
>>> at
>>> org/jenkinsci/plugins/jqsmonitoring/buildqueue/BuildQueue.retrieveQueueJobs(
>>> BuildQueue.java:87)
>>> at org/jenkinsci/plugins/jqsmonitoring/buildqueue/BuildQueue.(
>>> BuildQueue.java:36)
>>> at org/jenkinsci/plugins/jqsmonitoring/jqscore/JQSMonitoring.(
>>> JQSMonitoring.java:43)
>>> at
>>> org/jenkinsci/plugins/jqsmonitoring/jqscore/JQSMonitoring$$FastClassByGuice$$a25d5b0d.newInstance(
>>> )
>>> at com/google/inject/internal/cglib/reflect/$FastConstructor.newInstance(
>>> FastConstructor.java:40)
>>> at
>>> com/google/inject/internal/DefaultConstructionProxyFactory$1.newInstance(
>>> DefaultConstructionProxyFactory.java:61)
>>> at com/google/inject/internal/ConstructorInjector.provision(
>>> ConstructorInjector.java:105)
>>> at com/google/inject/internal/ConstructorInjector.access$000(
>>> ConstructorInjector.java:32)
>>> at com/google/inject/internal/ConstructorInjector$1.call(
>>> ConstructorInjector.java:89)
>>> at
>>> com/google/inject/internal/ProvisionListenerStackCallback$Provision.provision(
>>> ProvisionListenerStackCallback.java:115)
>>> at 
>>> hudson/ExtensionFinder$GuiceFinder$SezpozModule.onProvision(ExtensionFinder.java:567(Compiled
>>> Code))
>>> at
>>> com/google/inject/internal/ProvisionListenerStackCallback$Provision.provision(
>>> ProvisionLis

Jenkins Upgrade

[M.Madhusudana Reddy]

Hi Team,

We upgraded our jenkins instance from 2.107.3 to 2.204.3 and sometimes we 
notice that jenkins master is taking lot of time to come up and jenkins 
UI/application is unresponsive.

I took a thread dump while we ran into this issue and noticed that 
application is suffering from deadlock. 

Thread jenkins.util.Timer [#1] is in deadlock with thread 
CpsStepContext.isReady 
[#6]  

jenkins.util.Timer [#1]priority:0x5 - threadId:0x7F9C4C16EBE0 - 
nativeId:0x5AF5 - nativeId (decimal):23285 - state:BLOCKED
stackTrace:
at jenkins/model/lazy/AbstractLazyLoadRunMap.getByNumber(
AbstractLazyLoadRunMap.java:370)
at jenkins/model/lazy/LazyBuildMixIn.getBuildByNumber(
LazyBuildMixIn.java:228)
at org/jenkinsci/plugins/workflow/job/WorkflowJob.getBuildByNumber(
WorkflowJob.java:232)
at org/jenkinsci/plugins/workflow/job/WorkflowJob.getBuildByNumber(
WorkflowJob.java:103)
at hudson/model/Run.fromExternalizableId(Run.java:2446)
at 
org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution$PlaceholderTask.runForDisplay(
ExecutorStepExecution.java:445)
at 
org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution$PlaceholderTask.getDisplayName(
ExecutorStepExecution.java:461)
at org/jenkinsci/plugins/jqsmonitoring/buildqueue/QueueJob.(
QueueJob.java:50)
at 
org/jenkinsci/plugins/jqsmonitoring/buildqueue/BuildQueue.retrieveQueueJobs(
BuildQueue.java:87)
at org/jenkinsci/plugins/jqsmonitoring/buildqueue/BuildQueue.(
BuildQueue.java:36)
at org/jenkinsci/plugins/jqsmonitoring/jqscore/JQSMonitoring.(
JQSMonitoring.java:43)
at 
org/jenkinsci/plugins/jqsmonitoring/jqscore/JQSMonitoring$$FastClassByGuice$$a25d5b0d.newInstance(
)
at com/google/inject/internal/cglib/reflect/$FastConstructor.newInstance(
FastConstructor.java:40)
at com/google/inject/internal/DefaultConstructionProxyFactory$1.newInstance(
DefaultConstructionProxyFactory.java:61)
at com/google/inject/internal/ConstructorInjector.provision(
ConstructorInjector.java:105)
at com/google/inject/internal/ConstructorInjector.access$000(
ConstructorInjector.java:32)
at com/google/inject/internal/ConstructorInjector$1.call(
ConstructorInjector.java:89)
at 
com/google/inject/internal/ProvisionListenerStackCallback$Provision.provision(
ProvisionListenerStackCallback.java:115)
at 
hudson/ExtensionFinder$GuiceFinder$SezpozModule.onProvision(ExtensionFinder.java:567(Compiled
 
Code))
at 
com/google/inject/internal/ProvisionListenerStackCallback$Provision.provision(
ProvisionListenerStackCallback.java:126)
at com/google/inject/internal/ProvisionListenerStackCallback.provision(
Provision 

###

 
CpsStepContext.isReady [#6]priority:0x5 - threadId:0x7F9C6802DE40 - 
nativeId:0x5B72 - nativeId (decimal):23410 - state:BLOCKED
stackTrace:
at org/jenkinsci/plugins/workflow/cps/CpsGroovyShell.doParse(
CpsGroovyShell.java:133)
at org/jenkinsci/plugins/workflow/cps/CpsGroovyShell.reparse(
CpsGroovyShell.java:127)
at org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.parseScript(
CpsFlowExecution.java:561)
at org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.loadProgramAsync(
CpsFlowExecution.java:770)
at org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.onLoad(
CpsFlowExecution.java:740)
at org/jenkinsci/plugins/workflow/job/WorkflowRun.getExecution(
WorkflowRun.java:672)
at org/jenkinsci/plugins/workflow/job/WorkflowRun.onLoad(
WorkflowRun.java:533)
at hudson/model/RunMap.retrieve(RunMap.java:225)
at hudson/model/RunMap.retrieve(RunMap.java:57)
at jenkins/model/lazy/AbstractLazyLoadRunMap.load(
AbstractLazyLoadRunMap.java:501)
at jenkins/model/lazy/AbstractLazyLoadRunMap.load(
AbstractLazyLoadRunMap.java:483)
at jenkins/model/lazy/AbstractLazyLoadRunMap.getByNumber(
AbstractLazyLoadRunMap.java:381)
at hudson/model/RunMap.getById(RunMap.java:205)
at org/jenkinsci/plugins/workflow/job/WorkflowRun$Owner.run(
WorkflowRun.java:921)
at org/jenkinsci/plugins/workflow/job/WorkflowRun$Owner.get(
WorkflowRun.java:932)
at org/jenkinsci/plugins/workflow/cps/CpsStepContext.getExecution(
CpsStepContext.java:217)
at 
org/jenkinsci/plugins/workflow/cps/CpsStepContext.getThreadGroupSynchronously(
CpsStepContext.java:242)
at org/jenkinsci/plugins/workflow/cps/CpsStepContext.access$000(
CpsStepContext.java:97)
at org/jenkinsci/plugins/workflow/cps/CpsStepContext$1.call(
CpsStepContext.java:263)
at org/jenkinsci/plugins/workflow/cps/CpsStepContext$1.call(
CpsStepContext.java:261)
at jenkins/util/ContextResettingExecutorService$2.call(
ContextResettingExecutorService.java:46)
at java/util/concurrent/FutureTask.run(FutureTask.java:277)
at 
java/util/concurrent/ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153(Compiled
 
Code))
at java/util/concurrent/ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:628)
at java/lang/Thread.run(Thread.java:785)

#

Any one ran into the same issue and any help on this is highly appreciated 
please.

-- 
You received this message because you are subscribed to the Google Groups