GCP Fundamentals: Primeiros passos com Deployment Manager e Cloud Monitoring avaliações

薇 陳. · Revisado há almost 6 years

got an error while installing the logging for stackdriver. Process: 3065 ExecStart=/etc/init.d/google-fluentd start (code=exited, status=1/FAILURE) Nov 19 14:00:56 my-vm google-fluentd[3065]: from /opt/google-fluentd/embedded/lib/ruby/gems/2.6.0/g…ired)>' Nov 19 14:00:56 my-vm google-fluentd[3065]: from /opt/google-fluentd/embedded/bin/fluentd:23:in `load' Nov 19 14:00:56 my-vm google-fluentd[3065]: from /opt/google-fluentd/embedded/bin/fluentd:23:in `<t…ired)>' Nov 19 14:00:56 my-vm google-fluentd[3065]: from /usr/sbin/google-fluentd:7:in `load' Nov 19 14:00:56 my-vm google-fluentd[3065]: from /usr/sbin/google-fluentd:7:in `<main>' Nov 19 14:00:56 my-vm google-fluentd[3065]: google-fluentd ... failed! Nov 19 14:00:56 my-vm systemd[1]: google-fluentd.service: Control process exited, code=exited status=1 Nov 19 14:00:56 my-vm systemd[1]: Failed to start LSB: data collector for Treasure Data. Nov 19 14:00:56 my-vm systemd[1]: google-fluentd.service: Unit entered failed state. Nov 19 14:00:56 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.

Yen Chuan N. · Revisado há almost 6 years

Jiaquan P. · Revisado há almost 6 years

Gil T. · Revisado há almost 6 years

script install-logging-agent.sh does not work, on the dashboard I can see the increase in CPU but the metrics, which is exactly the screen which is so confusing the instructions are not clear and do not show the increase

Oskar H. · Revisado há almost 6 years

uma kant v. · Revisado há almost 6 years

Madhusmita J. · Revisado há almost 6 years

Ashish K. · Revisado há almost 6 years

mark k. · Revisado há almost 6 years

Paulus S. · Revisado há almost 6 years

Kevin L. · Revisado há almost 6 years

ONI E. · Revisado há almost 6 years

Kevin L. · Revisado há almost 6 years

Muralidharan R. · Revisado há almost 6 years

Paulus S. · Revisado há almost 6 years

Command: sudo bash install-logging-agent.sh failed with message: Apr 19 20:29:23 agentur-m-wp-vm systemd[1]: Starting LSB: data collector for Treasure Data

Konrad S. · Revisado há almost 6 years

Fred V. · Revisado há almost 6 years

Amine L. · Revisado há almost 6 years

Brilliant

MANAV M. · Revisado há almost 6 years

Jukka H. · Revisado há almost 6 years

OK

Nana K. · Revisado há almost 6 years

Installation of logging agent failed, and I cannot see any monitoring result when specified VM Instance and CPU Usage to query

Rawich K. · Revisado há almost 6 years

Pinak J. · Revisado há almost 6 years

Y N. · Revisado há almost 6 years

Savad T. · Revisado há almost 6 years