gcloud - Google App Engine service (module) not starting, and flooding 404's to /_ah/start -


i'm refactoring existing codebase. switched using appcfg.py using gcloud command, seemed go fine. our entire codebase running on 1 default frontend instance, i'm trying break services. start, created 1 "worker" backend service, , i'm using cron job test.

i can see worker in console, no instance started. logs service rapidly flooded 404's /_ah/start. i've tried manual , basic scaling. documentation states it's okay not have startup script, , 404 @ endpoint considered success. however, instance not starting.

logs logs rapidly filling 404's

worker.yaml

service: worker runtime: python27 api_version: 1 instance_class: b2 manual_scaling:         instances: 1 threadsafe: false  handlers: - url: /work/.*   script: worker.app   secure:   login: admin 

worker.py

import webapp2 import handlers  config = {     #... }  app = webapp2.wsgiapplication([     webapp2.route(         '/work/test<:/?>',         handlers.test,         methods=['get'],     ), ], debug=true, config=config) 

dispatch.yaml

dispatch:      - url: "*/work/*"     module: worker 


Comments

Popular posts from this blog

javascript - Slick Slider width recalculation -

jsf - PrimeFaces Datatable - What is f:facet actually doing? -

angular2 services - Angular 2 RC 4 Http post not firing -