Installing Netdata
- Thread starter creaky
- Start date
Yes it supports QEMU so if you install it on the host it can show things like CPU / RAM / IO use for the VM’s along with information about the host node itself.
You can run that command yes
You can run that command yes
Trying to install but I get this at the end. Is this normal?
All Done! - Now proceed to the next step.
OK /bin/bash /tmp/netdata-kickstart-SeoucZ/install-required-packages.sh netdata
$'[\E[2m/tmp/netdata-kickstart-SeoucZ\E(B\E[0m]# \E[1m\E[33m' curl -sSL --connect-timeout 10 --retry 3 https://storage.googleapis.com/netdata-nightlies/sha256sums.txt $'\E(B\E[0m\\n' curl: (60) SSL certificate problem: self signed certificate
More details here: https://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
FAILED curl -sSL --connect-timeout 10 --retry 3 https://storage.googleapis.com/netdata-nightlies/sha256sums.txt
ABORTED Cannot download https://storage.googleapis.com/netdata-nightlies/sha256sums.txt
All Done! - Now proceed to the next step.
OK /bin/bash /tmp/netdata-kickstart-SeoucZ/install-required-packages.sh netdata
$'[\E[2m/tmp/netdata-kickstart-SeoucZ\E(B\E[0m]# \E[1m\E[33m' curl -sSL --connect-timeout 10 --retry 3 https://storage.googleapis.com/netdata-nightlies/sha256sums.txt $'\E(B\E[0m\\n' curl: (60) SSL certificate problem: self signed certificate
More details here: https://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
FAILED curl -sSL --connect-timeout 10 --retry 3 https://storage.googleapis.com/netdata-nightlies/sha256sums.txt
ABORTED Cannot download https://storage.googleapis.com/netdata-nightlies/sha256sums.txt
I tired to do this but it says " -bash: curl: command not found" so tried to install curl using "apt install curl" but it will not let me install it. I get the below:
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Hvisage after some tinkering around I was again to get it installed on the VM I wanted so it works there. Now still no joy on getting directly to Proxmox server itself but I am not sure I want to really monitor that. I really wanted to monitor the VM devices on their own, so I think we are all good now. Thanks for the reply. Yes I did run as root too.
I've been deploying it on the ProxMox hosts... and it started to show me a reason for something I've been experiencing for awhile, which was outside of the VMs....
However, I found that it was better to do it via the "direct fetch" script (curl url | sh something) though I've stopped before the actual Netdata installation to put it in /opt, that ran fine as root