Jira (PUP-11373) Server hangs after upgrade v6 -> v7

[Pavel Sapezhka (Jira)]

Pavel Sapezhka created an issue

Puppet / PUP-11373 Server hangs after upgrade v6 -> v7 Issue Type: Bug Affects Versions: PUP 7.12.0 Assignee: Unassigned Attachments: env, ps_grafana.png, ps_mem.png, puppetserver-1.log, puppetserver.conf, threaddump.tdump Created: 2021/12/01 6:19 AM Environment: Debian: 10 PuppetDB: 7.7.1 PuppetServer: 7.4.2 Agent: 7.12.1 JVM Report: awt.toolkit=sun.awt.X11.XToolkit com.sun.management.jmxremote= com.sun.management.jmxremote.authenticate=false com.sun.management.jmxremote.local.only=false com.sun.management.jmxremote.port=9132 com.sun.management.jmxremote.rmi.port=9133 com.sun.management.jmxremote.ssl=false file.encoding=UTF-8 file.separator=/ java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment java.awt.printerjob=sun.print.PSPrinterJob java.class.path=/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar:/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.jar:/opt/puppetlabs/server/data/puppetserver/jars/* java.class.version=55.0 java.home=/usr/lib/jvm/java-11-openjdk-amd64 java.io.tmpdir=/tmp java.library.path=/usr/java/packages/lib:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib java.rmi.server.hostname=localhost java.rmi.server.randomIDs=true java.runtime.name=OpenJDK Runtime Environment java.runtime.version=11.0.12+7-post-Debian-2deb10u1 java.specification.name=Java Platform API Specification java.specification.vendor=Oracle Corporation java.specification.version=11 java.vendor=Debian java.vendor.url=https://tracker.debian.org/openjdk-11 java.vendor.url.bug=https://bugs.debian.org/openjdk-11 java.version=11.0.12 java.version.date=2021-07-20 java.vm.compressedOopsMode=Zero based java.vm.info=mixed mode, sharing java.vm.name=OpenJDK 64-Bit Server VM java.vm.specification.name=Java Virtual Machine Specification java.vm.specification.vendor=Oracle Corporation java.vm.specification.version=11 java.vm.vendor=Debian java.vm.version=11.0.12+7-post-Debian-2deb10u1 jdk.debug=release jdk.tls.ephemeralDHKeySize=matched jetty.git.hash=526006ecfa3af7f1a27ef3a288e2bef7ea9dd7e8 jruby.invokedynamic.yield=false jruby.logger.class=com.puppetlabs.jruby_utils.jruby.Slf4jLogger line.separator=\n os.arch=amd64 os.name=Linux os.version=5.8.0-0.bpo.2-amd64 path.separator=: sun.arch.data.model=64 sun.boot.library.path=/usr/lib/jvm/java-11-openjdk-amd64/lib sun.cpu.endian=little sun.cpu.isalist= sun.io.unicode.encoding=UnicodeLittle sun.java.command=clojure.main -m puppetlabs.trapperkeeper.main --config /etc/puppetlabs/puppetserver/conf.d --bootstrap-config /etc/puppetlabs/puppetserver/services.d/,/opt/puppetlabs/server/apps/puppetserver/config/services.d/ --restart-file /opt/puppetlabs/server/data/puppetserver/restartcounter sun.java.launcher=SUN_STANDARD sun.jnu.encoding=UTF-8 sun.management.compiler=HotSpot 64-Bit Tiered Compilers sun.os.patch.level=unknown user.country=US user.dir=/ user.home=/opt/puppetlabs/server/data/puppetserver user.language=en user.name=puppet   Priority: Normal Reporter: Pavel Sapezhka After upgrading from Puppet v6 to v7, the server hangs after ~10 min of work. More precisely, there are no free JRuby Instances. All configs (puppetserver, puppetdb, puppetagent) including resources are absolutely equal between v6 and v7.  We have ~300 agents, the server is configured according to an official guideline. v6 has worked with no issues.  Config, environment, thread dump, graphs, and logs are attached.  Heapdump is here.  Add Comment

This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)