You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Marty Godsey <ma...@rudio.net.INVALID> on 2025/07/16 01:23:46 UTC

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

Re: Upgrade from 4.19 to 4.20 stopped logging

Posted by Marty Godsey <ma...@rudio.net.INVALID>.
Nevermind, I see it’s a symlink to the cloud file.

Regards,
Marty Godsey
Rudio, LLC

Support: support@rudio.net<ma...@rudio.net>

Ph: 859-328-1100
The content of this email is intended only for the person or entity to which it is addressed. This email may contain confidential information. If you are not the person to whom this message is addressed, be aware that any use, reproduction, or distribution of this message is strictly prohibited. If you received this in error, please contact the sender and immediately delete this email and any attachments.

From: Rohit Yadav <ro...@shapeblue.com>
Date: Tuesday, July 15, 2025 at 11:23 PM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: Re: Upgrade from 4.19 to 4.20 stopped logging
WARNING: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


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 <ma...@rudio.net.INVALID>
Sent: Wednesday, July 16, 2025 06:53
To: users@cloudstack.apache.org <us...@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

Re: Upgrade from 4.19 to 4.20 stopped logging

Posted by Marty Godsey <ma...@rudio.net.INVALID>.
Thank you, Rohit.

Do I also need to replace the log4j2.xml file as well along with the log4j2-cloud.xml file?

Regards,
Marty Godsey
Rudio, LLC


From: Rohit Yadav <ro...@shapeblue.com>
Date: Tuesday, July 15, 2025 at 11:23 PM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: Re: Upgrade from 4.19 to 4.20 stopped logging
WARNING: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


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 <ma...@rudio.net.INVALID>
Sent: Wednesday, July 16, 2025 06:53
To: users@cloudstack.apache.org <us...@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

Re: Upgrade from 4.19 to 4.20 stopped logging

Posted by Marty Godsey <ma...@rudio.net.INVALID>.
I replaced the log4j-cloud file with the one from the link, and CS still starts, but is still not logging. I did re-added my customizations, which involve sending logs to an external log server. To test, I removed my customizations, and I am now logging. I noticed that I am now logging to the @MSLOG@ file, however.

Is there a different way this is handled in 4.20? Is it in the documentation? I still need to send these logs to an external source.

Regards,
Marty Godsey
Rudio, LLC

Support: support@rudio.net<ma...@rudio.net>


From: Rohit Yadav <ro...@shapeblue.com>
Date: Tuesday, July 15, 2025 at 11:23 PM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: Re: Upgrade from 4.19 to 4.20 stopped logging
WARNING: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


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 <ma...@rudio.net.INVALID>
Sent: Wednesday, July 16, 2025 06:53
To: users@cloudstack.apache.org <us...@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

Re: Upgrade from 4.19 to 4.20 stopped logging

Posted by Rohit Yadav <ro...@shapeblue.com>.
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 <ma...@rudio.net.INVALID>
Sent: Wednesday, July 16, 2025 06:53
To: users@cloudstack.apache.org <us...@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