Laravel deployment issues

[Brad Kilshaw]

I'm using GAE for a Laravel PHP site and using flex instances. I've always had no problem doing a "gcloud app deploy" to get my app deployed. However, for the last 24 hours or so when I attempt to deploy I get the following error:

Step #1: Package manifest generated successfully.
Step #1: > chmod -R 755 bootstrap/cache
Step #1: > php artisan cache:clear
Step #1: 
Step #1: In AbstractConnection.php line 155:
Step #1:                                               
Step #1:   Connection timed out [tcp://1.2.3.4:6379]  
Step #1:                                               
Step #1: 
Step #1: Script php artisan cache:clear handling the post-install-cmd event returned with error code 1
Step #1: The command '/bin/sh -c /build-scripts/composer.sh' returned a non-zero code: 1
Finished Step #1
ERROR
ERROR: build step 1 "gcr.io/cloud-builders/docker@sha256:12345" failed: exit status 1
Step #1: 
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

ERROR: (gcloud.app.deploy) Cloud build failed. Check logs at https://console.cloud.google.com/gcr/builds/12345?project=1234 Failure status: UNKNOWN: Error Response: [2] Build failed; check build logs for details

I have a Memorystore (redis) instance I use since GAE memcache isn't available on flex instances yet. My app uses redis as a cache, so as you can see above, once the new code is deployed composer is configured to clear the cache, which is where it's timing out and failing.

If I SSH into an existing instance, I can run php artisan cache:clear no problem. However, it's failing on deploy. It's a pretty simple code change that's only UI tweaks (html/javascript) so none of the redis or connection code has changed.

Any ideas?

[Ankit Mihari]

How long does your deploy take ? There is a default timeout with  gcloud app deploy. You many want to pass a higher timeout with gcloud app deploy  if your app deploy takes long that is my guess looking at the connection timeout message?

--
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-appengi...@googlegroups.com.
To post to this group, send email to google-a...@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/ae72db8f-323f-45d5-83a6-feb4afc11745%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Katayoon (Cloud Platform Support)]

I should note that there was an incident had been reported on Google Compute Engine on November 5th. Since VM instances in the flexible environment are Google Compute Engine virtual machines, there is a likelihood that this incident caused the issue. If the issue still persists, I recommend to report it to the Issue Tracker and provide us with the REDACTED output of the "gcloud app deploy --verbosity debug" along with the output of the "gcloud info --anonymize" command to investigate the root cause of the issue.

[Brad Kilshaw]

It's not the GAE deployment that's timing out, it's when my composer's post-install command runs

php artisan cache:clear

This command tries to communicate with Memorystore (redis) and times out because for some reason it's no longer able to communicate with it during the deployment process. This wasn't an issue a week or so ago when the same script deployed just fine.