Reading package lists… Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packagecloud.io/netdata/netdata-repoconfig/ubuntu jammy InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 53BC0238C6ADB1FD
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packagecloud.io/netdata/netdata-edge/ubuntu jammy InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 906E08CB997741FC
Attempted to apt-get update && upgrade, but was met with this. I also has netdata on several other servers and it only happened to one. Not sure how the GPG key got messed up, but any help would be appricated thanks in advance.
I also just noticed that my other servers have different repos and this on has packagecloud.io…?
Hit:7 Index of /repos/edge/ubuntu/ jammy/ Release
Hit:8 Index of /repos/repoconfig/ubuntu/ jammy/ Release
I’m not sure what’s going on with PackageCloud in this situation, but we’ve recently switched our primary hosting of native packages to self-hosted infrastructure at repo.netdata.cloud (more details, including info about manual setup, can be found here). Most systems should have been switched over automatically as a result of either netdata-repo
or netdata-repo-edge
upgrading (and this is likely why you’re seeing different behavior for your other servers, they likely got switched automatically).
It looks like the affected system was already using the netdata-repo-edge
package, but something went wrong during an upgrade so it did not get switched over automatically. You can most likely fix this (and get rid of the PackageCloud issue) by manually fetching the correct repository configuration package from the repoconfig repository at repo.netdata.cloud (for nightly builds on Ubuntu 22.04, which appears to be what you were using previously, you would want https://repo.netdata.cloud/repos/repoconfig/ubuntu/jammy/netdata-repo-edge_2-1+ubuntu22.04_all.deb), and then manually installing the package using APT (you can pass the downloaded package file as an argument to apt install
and it should just work).
FYI, I’m getting a similar error on the netdata.cloud repo, Ubuntu 22.04.01
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repo.netdata.cloud/repos/edge/ubuntu jammy/ Release: The following signatures were invalid: BADSIG F9177B5265F56346 Netdatabot <bot@netdata.cloud>
W: Failed to fetch http://repo.netdata.cloud/repos/edge/ubuntu/jammy/Release.gpg The following signatures were invalid: BADSIG F9177B5265F56346 Netdatabot <bot@netdata.cloud>
W: Some index files failed to download. They have been ignored, or old ones used instead.
I was able to resolve this by re-running the kickstarter script.