Skip to content

Commit f692eb2

Browse files
Notes regarding Log4j2 format check in the log configuration (#604)
Co-authored-by: Suresh Kumar Anaparti <sureshkumar.anaparti@gmail.com>
1 parent aac9e8f commit f692eb2

File tree

4 files changed

+32
-0
lines changed

4 files changed

+32
-0
lines changed
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
.. Licensed to the Apache Software Foundation (ASF) under one
2+
or more contributor license agreements. See the NOTICE file
3+
distributed with this work for additional information#
4+
regarding copyright ownership. The ASF licenses this file
5+
to you under the Apache License, Version 2.0 (the
6+
"License"); you may not use this file except in compliance
7+
with the License. You may obtain a copy of the License at
8+
http://www.apache.org/licenses/LICENSE-2.0
9+
Unless required by applicable law or agreed to in writing,
10+
software distributed under the License is distributed on an
11+
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
12+
KIND, either express or implied. See the License for the
13+
specific language governing permissions and limitations
14+
under the License.
15+
16+
.. sub-section included in upgrade notes.
17+
18+
.. note::
19+
20+
During upgrades from versions prior to 4.20, the logging configuration file may not be migrated automatically to the new Log4j2 format - especially if the original log4j configuration file was manually customized or modified.
21+
22+
It is strongly recommended to verify **before starting the Management Server and the Usage Server** that the configuration file (e.g. `log4j-cloud.xml`) under `/etc/cloudstack/management` and `/etc/cloudstack/usage` respectively uses the Log4j2 format.
23+
24+
If the file still uses legacy Log4j (version 1) syntax or structure, **manually replace or update** the configuration using the default Log4j2 configuration supplied with the latest package.
25+
26+
Failure to update may result in missing or incomplete log generation after upgrade.

source/upgrading/upgrade/upgrade-4.20.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -207,6 +207,8 @@ Setup the GPG public key if you wish to enable ``gpgcheck=1``:
207207
208208
$ sudo yum upgrade cloudstack-usage
209209
210+
.. include:: _log4j_file_check.rst
211+
210212
.. _upg_hyp_414:
211213

212214
Upgrade Hypervisors

source/upgrading/upgrade/upgrade-4.21.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -207,6 +207,8 @@ Setup the GPG public key if you wish to enable ``gpgcheck=1``:
207207
208208
$ sudo yum upgrade cloudstack-usage
209209
210+
.. include:: _log4j_file_check.rst
211+
210212
.. _upg_hyp_414:
211213

212214
Upgrade Hypervisors

source/upgrading/upgrade/upgrade-4.22.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -216,6 +216,8 @@ Setup the GPG public key if you wish to enable ``gpgcheck=1``:
216216
217217
$ sudo yum upgrade cloudstack-usage
218218
219+
.. include:: _log4j_file_check.rst
220+
219221
.. _upg_hyp_414:
220222

221223
Upgrade Hypervisors

0 commit comments

Comments
 (0)