Backups failing with ERR_STREAM_WRITE_AFTER_END
-
@peter-newman this is maybe the same as already reported https://git.cloudron.io/cloudron/box/-/issues/779
-
@peter-newman is this with linode object storage? I am trying to figure what the correct fix is with the upstream authors at https://github.com/aws/aws-sdk-js/issues/3404
-
Alright, I found the issue.
Linode Object Storage has some strange behavior with
Expect: 101-continue
. You can see a more detailed analysis at https://www.linode.com/community/questions/21180/object-storage-upload-err_stream_write_after_end-write-after-end and https://github.com/aws/aws-sdk-js/issues/3404#issuecomment-805448190At this point, I need either aws-js-sdk or linode guys to tell me who is wrong
-
@peter-newman As a workaround, you can try this:
# cd /home/yellowtent/box # sudo -u yellowtent npm install git+https://github.com/cloudron-io/aws-sdk-js.git#continue_once # systemctl restart box
I think it will take a while for AWS or Linode to sort out the issue. If you try the workaround, let me know if it makes things work.
-
@girish said in Backups failing with ERR_STREAM_WRITE_AFTER_END:
npm install git+https://github.com/cloudron-io/aws-sdk-js.git#continue_once
This has worked for me.
Just as a note, I had to
su yellowtent
rather thansudo
, as NPM kept complaining about root owned cache files (sinceHOME
was still pointing at/root/
). Just in case anyone else needs to follow these instructions. -
AWS team merged the PR https://github.com/aws/aws-sdk-js/pull/3674 . So, linode object storage should get fixed next release (6.3).