Jump to content

Potential contamination of storage


Numbered
 Share

Recommended Posts

Today I watched some stats and see some interesting:

Clip2net_180130160227.thumb.png.01d71e4b29ca754883db7427ee63888a.png

very flat line of storage consumption. This is not possible in the case of user activity. And off course, I went to study this issue :lol:

First I checked the directory with logs. This dir empty (bacause we not store logs in storage :lol:). Second stage - i get the size of imageproxy folder:

Clip2net_180130160749.png.ce68d853f4b716efbf4cd317687aeafd.png

Hmmm... so much. Actually we didn't set any expire date for them. So it should store all files - it's okay. But.

49d825ee89b67a064b7e68461bd41c44.png.d0484bf7b137582c50c0ded0697b1b6a.png

Hmm.. let's check how many files we stored..

Clip2net_180130163807.png.bafdf7d1fccf7940783b70a8c30e9d45.png

I tried to put Xzibit image here (got it from google image).. and didn't know why it's not embed. Just a red field error. Ok.. Forget it)
6a7c7ee61bef029250695c87a91b202e.thumb.png.5d7edc96266cd51658b7a234967a0431.png

 

Ok. Stop fun. Let's investigate it. At first i create temp amazon s3 bucket and configure it in my IPS docker container. I has 4 members with letter photos. After configure they images moved to new bucket. Ok. After thet i upload a profile image and got error... Ok. May be my environment issue. Let's try again. Second try was success and original and thumb image stored well. But! My image which i try to upload at first time stored too. It's not deleted. And letter photo of user not deleted too. Ok. Let's switch back to 'no photo' = letter photo. Thumb and original image deleted well. First error image stored. So, i think you already understand the problem.

Clip2net_180130164439.thumb.png.e4579127f0184b8b0047f4aa49e34999.png

This is basically enough to ask the guys to figure out the error. But you know me. I love to goo deeper and help to solve source of problem. Let's see that code:

Clip2net_180130163428.thumb.png.13fbbe8078a5cd5d52b4a4c34f743d5a.png

We have just two error handlers. First - if the responce code is not 200 and second - only for specific error \IPS\Http\Request\Exception. Of something other happened - nothing will logged. On production forums i have 0 errors of that lines. I am sure there are a lot of situations, when something happend bad (i remember that problems). But nothing logged.

So first proposal - improve this error catching. It's important to controll and understand current health.

I'll investigate what actuall error i got in response there and post it here soon.

Thanks for you attension :thumbsup:

Edited by Upgradeovec
Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...