Hi Rich,
As Amit mentioned in his last comment I would recommend you to open an Issue Tracker <https://issuetracker.google.com/issues/new?component=491371&template=1161230> for yourself with your own information (project ID, App Engine deployment debug logs (with using --verbosity=debug <https://cloud.google.com/sdk/gcloud/reference/#--verbosity>), Cloud Build logs,the reproduction steps, etc) as even if the error can look the same root cause can be different. Thanks! On Wednesday, June 26, 2019 at 10:59:30 AM UTC-4, Rich Vida wrote: > > Hi Brad, were you ever able to get this figured out? I'm currently running > into the same issue. > > On Monday, November 5, 2018 at 8:38:54 AM UTC-5, Brad Kilshaw wrote: >> >> 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 >> >> >> >> >> >> >> >> For reference, here is the relevant section of the composer.json: >> >> >> "scripts": { >> "post-root-package-install": [ >> "php -r \"copy('.env.example', '.env');\"" >> ], >> "post-create-project-cmd": [ >> "php artisan key:generate" >> ], >> "post-autoload-dump": [ >> "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump", >> "@php artisan package:discover" >> ], >> "post-install-cmd": [ >> "Illuminate\\Foundation\\ComposerScripts::postInstall", >> "chmod -R 755 bootstrap/cache", >> "php artisan cache:clear", >> "php artisan config:clear" >> ] >> } >> >> >> >> 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? >> >> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/c80aea0f-0ea4-4f84-ab69-d50366071a2a%40googlegroups.com.
