[JIRA] (JENKINS-50973) Insufficient free memory triggers Java install attempt
Title: Message Title Theral Mackey created an issue Jenkins / JENKINS-50973 Insufficient free memory triggers Java install attempt Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: ssh-slaves-plugin Created: 2018-04-24 19:01 Labels: java memory install version Priority: Minor Reporter: Theral Mackey Recently Jenkins disconnected from one of our linux slaves. When we tried restarting it, it failed. Investigating found insufficient memory to start Java (runaway python processes). The Agent, however, decided this was a problem with java not being installed and tried to reinstall it. More: The log in jenkins shows the ssh agent connecting to the slave, verifying environment settings, then attempting to get the Java Version. Due to low-memory, it can't start Java to get its version (Java err12). After this failure it tries a few other locations for the Java bin that we do not use, then determines Java must not be installed. It then attempts to download and install Java, which fails due to Oracle's credential requirement for downloads (reported in other tickets, but not a bug, we install Java by puppet/hand). Expected: It finds that Java exists, but fails to start due to Memory (errno 12), reports this and exits. It does NOT try to install Java. The OOM condition is unrelated to Java (runaway python processes on the same machine), and we are addressing the xxMaxPermSize attribute though it should not have contributed here either. [04/24/18 09:47:25] [SSH] Opening SSH connection to ourslave.build.slaves:22. [04/24/18 09:47:25] [SSH] Authentication successful. [04/24/18 09:47:25]
[JIRA] (JENKINS-14046) git operations occasionally hang in Jenkins on Windows
Theral Mackey commented on JENKINS-14046 git operations occasionally hang in Jenkins on Windows We hit the same problem, project builds will randomly fail and once one project fails it will not build again until the processes holding the git pack files locked are killed off so the files can be removed. Other projects continue building fine. In our case, this involved one git.exe process and an ssh.exe process (win7-64 w/cygwin). Once removed the Jenkins process was restarted and the build that was failing built successfully. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14470) S3 Plugin publishing fails spontaneously
Theral Mackey commented on JENKINS-14470 S3 Plugin publishing fails spontaneously This appears to be related to our using multiple S3 Profiles. We have ~18 projects on the problematic Jenkins server, most using the S3 uploader. We have 3 profiles setup in the general config area for S3. 2 are identical with the second being setup when the first set appeared to fail (adding credentials seems to temporarily get it working again as well). The other set was added for a different S3 bucket on a different project. We have noticed that when most builds go "unstable" due to S3 uploads failing, this other project still works. After restarting Jenkins to get the other projects working again, this project fails. It looks like Jenkins is switching credential sets between projects. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14470) S3 Plugin switches credential profiles
Theral Mackey updated JENKINS-14470 S3 Plugin switches credential profiles Change By: Theral Mackey (27/Jul/12 5:41 PM) Summary: S3Plugin publishingfailsspontaneously switchescredentialprofiles This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14470) S3 Plugin publishing fails spontaneously
Theral Mackey created JENKINS-14470 S3 Plugin publishing fails spontaneously Issue Type: Bug Affects Versions: current Assignee: Michael Watt Components: s3 Created: 17/Jul/12 5:03 PM Description: We use the S3 plugin in both a newer Jenkins install (v1.471, waiting for some important stuff to clear before we update it to 1.474) and a few older Hudson builds. The current Jenkins w/S3 (v0.3) works for a while, then all our builds stop uploading to S3 with an "Access Denied" error from Amazon. The builds on the older Hudson/S3 still work to the same bucket, and our credentials still work when I test with s3fs on the same machine. Error from Jenkins build console of one failure (buckets and filenames changed to x): Archiving artifacts Publish artifacts to S3 Bucket Using S3 profile: builds2 Publish artifacts to S3 Bucket bucket=xxx/store, file=xxx.latest.apk ERROR: Failed to upload files java.io.IOException: put Destination bucketName=x, objectName=xxx/store/xxx.latest.apk: Status Code: 403, AWS Request ID: 85F9CB0156BF7CF6, AWS Error Code: AccessDenied, AWS Error Message: Access Denied, S3 Extended Request ID: swP7ylP4SQNW3o9uP3alhBO/VZthqvuFxWiZ2Pn54mqhSHk2uEtSrIlhPXlJLPUM at hudson.plugins.s3.S3Profile.upload(S3Profile.java:82) at hudson.plugins.s3.S3BucketPublisher.perform(S3BucketPublisher.java:119) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1509) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Build step 'Publish artifacts to S3 Bucket' changed build result to UNSTABLE Project: Jenkins Priority: Major Reporter: Theral Mackey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14395) S3 Plugin credentials stored insecurely
Theral Mackey created JENKINS-14395 S3 Plugin credentials stored insecurely Issue Type: Bug Assignee: mcrooney Components: s3 Created: 11/Jul/12 10:07 PM Description: S3 Bucket credential keys (both access and secret) are stored/managed in such a way that anyone with access to the config page can easily retreive them (easy as in view-source). Once saved, they should not be retrievable through the web interface. Project: Jenkins Priority: Critical Reporter: Theral Mackey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
