SOLVED Backups failing with ERR_STREAM_WRITE_AFTER_END
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-805448190
At this point, I need either aws-js-sdk or linode guys to tell me who is wrong
I submitted a PR at https://github.com/aws/aws-sdk-js/pull/3674
@girish Ah, great - I'm one of the comments on that thread as well. That's an interesting problem.
@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.
I opened a linode support ticket #15378267 if anyone wants to take this up with linode.
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 yellowtentrather than
sudo, as NPM kept complaining about root owned cache files (since
HOMEwas 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).
For completeness, the working instructions is:
# cd /home/yellowtent/box # sudo -u yellowtent npm install firstname.lastname@example.org # systemctl restart box