terminated the connection. When we bypassed that rule everything worked as
expected, so I just did all my updates and reactivated the rule.
On Tue, Feb 4, 2020 at 8:42 AM Steve Rogers wrote:
> I changed the configuration to point directly to /home/jenkins (plugin
> installs still fail) an
at
> configuration.
>
> On Mon, Feb 3, 2020 at 4:09 PM Steve Rogers wrote:
>
>> Yes, plenty of space and permissions are correct. I should have added in
>> the original that I can install manually by downloading the plugin file
>> directly and then uploading into jenkin
That was my first guess too. I tried with both.
On Mon, Feb 3, 2020 at 7:22 PM Jan Monterrubio
wrote:
>
> Could it be an http vs https problem? We had some of those with maven
> before.
>
> On Mon, Feb 3, 2020 at 16:05 Steve Rogers wrote:
>
>> I'll give that
enkins.
>>
>> On Mon, Feb 3, 2020 at 2:50 PM Mark Waite
>> wrote:
>>
>>> It may be worth checking the directory permissions to confirm that the
>>> Jenkins user can still write to that directory. You may also want to check
>>> that the disc has av
to confirm that the
> Jenkins user can still write to that directory. You may also want to check
> that the disc has available free space and available inodes to allow new
> files to be created.
>
> On Mon, Feb 3, 2020 at 3:42 PM Steve Rogers wrote:
>
>> Any plugin that I try
Any plugin that I try to download results in the following error:
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:210)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(Buf
