For information about how to identify the cause of the error to start up the backend

[linkseed]

/ 301 is returned in the _ah / start, seems to fail to start.

In such a case, what do I do to identify the cause in any way.

- Once the back-end, Stop -> Shutdown -> Start.

- Dynamic Instance type of a back-end - change to> Resident.

- Update the application again on the back end.

- Set new alias the back-end.

- Purge of the task that was piled up in the back end.

 (On the back end is processing a task only)

But I went like, however, it does not improve.

Application configuration is as follows.

In addition, I have attached a screenshot of the management screen.

application: hoge

version: 1

runtime: python27

api_version: 1

threadsafe: true

inbound_services:

- warmup

backends:

- name: backends

  class: B1

  options: dynamic

  instances: 1

Professor Helps to enjoy later.

[Robert Kluin]

Hi,
Have you tried to define a warmup handler? You just need something
to handle that request.
http://code.google.com/appengine/docs/python/config/appconfig.html#Warmup_Requests

Robert

> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/roiwXoBiO7sJ.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengi...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.

[linkseed]

Thank you for advice.

  Have you tried to define a warmup handler?  You just need something
to handle that request. 

 I tried to define, the results did not change.

Was the same even if you change to an undefined further.

[Robert Kluin]

Could you include your app.yaml and corresponding url mapping for the
warmup request?

Robert

> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/google-appengine/-/25mbdIqDkGAJ.

[linkseed]

Could you include your app.yaml and corresponding url mapping for the
warmup request?

Do you need something other than this description to app.yaml?

inbound_services:

- warmup

[Robert Kluin]

That will cause a request to /_ah/warmup. As I recall, you should
handle that. The whole point in warmup requests is to give you a way
to initialize your app.

Robert

> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/google-appengine/-/7_pUTOL7L-MJ.

[linkseed]

I have a script for initialization, and you hook up to the start of backends, was successful to start the backend.

backends.yaml

backends:

- name: backend

  class: B1

  options: dynamic

  instances: 1

  start: warmup.py

But, in the hook to the warmup, you could not be started.

You need to make carefully advice many times, thank you very much.

[Robert Kluin]

Sorry, I'm not sure I understand. Are you saying you got this working
or that it still isn't working? If it isn't working, what errors are
you getting in your logs?

Robert

> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/google-appengine/-/WcrGwDtL9MkJ.

[linkseed]

The script for loading a library was prepared and it set to /_ah/warmup. 

However, the error did not change. 

*For more information, please look at the attached image of the first post.

(app.yaml)

- url: /_ah/warmup

  script: warmup.app

When I specified "warmup.app" as start handler, it succeeded in starting of the backend. 

(backends.yaml)

backends:

- name: backend

  class: B1

  options: dynamic

  instances: 1

  start: warmup.py

Sorry...