[JIRA] [ssh-slaves-plugin] (JENKINS-25793) Set ssh KeepAlive

2015-03-19 Thread mrjewes+jenkins...@gmail.com (JIRA)












































  
Mingjiang Shi
 edited a comment on  JENKINS-25793


Set ssh KeepAlive
















+1 to this improvement. 

I have found a workaround for this.
1. Change the /etc/ssh/ssh_config by appending the following line to the end of this file. This tells the ssh client to send nop command periodically to avoid the ssh connection being disconnected. The unit of 80 is seconds. You may tune this parameter based on your network condition.

ServerAliveInterval 80

2. In the Jenkins slave configuration page, change the Launch method to "Launch slave via execution of command on the Master". See the Jenkins built-in help for more details.

So far, I haven't see any issues in this configuration. Hope this helps. 



























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/d/optout.


[JIRA] [ssh-slaves-plugin] (JENKINS-25793) Set ssh KeepAlive

2015-03-19 Thread mrjewes+jenkins...@gmail.com (JIRA)














































Mingjiang Shi
 commented on  JENKINS-25793


Set ssh KeepAlive















+1 to this improvement. 
@BBVA have you got any workaround for this issue? Thanks!



























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/d/optout.


[JIRA] [core] (JENKINS-27184) Jenkins 1.600 update center not working

2015-03-02 Thread mrjewes+jenkins...@gmail.com (JIRA)















































Mingjiang Shi
 resolved  JENKINS-27184 as Not A Defect


Jenkins 1.600 update center not working
















It's caused by a chrome proxy plugin. Close it.





Change By:


Mingjiang Shi
(02/Mar/15 8:19 AM)




Status:


Open
Resolved





Resolution:


Not A Defect



























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/d/optout.


[JIRA] [core] (JENKINS-27184) Jenkins 1.600 update center not working

2015-03-01 Thread mrjewes+jenkins...@gmail.com (JIRA)














































Mingjiang Shi
 created  JENKINS-27184


Jenkins 1.600 update center not working















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


02/Mar/15 7:57 AM



Description:


No plugin is displayed in the available tab of the plugin management page.  If clicking the Check Now button in the advanced tab, it says: Signature verification failed in update site 'default'

And the following exception is found in the log file:

SEVERE: ERROR: Signature verification failed in update site 'default' (show details)java.security.cert.CertPathValidatorException: timestamp check failed
at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:139)
at sun.security.provider.certpath.PKIXCertPathValidator.doValidate(PKIXCertPathValidator.java:330)
at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:178)
at java.security.cert.CertPathValidator.validate(CertPathValidator.java:250)
at org.jvnet.hudson.crypto.CertificateUtil.validatePath(CertificateUtil.java:93)
at jenkins.util.JSONSignatureValidator.verifySignature(JSONSignatureValidator.java:76)
at hudson.model.UpdateSite.verifySignature(UpdateSite.java:219)
at hudson.model.UpdateSite.updateData(UpdateSite.java:198)
at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:170)
at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:890)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
 1006,185%
at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960)
at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)
at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.security.cert.CertificateExpiredException: NotAfter: Wed Jan 28 05:04:07 CST 2015
at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:256)
at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:570)
at sun.security.provider.certpath.BasicChecker.verifyTimestamp(BasicChecker.java:157)
at sun.security.provider.certpath.BasicChecker.check(BasicChecker.java:109)
at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:117)
... 84 more





Environment:


Linux, jenkins 1.600




Project:


Jenkins



Priority:


Blocker



Reporter:


Ming

[JIRA] (JENKINS-16186) Jenkins hungs and takes all the CPU

2013-01-04 Thread mrjewes+jenkins...@gmail.com (JIRA)















































Mingjiang Shi
 assigned  JENKINS-16186 to Mingjiang Shi



Jenkins hungs and takes all the CPU
















Change By:


Mingjiang Shi
(05/Jan/13 1:31 AM)




Assignee:


Mingjiang Shi



























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-16186) Jenkins hungs and takes all the CPU

2013-01-04 Thread mrjewes+jenkins...@gmail.com (JIRA)















































Mingjiang Shi
 resolved  JENKINS-16186 as Fixed


Jenkins hungs and takes all the CPU
















The issues goes away after upgrading to Jenkins 1.496





Change By:


Mingjiang Shi
(05/Jan/13 1:32 AM)




Status:


Open
Resolved





Resolution:


Fixed



























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-16186) Jenkins hungs and takes all the CPU

2012-12-20 Thread mrjewes+jenkins...@gmail.com (JIRA)














































Mingjiang Shi
 created  JENKINS-16186


Jenkins hungs and takes all the CPU















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


Notepad_2012_12_21_0.txt



Components:


core



Created:


21/Dec/12 1:54 AM



Description:


Symptom: Cannot open the webpage of the jenkins.  Login to the machine, found that the Java process takes all the CPU. All I can do is to restart the server, and it hungs after a few hours.

The issue happens when Jenkins is running as a Windows service or start from command line.  It happens on the latest version 1.494 and the previous version 1.493. 

The recent change I made to the server was added about 20 simple jobs which just ping other server see if they respond to ping.

Meanwhile, I have a few slaves node in the Server.  I captured a stack dump attached. 





Environment:


Windows 2003 server 32-bit




Project:


Jenkins



Labels:


jenkins




Priority:


Blocker



Reporter:


Mingjiang Shi

























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-13066) unable to update CVS plugin

2012-03-13 Thread mrjewes+jenkins...@gmail.com (JIRA)
Mingjiang Shi created JENKINS-13066:
---

 Summary: unable to update CVS plugin
 Key: JENKINS-13066
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13066
 Project: Jenkins
  Issue Type: Bug
  Components: cvs
Affects Versions: current
 Environment: Jenkins: 1.454
Current CVS version:1.6
Available version:2.0
Reporter: Mingjiang Shi
Priority: Blocker


Unable to install the new plugin.  Once I tried to install it as other plugins 
and resart Jenkins, cvs plugin version 1.6 is displayed and the button revert 
to 1.6 is also displayed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-9117) Jenkins hangs in the shutdown mode after thinBackup is triggered

2012-02-08 Thread mrjewes+jenkins...@gmail.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-9117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158798#comment-158798
 ] 

Mingjiang Shi commented on JENKINS-9117:


@Thomas Fürer,
If a time-consuming job is triggered, the message "Jenkins is going to 
shutdown" will be displayed.  After I disabled the plugin, the message is not 
displayed any more.

Please let me know what information you need to diagnose the issue.  This is a 
very annoying issue. 

> Jenkins hangs in the shutdown mode after thinBackup is triggered
> 
>
> Key: JENKINS-9117
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9117
> Project: Jenkins
>  Issue Type: Bug
>  Components: thinBackup
>Reporter: Thomas Fürer
>Assignee: Thomas Fürer
>
> thinBackup triggers a backup job and did not return from the shutdown mode

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira