I have three servers all running debian. 2 of which are jispconfig and virtualmin servers that are having the same problem. Strangely enough, the third server which is running vestacp doesnt appear to have the same issue?? These servers all use different control panels but are all google cloud compute (micro) instances. The virtualmin server is debian 9 Ispconfig server is debian 8.9 Vestacp server is debian 8.9 (this is the only one where the google cloud sdk update works) On one of the servers (virtualmin), i increased its resources to a "Standard" instance (17.GB memory and 1 vcpu), this did not help. I am not sure how to correct this error...its causing a lot of problems because whever any installation, update, or upgrade is performed it ties up the system for a long long time before moving on. Setting up google-cloud-sdk (175.0.0-0) ... Generating the gcloud CLI and caching in [/usr/lib/google-cloud-sdk/.install/cli/gcloud.py]. ..-Killed dpkg: error processing package google-cloud-sdk (--configure): subprocess installed post-installation script returned error exit status 137 Setting up apt-transport-https (1.4.8) ... Errors were encountered while processing: google-cloud-sdk E: Sub-process /usr/bin/dpkg returned an error code (1) A second update and upgrade later produced the following error... Setting up google-cloud-sdk (175.0.0-0) ... /var/lib/dpkg/info/google-cloud-sdk.postinst: line 8: 788 Killed HOME="$tempdir" /usr/bin/gcloud components post-process dpkg: error processing package google-cloud-sdk (--configure): subprocess installed post-installation script returned error exit status 137 Errors were encountered while processing: google-cloud-sdk E: Sub-process /usr/bin/dpkg returned an error code (1)
For at least one of my servers this issue was resolved by increasing system resources whilst updating...and reducing them back to my desired ones after updating google cloud sdk.
