Hi George, Yes that's correct - it's happened once outside of deployments.
To answer your questions sir: - We require a custom PHP installation in order to make use of modules that are missing from Google's offering. I've not checked the latest list of extension but it may be that we may be able to move back to using the standard PHP image so I'll check this for sure. - Scaling is another challenge that we're looking and we're certainly aware that we need to move to auto scaling for contingency etc... - I'll test configuring the readiness check and report back if we notice any difference in behaviour. Were the logs helpful? I'd be grateful if you could shed some light on the investigation your end. This is the first time we've noticed an issue such as this during the maintenance process, which should be innocuous and invisible to us. At this point I'm unsure if the issues we face during deployments are related to the incident that happened with our running app, which continue to occur daily. It's worth noting that the behaviour of the VM is identical (in the way of the abrupt restarts as it's trying to boot). I may look at trying a test deployment using another image and seeing if that helps. Many thanks again, Karl On Wednesday, February 28, 2018 at 12:52:06 AM UTC, George (Cloud Platform Support) wrote: > > Hello Karl, > > You seem to indicate that the outage is a one-time event, and that there > is no other similar occurrence as yet. If this is so, to prevent similar > unwanted events in future, you may configure your app for health checks, in > detail. For reference, the "Configuring your App with app.yaml" should > prove of great help. In your app.yaml, you can specify either liveness > check (choosing appropriate parameter values): > > liveness_check: > path: "/liveness_check" > check_interval_sec: 30 > timeout_sec: 4 > failure_threshold: 2 > success_threshold: 2 > > or readiness check: > > readiness_check: > path: "/readiness_check" > check_interval_sec: 5 > timeout_sec: 4 > failure_threshold: 2 > success_threshold: 2 > app_start_timeout_sec: 300 > > It is worthwhile noting that the usual way of specifying PHP for you app > is: > > runtime: php //This setting is required. It is the name of the App > Engine language runtime used by this application. To specify PHP, use php > env: flex > > You app uses: runtime: custom , by contrast. > > You may also switch to automatic scaling from manual, and one only > instance. If this makes a difference in your app's behavior, the > information would help us with debugging. > > > -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/11910416-8d95-437c-886c-d2e6748d47f2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
