Expand my Community achievements bar.

SOLVED

duplicated lines in certain log files

Avatar

Level 2

Somehow in our Adobe Campaign classic deployment, there were always duplicated lines in certain log files where all log lines were printed twice. For example, this is the case in sms.log:

2022-02-18 10:53:03.980Z 00004CE7 00003032 1 info log PDU sent to 'smsgateway:8888':\nENQUIRE_LINK sequence_number=0x00000005\n
2022-02-18 10:53:03.981Z 00004CE7 00003032 1 info log PDU sent to 'smsgateway:8888':\nENQUIRE_LINK sequence_number=0x00000005\n
2022-02-18 10:53:04.035Z 00004CE7 00003032 1 info log PDU received from 'smsgateway:8888':\nENQUIRE_LINK_RESP command_status=0x00000000 sequence_number=0x00000005\n
2022-02-18 10:53:04.035Z 00004CE7 00003032 1 info log PDU received from 'smsgateway:8888':\nENQUIRE_LINK_RESP command_status=0x00000000 sequence_number=0x00000005\n
2022-02-18 10:53:33.981Z 00004CE7 00003032 1 info log PDU sent to 'smsgateway:8888':\nENQUIRE_LINK sequence_number=0x00000006\n
2022-02-18 10:53:33.981Z 00004CE7 00003032 1 info log PDU sent to 'smsgateway:8888':\nENQUIRE_LINK sequence_number=0x00000006\n
2022-02-18 10:53:34.035Z 00004CE7 00003032 1 info log PDU received from 'smsgateway:8888':\nENQUIRE_LINK_RESP command_status=0x00000000 sequence_number=0x00000006\n
2022-02-18 10:53:34.036Z 00004CE7 00003032 1 info log PDU received from 'smsgateway:8888':\nENQUIRE_LINK_RESP command_status=0x00000000 sequence_number=0x00000006\n
2022-02-18 10:54:03.981Z 00004CE7 00003032 1 info log PDU sent to 'smsgateway:8888':\nENQUIRE_LINK sequence_number=0x00000007\n
2022-02-18 10:54:03.981Z 00004CE7 00003032 1 info log PDU sent to 'smsgateway:8888':\nENQUIRE_LINK sequence_number=0x00000007\n

 
But for other logs like 'runwf.log' or 'inMail.log' there is no such duplications. Have anybody met similar issues before? I know this is due to the configuration for the logging library nlserver is using but don't know exactly where to tune this to remove the duplications.

 

Thanks!

Shaohong

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

I'd recommend raising a ticket to TechOps as they can check whether is a glitch/bug with your current version and/or check if there is a temp workaround and feedback also whether this impacts any other processes.

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

I'd recommend raising a ticket to TechOps as they can check whether is a glitch/bug with your current version and/or check if there is a temp workaround and feedback also whether this impacts any other processes.