GCP Fundamentals : Premiers pas avec Deployment Manager et Cloud Monitoring avis

薇 陳. · Examiné il y a presque 6 ans

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. · Examiné il y a presque 6 ans

Jiaquan P. · Examiné il y a presque 6 ans

Gil T. · Examiné il y a presque 6 ans

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. · Examiné il y a presque 6 ans

uma kant v. · Examiné il y a presque 6 ans

Madhusmita J. · Examiné il y a presque 6 ans

Ashish K. · Examiné il y a presque 6 ans

mark k. · Examiné il y a presque 6 ans

Paulus S. · Examiné il y a presque 6 ans

Kevin L. · Examiné il y a presque 6 ans

ONI E. · Examiné il y a presque 6 ans

Kevin L. · Examiné il y a presque 6 ans

Muralidharan R. · Examiné il y a presque 6 ans

Paulus S. · Examiné il y a presque 6 ans

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. · Examiné il y a presque 6 ans

Fred V. · Examiné il y a presque 6 ans

Amine L. · Examiné il y a presque 6 ans

Brilliant

MANAV M. · Examiné il y a presque 6 ans

Jukka H. · Examiné il y a presque 6 ans

OK

Nana K. · Examiné il y a presque 6 ans

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

Rawich K. · Examiné il y a presque 6 ans

Pinak J. · Examiné il y a presque 6 ans

Y N. · Examiné il y a presque 6 ans

Savad T. · Examiné il y a presque 6 ans