Laravel-backup: Backup wont upload to s3

[gergo2007]

Hi

I get an error message after a while that: Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.

My backup is 220 MBs.

Thank you

[freekmurze]

Could you check if you're having the same problem on another system? Good change is probably related to something with the server you're trying it on now.

[inlinkz]

First of all thank you for the awesomely easy lib!

I am having the same problem and I can confirm it happens from different systems.

It started happening 2 days ago with a 50MB backup.

While it runs wonderfully up to the creation of the zip (and the local save), when the disk is s3,
it produces the following:

Copying zip failed because: An exception occurred while uploading parts to a multipart upload. The following parts had errors: - Part 1: Error executing "UploadPart" on "https://example.s3.amazonaws.com/https---example.com/2017-07-05-10-47-51.zip?partNumber=1&uploadId=AOHXHJK9bhs76VjhegSo9Q3HiUsTxeW9EXWcNktu5uyQ7x1RWgLtNFA049IUimeb9Z4uQiqwdd336TLRN7t2vw--"; AWS HTTP error: Client error: PUT https://example.s3.amazonaws.com/https---example.com/2017-07-05-10-47-51.zip?partNumber=1&uploadId=AOHXHJK9bhs76VjhegSo9Q3HiUsTxeW9EXWcNktu5uyQ7x1RWgLtNFA049IUimeb9Z4uQiqwdd336TLRN7t2vw-- resulted in a 400 Bad Request response:
<?xml version="1.0" encoding="UTF-8"?>
<Code>RequestTimeout</Code><Message>Your socket connection to the server w (truncated...)
 RequestTimeout (client): Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. - <?xml version="1.0" encoding="UTF-8"?>
<Code>RequestTimeout</Code><Message>Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.</Message><RequestId>43D7743701C57F31</RequestId><HostId>zLkhMnCpku5DTidKgWuzD7Zcy+673l3RDg8mpDV6gSQzQCLV2Hrv4Ht5AkiIBcqnGi4/scsSvCA=</HostId>

This happens on the writeStream command on BackupDestination file.

Everything else I use through the S3 library, works/uploads normally.

Let me know if I can provide any additional info!

Thanks again!

[gergo2007]

Same error on another server.

[freekmurze]

Hi, I just tried this with one of my applications, and it worked perfectly.

If you found the problem / solution, report it back here.

[aaronhuisinga]

We are all of a sudden experiencing this same issue on our production server as well when trying to run our daily backups. The DB is properly dumped and GZipped. It's properly saving locally, but doesn't properly upload to AWS. We're on Ubuntu 16.04.

[aaronhuisinga]

@freekmurze It looks like this might have something to do with the latest release of the AWS SDK package for PHP. Upgrading to v3.31.0 causes backups to fail, but when I downgrade back to v3.30.4 they work again.

https://github.com/aws/aws-sdk-php/releases

The newest AWS PHP SDK release notes a bunch of changes to the multipart uploads to S3, so I'm not sure if there was something breaking that we'll need to update for, or if there's an actual bug in the latest release.

[gergo2007]

I can also confirm that with v3.30.4 works fine.

[freekmurze]

@aaronhuisinga I think it's best to open up an issue at their repo.

[ghost]

I can also confirm this to be an issue.

[graphem]

Yes same here. Seems to be issue with AWS update, running 3.31.1

[graphem]

This has been fixed in AWS 3.31.3

[freekmurze]

Great, thanks for letting me and the other users of this package know.

[graphem]

Thanks to you to all the amazing packages you put out there, they are priceless!

[kstich]

Thanks to everyone who raised this issue and brought it to our attention over on the AWS PHP SDK!

[jsartisan]

experiencing this issue occasionally. any solution for this? My backup is around 4gb.