OK, I think I've been getting lucky for years. It appears I'm supposed to be updating jenkins-cli.jar as jenkins is updated (happening from yum update all, but it's not me doing it so I don't think about it). Updating the jenkins client, I'll respond how that worked in a bit. Thanks!
On Tuesday, June 25, 2019 at 8:12:58 AM UTC-6, Eric Fetzer wrote: > > This makes no sense. When I run the command: > > java -cp /my/path/to/jar/jenkins-cli.jar -s http://myJenkinsServer:8080 > -i /my/key/id_rsa help > > I get: > > Neither -s nor the JENKINS_URL env var is specified. > Jenkins CLI > Usage: java -jar jenkins-cli.jar [-s URL] command [opts...] args... > Options: > -s URL : the server URL (defaults to the JENKINS_URL env var) > -i KEY : SSH private key file used for authentication > -p HOST:PORT : HTTP proxy host and port for HTTPS proxy tunneling. See > http://jenkins-ci.org/https-proxy-tunnel > -noCertificateCheck : bypass HTTPS certificate check entirely. Use with > caution > -noKeyAuth : dont try to load the SSH authentication private key. > Conflicts with -i > > The available commands depend on the server. Run the help command to > see the list. > > > So I figure I'll play, and set the env variable even though the -s was in > there plain as day. So I do: > > export JENKINS_URL='http://my.JenkinsServer:8080' > java -cp /my/path/to/jar/jenkins-cli.jar -jar > /my/path/to/jar/jenkins-cli.jar -i /my/key/id_rsa help > > I get: > > > Exception in thread "main" java.io.IOException: Failed to connect to > http://my.JenkinsServer:8080/ > at hudson.cli.CLI.getCliTcpPort(CLI.java:271) > at hudson.cli.CLI.<init>(CLI.java:126) > at > hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) > at hudson.cli.CLI._main(CLI.java:471) > at hudson.cli.CLI.main(CLI.java:387) > Caused by: java.net.UnknownHostException: my.JenkinsServer > at > java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:175) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:384) > at java.net.Socket.connect(Socket.java:543) > at java.net.Socket.connect(Socket.java:492) > at sun.net.NetworkClient.doConnect(NetworkClient.java:178) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:417) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:519) > at sun.net.www.http.HttpClient.<init>(HttpClient.java:203) > at sun.net.www.http.HttpClient.New(HttpClient.java:296) > at sun.net.www.http.HttpClient.New(HttpClient.java:315) > at > sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1004) > at > sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:940) > at > sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:858) > at hudson.cli.CLI.getCliTcpPort(CLI.java:269) > ... 4 more > > > A week ago I had no issues whatsoever. Both of these servers were patched > since then. Both servers are RHEL 6.10. Jenkins version 2.176.1. Any > ideas of what my sudden issue could be or where to start trouble shooting > this? > > Thanks, > Eric > -- 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/90dcf58e-8998-4e9e-b7db-b20ab9e8fbf9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
