Google Cloud Fundamentals : Premiers pas avec Cloud Storage et Cloud SQL avis

Kelly E. · Examiné il y a 11 jours

good

Ganesh s. · Examiné il y a 11 jours

Sini R. · Examiné il y a 11 jours

Dániel G. · Examiné il y a 11 jours

Gargi B. · Examiné il y a 11 jours

Lekhana C. · Examiné il y a 11 jours

Awesome!

Hariharan P. · Examiné il y a 11 jours

padmanaban B. · Examiné il y a 11 jours

Ehsan H. · Examiné il y a 11 jours

Sunil N. · Examiné il y a 11 jours

Harold C. · Examiné il y a 11 jours

Startup script provided in the instructions did not install apache because running cd /var/www/html returned a no such file or directory message. Used Gemini to get a new updated script 1. Root Cause: Package Lock Contention The startup script failed because it could not acquire the dpkg lock required to install software. On fresh Google Cloud VMs (specifically Debian/Ubuntu), the system often runs automatic background updates (like unattended-upgrades) immediately upon first boot. The logs show: E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 1152 (apt-get) Because the installation of apache2 failed, the service was never created, and the web server directory (/var/www/html) was never generated. 2. Missing apt-get update Your current script attempts to install packages without first updating the package index: Updated script #!/bin/bash # Wait for any background updates to finish while fuser /var/lib/dpkg/lock-frontend >/dev/null 2>&1 ; do echo "Waiting for other apt-get instances to finish..." sleep 5 done # Update package index and install Apache apt-get update apt-get install apache2 php php-mysql -y # Ensure the service is running systemctl restart apache2 After applying this fix, the vm instance was restarted and apache installed successfully.

Minal P. · Examiné il y a 11 jours

Robert S. · Examiné il y a 11 jours

OWOLABI y. · Examiné il y a 11 jours

Fatma M. · Examiné il y a 11 jours

Excellent lab

David W. · Examiné il y a 11 jours

Ahmed R. · Examiné il y a 11 jours

Leonor L. · Examiné il y a 11 jours

Jaime R. · Examiné il y a 11 jours

Juan Antonio C. · Examiné il y a 11 jours

Todo ok

Javier G. · Examiné il y a 11 jours

Celia L. · Examiné il y a 11 jours

the url throws an error: This site can't be reached. The server is taking too long to respond. The site could be temporarily unavailable or busy.

Celia P. · Examiné il y a 11 jours

Gonzalo D. · Examiné il y a 11 jours

Izuchukwu O. · Examiné il y a 11 jours