Skip to content
Home » security » How to downgrade a Log Logic universal collector

How to downgrade a Log Logic universal collector

If you’ve ever upgraded a LogLogic universal collector and had it fail to work, it’s very disconcerting to see the error message when you try to reinstall the previous version: Downgrades aren’t supported. But there is a solution if you need to downgrade a Log Logic universal collector.

The solution, once I got over my panic of seeing 342 hosts in error status, was fairly simple. Downgrades aren’t supported, but uninstalls are. To be on the safe side, I backed up the configuration—launch the UC, navigate to Manage Configuration and click Save As. Then enter a filename.

Next, I uninstalled the 2.4 UC from the Windows control panel. After that finished, I re-ran the old 2.3 UC installation file.  Neither process takes much more than a minute or two. After the 2.3 UC completed installation, I launched the UC (which by default resides at c:\program files\loglogic\universal collector\bin\uc-console.bat), which greeted me with 342 hosts collecting. I didn’t even need to restore the configuration, which was nice.

I don’t know if anyone else is having issues with the new 2.4.0 universal collector, but I am. If you haven’t upgraded to 2.4.0 yet, and you value your heart health, try it out in the lab first, and when you go to deploy it in production, deploy very slowly and carefully.

And while we’re talking Log Logic hacks, here’s a way to increase your storage capacity by 45%. This makes Log Logic more cost-effective, even though I do think Splunk is worth it.

If you found this post informative or helpful, please share it!
%d bloggers like this: