Running jenkins-cli.jar for https

2015-04-23 Thread Grace Lee
Hi,

Has anyone successfully run Jenkins-cli.jar for https protocol?

I kept getting connection error from client side to Jenkins on https. Could 
anyone help me on this? My sincere appreciation.

- java -Djavax.net.ssl.trustStore=/tmp/jenkins2/jenkinskeystore.jks 
-Djavax.net.ssl.trustStorePassword=password -jar jenkins-cli.jar -s 
https://jenkins2.eng.proofpoint.com:8443 help
Exception in thread main java.io.IOException: Failed to connect to 
https://jenkins2.eng.proofpoint.com:8443/
at hudson.cli.CLI.getCliTcpPort(CLI.java:266)
at hudson.cli.CLI.init(CLI.java:126)
at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72)
at hudson.cli.CLI._main(CLI.java:466)
at hudson.cli.CLI.main(CLI.java:382)
Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection 
during handshake
at 
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:882)
at 
com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1188)
at 
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1215)
at 
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1199)
at 
sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:434)
at 
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:166)
at 
sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:133)
at hudson.cli.CLI.getCliTcpPort(CLI.java:264)
... 4 more
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:462)
at 
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:863)
... 11 more

* Where:

o   /tmp/jenkins2/jenkinskeystore.jks is a copy of 
/u/xbuild/.ssh/jenkinskeystore.jks from following server command.

o   password is same password as in the following server command

o   jar jenkins-cli.jar was extracted from 
/share/pub/build/jenkins2/bin/jenkins.war in the following server command

o   the following Jenkins server is running on Jenkins ver. 1.605.
The server process:
$ /etc/alternatives/java -Djava.awt.headless=true -server -Xms2048m -Xmx8192m 
-XX:PermSize=512m -XX:MaxPermSize=1024m 
-DJENKINS_HOME=/share/pub/build/jenkins2 -jar 
/share/pub/build/jenkins2/bin/jenkins.war 
--logfile=/share/pub/build/jenkins2/log/jenkins.log 
--webroot=/var/cache/jenkins/war --httpPort=-1 --httpsPort=8443 
--httpsKeyStore=/u/xbuild/.ssh/jenkinskeystore.jks 
--httpsKeyStorePassword=password --ajp13Port=-1 --debug=5 
--handlerCountMax=100 --handlerCountMaxIdle=20
$ hostname
jenkins2.eng.proofpoint.com

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/14E16BAE45DBED4D8514D0C53BC00B86C019DD2C%40hq-mdb001.corp.proofpoint.com.
For more options, visit https://groups.google.com/d/optout.


Start Jenkins slave from Windows 7 while master is run with https protocol

2014-08-27 Thread Grace Lee
Has anyone successfully started Jenkins slave via ‘Launch slave agents via Java 
Web Start’ when master is running in https protocol?

We are running Jenkins 1.568 on Linux Centos 5.5.

Jenkins suggested the following command to run on slave machine, but I think 
it’s lack of the cert key. Has anyone successfully done this? Thanks.

-java -jar slave.jar -jnlpUrl https://master:8080/hudson/computer/slave/s
lave-agent.jnlp -secret 
9344091d1e0c6b2582d277761105f8380f799bc318cce577480c9aeaf31b0309
Exception in thread main javax.net.ssl.SSLHandshakeException: 
java.security.cert.CertificateException: No subject alternative names present
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.SSLSocketImpl.fatal(Unknown Source)
at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source)
at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source)
at sun.security.ssl.Handshaker.processLoop(Unknown Source)
at sun.security.ssl.Handshaker.process_record(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown 
Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
at 
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown 
Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(Unknown 
Source)
at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:245)
at hudson.remoting.Launcher.run(Launcher.java:207)
at hudson.remoting.Launcher.main(Launcher.java:180)
Caused by: java.security.cert.CertificateException: No subject alternative 
names present
at sun.security.util.HostnameChecker.matchIP(Unknown Source)
at sun.security.util.HostnameChecker.match(Unknown Source)
at sun.security.ssl.X509TrustManagerImpl.checkIdentity(Unknown Source)
at sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source)
at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown 
Source)
... 14 more

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: git polling saw a lot of connection error

2014-08-12 Thread Grace Lee
Mark,

