关于“Google Cloud Fundamentals: Getting Started with Deployment Manager and Cloud Monitoring”的评价

薇 陳. · 已于 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. · 已于 almost 6 years前审核

Jiaquan P. · 已于 almost 6 years前审核

Gil T. · 已于 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. · 已于 almost 6 years前审核

uma kant v. · 已于 almost 6 years前审核

Madhusmita J. · 已于 almost 6 years前审核

Ashish K. · 已于 almost 6 years前审核

mark k. · 已于 almost 6 years前审核

Paulus S. · 已于 almost 6 years前审核

Kevin L. · 已于 almost 6 years前审核

ONI E. · 已于 almost 6 years前审核

Kevin L. · 已于 almost 6 years前审核

Muralidharan R. · 已于 almost 6 years前审核

Paulus S. · 已于 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. · 已于 almost 6 years前审核

Fred V. · 已于 almost 6 years前审核

Amine L. · 已于 almost 6 years前审核

Brilliant

MANAV M. · 已于 almost 6 years前审核

Jukka H. · 已于 almost 6 years前审核

OK

Nana K. · 已于 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. · 已于 almost 6 years前审核

Pinak J. · 已于 almost 6 years前审核

Y N. · 已于 almost 6 years前审核

Savad T. · 已于 almost 6 years前审核