[JIRA] (JENKINS-39179) All builds hang, JNA load deadlock on Windows slave
Title: Message Title Helder Magalhães commented on JENKINS-39179 Re: All builds hang, JNA load deadlock on Windows slave @Jesse Glick: I've verified that the plug-in works properly for Windows slaves. Unfortunately we have a mixed installation base of Linux slaves as well, which break when "Launch slave agents via SSH" option is used: <===[JENKINS REMOTING CAPACITY]===>channel started Slave.jar version: 2.53.2 This is a Unix slave Preloading JNA to avoid JENKINS-39179 Slave JVM has not reported exit code. Is it still running? [04/23/18 08:29:08] Launch failed - cleaning up connection [04/23/18 08:29:08] [SSH] Connection closed. ERROR: Connection terminated I'm attaching MyLinuxSlave-SystemInformation.txt. May the problem be related with using a somehow old (1.7) Java version? Although it doesn't work (yet), thanks for the effort! I really prefer this to be the way (instead of changing configuration in all Windows nodes) until an official fix is provided. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-39179) All builds hang, JNA load deadlock on Windows slave
Title: Message Title Helder Magalhães updated an issue Jenkins / JENKINS-39179 All builds hang, JNA load deadlock on Windows slave Change By: Helder Magalhães Attachment: MyLinuxSlave-SystemInformation.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] [active-directory-plugin] (JENKINS-13750) Failed to retrieve tokenGroups
Title: Message Title Helder Magalhães commented on JENKINS-13750 Re: Failed to retrieve tokenGroups I got here while investigating a few occurrences of these weird Failed to retrieve tokenGroups for ... warning messages. By comparing two users (myself and a user which triggers this message), it seems that the errors are caused by: User which triggers the warning doesn't belong to any groups (which would then be considered a false warning and therefore, in this case, should be silenced IMHO) Domain is configured in a way that me (nor Jenkins) don't have permissions to list the tokenGroups (somehow unlikely given other attributes are being correctly retrieved) Unfortunately my Active Directory knowledge doesn't allow me to go much further. If a set of simple checks can be made, though, please provide a set of commands and I (and maybe other users seeing this "issue") will try to run and provide their output. I've seen the code pointing at JENKINS-11644 but that issue is fixed for a long time... Maybe the comment in the code should be updated (for this issue or removed?). 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] [active-directory-plugin] (JENKINS-13750) Failed to retrieve tokenGroups
Title: Message Title
Helder Magalhães edited a comment on JENKINS-13750
Re: Failed to retrieve tokenGroups
Jenkins: {{1.644}}Active Directory plugin: {{1.41}} I got here while investigating a few occurrences of these weird {{Failed to retrieve tokenGroups for ...}} warning messages.By comparing two users (myself and a user which triggers this message), it seems that the errors are caused by:* User which triggers the warning doesn't belong to any groups (which would then be considered a false warning and therefore, in this case, should be silenced IMHO)* Domain is configured in a way that me (nor Jenkins) don't have permissions to list the {{tokenGroups}} (somehow unlikely given other attributes are being correctly retrieved)Unfortunately my Active Directory knowledge doesn't allow me to go much further. If a set of simple checks can be made, though, please provide a set of commands and I (and maybe other users seeing this "issue") will try to run and provide their output.I've seen the [code|https://github.com/jenkinsci/active-directory-plugin/blob/master/src/main/java/hudson/plugins/active_directory/ActiveDirectoryUnixAuthenticationProvider.java#L402] pointing at JENKINS-11644 but that issue is fixed for a long time... Maybe the comment in the code should be updated (for this issue or removed?).
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] [subversion-plugin] (JENKINS-32515) "E200030: Index not exists: I_NODES_MOVED" while reverting working copies
Title: Message Title
Helder Magalhães updated an issue
Jenkins / JENKINS-32515
"E200030: Index not exists: I_NODES_MOVED" while reverting working copies
Change By:
Helder Magalhães
Environment:
Java: 1.8.0 update 66 (build 17) 64-bitJenkins: {{ 1.644 }} (upgrade from {{ 1.638 }} )Subversion plug-in: {{ 2.5.7 }} (upgrade from {{ 2.5.4 }} )
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] [subversion-plugin] (JENKINS-32515) "E200030: Index not exists: I_NODES_MOVED" while reverting working copies
Title: Message Title
Helder Magalhães updated an issue
Jenkins / JENKINS-32515
"E200030: Index not exists: I_NODES_MOVED" while reverting working copies
Change By:
Helder Magalhães
After upgrading Jenkins, SVN checkouts started to fail. An exception is thrown during working copy revert:{ code noformat }org.tmatesoft.svn.core.SVNException: svn: E200030: Index not exists: I_NODES_MOVED at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.createSqlJetError(SVNSqlJetDb.java:195) at org.tmatesoft.svn.core.internal.db.SVNSqlJetSelectStatement.openCursor(SVNSqlJetSelectStatement.java:63) at org.tmatesoft.svn.core.internal.db.SVNSqlJetStatement.next(SVNSqlJetStatement.java:90) at org.tmatesoft.svn.core.internal.db.SVNSqlJetSelectStatement.next(SVNSqlJetSelectStatement.java:108) at org.tmatesoft.svn.core.internal.wc17.db.SvnWcDbRevert.revertRecursive(SvnWcDbRevert.java:329)[complete stacktrace attached]{ code noformat }This seems to be triggered by _Check-out Strategy_ being set to _Use 'svn update' as much as possible, with 'svn revert' before update_ in project settings (which causes SVN revert to run as a result).The origin seems to be [SVNKIT-582|https://issues.tmatesoft.com/issue/SVNKIT-582]. According to the [change log|https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin#SubversionPlugin-ChangeLog], the regression seems to have been introduced in {{2.5.5}} with _SVNKit library upgraded to 1.8.11_.Although this seems to be a [known issue|https://www.mail-archive.com/dev@wso2.org/msg50593.html], I believe reporting it here can be valuable as while the original issue isn't fixed people may decide to downgrade the plug-in or plug-in developers may downgrade the library within the plug-in to the latest working version (which is...?).
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [subversion-plugin] (JENKINS-32515) "E200030: Index not exists: I_NODES_MOVED" while reverting working copies
Title: Message Title
Helder Magalhães created an issue
Jenkins / JENKINS-32515
"E200030: Index not exists: I_NODES_MOVED" while reverting working copies
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
E200030-IndexNotExistsI_NODES_MOVED(Stacktrace).txt
Components:
subversion-plugin
Created:
19/Jan/16 12:53 PM
Environment:
Java: 1.8.0 update 66 (build 17) 64-bit Jenkins: {{1.644}} (upgrade from {{1.638}}) Subversion plug-in: {{2.5.7}} (upgrade from {{2.5.4}})
Labels:
regression
Priority:
Major
Reporter:
Helder Magalhães
After upgrading Jenkins, SVN checkouts started to fail. An exception is thrown during working copy revert:
[JIRA] [vsphere-cloud-plugin] (JENKINS-32112) NullPointerExceptions about templates in various places
Title: Message Title Helder Magalhães commented on JENKINS-32112 Re: NullPointerExceptions about templates in various places I also noticed this error after upgrading from Jenkins 1.638 to 1.644 (vCloud plugin from 2.7 to 2.9). > resolution for me was to re-save in jenkins/manage jenkins/configure system to get appropriate values set in the vsphere cloud/advanced/number of slaves fields. Similarly, I was able to workaround the issue by: 1. Go to Jenkins, Manage Jenkins, Configure 2. Scroll down to Cloud, vSphere Cloud 3. In Slave Templates, press Add (one may leave the contents blank) 4. Press Save to persist configuration Back to project configuration, no more ERROR displayed. 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] [core] (JENKINS-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Helder Magalhães created an issue Jenkins / JENKINS-31321 Renaming a node over another is possible and destroys both configurations Issue Type: Bug Assignee: Unassigned Attachments: Jenkins-BuildBreakageAfterNodeRename.txt Components: core Created: 30/Oct/15 7:28 PM Environment: Software version: Jenkins ver. 1.635 Possibly related plug-in: Windows Slaves Plugin Java version: 1.8.0_66 Operating system: Windows Server 2008 R2 Priority: Major Reporter: Helder Magalhães When performing a node name rework, I was able to overwrite a node with another one simply by renaming (which is a bit strange) but, apparently, the configuration of the "new" node was broken so it was necessary to delete it and create it from scratch. Steps to reproduce: Create a node named foo
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Helder Magalhães commented on JENKINS-20630 Jenkins fails to start This issue is being wrongly listed in the changelog as "26030" (instead of "20630"), leading to a deceiving "Issue Does Not Exist" JIRA page. [1] http://jenkins-ci.org/changelog 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.
