Closed Hydrocephalic closed 4 years ago
Thanks @Hydrocephalic – it looks like we bumped the Agent's version of Node and it affected far more distros of Linux than we thought it would. We're going to be reverting the yum repo to the earlier version and changing the Node version before redeploying agent 1.6.2. A workaround for now would be to use 1.5.6-1
for now.
I'll update this issue as we rebuild and redeploy the agent to the various repos.
New builds of the 1.6.2 version of the agent are now available, including updated .rpm packages.
Unfortunately, we're unable to offer any ongoing support for CentOS 6; the last working version of the Agent for CentOS 6 users will be 1.5.6. I understand this far from an ideal notification process, and I regret that deprecating CentOS 6 support in 1.6.2 was the only real viable path to releasing the new version. We've learned why our communications fell apart around notifying CentOS 6 users in advance, why our testing failed to identify that CentOS 7 and Amazon Linux users would be affected, and why we were unable to simply revert or remove the latest packages from our yum repo. Together, these events compounded in ways that became serious frustrations, and we'll be working to resolve the underlying causes before we release any future versions of the agent.
For CentOS 7 users, as well as Amazon Linux users, simply re-run this command and it should pull the latest package:
sudo yum -y install logdna-agent
Latest version (1.6.2-1) of LogDNA Agent does not start on RHEL7 server.
These are the error messages:
LogDNA Agent version:
Previous version (1.5.6-1) works perfectly.
Looking at available
GLIBCXX_*
:GLIBCXX_3.4.21
is not available.RHEL version: 7.6