I am trying to upload a 30 GB file to Amazon S3 using the AWS PHP SDK.
require('../vendor/autoload.php');
$client = new Aws\S3\S3Client([
'version' => 'latest',
'region' => 'us-east-1'
]);
$bucket_name = 'My-new-bucket';
$file_name = 'S3_www_1443369605.zip';
try {
$client->upload($bucket_name, $file_name, fopen($file_name, 'rb'), 'public-read');
echo "File has been uploaded";
} catch(Exception $e) {
echo "File upload error: $e";
}
I am getting the following error after the script has run for about 2 hours:
2015-09-28 23:48:22 - File upload error: exception 'Aws\Exception\MultipartUploadException' with message 'An exception occurred while uploading parts to a multipart upload. The following parts had errors: - Part 560: Error executing "UploadPart" on "http://ift.tt/1MWEJSA"; AWS HTTP error: cURL error 56: SSL read: error:00000000:lib(0):func(0):reason(0), errno 104 (see http://ift.tt/1mgwZgQ) (server): 100 Continue - - Part 1285: Error executing "UploadPart" on "http://ift.tt/1RcVpUC"; AWS HTTP error: cURL error 56: SSL read: error:00000000:lib(0):func(0):reason(0), errno 104 (see http://ift.tt/1mgwZgQ) (server): 100 Continue - - Part 1429: Error executing "UploadPart" on "http://ift.tt/1MWEMO0"; AWS HTTP error: cURL error 56: SSL read: error:00000000:lib(0):func(0):reason(0), errno 104 (see http://ift.tt/1mgwZgQ) (server): 100 Continue - - Part 1572: Error executing "UploadPart" on "http://ift.tt/1RcVqYF"; AWS HTTP error: Client error: 400 RequestTimeout (client): Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. -
RequestTimeoutYour socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.6BEC8DF91606DF30NxhmBOBd/rSPtXvmYyzsyjXVY9yxneFB0FMs6lyRryxxOoc2ZeRP27k+f4DkpX3G - Part 1573: Error executing "UploadPart" on "http://ift.tt/1MWEKpm"; AWS HTTP error: Client error: 400 RequestTimeout (client): Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. -RequestTimeoutYour socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.272146C78077924BEqhJPwmAIgNBGdj4TvxOcIaD1JA6qIad1vFWW6+C6IiCl7lCyU7sfb09e5qTDDvx - Part 1574: Error executing "UploadPart" on "http://ift.tt/1RcVqaU"; AWS HTTP error: cURL error 28: Connection timed out after 286198 milliseconds (see http://ift.tt/1mgwZgQ) - Part 1575: Error executing "UploadPart" on "http://ift.tt/1MWEKpo"; AWS HTTP error: cURL error 28: Connection timed out after 347552 milliseconds (see http://ift.tt/1mgwZgQ) - Part 1576: Error executing "UploadPart" on "http://ift.tt/1RcVreV"; AWS HTTP error: cURL error 28: Connection timed out after 347552 milliseconds (see http://ift.tt/1mgwZgQ) - Part 1577: Error executing "UploadPart" on "http://ift.tt/1MWEMO3"; AWS HTTP error: cURL error 55: SSL_write() returned SYSCALL, errno = 32 (see http://ift.tt/1mgwZgQ) (client): 400 Bad Request (Request-ID: 3661520AE3994ED6) - - Part 1578: Error executing "UploadPart" on "http://ift.tt/1RcVreZ"; AWS HTTP error: cURL error 55: SSL_write() returned SYSCALL, errno = 32 (see http://ift.tt/1mgwZgQ) (client): 400 Bad Request (Request-ID: 712FF19818857C63) - - Part 1580: Error executing "UploadPart" on "http://ift.tt/1MWEKpu"; AWS HTTP error: cURL error 28: Resolving timed out after 255566 milliseconds (see http://ift.tt/1mgwZgQ) - Part 1582: Error executing "UploadPart" on "http://ift.tt/1RcVrf1"; AWS HTTP error: Client error: 400 RequestTimeout (client): Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. -RequestTimeoutYour socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.1FE5DBFFFE78CBBD+fM9TeEjRhUxcbxPzAkZ9uv5yz/tTlABVfjylq0l2aLgaY2zETABlvNJmlKAOccqCX3xfl/t0UA= - Part 1583: Error executing "UploadPart" on "http://ift.tt/1MWEKpw"; AWS HTTP error: Client error: 400 RequestTimeout (client): Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. -RequestTimeoutYour socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.42427D58F4C1B723WYAZT3F7Zb0zInnKfEsZ46fYuHiMQ3gjVVMWFVCLKdzvFLHNYSjJ970yMtWkwhgX6gdqYpPUmT0= - Part 1584: Error executing "UploadPart" on "http://ift.tt/1RcVrf4"; AWS HTTP error: cURL error 52: Empty reply from server (see http://ift.tt/1mgwZgQ) - Part 1585: Error executing "UploadPart" on "http://ift.tt/1MWEKpy"; AWS HTTP error: cURL error 35: Unknown SSL protocol error in connection to s3.amazonaws.com:443 (see http://ift.tt/1mgwZgQ) - Part 1586: Error executing "UploadPart" on "http://ift.tt/1RcVqb0"; AWS HTTP error: cURL error 35: Unknown SSL protocol error in connection to s3.amazonaws.com:443 (see http://ift.tt/1mgwZgQ) - Part 1615: Error executing "UploadPart" on "http://ift.tt/1MWEMOa"; AWS HTTP error: Client error: 400 RequestTimeout (client): Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. -RequestTimeoutYour socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.20198435D3C4445A4rSMxm75tBfDfc1jcGB35iYMRz0wwMI4n7uekgW8IEUjFJT+5moppego4wbzIL1LxeQA4ZM1/88= - Part 1619: Error executing "UploadPart" on "http://ift.tt/1RcVqb4"; AWS HTTP error: cURL error 56: SSL read: error:00000000:lib(0):func(0):reason(0), errno 104 (see http://ift.tt/1mgwZgQ) (server): 100 Continue - - Part 1617: Error executing "UploadPart" on "http://ift.tt/1MWEMOc"; AWS HTTP error: cURL error 56: SSL read: error:00000000:lib(0):func(0):reason(0), errno 104 (see http://ift.tt/1mgwZgQ) (server): 100 Continue - - Part 1744: Error executing "UploadPart" on "http://ift.tt/1RcVrf7"; AWS HTTP error: cURL error 56: SSL read: error:00000000:lib(0):func(0):reason(0), errno 104 (see http://ift.tt/1mgwZgQ) (server): 100 Continue - - Part 1860: Error executing "UploadPart" on "http://ift.tt/1MWEKpC"; AWS HTTP error: cURL error 56: SSL read: error:00000000:lib(0):func(0):reason(0), errno 104 (see http://ift.tt/1mgwZgQ) (server): 100 Continue - - Part 3322: Error executing "UploadPart" on "http://ift.tt/1MWEKpE"; AWS HTTP error: Client error: 400 RequestTimeout (client): Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. -RequestTimeoutYour socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.999CEBF77A9F9B65uM19WpqUdM4xtFzx64saG28b4ZbMT+r7wMUxdJbHqo9ue4A0JrfSDpKzr1bPx2Sf - Part 3509: Error executing "UploadPart" on "http://ift.tt/1RcVrfb"; AWS HTTP error: cURL error 56: SSL read: error:00000000:lib(0):func(0):reason(0), errno 104 (see http://ift.tt/1mgwZgQ) (server): 100 Continue - - Part 3513: Error executing "UploadPart" on "http://ift.tt/1MWEKFS"; AWS HTTP error: cURL error 56: SSL read: error:00000000:lib(0):func(0):reason(0), errno 104 (see http://ift.tt/1mgwZgQ) (server): 100 Continue - - Part 3869: Error executing "UploadPart" on "http://ift.tt/1RcVqrm"; AWS HTTP error: cURL error 56: SSL read: error:00000000:lib(0):func(0):reason(0), errno 104 (see http://ift.tt/1mgwZgQ) (server): 100 Continue - - Part 3909: Error executing "UploadPart" on "http://ift.tt/1MWEKFV"; AWS HTTP error: Client error: 400 RequestTimeout (client): Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. -RequestTimeoutYour socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.19DD76BFEA8BAD65zuCKmopCCVjVSbQMKW5RwF1XesF6ra3BvoHHTKfZG2CCPMBvOpxXT6kUioxaa8mK - Part 4179: Error executing "UploadPart" on "http://ift.tt/1RcVqrq"; AWS HTTP error: cURL error 52: Empty reply from server (see http://ift.tt/1mgwZgQ) - Part 4235: Error executing "UploadPart" on "http://ift.tt/1RcVrvs"; AWS HTTP error: Client error: 400 RequestTimeout (client): Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. -RequestTimeoutYour socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.A0E8C2D2F04B7F94GlXHDS46iry5XlYJY90aFT38ceGsCUL+96F4tpV96wHLN15jtZtxm22x89CMBRjG - Part 4456: Error executing "UploadPart" on "http://ift.tt/1MWEMOi"; AWS HTTP error: cURL error 55: SSL_write() returned SYSCALL, errno = 32 (see http://ift.tt/1mgwZgQ) (client): 400 Bad Request (Request-ID: 97DA77193B81F7BF) - - Part 4478: Error executing "UploadPart" on "http://ift.tt/1RcVrvx"; AWS HTTP error: cURL error 35: Unknown SSL protocol error in connection to s3.amazonaws.com:443 (see http://ift.tt/1mgwZgQ) - Part 4476: Error executing "UploadPart" on "http://ift.tt/1MWEN4w"; AWS HTTP error: Client error: 400 RequestTimeout (client): Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. -RequestTimeoutYour socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.289C02F755195F44YzOaPEuyKXWBy7ROcjyR4E+ayTnEXuSox54OUgOBeHTTl8K1U10S07SI4V4uo3MI - Part 4494: Error executing "UploadPart" on "http://ift.tt/1RcVrvz"; AWS HTTP error: cURL error 55: SSL_write() returned SYSCALL, errno = 104 (see http://ift.tt/1mgwZgQ) (client): 400 Bad Request (Request-ID: F85D869ECA9E370C) - - Part 4507: Error executing "UploadPart" on "http://ift.tt/1MWEKFZ"; AWS HTTP error: cURL error 56: SSL read: error:00000000:lib(0):func(0):reason(0), errno 104 (see http://ift.tt/1mgwZgQ) (server): 100 Continue - - Part 4506: Error executing "UploadPart" on "http://ift.tt/1RcVrvD"; AWS HTTP error: Client error: 400 RequestTimeout (client): Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. -RequestTimeoutYour socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.8268F4193D4F4BCAR4JMpQGtet5Sah3OVdTZxXOP9eILKN1FZI607pu/Jghw0gRR7HDowp+8zMWGLzQL - Part 4508: Error executing "UploadPart" on "http://ift.tt/1MWEN4C"; AWS HTTP error: cURL error 55: SSL_write() returned SYSCALL, errno = 104 (see http://ift.tt/1mgwZgQ) (server): 100 Continue - ' in /var/www/AWS/vendor/aws/aws-sdk-php/src/Multipart/AbstractUploader.php:130 Stack trace:0 [internal function]: Aws\Multipart\AbstractUploader::Aws\Multipart{closure}()
1 /var/www/AWS/vendor/guzzlehttp/promises/src/functions.php(484): Generator->send(NULL)
2 /var/www/AWS/vendor/guzzlehttp/promises/src/Promise.php(199): GuzzleHttp\Promise{closure}(NULL)
3 /var/www/AWS/vendor/guzzlehttp/promises/src/Promise.php(152): GuzzleHttp\Promise\Promise::callHandler(1, NULL, Array)
4 /var/www/AWS/vendor/guzzlehttp/promises/src/TaskQueue.php(60): GuzzleHttp\Promise\Promise::GuzzleHttp\Promise{closure}()
5 /var/www/AWS/vendor/guzzlehttp/guzzle/src/Handler/CurlMultiHandler.php(96): GuzzleHttp\Promise\TaskQueue->run()
6 /var/www/AWS/vendor/guzzlehttp/guzzle/src/Handler/CurlMultiHandler.php(123): GuzzleHttp\Handler\CurlMultiHandler->tick()
7 /var/www/AWS/vendor/guzzlehttp/promises/src/Promise.php(240): GuzzleHttp\Handler\CurlMultiHandler->execute(true)
8 /var/www/AWS/vendor/guzzlehttp/promises/src/Promise.php(217): GuzzleHttp\Promise\Promise->invokeWaitFn()
9 /var/www/AWS/vendor/guzzlehttp/promises/src/Promise.php(261): GuzzleHttp\Promise\Promise->waitIfPending()
10 /var/www/AWS/vendor/guzzlehttp/promises/src/Promise.php(219): GuzzleHttp\Promise\Promise->invokeWaitList()
11 /var/www/AWS/vendor/guzzlehttp/promises/src/Promise.php(261): GuzzleHttp\Promise\Promise->waitIfPending()
12 /var/www/AWS/vendor/guzzlehttp/promises/src/Promise.php(219): GuzzleHttp\Promise\Promise->invokeWaitList()
13 /var/www/AWS/vendor/guzzlehttp/promises/src/Promise.php(62): GuzzleHttp\Promise\Promise->waitIfPending()
14 /var/www/AWS/vendor/aws/aws-sdk-php/src/Multipart/AbstractUploader.php(86): GuzzleHttp\Promise\Promise->wait()
15 /var/www/AWS/vendor/aws/aws-sdk-php/src/S3/S3Client.php(417): Aws\Multipart\AbstractUploader->upload()
16 /var/www/AWS/s3/04-upload_backup.php(15): Aws\S3\S3Client->upload('Server3-27-SEP-...', 'S3_www_14433696...', Resource id 76, 'public-read')
17 {main}
Please help.
Aucun commentaire:
Enregistrer un commentaire