Security log successful but

Support Security
1

I added “enableSecurityLog = yes” to axigen.cfg and it is generating entries to the file but I observed
duplicate security file items. Is this a problem?

log = {
logType = internal
logLevel = 15
logHost = 127.0.0.1:2000
listeners = (
{
address = 127.0.0.1:2000
enable = no
}
)
path = “log”
enableSecurityLog = yes
rules = (
{
priority = 49
hostname = “"
module = SECURITY
logLevel = 31
fileName = “security.txt”
fileSize = 5120
fileTime = 86400
fileCount = 0
rotatePeriod = none
type = local
}
{
priority = 100
hostname = “x2mailx”
module = SECURITY
logLevel = 31
fileName = “security.txt”
fileSize = 5120
fileTime = 86400
fileCount = 900
rotatePeriod = none
type = local
}
{
priority = 101
hostname = “x2mailx”
module = *
logLevel = 31
fileName = “everything.txt”
fileSize = 5120
fileTime = 86400
fileCount = 900
rotatePeriod = none
type = local
}
{
priority = 1000
hostname = "”
module = *
logLevel = 31
fileName = “default.txt”
fileSize = 5120
fileTime = 86400
fileCount = 0
rotatePeriod = none
type = local
}
)
}

2

Hello,

Could you post such duplicates?

I’ve some doubts that there are duplicates because each line contain, beside a timestamp (that have second resolution) the ID of the session used for authenticating a specific request.

Looking forward for your data.

BR,
Ioan

3

I meant that in the clipping from axigen.cfg there are two SECURITY modules pointing at

the same log file “security.txt”

4

Rule with higher priority is storing the logs in defined file.

you can manage the rules in “WEBADMIN>LOGGING>Log Collection Rulls” more easier.

5

Hello Peter,

There is a difference between the mentioned log rules - please double check the “hostname” parameter that is empty for rule with priority 49 and set to ‘x2mailx’ on rule with priority 100.

HTH,
Ioan