[JIRA] (JENKINS-16810) CLI: java.io.EOFException
Title: Message Title Shabna Siraj closed an issue as Cannot Reproduce Jenkins / JENKINS-16810 CLI: java.io.EOFException Change By: Shabna Siraj Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-16810) CLI: java.io.EOFException
Title: Message Title Shabna Siraj assigned an issue to Shabna Siraj Jenkins / JENKINS-16810 CLI: java.io.EOFException Change By: Shabna Siraj Assignee: Shabna Siraj Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-16810) CLI: java.io.EOFException
Manuel Coenen edited a comment on JENKINS-16810 CLI: java.io.EOFException After a few days of working without problems the problem no occurs again with Jenkins 1.506 and AD plugin 1.30. Interestingly when downgrading Jenkins to 1.499 it always works no matter of the AD plugin version. 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 -- 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/groups/opt_out.
[JIRA] (JENKINS-16810) CLI: java.io.EOFException
Manuel Coenen commented on JENKINS-16810 CLI: java.io.EOFException After a few days of working without problems the problem no occurs again with Jenkins 1.506 and AD plugin 1.30. 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 -- 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/groups/opt_out.
[JIRA] (JENKINS-16810) CLI: java.io.EOFException
Manuel Coenen commented on JENKINS-16810 CLI: java.io.EOFException @Paul Landolt you were right. I just upgraded to Jenkins 1.506 and in the mean time also the AD plugin has been updated to 1.30 and it works again. The changlog of the AD plugin states for version 1.28: If an authentication fails (as opposed to a communication problem), don't fallback to other domain controllers to prevent a cascade of login failures, which can result in an account lock out. That probably fixed the problem. 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 -- 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/groups/opt_out.
[JIRA] (JENKINS-16810) CLI: java.io.EOFException
Paul Landolt commented on JENKINS-16810 CLI: java.io.EOFException Rather than focusing on the CLI, I went to look at the plugin. With the latest version (v1.505) of Jenkins, I am getting the error with the active-directory plugin v1.25, but NOT with v1.24. The changelog for v1.25 say "Fixed a security vulnerability that affects AD with anonymous binding enabled". So I'm wondering what the relationship is to anonymous binding and the error above. 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 -- 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/groups/opt_out.
[JIRA] (JENKINS-16810) CLI: java.io.EOFException
Chris Williams commented on JENKINS-16810 CLI: java.io.EOFException I am having the same problem on a Windows Server 2008 R2 system using Jenkins 1.501 and Jenkins Active Directory plugin 1.30. If I roll back to Jenkins 1.498 it works. I also see the same behavior as Manuel; I see an error in the Jenkins system log, but the CLI call still works (on 1.498): Mar 6, 2013 10:17:01 AM hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider FINE: Failed toretrieve user my_jenkins_user org.acegisecurity.BadCredentialsException: Failed to retrieve user information for my_jenkins_user; nested exception is javax.naming.NamingException: [LDAP: error code 1 - : LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]; remaining name 'DC=foo,DC=bar,DC=com' 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 -- 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/groups/opt_out.
[JIRA] (JENKINS-16810) CLI: java.io.EOFException
Manuel Coenen commented on JENKINS-16810 CLI: java.io.EOFException It was working for me until 1.499 and stopped working from 1.5xx for me. I use the Active Directory plugin and interesting is, that I get the same Exceptions in the log but on 1.499 it continues to perform the action on 1.5xx it fails. 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 -- 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/groups/opt_out.
[JIRA] (JENKINS-16810) CLI: java.io.EOFException
Viktor Tarasov updated JENKINS-16810 CLI: java.io.EOFException Change By: Viktor Tarasov (20/Feb/13 2:02 PM) Description: Starting from jenkins-1.486-55-gb44787d and until jenkins-1.501 (the latest that I could build) ,every second CLI command fails with 'java.io.EOFException'.Here is the sequence of four attempts to run the same test build:(it can be any other CLI command.)$ java -jar ./jenkins-cli.jar -s https://jenkins.rd.opentrust.com/ build job-test$ java -jar ./jenkins-cli.jar -s https://jenkins.rd.opentrust.com/ build job-testException in thread "main" java.io.EOFException at java.io.DataInputStream.readBoolean(DataInputStream.java:244) at hudson.cli.Connection.readBoolean(Connection.java:95) at hudson.cli.CLI.authenticate(CLI.java:604) at hudson.cli.CLI._main(CLI.java:444) at hudson.cli.CLI.main(CLI.java:374)$ java -jar ./jenkins-cli.jar -s https://jenkins.rd.opentrust.com/ build job-test$ java -jar ./jenkins-cli.jar -s https://jenkins.rd.opentrust.com/ build job-testException in thread "main" java.io.EOFException at java.io.DataInputStream.readBoolean(DataInputStream.java:244) at hudson.cli.Connection.readBoolean(Connection.java:95) at hudson.cli.CLI.authenticate(CLI.java:604) at hudson.cli.CLI._main(CLI.java:444) at hudson.cli.CLI.main(CLI.java:374)It seems that "b44787ddeaf203d26baf456cb12603b6f2ad232a is the first bad commit" .Kind regards,Viktor. 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 -- 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/groups/opt_out.
[JIRA] (JENKINS-16810) CLI: java.io.EOFException
Paul Landolt commented on JENKINS-16810 CLI: java.io.EOFException Happening in 1.502 as well: 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 -- 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/groups/opt_out.
[JIRA] (JENKINS-16810) CLI: java.io.EOFException
Viktor Tarasov created JENKINS-16810 CLI: java.io.EOFException Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cli Created: 14/Feb/13 3:28 PM Description: Starting from jenkins-1.486-55-gb44787d and until jenkins-1.501, every second CLI command fails with 'java.io.EOFException'. Here is the sequence of four attempts to run the same test build: (it can be any other CLI command.) $ java -jar ./jenkins-cli.jar -s https://jenkins.rd.opentrust.com/ build job-test $ java -jar ./jenkins-cli.jar -s https://jenkins.rd.opentrust.com/ build job-test Exception in thread "main" java.io.EOFException at java.io.DataInputStream.readBoolean(DataInputStream.java:244) at hudson.cli.Connection.readBoolean(Connection.java:95) at hudson.cli.CLI.authenticate(CLI.java:604) at hudson.cli.CLI._main(CLI.java:444) at hudson.cli.CLI.main(CLI.java:374) $ java -jar ./jenkins-cli.jar -s https://jenkins.rd.opentrust.com/ build job-test $ java -jar ./jenkins-cli.jar -s https://jenkins.rd.opentrust.com/ build job-test Exception in thread "main" java.io.EOFException at java.io.DataInputStream.readBoolean(DataInputStream.java:244) at hudson.cli.Connection.readBoolean(Connection.java:95) at hudson.cli.CLI.authenticate(CLI.java:604) at hudson.cli.CLI._main(CLI.java:444) at hudson.cli.CLI.main(CLI.java:374) It seems that "b44787ddeaf203d26baf456cb12603b6f2ad232a is the first bad commit" . Kind regards, Viktor. Environment: server on SLES-11-1 Project: Jenkins Priority: Major Reporter: Viktor Tarasov 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 -- 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/groups/opt_out.
