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?
NeophyteHi there Team.
I have just attempted to upgrade our Linux Collector from 36.001 to 38.000.
Seems our Collector has been Down ever since. Can anyone suggest some
Tshooting steps to get the Collector up again with the upgraded version.
Support seems to be taking some time to come online.
NeophyteThere is a known and acknowledged issue when moving from 36.x version to anything above that. I can't say that's the issue but see my earlier post which still isn't resolved:
Warning: Linux Collector Upgrades Leaving Collectors Unusable | LogicMonitor - 18283
Be warned support has claimed that the GD release 37.003 fixes the issue but it is still breaking our collectors.
Troubleshooting? Uninstall the collector and re-install the version that was working.
Best of luck!
NeophyteAnother thing you could do is manually run (as root) the enableUserServices.sh if it exists and see if the output (it should be in usr/local/logicmonitor/agent/bin), assuming Linux. If you see no such file or directory issues then I might have a fix (that script was wrong for several releases.
LM ConquerorSorry to hear that the Linux Collectors are hard down after a Collector version upgrade.
Have you done any troubleshooting?
Are the Collector Services running on the host device?
If possible place the Collector logs in a .zip file and share with LM support for further evaluation. The log files can be found in the /usr/local/logicmonitor/agent/logs directory.
