Concetti fondamentali di Google Cloud: introduzione a Deployment Manager e Cloud Monitoring recensioni

Mazen A. · Recensione inserita quasi 6 anni fa

Devan O. · Recensione inserita quasi 6 anni fa

Mohamed Rabik A. · Recensione inserita quasi 6 anni fa

Martin N. · Recensione inserita quasi 6 anni fa

Pradeep A. · Recensione inserita quasi 6 anni fa

Rajan B. · Recensione inserita quasi 6 anni fa

nice

sagar g. · Recensione inserita quasi 6 anni fa

Preeti T. · Recensione inserita quasi 6 anni fa

okay

Vybhav E. · Recensione inserita quasi 6 anni fa

Ledio R. · Recensione inserita quasi 6 anni fa

Mudassarnazar M. · Recensione inserita quasi 6 anni fa

Saurav N. · Recensione inserita quasi 6 anni fa

Mudassarnazar M. · Recensione inserita quasi 6 anni fa

ok

Lakshmi P. · Recensione inserita quasi 6 anni fa

Sarah S. · Recensione inserita quasi 6 anni fa

Eduardo L. · Recensione inserita quasi 6 anni fa

jacksonkelly@adt.com J. · Recensione inserita quasi 6 anni fa

Dorota Z. · Recensione inserita quasi 6 anni fa

Fernando L. · Recensione inserita quasi 6 anni fa

Love it!!!!!!!!!!

Jorge E. · Recensione inserita quasi 6 anni fa

Пашко О. · Recensione inserita quasi 6 anni fa

Ok

Varaprasad G. · Recensione inserita quasi 6 anni fa

Anthony S. · Recensione inserita quasi 6 anni fa

An error occurred during the lab. When I run a command " curl -sSO https://dl.google.com/cloudagents/install-logging-agent.sh sudo bash install-logging-agent.sh " Error details: 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 Wed 2020-11-25 15:53:29 UTC; 14ms ago Docs: man:systemd-sysv-generator(8) Process: 3475 ExecStart=/etc/init.d/google-fluentd start (code=exited, status=1/FAILURE) Nov 25 15:53:29 my-vm google-fluentd[3475]: from /opt/google-fluentd/embedded/lib/ruby/gems/2.6.0/gems/fluentd-1.11.2/bin/fluentd:8:in `<top (required)>' Nov 25 15:53:29 my-vm google-fluentd[3475]: from /opt/google-fluentd/embedded/bin/fluentd:23:in `load' Nov 25 15:53:29 my-vm google-fluentd[3475]: from /opt/google-fluentd/embedded/bin/fluentd:23:in `<top (required)>' Nov 25 15:53:29 my-vm google-fluentd[3475]: from /usr/sbin/google-fluentd:7:in `load' Nov 25 15:53:29 my-vm google-fluentd[3475]: from /usr/sbin/google-fluentd:7:in `<main>' Nov 25 15:53:29 my-vm google-fluentd[3475]: google-fluentd ... failed! Nov 25 15:53:29 my-vm systemd[1]: google-fluentd.service: Control process exited, code=exited status=1 Nov 25 15:53:29 my-vm systemd[1]: Failed to start LSB: data collector for Treasure Data. Nov 25 15:53:29 my-vm systemd[1]: google-fluentd.service: Unit entered failed state. Nov 25 15:53:29 my-vm systemd[1]: google-fluentd.service: Failed with result 'exit-code'. 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.

Borys B. · Recensione inserita quasi 6 anni fa

had issues after updating yaml file bur managed to sort. log agent would not install, tried deleting vm and re-creating. also could not see cpu in metrics although i could see my_vm in dashboard

Gavin H. · Recensione inserita quasi 6 anni fa