Google Cloud Fundamentals: Getting Started with Deployment Manager and Cloud Monitoring Reviews

薇 陳. · Reviewed neredeyse 6 yıl ago

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. · Reviewed neredeyse 6 yıl ago

Jiaquan P. · Reviewed neredeyse 6 yıl ago

Gil T. · Reviewed neredeyse 6 yıl ago

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. · Reviewed neredeyse 6 yıl ago

uma kant v. · Reviewed neredeyse 6 yıl ago

Madhusmita J. · Reviewed neredeyse 6 yıl ago

Ashish K. · Reviewed neredeyse 6 yıl ago

mark k. · Reviewed neredeyse 6 yıl ago

Paulus S. · Reviewed neredeyse 6 yıl ago

Kevin L. · Reviewed neredeyse 6 yıl ago

ONI E. · Reviewed neredeyse 6 yıl ago

Kevin L. · Reviewed neredeyse 6 yıl ago

Muralidharan R. · Reviewed neredeyse 6 yıl ago

Paulus S. · Reviewed neredeyse 6 yıl ago

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. · Reviewed neredeyse 6 yıl ago

Fred V. · Reviewed neredeyse 6 yıl ago

Amine L. · Reviewed neredeyse 6 yıl ago

Brilliant

MANAV M. · Reviewed neredeyse 6 yıl ago

Jukka H. · Reviewed neredeyse 6 yıl ago

OK

Nana K. · Reviewed neredeyse 6 yıl ago

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

Rawich K. · Reviewed neredeyse 6 yıl ago

Pinak J. · Reviewed neredeyse 6 yıl ago

Y N. · Reviewed neredeyse 6 yıl ago

Savad T. · Reviewed neredeyse 6 yıl ago