Elevated Images Service Errors

73 views
Skip to first unread message

David Fischer

unread,
Feb 22, 2016, 4:57:53 PM2/22/16
to Google App Engine
I'm seeing elevated error levels with the request to "get_serving_url" and for completely valid images and formats (PNGs and JPGs). It is not failing 100% but I'm seeing errors at a much higher rate than normal. I've had about 100 errors in the past hour and it started about an hour ago.

Is anyone else seeing the same?

While testing this, I uploaded PNGs taken directly as screenshots and still saw the problem. These images do not cause the same problem on the dev appserver and I'm unable to reproduce it locally. Interestingly enough, it took about 3 minutes to post my 51kb image to this post. That might be unrelated.


Traceback (most recent call last):
 
File "/base/data/home/apps/.../views.py", line xxx,
 
in ajax_upload_image
    url_thumbnail
= images.get_serving_url(files[0].key(), size=150,
secure_url
=True)
 
File
"/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/images/__init__.py",
 line
1794, in get_serving_url
   
return rpc.get_result()
 
File
"/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/apiproxy_stub_map.py",
 line
613, in get_result
   
return self.__get_result_hook(self)
 
File
"/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/images/__init__.py",
 line
1892, in get_serving_url_hook
   
raise _ToImagesError(e, readable_blob_key)
TransformationError


Screen Shot 2016-02-22 at 1.41.49 PM.png

John Lowry

unread,
Feb 22, 2016, 5:19:49 PM2/22/16
to Google App Engine
Hi,

Google Cloud support here.

Just to confirm that we did have an incident that caused elevated errors for the get_serving_url() API call starting at 12:50 PST today.

We have applied a fix and the error rate has been steadily decreasing since 13:25.

I will post to this thread if we have any significant updates.

John Lowry

David Fischer

unread,
Feb 22, 2016, 5:36:20 PM2/22/16
to Google App Engine
Thanks for the update, John.
Reply all
Reply to author
Forward
0 new messages