-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Puppetdb restarts because of java.lang.NoSuchMethodError #3947
Comments
We are also having this problem since updating puppetdb |
we are also running into this seems related to this bug: pgjdbc/pgjdbc#3014 |
Running PuppetDB with java 11 will avoid this issue. It's also preferable because our testing prioritizes that version on the 7.x branch. I reproduced the issue on our pgjdbc version asked if the fix can be backported to 42.4.x, which is the stream of pgjdbc we are using in PuppetDB 7.x. |
Migrated issue to PDB-5730 |
The FAQ also recommends JDK8 . Perhaps that needs to be updated then https://www.puppet.com/docs/puppetdb/7/puppetdb-faq.html#which-versions-of-java-are-supported
While looking it up we did notice that JDK11 is mentioned on the overview page But the actual apt package still depends on openjdk-8-jre-headless
|
Thanks for pointing out the FAQ updates were missed, I will look into getting that updated. Yes, that package dependency issue was an oversight when we initially released Puppet Platform 7. I was not able to get permission to change it after the fact for fear we would break someones upgrade and leave them stuck on an old PuppetDB 7.x version. It is fixed in PuppetDB 8 and going forward I made our packaging force us to pick new java package versions for every major version. By default, PuppetDB will use whatever java version it finds at |
Hi can PuppetLabs release a new version of puppetdb 7.17.1 to use jdk11? As @KoenDierckx said
this Ubuntu package is built by PuppetLabs, so updating this shouldn't be too difficult? Edit: On Ubuntu, instead of downgrading, installing
|
If jdk11 ist mandatory for 7.17.1 their should be an Info in the documentation about that. So please at that to the change/releaselog if it is mandatory. |
@waipeng the pgjdbc maintainers are working on resolving the issue. If you'd like, you can follow along in pgjdbc/pgjdbc#3014. I have verified their fix, so once they get a release out we will release a PuppetDB version with that update.
No, it is not difficult (and I have wanted to update it), but I have been prevented from doing so when I attempted to do so. The compromise was my work in puppetlabs/ezbake#611, which should prevent us from missing our java dependency update on major version boundaries in the future. |
Is the recommended fix for this to upgrade to Java 11 or greater, or will there be a new package release soon including what appears to be the fix? We're right at a turning point where we're about to uplift the underlying OS and major Puppet version, so I'm just trying to determine a path forward since we had to roll back from 7.17.1 to 7.16.0 in the interim. Thanks! |
Are their any new Infos about this? We stopped the puppetdb patches because of this issue. Would be good to know if the only fix is to upgrade to java 11. Thanks! |
@jplindquist @ochnerd I am not from Puppet; as a user we install jre11 and that worked. See #3947 (comment) |
Describe the Bug
After the update from version 7.16.0 to version 7.17.1, Puppetdb restarts every minute.
The error we see in the logs is the following:
Expected Behavior
Puppetdb does not restart every minute and runs without a problem
Steps to Reproduce
Steps to reproduce the behavior:
Happens after a minute.
Environment
Additional Context
Our first hint what could be the issue was this change in clj-parent: https://github.com/puppetlabs/clj-parent/blob/5.6.11/project.clj#L100
Our workaround was a downgrade to version 7.16.0.
The text was updated successfully, but these errors were encountered: