BeeIMG Blog

We faced some blackouts recently, and it was because we got very popular in china. The images that was generating lot of traffic were violating our TOS, but as they were generating lot of traffic and I thought it was a good time to stress test our image delivery systems. At first we were handling the load fine. after some time our redis server start acting wired. the issue was with dumping the db to disk, but as the images were generating lot of data the redis server crashed. we started to migrate the all gif images to be served by our CDN while still collecting views data. but at some point our real time stats handling script started to fail due to redis connection issues. after that the data started to collect and the redis server crashed every time it was started. While all that was happening we noticed that our php front end started throwing errors. this was due the connectivity issues to our redis server. The image serving end do not use redis server and was not afflicted. its usi...

below is the post mortem report of the October 6 outage. Our server had an outage at 13:30 GMT due to a high trafficked image. ( http://beeimg.com/view/h8150456397/ ) according to the referral logs the image was linked to several "LiveJournal" blogs. The outage was recorded by pingdom at 13:31 GMT. ( http://stats.pingdom.com/pdc110r2vx7j/889337/2014/10 ) I was notified about this outage at 13:36 GMT via SMS (Email too) by Pingdom. Which then I quickly went online and started investigating this issue.( https://twitter.com/beeimg/status/519120005695537152 ) Normally whole server is monitored and if the Apache server is crashed, it automatically get restarted. during this outage the whole server got crashed making the monitoring mechanism useless. the server was returning pings, meaning the server was accessible, but was under high load. I gave the server a hard reboot at 13:50 GMT via DigitalOcean CP and the server was back online 13:52 GMT. The server was completely inaccessib...

below is the post mortem report of the October 6 outage. Our server had an outage at 13:30 GMT due to a high trafficked image. ( http://beeimg.com/view/h8150456397/ ) according to the referral logs the image was linked to several "LiveJournal" blogs. The outage was recorded by pingdom at 13:31 GMT. ( http://stats.pingdom.com/pdc110r2vx7j/889337/2014/10 ) I was notified about this outage at 13:36 GMT via SMS (Email too) by Pingdom. Which then I quickly went online and started investigating this issue.( https://twitter.com/beeimg/status/519120005695537152 ) Normally whole server is monitored and if the Apache server is crashed, it automatically get restarted. during this outage the whole server got crashed making the monitoring mechanism useless. the server was returning pings, meaning the server was accessible, but was under high load. I gave the server a hard reboot at 13:50 GMT via DigitalOcean CP and the server was back online 13:52 GMT. The server was completely inaccessib...

Hello readers, We were offline for nearly 4 days due to budgetary problems. I have taken measures to NOT to make budgetary problems in the future. you can help us buy donating via paypal, and even small $1 helps. :) During the blackout I was able to develop some more codes, which includes user image deletion. furthermore I am planning to add AJAX to the image view page, and to use gravatar for the user profiles. Also there has been some spamming on the site, uploading the same image over and over using bulk uploader. which lead me to limit the number of uploads in the new upload page which I will soon finish. I working with PHP MD5 to stop this spamming but it will take some time because the uploader needs to work properly at all the time. It will increase the image upload time, use more MySQL queries and may overload the MySQL sever. Thanks for reading this Article :)