We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've been attempting to install the agent on a ppc64 architecture, following the instructions for RedHat on the LogDNA website:
[root@server ~]# cat /etc/yum.repos.d/logdna.repo [logdna] baseurl = https://assets.logdna.com/el6/ enabled = 1 gpgcheck = 1 gpgkey = https://assets.logdna.com/logdna.gpg name = LogDNA repo
Loaded plugins: product-id, search-disabled-repos, subscription-manager, versionlock No package logdna-agent available. Error: Nothing to do
[root@server ~]# yum repolist |grep logdna logdna LogDNA repo 0+8 CPE OS Name: cpe:/o:redhat:enterprise_linux:7.5:GA:server Kernel: Linux 3.10.0-862.25.3.el7.ppc64le Architecture: ppc64-le
The text was updated successfully, but these errors were encountered:
Hi @rafapsedano, unfortunately we currently only provide binaries for aarch64/arm64 and x86_64/amd64. We don't have builds for ppc64, s390x etc yet.
Sorry, something went wrong.
No branches or pull requests
I've been attempting to install the agent on a ppc64 architecture, following the instructions for RedHat on the LogDNA website:
[root@server ~]# cat /etc/yum.repos.d/logdna.repo
[logdna]
baseurl = https://assets.logdna.com/el6/
enabled = 1
gpgcheck = 1
gpgkey = https://assets.logdna.com/logdna.gpg
name = LogDNA repo
yum install logdna-agent
Loaded plugins: product-id, search-disabled-repos, subscription-manager, versionlock
No package logdna-agent available.
Error: Nothing to do
[root@server ~]# yum repolist |grep logdna
logdna LogDNA repo 0+8
CPE OS Name: cpe:/o:redhat:enterprise_linux:7.5:GA:server
Kernel: Linux 3.10.0-862.25.3.el7.ppc64le
Architecture: ppc64-le
The text was updated successfully, but these errors were encountered: