Another CLI question

[Richard Ginga]

I see a thread happening on CLI issues. I have a different question/issue and do not want to hijack that other discussion.

when running any cli in a pipeline script I an getting below but the command works

00:04:11.368 + java -jar /Users/jenkins/Downloads/jenkins-cli.jar -noKeyAuth -s https://stt-jenkins.disruptorbeam.com/ -auth rginga:xxxxxxxxxx connect-node perf-test-client3
00:04:28.597 Oct 04, 2017 9:52:34 AM hudson.cli.CLI$5 run
00:04:28.597 WARNING: null
00:04:28.597 java.io.IOException: Stream is closed
00:04:28.597 	at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:3512)
00:04:28.597 	at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:3486)
00:04:28.597 	at java.io.DataOutputStream.writeInt(DataOutputStream.java:197)
00:04:28.597 	at hudson.cli.PlainCLIProtocol$EitherSide.send(PlainCLIProtocol.java:175)
00:04:28.597 	at hudson.cli.PlainCLIProtocol$ClientSide.sendEndStdin(PlainCLIProtocol.java:347)
00:04:28.597 	at hudson.cli.CLI$5.run(CLI.java:679)
00:04:28.597 

--

Dick Ginga

Build Engineer

rgi...@disruptorbeam.com

[Richard Ginga]

is anybody out there?

my script syntax for this is 

        cmd = 'java -jar ~/Downloads/jenkins-cli.jar -noKeyAuth -s https://stt-jenkins.disruptorbeam.com/ -auth rginga:0793b086e3c9272ddeb0daff1093518c connect-node ' + params.NODENAME

        st = sh(returnStatus: true, script: cmd)

        

[Michael Pailloncy]

If you run this very same command directly on the Jenkins server and without reaching it through your reverse proxy, does it work ?

I'm wondering if it's not related to the configuration of your reverse proxy. As described in this documentation, you need to ensure that it doesn't buffer request/response bodies when serving Jenkins through HTTPS.

Hopefully it helps.

--
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+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAL3PpaU2vJiaU65icq6vBNwBs%3D7_%3DvG_a4_tOq_vdVxHbLo4Ug%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Richard Ginga]

Hi Michael, thanks for the response, nothing in my nginx configuration indicates any buffering explicitly one way or the other.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPO77c2yn_VvCtXNbeA9R27E2yNm8xb2_PTn1UEK-0ocoTHvXw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Riccardo Foschia]

Am 04.10.2017 um 22:37 schrieb Richard Ginga:
> Hi Michael, thanks for the response, nothing in my nginx configuration
> indicates any buffering explicitly one way or the other.
>

Richard, just in case you are using any kind of anti-virus software on
the machine executing the CLI commands, it's probably an issue with an
anti-virus software (as in the other thread with CLI issues you didn't
wan't to hijack ;-) ): try to disable the scanning of HTTP responses in
your anti-virus software.


You should also try to enable logging in the CLI client like this:

java -jar jenkins-cli.jar -noKeyAuth -s
https://stt-jenkins.disruptorbeam.com/ -logging FINE connect-node ....

>
> On Wed, Oct 4, 2017 at 3:17 PM, Michael Pailloncy <
> michael....@gmail.com> wrote:
>
>> If you run this very same command directly on the Jenkins server and
>> without reaching it through your reverse proxy, does it work ?
>> I'm wondering if it's not related to the configuration of your reverse
>> proxy. As described in this documentation

>> <https://jenkins.io/doc/book/managing/cli/#http-connection-mode>, you

>> need to ensure that it doesn't buffer request/response bodies when serving
>> Jenkins through HTTPS.
>>
>> Hopefully it helps.
>>
>> 2017-10-04 19:01 GMT+02:00 Richard Ginga <rgi...@disruptorbeam.com>:
>>
>>> is anybody out there?
>>>
>>> my script syntax for this is
>>>
>>> cmd = 'java -jar ~/Downloads/jenkins-cli.jar -noKeyAuth -s
>>> https://stt-jenkins.disruptorbeam.com/ -auth
>>> rginga:0793b086e3c9272ddeb0daff1093518c connect-node ' + params.NODENAME
>>> st = sh(returnStatus: true, script: cmd)
>>>
>>>
>>>
>>> On Wed, Oct 4, 2017 at 10:08 AM, Richard Ginga <rgi...@disruptorbeam.com>
>>> wrote:
>>>
>>>> I see a thread happening on CLI issues. I have a different
>>>> question/issue and do not want to hijack that other discussion.
>>>>
>>>> when running any cli in a pipeline script I an getting below but the
>>>> command works
>>>>

>>>> *00:04:11.368* + java -jar /Users/jenkins/Downloads/jenkins-cli.jar -noKeyAuth -s https://stt-jenkins.disruptorbeam.com/ -auth rginga:xxxxxxxxxx connect-node perf-test-client3
>>>>
>>>> *00:04:28.597* Oct 04, 2017 9:52:34 AM hudson.cli.CLI$5 run*00:04:28.597* WARNING: null*00:04:28.597* java.io.IOException: Stream is closed*00:04:28.597* at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:3512)*00:04:28.597* at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:3486)*00:04:28.597* at java.io.DataOutputStream.writeInt(DataOutputStream.java:197)*00:04:28.597* at hudson.cli.PlainCLIProtocol$EitherSide.send(PlainCLIProtocol.java:175)*00:04:28.597* at hudson.cli.PlainCLIProtocol$ClientSide.sendEndStdin(PlainCLIProtocol.java:347)*00:04:28.597* at hudson.cli.CLI$5.run(CLI.java:679)*00:04:28.597*

>>>>
>>>> --
>>>> Dick Ginga
>>>> Build Engineer
>>>> rgi...@disruptorbeam.com
>>>>
>>>>
>>>
>>>
>>> --
>>> Dick Ginga
>>> Build Engineer
>>> rgi...@disruptorbeam.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-use...@googlegroups.com.

>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-users/CAL3PpaU2vJiaU65icq6vBNwBs%3D7_%3DvG_a4_
>>> tOq_vdVxHbLo4Ug%40mail.gmail.com

>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAL3PpaU2vJiaU65icq6vBNwBs%3D7_%3DvG_a4_tOq_vdVxHbLo4Ug%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .

>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> 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-use...@googlegroups.com.

>> To view this discussion on the web visit https://groups.google.com/d/

>> msgid/jenkinsci-users/CAPO77c2yn_VvCtXNbeA9R27E2yNm8xb2_
>> PTn1UEK-0ocoTHvXw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAPO77c2yn_VvCtXNbeA9R27E2yNm8xb2_PTn1UEK-0ocoTHvXw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .

>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>

--

META-LEVEL Software AG
Lyonerring 1
66121 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: in...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 166667
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats: Reinhard Kuhn

[Daniel Beck]

> On 4. Oct 2017, at 22:37, Richard Ginga <rgi...@disruptorbeam.com> wrote:
>
> nothing in my nginx configuration indicates any buffering explicitly one way or the other.

Time to re-read the first snippet in https://wiki.jenkins.io/display/JENKINS/Jenkins+behind+an+NGinX+reverse+proxy