Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,462,949
Community Members
 
Community Events
176
Community Groups

(Some) artifacts can not be downloaded

I have a plan in bamboo which runs some tests, compile a file and produces some logs and pdf reports. All of these files should be available as an artifact which we can download if/when needed.

However, we experience a problem where only some of the artifacts can be downloaded. The binary file and text-files works. However, the pdf report and a zip file does not - for some reason I cannot understand.

The files are located in the correct artifact folder on the server, and I can see that the GET url matches the folder on the server, but the server seems to just close the connection when trying to access the file.

It should be noted that our Bamboo server is running on a windows xp machine.

Here is a wget-request for the our pdf file:

=============================================

user-7457@EX-LT-52:~$ wget --debug --verbose http://10.2.4.145:8085/browse/MAT-MTT-76/artifact/RMT/test-report.pdf/test-r
eport.pdf
Setting --verbose (verbose) to 1
DEBUG output created by Wget 1.17.1 on linux-gnu.

Reading HSTS entries from /home/bottiger/.wget-hsts
URI encoding = ‘UTF-8’
--2018-05-22 10:34:48--  http://10.2.4.145:8085/browse/MAT-MTT-76/artifact/RMT/test-report.pdf/test-report.pdf
Connecting to 10.2.4.145:8085... connected.
Created socket 3.
Releasing 0x00007fffe0129320 (new refcount 0).
Deleting unused 0x00007fffe0129320.

---request begin---
GET /browse/MAT-MTT-76/artifact/RMT/test-report.pdf/test-report.pdf HTTP/1.1
User-Agent: Wget/1.17.1 (linux-gnu)
Accept: */*
Accept-Encoding: identity
Host: 10.2.4.145:8085
Connection: Keep-Alive

---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
X-ASEN: SEN-11879269
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Expires: Wed, 22 May 2019 08:34:48 GMT
Cache-Control: max-age=31536000
Cache-Control: public
Last-Modified: Tue, 22 May 2018 07:54:21 GMT
Content-disposition: attachment; filename="test-report.pdf"
Content-Type: application/pdf
Content-Length: 126984
Date: Tue, 22 May 2018 08:34:48 GMT

---response end---
200 OK
Registered socket 3 for persistent reuse.
Length: 126984 (124K) [application/pdf]
Saving to: ‘test-report.pdf.2’

test-report.pdf.2              98%[================================================> ] 122.63K  --.-KB/s    in 0.001s

2018-05-22 10:34:48 (179 MB/s) - Connection closed at byte 125575. Retrying.

--2018-05-22 10:34:49--  (try: 2)  http://10.2.4.145:8085/browse/MAT-MTT-76/artifact/RMT/test-report.pdf/test-report.pdf
Disabling further reuse of socket 3.
Closed fd 3
Connecting to 10.2.4.145:8085... connected.
Created socket 3.
Releasing 0x00007fffe0129120 (new refcount 0).
Deleting unused 0x00007fffe0129120.

---request begin---
GET /browse/MAT-MTT-76/artifact/RMT/test-report.pdf/test-report.pdf HTTP/1.1
Range: bytes=125575-
User-Agent: Wget/1.17.1 (linux-gnu)
Accept: */*
Accept-Encoding: identity
Host: 10.2.4.145:8085
Connection: Keep-Alive

---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
X-ASEN: SEN-11879269
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Expires: Wed, 22 May 2019 08:34:49 GMT
Cache-Control: max-age=31536000
Cache-Control: public
Last-Modified: Tue, 22 May 2018 07:54:21 GMT
Content-disposition: attachment; filename="test-report.pdf"
Content-Type: application/pdf
Content-Length: 126984
Date: Tue, 22 May 2018 08:34:49 GMT

---response end---
200 OK
Registered socket 3 for persistent reuse.
Length: 126984 (124K) [application/pdf]
Saving to: ‘test-report.pdf.2’

test-report.pdf.2              98%[================================================> ] 122.63K  --.-KB/s    in 0.02s

2018-05-22 10:34:49 (6.86 MB/s) - Connection closed at byte 125575. Retrying.

1 answer

Simon says:

" From the debug output above I can see that the size of the PDF file in bytes is: Content-Length: 126984

and the transfer stops after transferring 125575 bytyes. There is a single tcp segment left to transfer of 1409 bytes payload.

Does the transfer of the zip file also stop at the last TCP segment ?

Do you have any antivirus on the machine you are downloading the pdf file to? If so please temporarily disable the antivirus. (Or alternatively change the configuration to accept pdf and zip files).

"

Simon out.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events