[GH-ISSUE #238] Upload fails with "Broken Pipe" #784

Closed
opened 2026-03-15 10:25:24 +03:00 by kerem · 14 comments
Owner

Originally created by @pwoolcoc on GitHub (Oct 13, 2017).
Original GitHub issue: https://github.com/asciinema/asciinema/issues/238

Hello, I've been able to record & upload sessions before, but last night I started getting an error when uploading:

image

The file is still present at the path shown in the screenshot, and every so often I've tried re-uploading it, but get the same results.

My recording was a few minutes long, so I thought maybe it is too big? Here are the relevant stats:

image

Also, my error is not quite the same as the one in https://github.com/asciinema/asciinema/issues/235, but I tried the fix from that issue anyway, with no change.

Originally created by @pwoolcoc on GitHub (Oct 13, 2017). Original GitHub issue: https://github.com/asciinema/asciinema/issues/238 Hello, I've been able to record & upload sessions before, but last night I started getting an error when uploading: ![image](https://user-images.githubusercontent.com/620392/31564083-9813e2bc-b02f-11e7-9cf0-dda4f8d227e7.png) The file is still present at the path shown in the screenshot, and every so often I've tried re-uploading it, but get the same results. My recording was a few minutes long, so I thought maybe it is too big? Here are the relevant stats: ![image](https://user-images.githubusercontent.com/620392/31564215-008f2b76-b030-11e7-8990-c4cbd8354ee7.png) Also, my error is not quite the same as the one in https://github.com/asciinema/asciinema/issues/235, but I tried the fix from that issue anyway, with no change.
kerem closed this issue 2026-03-15 10:25:29 +03:00
Author
Owner

@pwoolcoc commented on GitHub (Oct 13, 2017):

One more thing, since getting that error I have tried making new recordings (much shorter ones) and they upload just fine. Could it just be a file size issue?

<!-- gh-comment-id:336554165 --> @pwoolcoc commented on GitHub (Oct 13, 2017): One more thing, since getting that error I have tried making new recordings (much shorter ones) and they upload just fine. Could it just be a file size issue?
Author
Owner

@ku1ik commented on GitHub (Oct 18, 2017):

Yes, this may be file size issue, however in such case you probably should get better error message saying exactly this. What's the filesize of the one that fails?

<!-- gh-comment-id:337478252 --> @ku1ik commented on GitHub (Oct 18, 2017): Yes, this may be file size issue, however in such case you probably should get better error message saying exactly this. What's the filesize of the one that fails?
Author
Owner

@pwoolcoc commented on GitHub (Oct 18, 2017):

@sickill it's about 13M

<!-- gh-comment-id:337709192 --> @pwoolcoc commented on GitHub (Oct 18, 2017): @sickill it's about 13M
Author
Owner

@ku1ik commented on GitHub (Oct 24, 2017):

Yeah, so the instance at asciinema.org has a limit of 5MB. It's weird though you didn't get better error message, as we actually handle this case here: https://github.com/asciinema/asciinema/blob/develop/asciinema/api.py#L62 The server should nicely respond with 413 in this case. Maybe there's some proxy on the way which is killing requests with big payloads...?

<!-- gh-comment-id:339109725 --> @ku1ik commented on GitHub (Oct 24, 2017): Yeah, so the instance at asciinema.org has a limit of 5MB. It's weird though you didn't get better error message, as we actually handle this case here: https://github.com/asciinema/asciinema/blob/develop/asciinema/api.py#L62 The server should nicely respond with 413 in this case. Maybe there's some proxy on the way which is killing requests with big payloads...?
Author
Owner

@pwoolcoc commented on GitHub (Oct 27, 2017):

@sickill not that I'm aware of. One time I tried it while connected to my work's VPN, but I also tried it while just on my regular home network. Same result both times.

<!-- gh-comment-id:340060597 --> @pwoolcoc commented on GitHub (Oct 27, 2017): @sickill not that I'm aware of. One time I tried it while connected to my work's VPN, but I also tried it while just on my regular home network. Same result both times.
Author
Owner

@ku1ik commented on GitHub (Oct 28, 2017):

Ok. What's the asciinema version this happens on? And what's your OS/distro?

<!-- gh-comment-id:340158584 --> @ku1ik commented on GitHub (Oct 28, 2017): Ok. What's the asciinema version this happens on? And what's your OS/distro?
Author
Owner

@ku1ik commented on GitHub (Nov 28, 2017):

@pwoolcoc If it's still an issue for you then let's dig deeper, you could try latest version from develop branch (https://github.com/asciinema/asciinema#running-latest-version-from-source-code-checkout).

Otherwise let's close it.

<!-- gh-comment-id:347649055 --> @ku1ik commented on GitHub (Nov 28, 2017): @pwoolcoc If it's still an issue for you then let's dig deeper, you could try latest version from `develop` branch (https://github.com/asciinema/asciinema#running-latest-version-from-source-code-checkout). Otherwise let's close it.
Author
Owner

@richard-mauri commented on GitHub (Dec 17, 2018):

I hit this today too ....

Richards-MacBook:vaultssh richardmauri$ asciinema --version
asciinema 2.0.1

Richards-MacBook:vaultssh richardmauri$ ls -lh /var/folders/4k/h9xhvv6j1yg6dzncz3r5s1x80000gn/T/tmps_0q0ve6-ascii.cast
-rw------- 1 richardmauri staff 1.3M Dec 17 06:06 /var/folders/4k/h9xhvv6j1yg6dzncz3r5s1x80000gn/T/tmps_0q0ve6-ascii.cast

Richards-MacBook:vaultssh richardmauri$ asciinema upload /var/folders/4k/h9xhvv6j1yg6dzncz3r5s1x80000gn/T/tmps_0q0ve6-ascii.cast
asciinema: upload failed: <urlopen error [Errno 32] Broken pipe>
asciinema: retry later by running: asciinema upload /var/folders/4k/h9xhvv6j1yg6dzncz3r5s1x80000gn/T/tmps_0q0ve6-ascii.cast

<!-- gh-comment-id:447859477 --> @richard-mauri commented on GitHub (Dec 17, 2018): I hit this today too .... Richards-MacBook:vaultssh richardmauri$ asciinema --version asciinema 2.0.1 Richards-MacBook:vaultssh richardmauri$ ls -lh /var/folders/4k/h9xhvv6j1yg6dzncz3r5s1x80000gn/T/tmps_0q0ve6-ascii.cast -rw------- 1 richardmauri staff 1.3M Dec 17 06:06 /var/folders/4k/h9xhvv6j1yg6dzncz3r5s1x80000gn/T/tmps_0q0ve6-ascii.cast Richards-MacBook:vaultssh richardmauri$ asciinema upload /var/folders/4k/h9xhvv6j1yg6dzncz3r5s1x80000gn/T/tmps_0q0ve6-ascii.cast asciinema: upload failed: <urlopen error [Errno 32] Broken pipe> asciinema: retry later by running: asciinema upload /var/folders/4k/h9xhvv6j1yg6dzncz3r5s1x80000gn/T/tmps_0q0ve6-ascii.cast
Author
Owner

@occivink commented on GitHub (Dec 18, 2018):

Same here, I hit a 'broken pipe' with a 3MB file.

<!-- gh-comment-id:448263181 --> @occivink commented on GitHub (Dec 18, 2018): Same here, I hit a 'broken pipe' with a 3MB file.
Author
Owner

@ku1ik commented on GitHub (Dec 18, 2018):

That was server-side issue. It's fixed now. Sorry for inconvenience!

<!-- gh-comment-id:448364267 --> @ku1ik commented on GitHub (Dec 18, 2018): That was server-side issue. It's fixed now. Sorry for inconvenience!
Author
Owner

@richard-mauri commented on GitHub (Dec 19, 2018):

Thanks
I am again able to upload !

On Dec 18, 2018, at 12:46 PM, Marcin Kulik notifications@github.com wrote:

That was server-side issue. It's fixed now. Sorry for inconvenience!


You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/asciinema/asciinema/issues/238#issuecomment-448364267, or mute the thread https://github.com/notifications/unsubscribe-auth/AObO4yiJGca3CLvb0PjB260JJrYtvmHpks5u6VQsgaJpZM4P4_Qu.

<!-- gh-comment-id:448441386 --> @richard-mauri commented on GitHub (Dec 19, 2018): Thanks I am again able to upload ! > On Dec 18, 2018, at 12:46 PM, Marcin Kulik <notifications@github.com> wrote: > > That was server-side issue. It's fixed now. Sorry for inconvenience! > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub <https://github.com/asciinema/asciinema/issues/238#issuecomment-448364267>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AObO4yiJGca3CLvb0PjB260JJrYtvmHpks5u6VQsgaJpZM4P4_Qu>. >
Author
Owner

@pinpox commented on GitHub (Jan 9, 2019):

Having this error again, still an issue?

<!-- gh-comment-id:452693243 --> @pinpox commented on GitHub (Jan 9, 2019): Having this error again, still an issue?
Author
Owner

@lblasc commented on GitHub (Feb 7, 2019):

Today I'm having the same issue, cast is only 1.2M big.

<!-- gh-comment-id:461338484 --> @lblasc commented on GitHub (Feb 7, 2019): Today I'm having the same issue, cast is only 1.2M big.
Author
Owner

@ku1ik commented on GitHub (Mar 17, 2019):

We have related issue open, let's continue there: #335

<!-- gh-comment-id:473660766 --> @ku1ik commented on GitHub (Mar 17, 2019): We have related issue open, let's continue there: #335
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/asciinema#784
No description provided.