Hi Marty, You're likely hitting the log4j 2.x. If you've customisations in your log4j, you'll need to select the new log4j files during the upgrade. Or get from the source repo [1]. This is because ACS 4.20 moved to log4j 2.x.
[1] some variables may need expansion https://github.com/apache/cloudstack/blob/4.20/client/conf/log4j-cloud.xml.in Regards. ________________________________ From: Marty Godsey <mar...@rudio.net.INVALID> Sent: Wednesday, July 16, 2025 06:53 To: users@cloudstack.apache.org <users@cloudstack.apache.org> Subject: Upgrade from 4.19 to 4.20 stopped logging Hello, I saw the bug where upgrading from 4.19 to 4.20.1 stopped the logger, but it also stopped the management server from logging. I don’t have the issue of my management server not starting; it starts fine, but I have no logs being generated. I didn’t see a clear fix. What should I check? Regards, Marty Godsey Rudio, LLC