Thanks for the quick response.
A brief testing using the approach suggested in ‘polling must die’ worked for 
us. We’ll try this method.

For the polling failures, the Jenkins log didn’t have anything for it.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite
Sent: Monday, August 11, 2014 5:24 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: git polling saw a lot of connection error

It seems like you might first want to consider if you really need to poll.  
Refer to polling must die, the blog posting from Kohsuke Kawaguchi, for hints 
on how to configure Jenkins to respond more rapidly to changes, and to generate 
less load on your git servers as well.

If you still are committed to polling, then you probably should read the log 
files on the server to confirm that the polling failures are being reported in 
server log files.  If they are reported in server log files, then you can focus 
your efforts on finding and increasing the limits which cause the errors in the 
server log files.

If the polling failures do not result in entries in server log files, then you 
may need to investigate the messages from the git polling logs to see if the 
limit is in the computer hosting the Jenkins master server.  If you use slave 
nodes, and if the polling failures are in the Jenkins server log, then you 
could add Polling requires a workspace as an additional behavior on your 
jobs.  That will move the polling to the slave computer which has the 
workspace.  It doesn't reduce the amount of polling, but it can reduce the 
amount of polling from a single machine.

Mark Waite

On Mon, Aug 11, 2014 at 6:10 PM, Grace Lee 
g...@proofpoint.commailto:g...@proofpoint.com wrote:

Hi,

We often saw git server connection error when doing git polling in Jenkins. But 
we didn’t see this error outside of Jenkins.

We have 144 Jenkins projects doing SCM polling, while 136 of them doing git 
polling.

I had ‘Max #of concurrent polling’ configured to be 40 or 60, they didn’t make 
much of difference.

(I also did side-by-side monitor of the git polling log for same project on 
production Jenkins server and test server for about an hour . Only on the 
production server, the git connection error was seen. Both the servers are on 
same version of Jenkins and plugins. But on test server only this project was 
enabled.)

Does anyone have any suggestion on how to resolve the git connection issue on 
SCM polling?

Thanks.
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit 
https://groups.google.com/d/optouthttps://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optoutd=AAMFaQc=Vxt5e0Osvvt2gflwSlsJ5DmPGcPvTRKLJyp031rXjhgr=k6oisD67M2DonEly12tPl4mv6QNKvRUg1Gi7o9Bf5-Mm=cMBVfEV7A6dD3kTHFli18PJVWaBo6gPxhky1xou4zBIs=V0Xi7OGRVckxukXKbpLoeHrbIfgAhpwO3pULTXbLxPge=.



--
Thanks!
Mark Waite
--
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit 
https://groups.google.com/d/optouthttps://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optoutd=AAMFaQc=Vxt5e0Osvvt2gflwSlsJ5DmPGcPvTRKLJyp031rXjhgr=k6oisD67M2DonEly12tPl4mv6QNKvRUg1Gi7o9Bf5-Mm=cMBVfEV7A6dD3kTHFli18PJVWaBo6gPxhky1xou4zBIs=V0Xi7OGRVckxukXKbpLoeHrbIfgAhpwO3pULTXbLxPge=.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


git polling saw a lot of connection error

2014-08-11 Thread Grace Lee

Hi,

We often saw git server connection error when doing git polling in Jenkins. But 
we didn’t see this error outside of Jenkins.

We have 144 Jenkins projects doing SCM polling, while 136 of them doing git 
polling.

I had ‘Max #of concurrent polling’ configured to be 40 or 60, they didn’t make 
much of difference.

(I also did side-by-side monitor of the git polling log for same project on 
production Jenkins server and test server for about an hour . Only on the 
production server, the git connection error was seen. Both the servers are on 
same version of Jenkins and plugins. But on test server only this project was 
enabled.)

Does anyone have any suggestion on how to resolve the git connection issue on 
SCM polling?

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: How do I prevent Workspaces from being automatically deleted.

2012-08-23 Thread W. Grace Lee
Is there a way to configure longer keep time for a workspace (job)?



--
View this message in context: 
http://jenkins.361315.n4.nabble.com/How-do-I-prevent-Workspaces-from-being-automatically-deleted-tp956386p4638503.html
Sent from the Jenkins users mailing list archive at Nabble.com.