Symantec 10490452 Administration Guide - Page 195

Increasing the amount of information in BrightmailLog.log, On Windows

Page 195 highlights

Administering the system 195 Administering the Control Center Increasing the amount of information in BrightmailLog.log If you have problems with the Control Center, you can increase the detail of the log messages saved into BrightmailLog.log by changing settings in the log4j.properties file. The BrightmailLog.log contains logging information for the Control Center, including Spam Quarantine. When you increase the logging level of log4j.properties, it creates a lot of log information, so it's recommended to increase the maximum size of the BrightmailLog.log as described below. To increase the detail of logging messages saved into BrightmailLog.log 1 Open the following file in a text editor such as WordPad or vi: On Solaris or Linux: /opt/Symantec/SMSSMTP/tomcat/webapps/brightmail/WEB-INF/ classes/log4j.properties On Windows: C:\Program \ WEB-INF\classes\log4j.properties 2 Find the following line: #log4j.rootLogger=WARN, file 3 Change the word WARN to DEBUG. 4 Find the following line: log4j.appender.file.MaxFileSize=5MB 5 Change the 5MB to the desired number, such as 10MB. 6 Find the following line: log4j.appender.file.MaxBackupIndex=10 7 Change the number after MaxBackupIndex to the desired number, such as 40. This setting determines the number of saved BrightmailLog.log files. For example, if you specify 2, BrightmailLog.log contains the newest information, BrightmailLog.log.1 contains the next newest, and BrightmailLog.log.2 contains the oldest information. When BrightmailLog.log reaches the size indicated by log4j.appender.file.MaxFileSize, then it's renamed to BrightmailLog.log.1, and a new BrightmailLog.log file is created. The original BrightmailLog.log.1 is renamed to BrightmailLog.log.2, etc. This number times the value of log4j.appender.file.MaxFileSize determines the amount of disk space required for these logs. 8 Save and exit from the log4j.properties file. 9 On Windows, use Control Panel > Services to restart Tomcat.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258

195
Administering the system
Administering the Control Center
Increasing the amount of information in BrightmailLog.log
If you have problems with the Control Center, you can increase the detail of the
log messages saved into
BrightmailLog.log
by changing settings in the
log4j.properties
file. The
BrightmailLog.log
contains logging information
for the Control Center, including Spam Quarantine. When you increase the
logging level of
log4j.properties
, it creates a lot of log information, so it’s
recommended to increase the maximum size of the
BrightmailLog.log
as
described below.
To increase the detail of logging messages saved into BrightmailLog.log
1
Open the following file in a text editor such as WordPad or vi:
On Solaris or Linux:
/opt/Symantec/SMSSMTP/tomcat/webapps/brightmail/WEB-INF/
classes/log4j.properties
On Windows:
C:\Program \
WEB-INF\classes\log4j.properties
2
Find the following line:
#log4j.rootLogger=WARN, file
3
Change the word
WARN
to
DEBUG
.
4
Find the following line:
log4j.appender.file.MaxFileSize=5MB
5
Change the
5MB
to the desired number, such as
10MB
.
6
Find the following line:
log4j.appender.file.MaxBackupIndex=10
7
Change the number after
MaxBackupIndex
to the desired number, such as
40.
This setting determines the number of saved
BrightmailLog.log
files. For
example, if you specify 2,
BrightmailLog.log
contains the newest
information,
BrightmailLog.log.1
contains the next newest, and
BrightmailLog.log.2
contains the oldest information. When
BrightmailLog.log
reaches the size indicated by
log4j.appender.file.MaxFileSize
, then it’s renamed to
BrightmailLog.log.1
, and a new
BrightmailLog.log
file is created. The
original
BrightmailLog.log.1
is renamed to
BrightmailLog.log.2
, etc.
This number times the value of
log4j.appender.file.MaxFileSize
determines the amount of disk space required for these logs.
8
Save and exit from the
log4j.properties
file.
9
On Windows, use Control Panel > Services to restart Tomcat.