Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

GAE deploy pagespeed warning

form this morning (January 12 2016) there is a warning message appearing when we deploy to Google App Engine. We don't use PageSpeed so it's surprising that it tries to post something to its URL.

95% Closing update: new version is ready to start serving.
98% Uploading index definitions.
I 12, 2016 10:45:06 DOP. com.google.appengine.tools.admin.AbstractServerConnection send1
WARNING: Error posting to URL: https://appengine.google.com/api/appversion/updatepagespeed?module=yyy&app_id=xxx&version=1&
404 Not Found
You are using a decommissioned API.  Please upgrade to a more recent version of the App Engine SDK which can be found at:https://developers.google.com/appengine/downloads
This is try #0

We use latest GAE SDK (1.9.30), latest gradle appengine plugin (1.9.30) and gradle task that we run is appengineUpdate.

Why is that Pagespeed warning appearing now and wasn't appearing before? How can we get rid of it?

Thanks, Michal

like image 762
michal sankot Avatar asked Jan 12 '16 10:01

michal sankot


4 Answers

I filed a new bug report here:

https://code.google.com/p/googleappengine/issues/detail?id=12665

Please star it if you are affected. This should help fix the problem upstream, at Google.

UPDATE 2016-01-20, FIXED

Quote from Google, see link above:

"This issue is now fixed. Here is a summary of the cause:

The PageSpeed service was switched off on 3rd August. However, the App Engine deployment API continued to have a call for it. A couple of days ago, a new App Engine minor version was released to production, in which this call returns a HTTP 404 and the warning message above. Unfortunately, this App Engine change was released to production before the corresponding change in the App Engine SDK, which is still calling the decommissioned API endpoint. The error message you have received was harmless, the SDK still completed the app deployment.

The SDK team is working on preventative action items that will avoid asynchronous releases."

like image 178
CaptainCrunch Avatar answered Nov 14 '22 05:11

CaptainCrunch


Pagespeed has been decommissioned, that's why you're having these problems(although a bit late then expected as it was decommissioned 1.12.15).

For more info: https://cloud.google.com/appengine/docs/deprecations/pagespeed

Also it's worth checking once in a while: https://cloud.google.com/appengine/docs/deprecations

like image 33
Alonoaky Avatar answered Nov 14 '22 07:11

Alonoaky


Here is a reply from Google on this issue

As people have pointed out above, this is indeed a bug in the SDK — more specifically, an inconsistency between the SDK and the App Engine deployment API. However, it's harmless: the SDK handles the error gracefully, your app deployments will not be affected, and it's safe to ignore the message. If you're using the current SDK (1.9.30 at the time I send this message) then you can safely continue to do so.

The reason for the error is that the "updatepagespeed" call is to be removed from both the API backend and the SDK frontend. Due to an oversight and different release schedules, the API change went out before the SDK change, so the SDK is still invoking the obsolete RPC. Sorry about the noise! Our engineers are fixing the inconsistency, and we'll make a notification here when the fix has been posted.

Dave Hughes, Google Cloud Platform Support

like image 2
nsgulliver Avatar answered Nov 14 '22 07:11

nsgulliver


We had the same problem, and it was partly caused by a pagespeed entry in appengine-web.xml file.

The second warning is caused by a bug in the Google SDK, but it is harmless, the deploy succeeds. (According to the google comments in the link by CaptainCrunch: https://code.google.com/p/googleappengine/issues/detail?id=12665)

like image 1
toadstool Avatar answered Nov 14 '22 06:11

toadstool