The first 500 error is likely the backend getting allocated and built by the GAE scheduler. The subsequent 503s indicate that there may be a problem with the backend application.
Are you sure that there are no logs? Try going into the logs page, and using the dropdown box in the middle of the page. It has separate entries for frontend version log and backend version logs. Is the backend log entry selected? ----------------- -Vinny P Technology & Media Advisor Chicago, IL My Go side project: http://invalidmail.com/ On Friday, April 26, 2013 11:08:20 AM UTC-5, GAEfan wrote: > > Must be something simple I'm missing out of the docs... I have set up a > backend, but cannot access it. I have the backend running (see > screenshot), but if I click the link, or access it by > <backend-name>.<app-name>.appspot.com (or with 0. prefix), it throws a > 503: > > Error: Server ErrorThe service you requested is not available yet. > > Please try again in 30 seconds. > > (BTW... When I first hit it, it gave a 500, like it was inaccessible. On > subsequent hts, it gives the 503) > backends.py: > > backends: > - name: backend-name > class: B2 > instances: 1 > options: dynamic, public > > Since I see it as running in the dashboard, there is no need to start/stop > it via appcfg, correct? > > Nothing shows up in the logs, so not sure how to proceed to troubleshoot. > > Thanks. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
