Opinie (Google Cloud Fundamentals: Getting Started with Deployment Manager and Cloud Monitoring)

It worked very well.

Madhu C. · Sprawdzono prawie 6 lat temu

Gargi K. · Sprawdzono prawie 6 lat temu

Rana F. · Sprawdzono prawie 6 lat temu

Vishal G. · Sprawdzono prawie 6 lat temu

NIMITHA J. · Sprawdzono prawie 6 lat temu

Daniel R. · Sprawdzono prawie 6 lat temu

Shelly J. · Sprawdzono prawie 6 lat temu

Romnick C. · Sprawdzono prawie 6 lat temu

Theres-preme J. · Sprawdzono prawie 6 lat temu

nikki b. · Sprawdzono prawie 6 lat temu

● google-fluentd.service - LSB: data collector for Treasure Data Loaded: loaded (/etc/init.d/google-fluentd; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2020-11-24 15:04:58 UTC; 15ms ago Docs: man:systemd-sysv-generator(8) Process: 3067 ExecStart=/etc/init.d/google-fluentd start (code=exited, status=1/FAILURE) Nov 24 15:04:58 my-vm google-fluentd[3067]: from /opt/google-fluentd/embedded/lib/ruby/gems/2.6.0/g…ired)>' Nov 24 15:04:58 my-vm google-fluentd[3067]: from /opt/google-fluentd/embedded/bin/fluentd:23:in `load' Nov 24 15:04:58 my-vm google-fluentd[3067]: from /opt/google-fluentd/embedded/bin/fluentd:23:in `<t…ired)>' Nov 24 15:04:58 my-vm google-fluentd[3067]: from /usr/sbin/google-fluentd:7:in `load' Nov 24 15:04:58 my-vm google-fluentd[3067]: from /usr/sbin/google-fluentd:7:in `<main>' Nov 24 15:04:58 my-vm google-fluentd[3067]: google-fluentd ... failed! Nov 24 15:04:58 my-vm systemd[1]: google-fluentd.service: Control process exited, code=exited status=1 Nov 24 15:04:58 my-vm systemd[1]: Failed to start LSB: data collector for Treasure Data. Nov 24 15:04:58 my-vm systemd[1]: google-fluentd.service: Unit entered failed state. Nov 24 15:04:58 my-vm systemd[1]: google-fluentd.service: Failed with result 'exit-code'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package google-fluentd (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of google-fluentd-catch-all-config: google-fluentd-catch-all-config depends on google-fluentd (>= 1.3.0); however: Package google-fluentd is not configured yet. dpkg: error processing package google-fluentd-catch-all-config (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: google-fluentd google-fluentd-catch-all-config E: Sub-process /usr/bin/dpkg returned an error code (1) Job for google-fluentd.service failed because the control process exited with error code. See "systemctl status google-fluentd.service" and "journalctl -xe" for details. ============================================================================== Errors occurred while installing google-fluentd-1.8.4-1. See the log snippet above or run: sudo service google-fluentd status ==============================================================================

Петро Д. · Sprawdzono prawie 6 lat temu

per l. · Sprawdzono prawie 6 lat temu

Rana F. · Sprawdzono prawie 6 lat temu

There was an issue with the procedures in step 4 under the Create a Monitoring workspace section.

Billy K. · Sprawdzono prawie 6 lat temu

It is about Monitoring... It is not clear how to select CPU usage for VM instance and actually it does not show any charts just : "No data is available for the selected time frame."

ivan. t. · Sprawdzono prawie 6 lat temu

Koh M. · Sprawdzono prawie 6 lat temu

ALEXANDER A. · Sprawdzono prawie 6 lat temu

Wojtek H. · Sprawdzono prawie 6 lat temu

michael s. · Sprawdzono prawie 6 lat temu

ivan. t. · Sprawdzono prawie 6 lat temu

mohammad m. · Sprawdzono prawie 6 lat temu

Atelier obsolète ou bugué. Obligé de rajouter cette commande pour déployer sinon erreur sur le projet : gcloud config set project qwiklabs-gcp-02-1d9cbdd3585a Plus variable non fonctionnelle. Plus erreur de déploiement du script install-logging-agent.sh Conffile /etc/google-fluentd/google-fluentd.conf has been modified. Remain untouched. Job for google-fluentd.service failed because the control process exited with error code. See "systemctl status google-fluentd.service" and "journalctl -xe" for details. invoke-rc.d: initscript google-fluentd, action "start" failed. ● google-fluentd.service - LSB: data collector for Treasure Data Loaded: loaded (/etc/init.d/google-fluentd; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2020-11-24 14:17:04 UTC; 10ms ago Docs: man:systemd-sysv-generator(8) Process: 3977 ExecStart=/etc/init.d/google-fluentd start (code=exited, status=1/FAILURE) Nov 24 14:17:04 my-vm google-fluentd[3977]: from /opt/google-fluentd/embedded/lib/ruby/gems/2.6.0/gems/fluentd-1.11.2/bin/fluentd:8:in `<top (required)>' Nov 24 14:17:04 my-vm google-fluentd[3977]: from /opt/google-fluentd/embedded/bin/fluentd:23:in `load' Nov 24 14:17:04 my-vm google-fluentd[3977]: from /opt/google-fluentd/embedded/bin/fluentd:23:in `<top (required)>' Nov 24 14:17:04 my-vm google-fluentd[3977]: from /usr/sbin/google-fluentd:7:in `load' Nov 24 14:17:04 my-vm google-fluentd[3977]: from /usr/sbin/google-fluentd:7:in `<main>' Nov 24 14:17:04 my-vm systemd[1]: google-fluentd.service: Control process exited, code=exited status=1 Nov 24 14:17:04 my-vm google-fluentd[3977]: google-fluentd ... failed! Nov 24 14:17:04 my-vm systemd[1]: Failed to start LSB: data collector for Treasure Data.

David L. · Sprawdzono prawie 6 lat temu

The second install script failed.

Donald G. · Sprawdzono prawie 6 lat temu

Rushikesh Arjun B. · Sprawdzono prawie 6 lat temu

Lorenzo R. · Sprawdzono prawie 6 lat temu