report.CRITICAL: Unable to unserialize value, string is corrupted.

Question

report.CRITICAL: Unable to unserialize value, string is corrupted.

jobrandon opened this issue 6 years ago · 16 comments

Hi,

I execute the bin/magento s3:storage:export
and got this error.
{"exception":"[object] (InvalidArgumentException(code: 0): Unable to unserialize value, string is corrupted. at /var/www/html/stg/vendor/magento/framework/Serialize/Serializer/Serialize.php:38)"} []

Answer 1 · 2018-06-28T07:06:31.000Z

Hi @jobrandon,
This might have been caused by an old bug that should be addressed by the latest version. Can you confirm what version you're using?
Regards,
Thai

Answer 2 · 2018-06-28T07:07:34.000Z

Magento version 2.2.3. I found out that the problem is a unserializing the custom headers.

Answer 3 · 2018-06-28T07:08:44.000Z

Have you resolved the problem or do you still need assistance?

Answer 4 · 2018-06-28T07:10:37.000Z

My solution was a quick fix. I removed the custom header which actually not necessary for my use.

Answer 5 · 2018-06-28T07:15:45.000Z

Then I got this message. Is this related to the fix?

<?xml version=\"1.0\" encoding=\"UTF-8\"?> <Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>2EC08E0523DBAF47</RequestId><HostId>a/MrVnQgp2Yhm1jrl9AbXtcigMGSK8lbfswr4wEGQxln/G7Pb+lWrAbzLbGPGLrmu4Elvs3maZ0=</HostId></Error> at /var/www/html/vendor/aws/aws-sdk-php/src/WrappedHttpHandler.php:191, GuzzleHttp\\Exception\\ClientException(code: 403): Client error: PUT https://s3.ap-southeast-1.amazonaws.com/images-app.testing.com/assets/external/images/icons/icons_48-browsing-white.png` resulted in a 403 Forbidden response:

AccessDeniedAccess Denied2EC08E (truncated...)
at /var/www/html/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113)"} []
[2018-06-28 06:41:18] report.CRITICAL: Error executing "PutObject" on "https://s3.ap-southeast-1.amazonaws.com/images-app.testing.com/assets/external/images/icons/icons_48-browsing-white.png"; AWS HTTP error: Client error: PUT https://s3.ap-southeast-1.amazonaws.com/images-app.testing.com/assets/external/images/icons/icons_48-browsing-white.png resulted in a 403 Forbidden response:`

Answer 6 · 2018-06-28T12:11:47.000Z

That reads like your S3 credentials are incorrect. Can you review s3:config:list and see if everything is correct?

Answer 7 · 2018-06-28T12:12:44.000Z

Thanks!, it works fine now. The only thing now is the custom header whenever necessary to use it.

Answer 8 · 2018-06-29T02:26:13.000Z

Hey @jobrandon

Yeah, I'm planning on adding some new CLI tools for that as well eventually. Good to see everything is working now!

I'll be closing this ticket then.

Best of luck with your store.

Regards,

Thai

Answer 9 · 2018-08-12T14:56:42.000Z

Hi @jobrandon,

how you resoled this issue. i am also getting same issue.

report.CRITICAL: Unable to unserialize value, string is corrupted. {"exception":"[object] (InvalidArgumentException(code: 0): Unable to unserialize value, string is corrupted. at /spdata/specapps/vansdev4/vendor/magento/framework/Serialize/Serializer/Serialize.php:38)"} []

Thanks
Poonam

Answer 10 · 2018-08-12T14:57:59.000Z

Hi @thaiphan ,

Can you please suggest, how i can fix this issue.

Thanks

Answer 11 · 2018-08-17T07:19:38.000Z

Hi @jobrandom

Could you please let us know how you resolved that access denied issue

I have set $meta['ACL' =>'public-write']; in s3.php
But still issue persist

@thai you please also suggest the solution

Thanks

Answer 12 · 2018-08-17T07:23:12.000Z

Hi @vijaydcyb Try this one
Thai\S3\Model\MediaStorage\File\Storage\S3

public function getMetadata()
{
	$meta = [];
	/*$headers = $this->helper->getCustomHeaders();
	if ($headers) {
		$unserializedHeaders = $this->serializer->unserialize($headers);
		foreach ($unserializedHeaders as $header) {
			$meta[$header['header']] = $header['value'];
		}
	}*/
	return $meta;
}

Answer 13 · 2018-08-17T08:05:05.000Z

Hi @jobrandon

Hi already tried this. Commented the code but while adding images from admin it throws the access denied error

The credentials are correct ones

Answer 14 · 2018-10-11T02:24:12.000Z

hi @jobrandon
Thanks that worked for me.

Answer 15 · 2018-10-14T05:25:25.000Z

Hi @jobrandon, @cybpoonam, @keyurbhagat80

Sorry for taking so long to get back to you!

As described in #55, I have pushed up v1.3.2 that should hopefully resolve this problem. Can you update to the latest version of the extension and tell me if it's working now?

Regards,

Thai

Answer 16 · 2018-10-25T02:49:58.000Z

I'm closing this ticket. If problems persist, feel free to reply here or open a new ticket!