No management-server.log log after update from 4.19.0 to 4.22.0 and some VR VPC problems

[sptest232]

After upgrading from version 4.19.0 to version 4.22.0, issues with VR and VPC Live Patching appeared (VRs does not start after attempting to restart).
While attempting to analyze the cause of the problem, we noticed that the current management-server.log was missing (it stopped being created after the upgrade).

management-server.err:

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

management-server.out contains a lot of error:

[pool-574-thread-1] ERROR org.apache.cloudstack.framework.messagebus.MessageBusBase - NO EVENT PUBLISH CAN BE WRAPPED WITHIN DB TRANSACTION!
com.cloud.utils.exception.CloudRuntimeException: NO EVENT PUBLISH CAN BE WRAPPED WITHIN DB TRANSACTION!
at org.apache.cloudstack.framework.messagebus.MessageBusBase.publish(MessageBusBase.java:168) ~[cloudstack-4.22.0.0.jar:4.22.0.0]
at com.cloud.capacity.CapacityManagerImpl.updateCapacityForHost(CapacityManagerImpl.java:786) ~[cloudstack-4.22.0.0.jar:4.22.0.0]
at com.cloud.alert.AlertManagerImpl$1.doInTransactionWithoutResult(AlertManagerImpl.java:320) ~[cloudstack-4.22.0.0.jar:4.22.0.0]
at com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25) ~[cloudstack-4.22.0.0.jar:4.22.0.0]
at com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:48) ~[cloudstack-4.22.0.0.jar:4.22.0.0]
at com.cloud.utils.db.Transaction.execute(Transaction.java:38) ~[cloudstack-4.22.0.0.jar:4.22.0.0]
at com.cloud.utils.db.Transaction.execute(Transaction.java:45) ~[cloudstack-4.22.0.0.jar:4.22.0.0]
at com.cloud.alert.AlertManagerImpl.lambda$recalculateHostCapacities$0(AlertManagerImpl.java:316) ~[cloudstack-4.22.0.0.jar:4.22.0.0]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
at java.lang.Thread.run(Thread.java:840) ~[?:?]

[Pearl1594]

@sptest232 do you by any chance have an rpmnew log4j file created at /usr/share/cloudstack-management/conf/. This may happen due the new log4j2 format. You can backup your current log4j-cloud.xml and replace it with the one suffixed with "rpmnew" and restart the Management server and see if you can see the logs in the management-server.log file.

[sptest232]

Thank you very much! It helped!

[anntnzrb]

CloudStack 4.20+ migrated from Log4j 1.x to Log4j2, which has incompatible configuration format. Your /etc/cloudstack/management/log4j-cloud.xml file likely still uses the old Log4j 1.x format from 4.19. Replace it with the Log4j2 format (check the template at server/conf/log4j-cloud.xml.in in the repo), ensure the symlink log4j.xml → log4j-cloud.xml exists, then restart cloudstack-management. The SLF4J NOP warning confirms the logger failed to initialize due to config parsing failure.