[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title jake bishop resolved as Fixed Ignore me. It was a permissions problem caused by restoring a backup of the plugin when it failed. All works just fine. Thanks and sorry Jenkins / JENKINS-35242 Upgraded to new AWS-SDK plugin, jenkins would not start. Change By: jake bishop Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title jake bishop reopened an issue I tried to update to 1.10.45.2. Jenkins will now start but it seems to crash all the aws plugins and they show as nolonger installed. If i try to install them from the plugin manager it looks like it works and suggest to restart. Then the plgins are not installed again. Strangely it says " You have data stored in an older format and/or unreadable data." when i go to manage jenkins. This data looks like: Type Name Error hudson.model.Hudson CannotResolveClassException: hudson.plugins.ec2.EC2Cloud com.cloudbees.plugins.credentials.SystemCredentialsProvider CannotResolveClassException: com.cloudbees.jenkins.plugins.awscredentials.AWSCredentialsImpl Any ideas? Let me know if i can provide any more info. Jenkins / JENKINS-35242 Upgraded to new AWS-SDK plugin, jenkins would not start. Change By: jake bishop Resolution:
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title Vincent Latombe resolved as Fixed Fixed in 1.10.45.2 Jenkins / JENKINS-35242 Upgraded to new AWS-SDK plugin, jenkins would not start. Change By: Vincent Latombe Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35242 Re: Upgraded to new AWS-SDK plugin, jenkins would not start. Code changed in jenkins User: Andres Rodriguez Path: pom.xml http://jenkins-ci.org/commit/aws-java-sdk-plugin/e09506b9bb3809fb1565ea7873ea73a021cff9b9 Log: JENKINS-35242 Fix library bundling Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35242 Re: Upgraded to new AWS-SDK plugin, jenkins would not start. Code changed in jenkins User: Vincent Latombe Path: pom.xml http://jenkins-ci.org/commit/aws-java-sdk-plugin/8f4b72e1618869586125fba0c920cbd0d8e5ef07 Log: Merge pull request #4 from andresrc/JENKINS-35242 JENKINS-35242 Fix library bundling Compare: https://github.com/jenkinsci/aws-java-sdk-plugin/compare/ba91b53f06d2...8f4b72e16188 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title
Luigi Tagliamonte edited a comment on JENKINS-35242
Re: Upgraded to new AWS-SDK plugin, jenkins would not start.
got the same issue, I solved manually installing the prev version:go in JENKINS_HOME/plugins and performing the following commands:{code}mv aws-java-sdk aws-java-sdk.oldmv aws-java-sdk.bak aws-java-sdk.bak.oldmv aws-java-sdk.jpi aws-java-sdk.jpi.oldwget http://updates.jenkins-ci.org/download/plugins/aws-java-sdk/1.10.45/aws-java-sdk.hpichown jenkins:jenkins aws-java-sdk.hpichmod 775 aws-java-sdk.hpiservice restart jenkins{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title Luigi Tagliamonte commented on JENKINS-35242 Re: Upgraded to new AWS-SDK plugin, jenkins would not start. got the same issue, I solved manually installing the prev version: go in JENKINS_HOME/plugins and performing the following commands: mv aws-java-sdk aws-java-sdk.old mv aws-java-sdk.bak aws-java-sdk.bak.old mv aws-java-sdk.jpi aws-java-sdk.jpi.old wget http://updates.jenkins-ci.org/download/plugins/aws-java-sdk/1.10.45/aws-java-sdk.hpi chown jenkins:jenkins aws-java-sdk.hpi chmod 775 aws-java-sdk.hpi service restart jenkins Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title jake bishop edited a comment on JENKINS-35242 Re: Upgraded to new AWS-SDK plugin, jenkins would not start. Hmmm... how did you roll back? I just manually installed version 1.10.42 from [here|http://updates.jenkins-ci.org/download/plugins/aws-java-sdk/] and it just destroyed my aws configuration! Now nothing will build. Any ideas? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title jake bishop updated an issue Jenkins / JENKINS-35242 Upgraded to new AWS-SDK plugin, jenkins would not start. Change By: jake bishop Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title jake bishop commented on JENKINS-35242 Re: Upgraded to new AWS-SDK plugin, jenkins would not start. Hmmm... how did you roll back? I just manually installed version 1.10.42 from here and it just destroyed my aws configuration! Any ideas? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title Joe Arasin commented on JENKINS-35242 Re: Upgraded to new AWS-SDK plugin, jenkins would not start. jake bishop I was able to rollback to the previous version of the aws sdk plugin, and then I was able to get things rolling again. It'd probably be useful to get your setup and try to figure out what the common element is in our stacks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title jake bishop commented on JENKINS-35242 Re: Upgraded to new AWS-SDK plugin, jenkins would not start. We have this issue too, any workarounds? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title Joe Arasin commented on JENKINS-35242 Re: Upgraded to new AWS-SDK plugin, jenkins would not start. That is without the new version of the plugin installed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title Nicolas De Loof edited a comment on JENKINS-35242 Re: Upgraded to new AWS-SDK plugin, jenkins would not start. that's odd as plugin aws-java-sdk has direct dependency on httpclient 4. 5 3.6 which bundle includes org.apache.http.conn.ssl.SSLSocketFactory - this class is Deprecated in 4.3 , but still there present even with latest httpclient 4 . 5.2, so this could not result from another update and classloader conflict. Did you upgraded any other plugin ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title Nicolas De Loof commented on JENKINS-35242 Re: Upgraded to new AWS-SDK plugin, jenkins would not start. that's odd as plugin has direct dependency on httpclient 4.5 which bundle org.apache.http.conn.ssl.SSLSocketFactory - Deprecated, but still there. Did you upgraded any other plugin ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title
Joe Arasin updated an issue
Jenkins / JENKINS-35242
Upgraded to new AWS-SDK plugin, jenkins would not start.
Change By:
Joe Arasin
I upgraded to the awe-java-sdk plugin 1.10.45.1, and jenkins would no longer start.The error message: {{ hudson.util.HudsonFailedToLoad: java.lang.NoClassDefFoundError: org/apache/http/conn/ssl/SSLSocketFactory at hudson.WebAppMain$3.run(WebAppMain.java:234)Caused by: java.lang.NoClassDefFoundError: org/apache/http/conn/ssl/SSLSocketFactory at com.amazonaws.AmazonWebServiceClient.(AmazonWebServiceClient.java:136) at com.amazonaws.services.ec2.AmazonEC2Client.(AmazonEC2Client.java:196) at com.amazonaws.services.ec2.AmazonEC2Client.(AmazonEC2Client.java:173) at hudson.plugins.ec2.EC2Cloud.connect(EC2Cloud.java:640) at hudson.plugins.ec2.EC2Cloud.connect(EC2Cloud.java:609) at hudson.plugins.ec2.EC2Computer._describeInstanceOnce(EC2Computer.java:166) at hudson.plugins.ec2.EC2Computer._describeInstance(EC2Computer.java:149) at hudson.plugins.ec2.EC2Computer.describeInstance(EC2Computer.java:107) at hudson.plugins.ec2.EC2Computer.getUptime(EC2Computer.java:133) at hudson.plugins.ec2.EC2RetentionStrategy.internalCheck(EC2RetentionStrategy.java:104) at hudson.plugins.ec2.EC2RetentionStrategy.check(EC2RetentionStrategy.java:85) at hudson.plugins.ec2.EC2RetentionStrategy.check(EC2RetentionStrategy.java:43) at hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:717) at hudson.model.Queue._withLock(Queue.java:1306) at hudson.model.Queue.withLock(Queue.java:1189) at hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:714) at hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:118) at hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:44) at hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:186) at hudson.model.Queue._withLock(Queue.java:1306) at hudson.model.Queue.withLock(Queue.java:1189) at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:169) at jenkins.model.Jenkins.updateComputerList(Jenkins.java:1260) at jenkins.model.Jenkins.(Jenkins.java:846) at hudson.model.Hudson.(Hudson.java:83) at hudson.model.Hudson.(Hudson.java:79) at hudson.WebAppMain$3.run(WebAppMain.java:225)Caused by: java.lang.ClassNotFoundException: org.apache.http.conn.ssl.SSLSocketFactory at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1376) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1079) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 27 more }}
Add Comment
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title Joe Arasin updated an issue Jenkins / JENKINS-35242 Upgraded to new AWS-SDK plugin, jenkins would not start. Change By: Joe Arasin Summary: Upgraded to new AWS-SDK plugin, jenkins would n't not start. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.
Title: Message Title
Joe Arasin updated an issue
Jenkins / JENKINS-35242
Upgraded to new AWS-SDK plugin, jenkins would not start.
Change By:
Joe Arasin
I upgraded to the awe-java-sdk plugin 1.10.45.1, and jenkins would no longer start.The error message:{{ hudson.util.HudsonFailedToLoad: java.lang.NoClassDefFoundError: org/apache/http/conn/ssl/SSLSocketFactory at hudson.WebAppMain$3.run(WebAppMain.java:234)Caused by: java.lang.NoClassDefFoundError: org/apache/http/conn/ssl/SSLSocketFactory at com.amazonaws.AmazonWebServiceClient.(AmazonWebServiceClient.java:136) at com.amazonaws.services.ec2.AmazonEC2Client.(AmazonEC2Client.java:196) at com.amazonaws.services.ec2.AmazonEC2Client.(AmazonEC2Client.java:173) at hudson.plugins.ec2.EC2Cloud.connect(EC2Cloud.java:640) at hudson.plugins.ec2.EC2Cloud.connect(EC2Cloud.java:609) at hudson.plugins.ec2.EC2Computer._describeInstanceOnce(EC2Computer.java:166) at hudson.plugins.ec2.EC2Computer._describeInstance(EC2Computer.java:149) at hudson.plugins.ec2.EC2Computer.describeInstance(EC2Computer.java:107) at hudson.plugins.ec2.EC2Computer.getUptime(EC2Computer.java:133) at hudson.plugins.ec2.EC2RetentionStrategy.internalCheck(EC2RetentionStrategy.java:104) at hudson.plugins.ec2.EC2RetentionStrategy.check(EC2RetentionStrategy.java:85) at hudson.plugins.ec2.EC2RetentionStrategy.check(EC2RetentionStrategy.java:43) at hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:717) at hudson.model.Queue._withLock(Queue.java:1306) at hudson.model.Queue.withLock(Queue.java:1189) at hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:714) at hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:118) at hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:44) at hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:186) at hudson.model.Queue._withLock(Queue.java:1306) at hudson.model.Queue.withLock(Queue.java:1189) at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:169) at jenkins.model.Jenkins.updateComputerList(Jenkins.java:1260) at jenkins.model.Jenkins.(Jenkins.java:846) at hudson.model.Hudson.(Hudson.java:83) at hudson.model.Hudson.(Hudson.java:79) at hudson.WebAppMain$3.run(WebAppMain.java:225)Caused by: java.lang.ClassNotFoundException: org.apache.http.conn.ssl.SSLSocketFactory at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1376) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1079) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 27 more}}
Add Comment
[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would n't start.
Title: Message Title Joe Arasin created an issue Jenkins / JENKINS-35242 Upgraded to new AWS-SDK plugin, jenkins would n't start. Issue Type: Bug Assignee: Vincent Latombe Components: aws-java-sdk-plugin Created: 2016/May/31 5:07 PM Environment: Jenkins 1.651.2 using the official docker image Relevant plugins probably include: ace-editor 1.1 true false ansible 0.5 true false ansicolor 0.4.2 true false ant 1.3 true true antisamy-markup-formatter 1.3 true true authentication-tokens 1.2 true false aws-credentials 1.15 true false aws-java-sdk 1.10.45 true false branch-api 1.8 true false build-pipeline-plugin 1.5.3.1 true false cloudbees-folder 5.11 true false credentials 2.0.7 true true credentials-binding 1.7 true false cvs 2.12 true true delivery-pipeline-plugin 0.9.11 true false docker-build-publish 1.2.2 false false docker-build-step 1.35 true false docker-commons 1.3.1 true false docker-custom-build-environment 1.6.5 true false docker-workflow 1.4 true false durable-task 1.10 true false ec2 1.33 true false envinject 1.92.1 true false external-monitor-job 1.4 true false ghprb 1.32.2 true false git 2.4.4 true false git-client 1.19.6 true false git-server 1.6 true false github 1.19.1 true false github-api 1.75 true false github-branch-source 1.7 true false github-oauth 0.24 true false github-sqs-plugin 1.5 true false gradle 1.24 true false greenballs 1.15 true false handlebars 1.1.1 true false htmlpublisher 1.11 true false icon-shim 2.0.3 true false jackson2-api 2.7.3 true false javadoc 1.3 true true job-dsl 1.39 true false jquery 1.11.2-0 true false jquery-detached 1.2.1 true false junit 1.13 true true ldap 1.12 true true mailer 1.17 true true mapdb-api 1.0.9.0 true false matrix-auth 1.4 true true matrix-project 1.7 true true maven-plugin 2.13 true true momentjs 1.1.1 true false node-iterator-api 1.5 true false pam-auth 1.2 true true parameterized-trigger 2.30 true false pegdown-formatter 1.3 true false pipeline-build-step 2.0 true false pipeline-input-step 2.0 true false pipeline-rest-api 1.4 true false pipeline-stage-step 2.1 true false pipeline-stage-view 1.4 true false plain-credentials 1.2 true false postbuild-task 1.8 true false sbt 1.5 true false scm-api 1.2 true false script-security 1.19 true true slack 2.0.1 true false ssh-agent 1.10 true false
