NeophyteA heads up to the community: We've had several upgrades that have left collectors unusable.
It's probably related to the initial and upgrade versions (in our case 36.001 to 37.002). It's related to the move to user space for the services.
LM support is aware of this.
Community ManagerHi there!
Thanks for bringing this to our attention - I will let our product and support teams know immediately so we can get this sorted out.
LM ConquerorGreetings befuddled ,
Quite sorry to hear that Collector upgrading has been a pain recently. Typically the upgrade process is swift and the barely noticeable. I have come across some interesting issues regarding Linux hosts, between Collector versions 36.500 and 37.200/37.002. I actually just had a discussion with the Collector team about this moments ago.
Can you share any more details about the issue? If you have an open support case I would be happy to take a look.
NeophytePeople are looking at the open support case, and the answer is "it'll be fixed in the next General Release version".
I run a production environment with customer requirements, and I have no interest in running Early Access versions...."So, EA is not recommended for your entire infrastructure."
At this point, I can't upgrade collectors to any supported version without risking bricking them.
NeophyteLM says this is fixed in the EA release due at the end of April and fixed in the GD release due May/June. I typically don't run EA releases.
Do you guys run EA releases?
